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!
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?
if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)
If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.
Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.
SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....
I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well
Hi guys. I accidentaly wiped System and now my phone has no rom on it. I tried to install stock rom from https://xiaomifirmwareupdater.com via Fastboot but it won't install because of anti rollback. My Bootloader is unlocked and i have TWRP, can anybody please help me... THX!
If you can boot to TWRP, try to install a MIUI recovery rom: https://mifirm.net/model/davinci.ttt or a custom rom.
Or, try to flash the images with CMD/Terminal.
Schnedi said:
If you can boot to TWRP, try to install a MIUI recovery rom: https://mifirm.net/model/davinci.ttt or a custom rom.
Or, try to flash the images with CMD/Terminal.
Click to expand...
Click to collapse
Thx. for the reply. I flash stock rom with CMD but it boot loops ..then flashed again with TWRP but after reboot it goes back to recovery. Any ideas?
I forgot this two lines
"fastboot erase userdata"
"fastboot flash userdata userdata.img"
Now it boots ..Thank a lot!!!
Alin CG said:
I forgot this two lines
"fastboot erase userdata"
"fastboot flash userdata userdata.img"
Now it boots ..Thank a lot!!!
Click to expand...
Click to collapse
Dear Alin
Could you describe to us the steps you did to succesfully reflash your device?
In the future in case that happend again... its easy, if you still can enter to TWRP just connect to the PC and transfer any flasheable ROM... Flash it and thats it
mauriciocardoso said:
Dear Alin
Could you describe to us the steps you did to succesfully reflash your device?
Click to expand...
Click to collapse
Will post when i get back from work.
Hucast_DL said:
In the future in case that happend again... its easy, if you still can enter to TWRP just connect to the PC and transfer any flasheable ROM... Flash it and thats it
Click to expand...
Click to collapse
The TWRP method didn't work because i wiped everything : system, vendor. etc... my phone had nothing on it, not a single file of the original firmware. When i flashed the rom with TWRP it always booted to TWRP and not the rom , even if the rom was installed successfully. Even when i tried to flash with FlashTool i got the anti rollback error. The CMD/Terminal flash worked for me.
Alin CG said:
The TWRP method didn't work because i wiped everything : system, vendor. etc... my phone had nothing on it, not a single file of the original firmware. When i flashed the rom with TWRP it always booted to TWRP and not the rom , even if the rom was installed successfully. Even when i tried to flash with FlashTool i got the anti rollback error. The CMD/Terminal flash worked for me.
Click to expand...
Click to collapse
For example you flash xiaomi.eu already included all you said I think the only step you didnt was wipe data (tipyng yes)
mauriciocardoso said:
Dear Alin
Could you describe to us the steps you did to succesfully reflash your device?
Click to expand...
Click to collapse
Download the fastboot rom from first link and unzip it. It should have 6gb then folow the steps from second link.
https://xiaomifirmwareupdater.com/archive/miui/davinci/
https://www.xiaomigeek.com/flash-miui-fastboot-rom-using-command.html
Tried flashing the rom with miflash official tool?
So i was updating my Rom, Havoc OS, Same version, new patch
so i wiped the cache, Dalvik, and system and then installed it, then magisk stopped, and susbstratum stopped so all the apps patched I can't open, ok, i'll install magisk, but when i got to the substratum manager, it was empty, i tried using rescue my system failed, did nothing, and then i tried flashing the rescue me, nothing, and it just won't reboot now, and what's worse i can't access recovery, it's showing an empty battery even though i've been charging it and it will only go to fastboot, hell i tried wiping and factory resetting it trough fastboot it said failed
any help?
Rmdhn said:
So i was updating my Rom, Havoc OS, Same version, new patch
so i wiped the cache, Dalvik, and system and then installed it, then magisk stopped, and susbstratum stopped so all the apps patched I can't open, ok, i'll install magisk, but when i got to the substratum manager, it was empty, i tried using rescue my system failed, did nothing, and then i tried flashing the rescue me, nothing, and it just won't reboot now, and what's worse i can't access recovery, it's showing an empty battery even though i've been charging it and it will only go to fastboot, hell i tried wiping and factory resetting it trough fastboot it said failed
any help?
Click to expand...
Click to collapse
Install an official Rom with Flashtool
Enviado desde mi Redmi Note 7 mediante Tapatalk
Install a new recovery with fastboot flash tool.
Rangdrol said:
Install a new recovery with fastboot flash tool.
Click to expand...
Click to collapse
i tried installing a recovery via Fastboot but when i rebooted to recovery it went back to fastboot
Rmdhn said:
i tried installing a recovery via Fastboot but when i rebooted to recovery it went back to fastboot
Click to expand...
Click to collapse
Maybe bootloader locked?
Than trie mi flash tool. Flash the lastest official mi rom. Make sure that you flash the right rom for your device. I heard, there are problems, if you flash wrong one and downgrade. When flashing don't lock your bootloader again.
Wrong section!!!
Rangdrol said:
Maybe bootloader locked?
Than trie mi flash tool. Flash the lastest official mi rom. Make sure that you flash the right rom for your device. I heard, there are problems, if you flash wrong one and downgrade. When flashing don't lock your bootloader again.
Click to expand...
Click to collapse
My bootloader is unlocked, i reinstalled the custom recovery trough fastboot but it's still like this, i'll do this tommorow, i'm too tired of trying now
This should be on the Q/A thread. Not here.
Rmdhn said:
My bootloader is unlocked, i reinstalled the custom recovery trough fastboot but it's still like this, i'll do this tommorow, i'm too tired of trying now
Click to expand...
Click to collapse
Now you can flash the rom? If not, maybe this treat help you: https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543
Also check the helpful post page 2.
Kagamihara said:
This should be on the Q/A thread. Not here.
Click to expand...
Click to collapse
Moved to Q&A section :good: