On my Note 1 I tried to update CWM-Recovery with the cwm app - and I never sticked to the device.
When installing and booting into recovery though cwm-app it worked once, but then on next reboot it got reverted to the old version again.
Later then I found out that on the galaxy devices the recovery can only be hard-flashed with odin or similar method, but not through the cwm-app.
BUT the cwm-app used install-recovery.sh or some other method to start the new recovery at least once after the first reboot.
Couldn't we maybe get a custom recovery running on our devices while still having knox untouched?
Just as a temporary boot I mean, but if that would work over adb for example, we wouldnt need to flash a recovery on the phone but instead boot the recovery over adb.
Anyone know more maybe? How does install-recovery.sh actually work, or how ccan it be used to boot a custom recovery?
Related
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
It happened to me once. I pushed the power button for 60 seconds as it supposed to do a kind of battery pull, and it worked.
HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Lordificated said:
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Click to expand...
Click to collapse
I've done this twice to my nexus now and I think I found a reliable way to restore to running condition. YMMV
1)Boot the nexus into fastboot (power and both volume keys) when you power up.
2)Attach your usb cable from the PC (or MAC I guess, dont have one to try)
3)start WUG Nexxus Root Toolkit. 'Launch' advanced utilities.
4)Test your fastboot with Quick tools. check the button at Fastboot-Bootloader and click 'List Devices' if the box that pops up is empty then fastboot isn't working (I can't help you there and it must be working to continue).
5)If fastboot shows a device then go to "Boot Temporary" and click 'Custom Recovery'.
6)I selected 'Touch TWRP' but CMW may work as well. This will reboot you into (temp)TWRP and from there you can force a reboot that will reset the 'Recovery' flag that has locked your bootloader.
7)Give it a few minutes (be patient for 5 minutes) and hopefully you reboot to where you were prior to this mess.
Long time lurker and couldn't fix my fails without everyone here.
Thanks to all.
Bill
HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
zeroedout420 said:
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
Click to expand...
Click to collapse
I guess mine worked because I was still on stock bootloader and adding TWRP was an important key but the 5 minutes seems to be the solution after all the rest.
recovery boot loop:- Is coz, one of your partitions would be facing problems while mounting.. So Wipe the Partition and Format it with Ext-2 file format. and reboot the Mobile. Then it'll stops rebooting.
Do you have a Samsung device?
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
carltasmania said:
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
Click to expand...
Click to collapse
How do you install cf-autoroot when stuck in a boot loop with samsung galaxy S device if there is no fastboot?
My phone is stuck in bootloop too. It shows Twrp at the starting and then restarts. What am i supposed to do? I need help ASAP please
I was trying to unlock my Nexus 4. I've done this before on a Galaxy Nexus, successfully but something went wrong here.
Just got CWM Recovery on. I tried to reboot using the recovery and it provided me with two prompts:
1) Do you want to disable the stock recovery install? [ I hit NO ]
2) Do you want to root your device (I believe this is what it asked) [ I hit YES ]
Now my phone is stuck in a reboot loop. I can get into recovery with no problem (and it is still the CWM one). I've tried reloading the recovery to no avail. What are my options to try to fix this?
I have tried fastboot erase cache but it did not restore my phone.
Update your recovery or try to flash another recovery. Twrp is recommended here. Cwm also gave me some hard time with bootloop and stuff
CCody said:
Update your recovery or try to flash another recovery. Twrp is recommended here. Cwm also gave me some hard time with bootloop and stuff
Click to expand...
Click to collapse
I tried flashing TWRP, but I get the Can't mount /data, Can't mount internal storage, etc etc. I can't flash .zips at all and I feel like my only way out is to use fastboot to deal with things. Even now, I'm trying fastboot and it's stuck trying to send the factory Nexus 4 4.4.4 ROM over...
I have no idea how to safely fall back now. I just want my phone back ASAP.
Just tried flashing 5 out of the 6 imgs to my phone using fastboot (didn't flash recovery). and I'm STILL stuck on the loading screen (10 minutes). Which means I'm still having the problem...I have no idea what to do now.
limenuke said:
Just tried flashing 5 out of the 6 imgs to my phone using fastboot (didn't flash recovery). and I'm STILL stuck on the loading screen (10 minutes). Which means I'm still having the problem...I have no idea what to do now.
Click to expand...
Click to collapse
Flash recovery in fastboot. This'll put the stock recovery on. Do a factory rest in the stock recovery. Then flash the twrp image in fastboot and re-root
Sent from my Nexus 5 using XDA Free mobile app
limenuke said:
I was trying to unlock my Nexus 4. I've done this before on a Galaxy Nexus, successfully but something went wrong here.
Just got CWM Recovery on. I tried to reboot using the recovery and it provided me with two prompts:
1) Do you want to disable the stock recovery install? [ I hit NO ]
2) Do you want to root your device (I believe this is what it asked) [ I hit YES ]
Now my phone is stuck in a reboot loop. I can get into recovery with no problem (and it is still the CWM one). I've tried reloading the recovery to no avail. What are my options to try to fix this?
I have tried fastboot erase cache but it did not restore my phone.
Click to expand...
Click to collapse
Flash it again. Remember to clean out the cache and dalvik cache every time you flash a zip.
This is why most phones get stuck in a boot loop when flashing a new ROM.
As long as you have the custom recovery, you don't need to flash custom recovery
Hope this helps!
I would also recommend PhilZ's recovery. Best of both CWM and TWRP.
Sent from my Nexus 4 using XDA Free mobile app
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
abstractartemis said:
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
Click to expand...
Click to collapse
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
ashyx said:
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
Click to expand...
Click to collapse
So just keep flashing it until i can boot to twrp recovery basically?
abstractartemis said:
So just keep flashing it until i can boot to twrp recovery basically?
Click to expand...
Click to collapse
What's stopping you boot to Download mode?
ashyx said:
What's stopping you boot to Download mode?
Click to expand...
Click to collapse
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
abstractartemis said:
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
Click to expand...
Click to collapse
If you can flash twrp then not booting to twrp must be pilot error.
It MUST be done immediately after flashing in odin.
Hi everybody. I need a little help here. I bought used LG G6 to practice installing custom roms. So I unlock bootloader and now I trying to install TWRP (at this moment without root beacuse obviously with my luck on my phone doesnt work any program like kingo ROOT or something like this) and when flashing recovery with ADB is done I unplugg smartphone and enter to menu with wipe all data because in every corner in internet I was people say when I choose ..Yes" twice then TWRP would launch. Not this time. And whats strange that when I boot smartphone normally then all the data is still on it. Power key+volume down doesnt do anything, volume up too. I dont know what to do next.
My answer may be too late but it sounds like the recovery you flashed is broken in some way.
When I installed my custom recovery I had to enter into recovery IMMEDIATELY after flashing the recovery image from terminal, in fastboot mode. Upon entering the recovery I had to install a .zip file named "no-verity-opt-encrypt.zip". This is the .zip that prevents the recovery partition to be reflashed by the phone's OS back to stock. This "back to stock" flashing is done by the OS at boot time. If you fail to boot into recovery and let the phone boot up before installing the .zip, you may have the experiences you just described. I'll search for the thread I followed.
Edit: Here is a thread I found useful:
Wich twrp actually work on h870?
Hello. I've been trying to get twrp(official) working on h870 for some time. The only version that at least boots up is 3.1.1.0 I know that in order to make it "stick" I have to flash magisk or custom rom. However I don't want to do that prior to...
forum.xda-developers.com
And here is the one I *probably* followed:
https://forum.xda-developers.com/t/recovery-twrp-v3-2-3-1-for-h870-h872-us997-unofficial.3828254/
Sadly I can't say 100% sure if it was the thread I followed back in the day.
Hi, I'm trying to root my Samsung j3 phone, and i cant figure out how to do it. it seems quite simple, but i cant get it to boot twrp. Ive copied the twrp image to the recovery partition using Hemidall and then held power+volume-up+home to boot into recovery mode but the phone just boots into the normal recovery mode. Ive never rooted a phone before so i don't know what really to do.
Dont let it boot into the system, the system overwrites the recovery. Make sure as soon as its done flashing twrp, you restart instantly into the recovery. I'd recommend turning off auto reboot.