Hi, after flashing TWRP update from TWRP itself I am now stuck at download mode.
I can access downloading mode using Power + Volume down
I cannot boot into twrp using Power + Volume up, this brings download mode up.
I cannot boot into system, this results in the same behavior as previous situation.
The main problem is that for a long time my cable or port is not working correctly. I can charge tablet but the data transfer is not established. I cannot say if it is caused by cable or port but I think it is the port itself - other reduction does not work as well. Thanks to this I cannot easily flash recovery back.
So I am looking for other solutions than buying new port board/cable and replacing it. SD card is currently the only one interface working. I am asking if there is possibility to flash recovery/stock via sd card - maybe some files detected right after entering download mode, i. e. recovery.img.
Other possibility would be to get adb over wifi working.
Thank you.
Hi,
does the flash process even start when you try it with odin or heimdall?
Once recovery boot is triggered, it will alway's try to boot into.
You could try to:
heimdall print-pit
If this is succesfull, you may can boot into system and then flash a new twrp with root rights.
html6405 said:
Hi,
does the flash process even start when you try it with odin or heimdall?
Once recovery boot is triggered, it will alway's try to boot into.
You could try to:
heimdall print-pit
If this is succesfull, you may can boot into system and then flash a new twrp with root rights.
Click to expand...
Click to collapse
Hi,
my problem is that my cable (probably charging port) is not working (it does charge but does not transfer data) so I cannot do flash via cable.
I flashed twrp update using twrp. I do not understand however why I cannot boot into system or does bootloader need working recovery?
Here I am sending two pics:
1. boot into download mode directly using Power + Volume Down - https://pasteboard.co/JU4sQdr.jpg
2. standard reboot or Power + Volume up - https://pasteboard.co/JU4t6gR.jpg
Is I get somehow to system, I can flash recovery easily as I have rooted device.
Related
Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.
Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again
Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?
^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.
but, how can I overwrite it? it seems like they are read only...
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:
No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
tirtha2shredder said:
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
Click to expand...
Click to collapse
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
enrique_fire said:
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
Click to expand...
Click to collapse
Thank you! that worked perfect!
Hi which method did you use to root yu50101a? if possible can you share a link as well
:crying:I am also facing the same problem . i also have yu5010a but cannot root it . twrp or cwm not correctly flashing.just tell me if anyone have any solution .
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
When you are in recovery, is the tab detected via adb from pc?
bukaida said:
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
Click to expand...
Click to collapse
Signature verification fails because you are on stock recovery. Also have you tried booting in to download mode then plugging the USB cable to your tablet, then pressing volume up to start the download mode, then plugging the other end to your PC while odin is running? It should get detected
Power+ Vol up and Power + Vol down both are going to recovery mode. Plus getting an error 'logo_espresso7.jpg' draw failed at initial screen. Is there any <3e> compatable recovery without signature verification failed that can be run from sd card directly?
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
The Tab is not detected in ADB server either.
bukaida said:
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
Click to expand...
Click to collapse
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
john99ap said:
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
Click to expand...
Click to collapse
Yeah, the fault is mine, lack of knowledge. But what now? Can I recover my Tab ?
please help.
[Solved Problem]
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
bukaida said:
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
Click to expand...
Click to collapse
if you want to install the latest roms, you should update to the latest common twrp from android-andi http://andi34.github.io/recoveries_tab2.html
cwm recovery is outdated and causing issues with the latest roms
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
bukaida said:
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
Click to expand...
Click to collapse
install twrp as zip with your current cwm. its the easiest way. twrp will replace cwm, yes.
So I bricked my device again. *applause*
What Happened?
Flashed CWM using Odin
Booted into CWM Recovery
Deleted everything - /data, /sys, and most definitely the battery stats (I know that frustrated look on your face)
Rebooted *mwahahaha*
Output:
Stuck at boot logo
Can't boot into recovery anymore
Can't go into download mode either for unknown reasons (apart from faulty side buttons)
Odin shows COM1 port but can't establish connection when I try flashing and booting CWM (we know why; we haven't gone into download mode have we?!)
Stuck at boot logo
Stuck a-
Discovered solutions:
Strategy is to try going into EDL by hook or by crook. So we take the device apart (done), press on the power key and volume down key with a screw driver (done), and boot into download mode (done)
Flash CWM again via Odin
Reboot into Recovery (DOES NOT WORK)
It's probably because SAMSUNG does a battery check before the boot. And finds absolute garbage.
So my question is, is there a way to flash the entire firmware as a whole (including modem images, battery shiz and all that) VIA ODIN? This one solution if available will settle the whole puzzle for me.
BoundDroid said:
So I bricked my device again. *applause*
What Happened?
Flashed CWM using Odin
Booted into CWM Recovery
Deleted everything - /data, /sys, and most definitely the battery stats (I know that frustrated look on your face)
Rebooted *mwahahaha*
Output:
Stuck at boot logo
Can't boot into recovery anymore
Can't go into download mode either for unknown reasons (apart from faulty side buttons)
Odin shows COM1 port but can't establish connection when I try flashing and booting CWM (we know why; we haven't gone into download mode have we?!)
Stuck at boot logo
Stuck a-
Discovered solutions:
Strategy is to try going into EDL by hook or by crook. So we take the device apart (done), press on the power key and volume down key with a screw driver (done), and boot into download mode (done)
Flash CWM again via Odin
Reboot into Recovery (DOES NOT WORK)
It's probably because SAMSUNG does a battery check before the boot. And finds absolute garbage.
So my question is, is there a way to flash the entire firmware as a whole (including modem images, battery shiz and all that) VIA ODIN? This one solution if available will settle the whole puzzle for me.
Click to expand...
Click to collapse
I think ( yes think because I am not an expert ??!!! ) th problem is with recovery. Why don't you try again with different version of CWM. If still not, try TWRP.
BoundDroid said:
So I bricked my device again. *applause*
What Happened?
Flashed CWM using Odin
Booted into CWM Recovery
Deleted everything - /data, /sys, and most definitely the battery stats (I know that frustrated look on your face)
Rebooted *mwahahaha*
Output:
Stuck at boot logo
Can't boot into recovery anymore
Can't go into download mode either for unknown reasons (apart from faulty side buttons)
Odin shows COM1 port but can't establish connection when I try flashing and booting CWM (we know why; we haven't gone into download mode have we?!)
Stuck at boot logo
Stuck a-
Discovered solutions:
Strategy is to try going into EDL by hook or by crook. So we take the device apart (done), press on the power key and volume down key with a screw driver (done), and boot into download mode (done)
Flash CWM again via Odin
Reboot into Recovery (DOES NOT WORK)
It's probably because SAMSUNG does a battery check before the boot. And finds absolute garbage.
So my question is, is there a way to flash the entire firmware as a whole (including modem images, battery shiz and all that) VIA ODIN? This one solution if available will settle the whole puzzle for me.
Click to expand...
Click to collapse
(Sorry ! Read your post more carefully and am replying ) yes you can flash entire firmware via odin. What you actually did was you wiped out the whole system. Well try to install any recovery and you can also install a custom rom of android 7 ( the latest for our tab but outdated too ).
Hi,
I've managed to brick my S21+, after a mistake during flashing of a newer twrp version with Odin.
I basically placed the (patched) stock AP file in the AP slot instead of the TWRP tar, and the vbmeta_disabled_R.tar in the userdata slot.
After reboot, I got a boot loop, and I am not able to boot to recovery or to download mode as before when using the key-combo.
Previous to this flashing, I had the TWRP 3.6 and Lineageos 19 GSI for about 6 months, with no issues.
My question - how can I get to Download mode now? and is it possible that I ran over my recovery?
Is it possible that the download mode is no longer available due to the AP flashing (no BL, CSC files)?
Appreciate any suggestion and help!
connect it to the PC and do the combination that you did before, that is volume up and volume down pressed at the same time, that same thing happened to me, when I wanted to update twrp better install the stock first and then the new recovery, so you take advantage of updating the firmware of the phone and the new recovery
Strangely, the recovery entry or download does not work without being connected, so I recommend you better install the magisk to enter the recovery from there, otherwise you will have to do that process when you want to update or install custom roms
CallmeNeos503 said:
Strangely, the recovery entry or download does not work without being connected, so I recommend you better install the magisk to enter the recovery from there, otherwise you will have to do that process when you want to update or install custom roms
Click to expand...
Click to collapse
Thanks for your reply!
the key-combo in S21x are with USB plugged to PC, otherwise recovery cannot be reached, unless using ADB command. I have tried this many times since the wrong Odin flash occurred, but nothing happens except from reboot, warning screen (about unofficial software) and reboot again.
Even previous to the bricking, typically in order to get to download mode in this device, you need to go through recovery first and then select download mode. Alternatively, adb reboot download command, but neither are now an option.
So my last resort was a USB-JIG device to get to download mode - but I don't know of any such device for a USB-C connection.
Anyone here has experience with that? or can direct me to such a device for the newer Samsung models?
Thanks!
Wl40WaBL9hQcjo said:
CallmeNeos503 said:
connect it to the PC and do the combination that you did before, that is volume up and volume down pressed at the same time, that same thing happened to me, when I wanted to update twrp better install the stock first and then the new recovery, so you take advantage of updating the firmware of the phone and the new recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks for your help! - indeed the PLUS and MINUS volume keys with the usb cable plugged in gets you directly to d/l mode. I just tried it with the power key all the time, as in previous models, and that got me nothing.
Issue solved!