Background on phone: flashed TWRP recovery 2.4.4 and unlocked bootloader
Installed Paranoid Android custom rom
Do not like low call volume issues, low Bluetooth volume issues, and doesn't recognize my wired headset as containing a mic, people cannot hear me on it.
I am wanting to go back a stock rom. I dont care if its ICS or JB, preferably ICS. It seems the there were many options to going back stock. I tried running the .exe for the RUU, you must have a relocked boot loader. I relocked the bootloader, now i am stuck with a constant loop of booting bootloader, cannot access the recovery.
So i unlock bootloader again, reinstall recovery. Then now cannot load my rom. I keep getting errors in twrp stating it cannot mount the drive(internal sd) Get same error if i try to wipe caches. So i wipe system and rom off. Now I can clear caches and error about mounting internal drive goes away.
Now I am left without a rom. In order to run .exe RUU installer I must have locked bootloader, and have rom running in usb debug, As if right now that's impossible.
My last option is flashing the BORKED rom. My version of twrp is to new, i treid to install an older version and just messed up twrp.
Any help is appreciated, and returning to stock would be awesome. Thanks
OK...
You have a laundry list of issues...
First... You should get twrp 2.5.0.0
Then... Using fastboot...
Fastboot flash recovery (recovery name)
Then reboot to recovery...
Mount USB...
Plug phone into computer...
Hopefully windows will offer to format your internal sdcard...
After that...
If you want BORKED... find wcx recovery... Flash that with fastboot... Then install borked...
Good luck
Sent from my Vivid 4G using Tapatalk 4
Related
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
how do you flash the old bootloader? if you don't mind me asking.
I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.
ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus
You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063
I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.
anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.
Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse
Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.
Good morning all,
Got stuck in a bit of a situation today so I'm looking to see if I could get some help.
Got an S-Off Vivid and tried installing CM10 on it last night. Installed TWRP, installed the ROM, and got stuck at the Cyanogenmod boot logo. Tried rebooting, relocking the bootloader, reinstalling the ROM - no luck.
Figured I should RUU and start the process all over. Used this RUU: http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe (found here: http://forum.xda-developers.com/showthread.php?p=24042047). After returning to stock and starting the bootloader unlock process, I get a successful transfer of the unlock_code.bin, but the bootloader unlock confirmation screen doesn't load up when I'm in fastboot. The device reads "fastboot usb" and my OS detects it just fine, so I was a bit confused as to why the unlock procedure wouldn't continue as I've seen it do in the past.
Any help would be greatly appreciated!
Bumpage. Anyone?
Try another USB port USB cord or new computer. Something I listed will most likely be the fix. Or reinstall driverss
Sent from my Vivid 4G using Tapatalk 2
RUU'd, relocked bootloader, unlocked bootloader, installed TWRP and CM10.
Same problem. Guessing I'm just unlucky on this one?
Went through about 16 cycles of flashing the ROM and the boot.img (even though I'm S-Off) and now it works. Hep. /shrug
Homeslice talked about fastboot flashes not taking on the first try...
If you switch again... fastboot the boot image multiple times... it may help
Sent from my Vivid 4G using Tapatalk 2
I suffered this problem as well, but I did fix it. Try booting into recovery, clear all data/factory wipe, clear dalvik/cache, clear cache, mount /system, and THEN flash CM10. Use the newest nightly. THEN flash Gapps. You want: goo-inside.me/ gapps/ gapps-jb-20121011-signed.zip (I'm new so I can't post URLS.
The other gapps will have errors later on. This is the most stable.
Thanks if helped.
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
So I tried to flash Omni 4.4, coming from PAC, had to delete my old PAC zips to make space for a Nandroid. During flashing Omni, I got an error, turns out I needed the latest TWRP version which wasn't mentioned in the OP. Tried to restore the Nandroid but TWRP just freezes. Can't mount the storage in TWRP, flashed the latest version in boot loader, tried to flash but setup wizard force closes so that's useless. Flashed CWM recovery and it can't mount either.
Anyone got any ideas?
GANJDROID said:
So I tried to flash Omni 4.4, coming from PAC, had to delete my old PAC zips to make space for a Nandroid. During flashing Omni, I got an error, turns out I needed the latest TWRP version which wasn't mentioned in the OP. Tried to restore the Nandroid but TWRP just freezes. Can't mount the storage in TWRP, flashed the latest version in boot loader, tried to flash but setup wizard force closes so that's useless. Flashed CWM recovery and it can't mount either.
Anyone got any ideas?
Click to expand...
Click to collapse
At this point do you want to just go back to stock and try again from there, or still trying for Omni? I would fastboot flash recovery again, wipe with fastboot -w (if you're coming from 4.3 you might as well). If you can, ADB sideload Omni, if not, try your zip again.
Try restoring with TWRP again, too. Put your phone on the charger and start the restore, give it about 20 minutes before you give up, twrp semi freezes on me all the time.
ripin150 said:
At this point do you want to just go back to stock and try again from there, or still trying for Omni? I would fastboot flash recovery again, wipe with fastboot -w (if you're coming from 4.3 you might as well). If you can, ADB sideload Omni, if not, try your zip again.
Try restoring with TWRP again, too. Put your phone on the charger and start the restore, give it about 20 minutes before you give up, twrp semi freezes on me all the time.
Click to expand...
Click to collapse
I'll be happy with any sort of life. If I have to wipe everything, go to stock and root again then stick with PAC, then so be it. Do you have any links handy with flashing stock RUU via bootloader?
I'll try that now. Press on the backup to restore it and it hangs at that screen, but I still get feedback if I press the back soft key, is that what you get when it happens to you?
Edit: HA! Plug my phone in to charge, try to restore and it works first time. Cheers for the help anyway!
What's the output of fastboot getvar all?
GANJDROID said:
I'll be happy with any sort of life. If I have to wipe everything, go to stock and root again then stick with PAC, then so be it. Do you have any links handy with flashing stock RUU via bootloader?
I'll try that now. Press on the backup to restore it and it hangs at that screen, but I still get feedback if I press the back soft key, is that what you get when it happens to you?
Click to expand...
Click to collapse
Yes, that's what happens to me, only in TWRP
Are you S-OFF? If so you can Super CID and flash the Google Edition RUU
If you're S-ON, here is the AT&T RUU.
I followed all of the instructions in the Nexus 6 Guide to unlock, root and flash a custom recovery.
I was trying to sideload a rom into my phone and was doing advanced wipe in TWRP. I accidentally choose system thinking it would be fine since I am flashing a new rom anyway.
I think I force shut down the phone and now it just stays and hangs on the google logo. I can only get into the bootloader/fastboot. When I try getting into TWRP recovery it just flashes for a second and then attempts to reboot.
I figure I should try flashing a rom via adb bootloader/fastboot but I attempted a few times and failed. Can someone help walk me through this?
Edit: I can access TWRP recovery now... I tried doing sideload several more times but for some reason I keep getting loading rom.zip cannot read rom.zip
Well i going to geuss you know to to get to recovery though bootloader thought your phone
But your phone is semi Bricked
You can download wugs toolkit
And i will show unroot/flash stock you will click bootloop/ bricked and go though the steps
And it will download the stock software and reovery and go though the steps you will be fine
If you want use the same toolkit and root and install twrp again
Do you use a USB otg drive? If you don't you can send a rom to twrp using some commands.
Try to redownload the ROM that won't work and put it on the phone via a USB otg drive or using your pc and don't forgot gaps.
If you're not, use the WUG toolkit to reflash the stock ROM. Then you can use that to flash your new ROM
Unless im missing somethimg, why not just flash the factory image through fastboot and start over?
Like mentioned above, or just flash TWRP in fastboot. Then boot into TWRP, and flash ROM.