i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,
Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?
http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home
Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250
Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.
i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)
jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(
Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good:
Related
I checked through 100s of post tonight and could not find the answer to this and am in need of some help. I attempted to install a Cyanogen Nightly tonight through Rom Manager with no prior knowlege of the issues with CW 2.5 vs. CW 3.0. Stupid I know.
So natuaraly, when the download finished and Rom Manager tried to install, my MT4G just hung at the white boot screen. Through previous posts, the directions were simple to reflash the previous CW Recovery through Fastboot and reflash the Rom.
Well thats where the problem is.... When I attempt to flash ANY Rom earlier than 3.0.0.5, it will say OKAY in CMD, however the phone will never boot into the Recovery. I even tried fastboot erase recovery then reinstalled and still nothing.
So i decided to go a different root and reinstalled 3.0.0.5 to see if there was any work around through there. After i install 3.0 through Fastboot, I am able to go into Recovery, however when I select ANY option no matter what, the hat and the gear icon stay in the background and nothing happens.
I am very confused and lost and am hoping someone here will have had the same issue and can help me get my phone back in order.
Thanks in advance guys!
highrolla1866 said:
I checked through 100s of post tonight and could not find the answer to this and am in need of some help. I attempted to install a Cyanogen Nightly tonight through Rom Manager with no prior knowlege of the issues with CW 2.5 vs. CW 3.0. Stupid I know.
So natuaraly, when the download finished and Rom Manager tried to install, my MT4G just hung at the white boot screen. Through previous posts, the directions were simple to reflash the previous CW Recovery through Fastboot and reflash the Rom.
Well thats where the problem is.... When I attempt to flash ANY Rom earlier than 3.0.0.5, it will say OKAY in CMD, however the phone will never boot into the Recovery. I even tried fastboot erase recovery then reinstalled and still nothing.
So i decided to go a different root and reinstalled 3.0.0.5 to see if there was any work around through there. After i install 3.0 through Fastboot, I am able to go into Recovery, however when I select ANY option no matter what, the hat and the gear icon stay in the background and nothing happens.
I am very confused and lost and am hoping someone here will have had the same issue and can help me get my phone back in order.
Thanks in advance guys!
Click to expand...
Click to collapse
I havent had that issue exactly, but I might be able to help wlk you through getting this fixed. Ive had problems more than once myself on recovery, and helped a couple others solve other issues on here. If you want, add me on google talk (same username as on xda), and Ill walk you through it. Might have to wait till the morning, though, as Im probably gonna head to bed soon.
Fastboot 2.5 recovery and reflash froyo rom. If you decide to install CM7 again - read,search and make sure that you understand what you're doing. It has been stated at least few dozen times that Rom Manager is useless with gingerbread until Koush updates it.
Same Issue??
I believe my issue sounds similar.
I tried to go from Iced Glacier up to CM7. When I did I attempted to use the Clockwork Recovery 2.5 and of course it didn't work. Then I tried to upgrade it to 3.0.0.5. Now when I try to reboot into Clockwork recovery the phone just stays on the MyTouch 4G splash screen. The only way to get around it is use the Power/Volume down button and click on FASTBOOT and then select REBOOT.
The phone then boots in Iced Glacier. I have redownloaded ROM Manager and attempted to FLASH CLOCKWORKMOD RECOVERY. But it still won't load into recovery.
Essentially I need some step by step help to get back to clockworkmod recovery. I'm not too worried if I need to wipe everything. Just looking for the ability to restore again.
Alternatively I'm interested in upgrading to CM7 but not sure how I could do that without recovery working. I would also ask if you can give step by step instructions it would be much appreciated as I'm still pretty new to this.
Thanks!
I also have the similar problem. I have installed the Clockworkmod 3.0.0.5 and have rooted my phone before i was trying to install the gingerbread version. I made a recovery backup. i tried to restore the phone with that backup image but it still hung up with that "t-mobile mytouch " white splash screen.
What should i do now ? i have no idea how to bring my phone back to life :/
fosunite said:
I also have the similar problem. I have installed the Clockworkmod 3.0.0.5 and have rooted my phone before i was trying to install the gingerbread version. I made a recovery backup. i tried to restore the phone with that backup image but it still hung up with that "t-mobile mytouch " white splash screen.
What should i do now ? i have no idea how to bring my phone back to life :/
Click to expand...
Click to collapse
Jmg90300zx said:
I believe my issue sounds similar.
I tried to go from Iced Glacier up to CM7. When I did I attempted to use the Clockwork Recovery 2.5 and of course it didn't work. Then I tried to upgrade it to 3.0.0.5. Now when I try to reboot into Clockwork recovery the phone just stays on the MyTouch 4G splash screen. The only way to get around it is use the Power/Volume down button and click on FASTBOOT and then select REBOOT.
The phone then boots in Iced Glacier. I have redownloaded ROM Manager and attempted to FLASH CLOCKWORKMOD RECOVERY. But it still won't load into recovery.
Essentially I need some step by step help to get back to clockworkmod recovery. I'm not too worried if I need to wipe everything. Just looking for the ability to restore again.
Alternatively I'm interested in upgrading to CM7 but not sure how I could do that without recovery working. I would also ask if you can give step by step instructions it would be much appreciated as I'm still pretty new to this.
Thanks!
Click to expand...
Click to collapse
Sounds like both of you should of never of done this. This has been discussed a few times, and the end result is always the same.....
Download the correct Recovery image (which can be found in the Development section) and install it to your phone by using the ADB commands, in the fastboot mode. you can find a quick and painless way to set those up in my signature. Once you have installed the recovery image you can boot into hBoot and select recovery. from there you can flash CM7 and the gapps. Once you have done all that download the official clockwork ROM manager from the market and flash his current recovery image.
Seem to have an issue when i try and boot my device into recovery. It has CWM 6.0.1.9, which was flashed using the V4.0.0 toolkit, but every time i boot it into recovery i just get the standard recovery image of the android fella laying down with the red triangle above it. I have tried reflashing CWM onto it twice now and keep on getting the same issue. But i know CWM is on my device cos ive used it to make a backup about an hour ago. Any ideas?
lukehawkins1988 said:
Seem to have an issue when i try and boot my device into recovery. It has CWM 6.0.1.9, which was flashed using the V4.0.0 toolkit, but every time i boot it into recovery i just get the standard recovery image of the android fella laying down with the red triangle above it. I have tried reflashing CWM onto it twice now and keep on getting the same issue. But i know CWM is on my device cos ive used it to make a backup about an hour ago. Any ideas?
Click to expand...
Click to collapse
Use twrp mate, you'll never look back. Link: http://forum.xda-developers.com/showthread.php?t=1779092
Also, avoid toolkits. :silly:
Ok... I screwed up. I rooted my A500 and that worked great. I downloaded Goo manager and tried to flash recovery. It said it was successful, but when I selected reboot recover I got the dead andy with the red triangle....
So, I'm guessing what I missed doing was maybe unlocking the boot loader?
Anyway, any thoughts on how I can either get a recover installed, since I don't seem to have one right now?
nickjensz said:
Ok... I screwed up. I rooted my A500 and that worked great. I downloaded Goo manager and tried to flash recovery. It said it was successful, but when I selected reboot recover I got the dead andy with the red triangle....
So, I'm guessing what I missed doing was maybe unlocking the boot loader?
Anyway, any thoughts on how I can either get a recover installed, since I don't seem to have one right now?
Click to expand...
Click to collapse
See my post below, that worked for me, I could not get the bootloader to work and had to manually flash in APX mode. Just make sure to get the AfterOTA tool or use the A500manager to extract your CPUID and SBK and keep them around, you should be able to get these using the A500manager in APX mode. Once you have that you can use Blanthundr's APX Flash tool and manually flash a bootloader. I used Thor's successfully. Once you got that back you can load up a custom ROM and you should be back in business. Just make sure that you wipe the data, cache and Dalvik Cache before you apply the ROM to have a clean install. Hope this works for you, it worked for me.
http://forum.xda-developers.com/showthread.php?t=2163795
Mik
Hello everybody! I have a nexus 4 since a couple of months, and I had a Samsung galaxy s before. With that phone if you got stuck on a boot loop and couldn't access recovery, you used Odin to save you..what if it happens on nexus 4? Flash original image with a tool? Or there is some recovery file I can flash? Or what?
Thanks!
Sent from my Nexus 4 using xda app-developers app
It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.
Nuu~ said:
It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.
Click to expand...
Click to collapse
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.
kbeezie said:
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.
Click to expand...
Click to collapse
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.
gee2012 said:
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.
Click to expand...
Click to collapse
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.
kbeezie said:
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.
Click to expand...
Click to collapse
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others
gee2012 said:
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others
Click to expand...
Click to collapse
How exactly do you get out of a boot-loop, when you can't even get into the rom to bring up the Power dialog in the first place like that instruction says? (The instructions you posted only works if you're already in the rom, holding down the ok button before it reboots, and I suspect all that's doing is clearing the Dalvik-cache which you can do from recovery anyways).
Also my problem wouldn't have anything to do with that, because if you flash a galaxy nexus recovery onto an N4, and reboot, it won't let you in because it'll ask for a password to decrypt storage, an the recovery will do the same thing, and my post which you quoted didn't have anything to do with a bootloop, just simply that you can get out of just bout any situations with a Nexus 4.
These are the most common bootloop solutions http://droidviews.com/2012/how-to-recover-when-your-android-device-is-caught-in-bootloop/.
I'm using the tutorial on the LineageOS wiki for the Us996. I've unlocked the bootloader via official means from LG, but when it comes time to send the recovery via fastboot, it successfully sends and writes it, it even let's me boot into it, after pulling the battery, and using the correct button commands. But if I restart and try to enter again I'm greeted by the official erase everything recovery.
Does anyone know what I'm doing wrong? Do I need to flash root to get the recovery to stick?
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
baldybill said:
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=tDq0qMbgjL4
Click to expand...
Click to collapse
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
lowsnamebrand said:
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
Click to expand...
Click to collapse
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Phoenix591 said:
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Click to expand...
Click to collapse
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
lowsnamebrand said:
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
Click to expand...
Click to collapse
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
lowsnamebrand said:
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
Click to expand...
Click to collapse
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Phoenix591 said:
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Click to expand...
Click to collapse
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
lowsnamebrand said:
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
Click to expand...
Click to collapse
Its got more than a thread, has a whole section. Anyway heres the main release thread
Phoenix591 said:
Its got more than a thread, has a whole section. Anyway heres the main release thread
Click to expand...
Click to collapse
You've been a huge help, thank you! I'll report back later tonight, when I can actually work on my phone
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
lowsnamebrand said:
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
Click to expand...
Click to collapse
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Phoenix591 said:
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Click to expand...
Click to collapse
Sorry for the late reply, yeah I think I just let the boot animation go for around 5, I'm gonna have to try reflashing it and hoping for the best, I'll be sure to answer back when I get a chance
OK, I know this is an old thread - but I just got a replacement US996 phone; my old standby has a charger plug problem so I decided to get another one and put a rooted stock Oreo ROM on it. However, I'm having the same issue as the OP. Get into fastboot, flash TWRP (I have the 3.3.1-0 version, as the newer 3.3.1-1 version does not have any download mirrors). The flash appears to go just fine, it says the write was completed. However, when I reboot into adb mode and do "adb reboot recovery" I get "no command" and the little droid with his belly hatch open. So obviously TWRP wasn't flashed. The OP says he eventually was able to get it to work and install root. How did you fix the issue?
Do I still need to do the old recowvery shenanigans that we had to do back when the phone first came out?
Thanks!
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
pistacios said:
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
Click to expand...
Click to collapse
I've done that. The problem is that TWRP hasn't actually been installed via fastboot flash recovery - it goes through the motions, SAYS it's been installed, but when I do the button combo, it actually does reset my phone rather than booting into TWRP.
---------- Post added at 09:36 AM ---------- Previous post was at 08:55 AM ----------
Disregard the above. Flashed it again (4th time), and it finally took.
The same happened with my wife's US996 now that you mention it. Took a few tries and was a bit frustrating.
When I flashed TWRP on mine it was a "one and done".
Glad you got it sorted.
Thanks - all good. Rooted stock Oreo ROM installed, working great.