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...
Related
I don't know if I'm the only one or just a among a group of unlucky few but I managed to update to 4.1.2 no problems. Was able to restore root, no problems. It flashed the new bootloader 3.41 but now I can not get into Clockworkmod recovery. I tried installed it through rom manager and I tried flashing it through fastboot commands. I even tried the regular and the touch recovery. Is there a work around to this? Are these recoveries not compatible with the new bootloader? I suppose I can flash the old 3.34 bootloader and try again but does anyone actually know the deal here? Please help me out.
EDIT:
Thanks to SilverPosition and his post here . He has provided us with a link to a working CWM Touch Recovery. I've also been told that TWRP 2.3.1.1 found here also works with the 3.41 bootloader.
Thank you everyone for figuring this out
Update:
The only solution I found so far was to reflash the 3.34 bootloader in fastboot mode and then reflash my CWM recovery. Then I was able to get into recovery. What I don't understand is that many have been able to get the 3.41 bootloader flashed and then still have no trouble getting into recovery. So what am I missing? I installed the 3.41 bootloader 2 ways just to test. 1, with fastboot commands with the .img and the other in CWM with the .raw file. Both worked just fine updating the bootloader to 3.41 but no matter what recovery is then broken. Anyone got any input?
tucstwo said:
I don't know if I'm the only one or just a among a group of unlucky few but I managed to update to 4.1.2 no problems. Was able to restore root, no problems. It flashed the new bootloader 3.41 but now I can not get into Clockworkmod recovery. I tried installed it through rom manager and I tried flashing it through fastboot commands. I even tried the regular and the touch recovery. Is there a work around to this? Are these recoveries not compatible with the new bootloader? I suppose I can flash the old 3.34 bootloader and try again but does anyone actually know the deal here? Please help me out.
Click to expand...
Click to collapse
I have the same issue. I've tried every thing I can think of (except flashing the old bootloader) and nothing seems to work. Can't get into custom recovery (CWM, Goo Manager, TWRP, QuickBoot, ROM Manager), you name it I think I've tried it. I tried to flash CWM 6.0.X.X (can't remember exactly which one) thru the Toolkit but that didn't work either.
i used "fastboot boot recoveryimage.img" to get into cwm-recovery temporarily...
jpcalhoun said:
I have the same issue. I've tried every thing I can think of (except flashing the old bootloader) and nothing seems to work. Can't get into custom recovery (CWM, Goo Manager, TWRP, QuickBoot, ROM Manager), you name it I think I've tried it. I tried to flash CWM 6.0.X.X (can't remember exactly which one) thru the Toolkit but that didn't work either.
Click to expand...
Click to collapse
CWM will work with 3.34. I can't get it to work no way no how on 3.41.
tucstwo said:
CWM will work with 3.34. I can't get it to work no way no how on 3.41.
Click to expand...
Click to collapse
Cannot get TWRP to work with 3.41 either - works nicely with 3.34.
Is it possible to flash just the important stuff of 4.12 and leave out the bootloader (i.e., keep bootloader 3.34)?
Android 4.1.2
Bootloader 3.41
TWRP 2.3.0.0
I got it to work by erasing the stock recovery then flashing TWRP.
fastboot erase recovery
fastboot flash recovery
I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.
docfreed said:
Cannot get TWRP to work with 3.41 either - works nicely with 3.34.
Is it possible to flash just the important stuff of 4.12 and leave out the bootloader (i.e., keep bootloader 3.34)?
Click to expand...
Click to collapse
What I did was flashed the entire 4.1.2 and then flashed the 3.34 bootloader and my old CWM recovery back in if you choose to go that route. Its a lot easier to replace what doesnt work rather than pick and choose what you're gonna flash
tucstwo said:
What I did was flashed the entire 4.1.2 and then flashed the 3.34 bootloader and my old CWM recovery back in if you choose to go that route. Its a lot easier to replace what doesnt work rather than pick and choose what you're gonna flash
Click to expand...
Click to collapse
Thanks - yes, of course you're right. Are you able to repeatedly boot into CWM, make backups, etc... I hate to redo my whole setup again but I also believe that there's an issue with the 3.41 bootloader.
Did you flash the bootloader and CWM with fastboot?
docfreed said:
Thanks - yes, of course you're right. Are you able to repeatedly boot into CWM, make backups, etc... I hate to redo my whole setup again but I also believe that there's an issue with the 3.41 bootloader.
Did you flash the bootloader and CWM with fastboot?
Click to expand...
Click to collapse
Use the bootloaders provided in this thread : http://forum.xda-developers.com/showthread.php?t=1929270
There's 2 threads floating around but 1 of them provides to bootloaders in flashable format and the one I gave you in image format for fastboot flashing.
What I did was downloaded the OTA zip from here: http://forum.xda-developers.com/showthread.php?p=32672323
Downloaded Voodoo OTA Rootkeeper from the play store. Backed up my su binary and root access with that app.
Then I ran the ota zip in CWM.
I rebooted. went into Voodoo OTA and restored root access
I used root explorer and deleted /system/recovery-from-boot.p and /system/etc/install-recovery.sh this way it wouldnt keep attempting to flash the stock recovery on boot.
Rebooted into fastboot mode and fastboot flashed the 3.34 bootloader
rebooted the bootloader
then fastboot flashed cwm touch.
then rebotoed and everything works fine.
Only issue is im on the 3.34 bootloader and not the 3.41 one and just want to know WHY?! lol
tucstwo said:
Use the bootloaders provided in this thread : http://forum.xda-developers.com/showthread.php?t=1929270
There's 2 threads floating around but 1 of them provides to bootloaders in flashable format and the one I gave you in image format for fastboot flashing.
What I did was downloaded the OTA zip from here: http://forum.xda-developers.com/showthread.php?p=32672323
Downloaded Voodoo OTA Rootkeeper from the play store. Backed up my su binary and root access with that app.
Then I ran the ota zip in CWM.
I rebooted. went into Voodoo OTA and restored root access
I used root explorer and deleted /system/recovery-from-boot.p and /system/etc/install-recovery.sh this way it wouldnt keep attempting to flash the stock recovery on boot.
Rebooted into fastboot mode and fastboot flashed the 3.34 bootloader
rebooted the bootloader
then fastboot flashed cwm touch.
then rebotoed and everything works fine.
Only issue is im on the 3.34 bootloader and not the 3.41 one and just want to know WHY?! lol
Click to expand...
Click to collapse
Thanks - I'll try this tonight and let you know - I'd also like to know why there's so much issue with 3.41 but I'll be happy if I can update.
janedoesmith said:
Android 4.1.2
Bootloader 3.41
TWRP 2.3.0.0
I got it to work by erasing the stock recovery then flashing TWRP.
fastboot erase recovery
fastboot flash recovery
I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.
Click to expand...
Click to collapse
I removed the "recovery-from-boot.p" file, and erased the stock recovery, then flashed Clockwork Recovery, but still can't boot into Clockwork recovery. It just displays "boot downloaded image" on the top, then after a few seconds, it boots into android os...
I don't know about CWM but I got it to work with TWRP.
janedoesmith said:
Android 4.1.2
Bootloader 3.41
TWRP 2.3.0.0
I got it to work by erasing the stock recovery then flashing TWRP.
fastboot erase recovery
fastboot flash recovery
I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.
Click to expand...
Click to collapse
janedoesmith said:
I don't know about CWM but I got it to work with TWRP.
Click to expand...
Click to collapse
I tried exactly this
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-3.41
fastboot reboot-bootloader
fastboot erase recovery
fastboot flash recovery twrp2.2.2.1
fastboot reboot-bootloader
Then into recovery...nothing. Back to the google screen. That's it.
All I did was rename recovery-from-boot.p to recovery-from-book.bak, reinstalled TWRP from GooManager, and everything works just fine.
You have to disable/delete that file in /system or it will restore the stock recovery every time you reboot.
iElvis said:
All I did was rename recovery-from-boot.p to recovery-from-book.bak, reinstalled TWRP from GooManager, and everything works just fine.
You have to disable/delete that file in /system or it will restore the stock recovery every time you reboot.
Click to expand...
Click to collapse
Nah that's not it. Those files were the first thing I got rid of as soon as I restored root access, before I even bothered to access recovery. If u look a few posts up I told that other member how I installed stuff on my tablet and it included those steps.
tucstwo said:
Nah that's not it. Those files were the first thing I got rid of as soon as I restored root access, before I even bothered to access recovery. If u look a few posts up I told that other member how I installed stuff on my tablet and it included those steps.
Click to expand...
Click to collapse
Ah--I see that now. I'm not sure which bootloader I'm on, to be honest--I just took the OTA as-is.
I flashed my device with the JZO54K factory image. Then i flashed cwm 6.0.1.0 via fastboot. I can not boot recovery using any method (recovery via bootloader, adb, terminal, various apps) with the 3.41 bootloader. The only way I have been able to use recovery is to downgrade to the 3.34 bootloader from JRO03D.
Sent from my Nexus 7 using Tapatalk 2
I'm in the same ship. Only works using 3.34 bootloader.
Install the factory image or OTA, with 3.41 bootloader stop me from running cwm. Only solution is flash 3.34 bootloader image file to use it again.
Edit: C80 here.
+1, I'm on a C60 revision Nexus 7 and I spent hours trying to figure this out until I flashed back to 3.34 bootloader. Thanks for this!
Hi! Im a noob with a couple of questions hope anyone can help me...
I was recently at 4.2.1 on my nexus 7 had twrp installed, and accidentally updated to stock 4.2.2 my cstom recovery wash flashed by a stock one and forced me to install another via fastboot, but this time i installed cwm then i decided to go back to twrp coZ i dont personally like cwm,. So here is my problem i used rom toolbox to reboot into recovery and it said that i have a cwm installed but when i rebooted i was on twrp, its confusing did i installed both? And made me decide to use rom manager it said that i have twrp and cwm already installed how can i uninstall cmw...
Hope u could help me.. Anyone?
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
bftb0 said:
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
Click to expand...
Click to collapse
Hi thnx for the help, actualy i was able to boot into twrp already and i belive i flashed it completely, my only concern is did i overwrite the cwm in my rec partition? Or it is still there?
Sent from my Nexus 7 using xda app-developers app
There can be only one bootable image in the recovery partition at a time.
If you boot from the bootloader into recovery, and you see TWRP... then that is what is flashed there.
If you want to see what I am talking about, go into ROM manager and select the menu item that causes a boot into recovery. What you will see (after a little bit) is the CWM U/I.
What is going on is that ROM manager boots whatever recovery is actually flashed in the recovery partition, and then immediately replaces /sbin/recovery with it's own version (CWM) and then kills & restarts that same program.
So - what you *see* is the CWM version of /shin/recovery - running on top of the kernel & ramdisk were provisioned by the whatever recovery was actually flashed to the recovery partition.
If you want to actually flash CWM to the recovery partition, ROM Manager has a menu item for that. I'm not sure what the exact wording is.
If you are confused by this, just read the first two sentences in this post.
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?
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!