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.
Related
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
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.
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
atomus12 said:
Hi All,
I have the VZW DE and was having trouble deleting files when connecting my phone to Ubuntu (when I tried to delete a file, my phone would reboot). I figured I corrupted some files and had a nandroid backup from a few days ago. So I rebooted into TWRP and did a restore of the backup (system, data, and boot). But now when I reboot, my phone is stuck in a boot loop on the bootloader unlock screen. It will stay on for about 30 seconds, the phone will power down and then back to the bootloader unlock screen . I have no choice but to go back into TWRP.
I tried all that I could, I wiped then restored, same thing. I even had a back up from a few weeks ago but same results. Strange thing is, every time I go back into TWRP and click the Mount button, System mount is always unchecked even when I check it and reboot (same thing happens, stuck on bootloader unlock screen and will have to go back into TWRP)
Any ideas whats happening? I thought the restore would work perfectly but has completely stopped me from getting back on my phone.
Thanks guys!
Click to expand...
Click to collapse
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
jayboyyyy said:
what FW are you on? what twrp version are you using? did you try wiping cache and dalvik before and after restoring your back up?
Click to expand...
Click to collapse
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
atomus12 said:
Sorry about the delay. Thanks for your response jay!
If by FW you mean firmware, I'm on Verizon's 139.15.1_ghost. I just recently flashed twrp version 2.6.3.1 to prep for 4.4 and it flashed successfully. I wiped cache and dalvik before and after (always like to be on the safe side haha).
I tried a few other methods, like wiping the system and restoring, and wiping system, flashing the flashable zip 139.15.1 and restoring just data from the backup, etc.
I'm thinking about just RSDing my phone with the latest firmware (140.45.5_ghost) and start from scratch. Is that tool available for Linux?
Click to expand...
Click to collapse
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
jayboyyyy said:
thats your problem. you flashed twrp for 4.4 but you weren't on 4.4. I don't believe that twrp is backwards compatible. what you need to do is flash your old twrp back to the recovery. then restore your backup. then flash the stock recovery and system images. then take the ota. then flash the new twrp, then boot phone, say you wnat root. then create another back up of that twrp.
Click to expand...
Click to collapse
Never even thought about that! I will try those steps as soon as I get home today!
Thanks jay!!
Tried a new ROM but it froze on me. Then tried my back up and it would reboot after like a minute. So decided to do a full wipe but it deleted everything. I can get into the bootloader screen and TWRP but Windows can't read the phone and when it tries to install the drivers some of them fail. I have a copy of my recovery but need to know how to push it back to my phone and get the drivers installed right so that my PC can read my phone. Help.
TWRP seems to now act funny too where it'll like go to sleep and I have to press the home button or power button for a while before it turns the screen back on. Sometimes though I have to do the button combo to get back into recovery.
RUU
So I RUU'd the phone and it's working now, thanks. But it still shows unlocked and with S-OFF. So at this point can I just proceed with rooting it or do I have to lock it and put it back to S-ON before trying to re-root it? Or can I just try rooting it and putting a recovery image on it? It's been a while since I rooted it and obviously there was no 4.3 out at that time.
No need to re-lock or s-on just flash recovery and flash a rooted rom
bigdaddy619 said:
No need to re-lock or s-on just flash recovery and flash a rooted rom
Click to expand...
Click to collapse
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
QuiQNeZZ said:
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
Click to expand...
Click to collapse
You should be able to flash right over the older version make sure you download a fresh version of 2.6.3.0 from here http://techerrata.com/browse/twrp2/m7wls
Also remember after flashing the recovery.img type fastboot erase cache
The other thing is go into settings/screen and disable screen timeout that should take care of the "freezing" problem
I use TWRP 2.8.7.1(which was flashed to the phone) and now after flashing this nightly version, the recovery gets stuck on the TWRP screen and flashes every 60 seconds, but never lets me use it.
I've searched through all the forums, but can't find anyone else with this problem. I just want to flash CM12.1 Snapshot, but I can't without the recovery working.
Everytime I flash the same recovery(TWRP2.8.7.1), the bootloader gives me the error "Mismatched partition size". I've tried "Fastboot boot TWRP2.8.7.1.img, but it sits stuck on the loading TWRP screen. I've cleared the cache, but still nothing.
The only recovery that I can get to work is CWM by booting the .img from the bootloader, but that still does nothing because none of the directories will mount, so I cant flash from the recovery.
I'm waiting on motorola to send me the stock files and just reflash stock and start from scratch, but I really want to save my data.
Does anybody have any clue as to what I'm doing wrong before I reset to stock?
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
uluf said:
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
Click to expand...
Click to collapse
Nope.. didn't work. I had the 5.0 files from motorola that I flashed, and I'll update from there.
I really wish motorola would leave those files open to download instead of having to wait... sucks not having a phone, but I survived.
i have the same issue, any idea how to fix it ?