I've upgraded to 4.1.2 this morning and it went fine but I can now not go into custom recovery (CWM) it just shows a droid on his back with a red triangle.
After reading a number of other posts they recommend downgrading the boot loader to a previous version as no one has managed to get custom recovery to work with the 4.1.2 boot loader.
My question is can I re-flash the stock recovery without re-flashing back to stock?
Thanks
Jon
jonchill said:
no one has managed to get custom recovery to work with the 4.1.2 boot loader.
Click to expand...
Click to collapse
I did
This thread has instructions on how to flash just the recovery with fastboot you could also try with CMW recovery image
I've flashed a full 4.1.2 stock ROM and re-rooted without custom recovery and I still get the droid on his back with the red triangle and no access to stock recovery.
Any ideas?
Thanks
As I said the link I provided has instructions on flashing a recovery,download the image for CWM and flash following the instructions in that thread
Related
So... I was rooted using gfree method and had recovery 2.5.1.4 installed running the ice glacier rom. Then I decided i was going to upgrade to a gingerbread rom so I updated my rom manager and flashed the new CW 3.0.2.4 rom and now it wont boot into recovery. When I try to boot into recovery it shows the mytouch logo for a bit, the screen turns black and the phone reboots. I tried to flash the old recovery again but I get an error message saying: An error occurred while flashing your recovery. I can still flash CW 3.0.2.4 and CW 3.0.0.5 but both will not boot into recovery.
I also tried flashing the 3.0.2.4 recovery manually through fastboot flash recovery recovery.img but I still get the same problem. I couldn't find an active download link for the 2.5.1.4 recovery to try to flash manually so I don't know if it helps to do this.
I read on the forum somewhere to revert back to stock recovery using the stock PD15IMG IMG file and try again. This took me back to stock and I was able to boot into the stock recovery. Then i reran visionary for permroot again, deleted my clockworks folder from my sdcard and tried again, but the problem came back.... Mytouch logo then black screen then auto reboot.
My root access still works fine but I cant get into recovery to flash a new rom.... and now I am stuck on a stock rom. :[ After 6 hours of trying to fix the issue I'm still very confused.
Any help / suggestions would be appreciated Thanks.
Its doing this after you go into hboot and select "Recovery"?
JDV28 said:
Its doing this after you go into hboot and select "Recovery"?
Click to expand...
Click to collapse
Yes, from Hboot and from rom manager, but sometimes if i try from rom manager it will also hang at the white mytouch logo screen.
Update
Ok. So i have a partially functional recovery again i found the recovery image for 2.5.1.2 and flashed it using fastboot flash. I am now able to get into recovery again and install custom froyo roms, but every time i try to upgrade to a higher version like 3.0.0.5 or 3.0.2.5 no matter which method i use, I still get the same reboot while trying to get into recovery.
Please help. Thanks
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
This isn't my first android root but I'm stuck. I followed the video for rooting my Nexus 10. Got stuck in a boot loop but was able to flash cwm but still in boot loop. I tried doing the factory reset and now cwm is gone too and still stuck in boot loop. I tried reflashing cwm. When I try to access recovery I get the red triangle with ! on it. And I'm stuck in boot loop. I went here and tried to reflash recovery.img and no joy. Still no recovery access and no boot. ((
accidentally posted this in the samsung nexus forum #whoops
Boot back into recovery and press all 3 buttons (power, vol +, vol -) simultaneously until the menu comes up. The timing has to be very exact so don't worry if it takes 10+ tries. Then select factory reset and it should boot up properly.
I never could get CMW to stay. So I flashed TWRP as the recovery instead. Also follow wireroid advice about getting out of boot loop. If you want to SEE that method, check out the rooting N10 vid on youtube by qbking777.
some progress!
Ok I got back into the tablet with wireroid help YAH!!
I have a system update pending but when I tried to install it I got the red! with 'no command' ... after a near heart attack I did the factory reset again and got back to where I was before.
Now I need pointed in the right direction. So right now I'm unlocked but that's it. I have no custom recovery and presumably no su access because all I successfully did was unlock the bootloader.
I downloaded the nexux10 toolkit. Do I need to flash a recovery first? Do I try CMW again or go with TWRP? I've only used CMW in the past.
Do I ignore this Jelly Bean system update for now??
bg1906 said:
I never could get CMW to stay. So I flashed TWRP as the recovery instead. Also follow wireroid advice about getting out of boot loop. If you want to SEE that method, check out the rooting N10 vid on youtube by qbking777.
Click to expand...
Click to collapse
Try this toolkit by Wugfresh. http://www.wugfresh.com/nrt/
It's what I used and I went from locked and stock to unlocked, rooted, and with TWRP as my recovery in less than 15 minutes. I unlocked and rooted my GNex the "old-fashioned" way but wanted something easier for my N10.
Also, here's a YouTube video from QBKing77 walking you through the process using the above toolkit. https://www.youtube.com/watch?v=YtLvlrUDB04&feature=youtube_gdata_player
Since you're already unlocked you should be able to just skip to the part where root and a custom recovery are flashed (you'll end up with TWRP but you can always download ROM Manager and flash ClockworkMod if that's your preference).
Good luck.
I ran MSkip toolkit and it repaired everything. I got a failed on renaming my recovery images so my stock recovery images are just gone I guess? Anyway I'm good. Rooted and repaired thanks to Skips toolkit.
Thanks for all the help!
Rodeojones said:
Try this toolkit by Wugfresh. http://www.wugfresh.com/nrt/
It's what I used and I went from locked and stock to unlocked, rooted, and with TWRP as my recovery in less than 15 minutes. I unlocked and rooted my GNex the "old-fashioned" way but wanted something easier for my N10.
Also, here's a YouTube video from QBKing77 walking you through the process using the above toolkit. https://www.youtube.com/watch?v=YtLvlrUDB04&feature=youtube_gdata_player
Since you're already unlocked you should be able to just skip to the part where root and a custom recovery are flashed (you'll end up with TWRP but you can always download ROM Manager and flash ClockworkMod if that's your preference).
Good luck.
Click to expand...
Click to collapse
In this thread I got a great answer about how to fix a sizing problem with the data partition on my Razr M. You'll need this if you are running CMod, are encrypting, reformat your data partition with TWRP, and want to re-encrypt after the reformat.
There is only one silly problem. I am running CM 10.1, which is 4.2.2. I am also running TWRP 2.6. I can change versions of TWRP as easy as anything, but I cannot for the life of me figure out how to return to stock recovery. I really do not want to RSD, since Motorola has been working on how to relock the bootloader, and I don't want to give them that chance. And, of course, if I do RSD back to 4.2.2 stock, I'll have no way to get root back.
What I'd love to do is just to get the 4.2.2 stock recovery image, and flash it with fastboot. But I cannot for the life of me find the 4.2.2 stock recovery image. I have Matt's 4.1.2 stock recovery image, and I actually tried it with his utility, but...yeah. Android with exclamation point. It did not end well.
So, here's the question: is there any way to flash the 4.2.2 stock recovery without RSDing back to stock? Where is that darn disc image?
Thanks!
Brokkn said:
In this thread I got a great answer about how to fix a sizing problem with the data partition on my Razr M. You'll need this if you are running CMod, are encrypting, reformat your data partition with TWRP, and want to re-encrypt after the reformat.
There is only one silly problem. I am running CM 10.1, which is 4.2.2. I am also running TWRP 2.6. I can change versions of TWRP as easy as anything, but I cannot for the life of me figure out how to return to stock recovery. I really do not want to RSD, since Motorola has been working on how to relock the bootloader, and I don't want to give them that chance. And, of course, if I do RSD back to 4.2.2 stock, I'll have no way to get root back.
What I'd love to do is just to get the 4.2.2 stock recovery image, and flash it with fastboot. But I cannot for the life of me find the 4.2.2 stock recovery image. I have Matt's 4.1.2 stock recovery image, and I actually tried it with his utility, but...yeah. Android with exclamation point. It did not end well.
So, here's the question: is there any way to flash the 4.2.2 stock recovery without RSDing back to stock? Where is that darn disc image?
Thanks!
Click to expand...
Click to collapse
In my goodies. Stock recov & a prerooted restore method!
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Brokkn said:
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Click to expand...
Click to collapse
Normally when you boot into stock recovery , you wont be presented with a nice menu. It's almost a hidden menu that you have to pull up...
When you go in and get the Triangle or whatever is there, you will have to press volume + and - and power button to get the menu to display.
Try a few combinations, volume + and - then power, or power then + and -, or all three at the same time. Eventually it will come up.
Brokkn said:
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Click to expand...
Click to collapse
I was going to offer the xt897 stock recovery. It glides into action & has apply from cache. In goodies also.
Going to need some help on this one. Got root on stock through ioRoot22. Flashed twrp 2.6.3.3 through FreeGee. Backed up stock rom in twrp then reboot to stock rom to confirm boot
Went back into TWRP then Wiped device then attempted flashing Vanir.
Flashed Vanir zip
Flashed gapps zip
Attempted flashing kernel from here http://forum.xda-developers.com/showthread.php?t=2638091
Came back with flash failed with an assert issue with loki, knowing I probably shouldnt have rebooted and restored my stock backup. I didnt think anything of it. Now Im stuck in fastboot and can gain access to download mode.Currently downloading the 11A tot/kdz and reading over this guide
http://forum.xda-developers.com/showthread.php?t=2448960
Would I need a stock recovery for the VS980 to complete download mode restoral? if so would anyone have it?
Ok so in the end through some patience, I was able to restore my stock rom by gaining access to TWRP through the normal "factory reset with stock recovery" method of booting. Was tricky because it wouldnt power off and bootlooping to fastboot. While in fastboot I held Vol - and Power so I can gain access again to TWRP. Restored the stock rom and all is well.
Snuzzo said:
Ok so in the end through some patience, I was able to restore my stock rom by gaining access to TWRP through the normal "factory reset with stock recovery" method of booting. Was tricky because it wouldnt power off and bootlooping to fastboot. While in fastboot I held Vol - and Power so I can gain access again to TWRP. Restored the stock rom and all is well.
Click to expand...
Click to collapse
Thanks for sharing.
Sent from my LG-D802 using Tapatalk
Ok so apparently there are some kernels/roms who have not updated their loki_patch file yet. From what I've been reading up which needs to be done for the roms to correspond to the updates. Am I correct?