So im running CM12.1 and im trying to flash the CWM recovery i used for installing CM and i can get into fastboot mode and flash it, but then every tutorial says then go into recovery through the UI on the screen, but my bootloader screen is just black and obviously cause im in fastboot mode i cant boot directly into recovery without rebooting the device which will reflash the stock recovery
What can i do?
Cheers
Reboot and press the volume keys up and down simultaneously to boot into recovery.
I have cm12.1 but the problem is, the recovery is showing black screen. I tried flashing from fastboot twrp image file and xzdualrecovery only to cause boot loops.
Is there any method to install recover on cm12.1 without causing bootloops?
Sent from my Nexus 7 WiFi using Tapatalk
Try this.
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Sent from my Nexus 7 WiFi using Tapatalk
Related
Alright, I give up.
I've wasted one full day and all I do is keep going in circles. I have an unlocked bootloader but I am not able to flash custom recovery to it. When I do:
fastboot flash recovery recovery-RA-passion-v2.2.1.img
it is successful but am having the problem mentioned here:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android)."
http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
So, no custom rom because I cant turn off verification in order to flash custom rom zip file. Now the problem is that I can't even fix this problem because I don't have root so I can't delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
When I try adb shell it keeps saying "permission denied"
It gets better - I've managed to mess things up royally even further. I tried flashing FRG83 system image using "flashboot update update.zip". It was successful but now my phone is going in boot loop!!
Can someone please help me before I lose hope in humanity?
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
You can either flash a pre-rooted GB, flash the su.zip and then you'll have su access to delete the files when in system or adb, or flash this zip which will remove the two files...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
danger-rat said:
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
Click to expand...
Click to collapse
I totally did not know this. Thanks a lot buddy
Hi XDA,
After flashing Android M using fastboot (just the system.img), it appears it also removes TWRP recovery. I am then able to flash TWRP via fastboot and boot into recovery from fastboot (so I can install SuperSU). However, when I try to reboot back into the system, during the boot process there is message stating "Your device is corrupt. It can't be trusted and may not work properly.". From what I read, this prompt should disappear and the boot process should continue however that is not my case. After the prompt, the screen goes black but it appears something is going on since it vibrates when I get a hangout or turn down the volume.
So my question is has anyone experience this issue and what was your resolution? I need SuperSU for my Titanium Backup and Adaway however I do want to try the preview as well.
System images contain install-recovery.sh scripts that replace recovery in boot. Actually if you boot directly into recovery and flash supersu, it modifies that script and prevents that happening.
Are you flashing a supersu compatible with M?.ensure you have the latest beta.
I have a Sony Xperia Z1 and I have had cyanogenmod12.1 on my device for a little while now, but there are a couple of bugs and I wanted to go back to cyanogenmod11, so I downloaded the cm11 zip file onto my device and copyed it to the sd card,I then downloaded TWRP manager because the cyanogenmod recvoary does not have a zip file or flash part in the recovary, so I followed the procedures and then I flashed TWRP recovary. Once I got into the TWRP recovary I found the zip file for cm11 I then clicked flash. Not long later it said succesfull and then i had to reboot, i clicked reboot and this is where it whet wrong. My device then went into a bootloop because I left my device for 10mins. I then tried to access the custom recovary but it just came up with the sony logo and no custom recovary has come up since.
Jack Neilson said:
I ave a Sony Xperia Z1 and I have had cyanogenmod12.1 on my device for a little while now, but there are a couple of bugs and I wanted to go back to cyanogenmod11, so I downloaded the cm11 zip file onto my device and copyed it to the sd card,I then downloaded TWRP manager because the cyanogenmod recvoary does not have a zip file or flash part in the recovary, so I followed the procedures and then I flashed TWRP recovary. Once I got into the TWRP recovary I found the zip file for cm11 I then clicked flash. Not long later it said succesfull and then i had to reboot, i clicked reboot and this is where it whet wrong. My device then went into a bootloop because I left my device for 10mins. I then tried to access the custom recovary but it just came up with the sony logo and no custom recovary has come up since. Please help
-Jack
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to the right Q&A so that experts there maybe able to help.
-Vatsal
If you made a backup, flash dual recovery then restore the backup?
Otherwise flash stock and start again
The only solution is to flash your firmware and start from zero point
Since you said there is bootloop and no recovery
Or you can flash twrp img file through fastboot mode
But for safety flash is best
You do not need to do a fresh flash. Doing so without deselected some things might wipe data like photos.
1. If you don't already have the fastboot and ADB drivers, get them here
2. Download a kernel with recovery and extract the boot.img
3. Open up command prompt in the folder the boot.img is in
4. Make sure your device is turned off completely
5. Hold volume down while attaching it to your computer
6a. If you just want to have temporary acces to recovery type in this code:
Code:
fastboot boot boot.img
6b. If you want to keep acces and use the recovery after rebooting type in this code:
Code:
fastboot flash boot boot.img
7. Enter recovery the way you would normally do, backup your important files and/or flash the new rom and kernel you would like to use
I have tried a number of times to install TWRP (unrooted) on my Nexus 6. I am following the instructions from here
https://twrp.me/devices/motorolanexus6.html
I am noting the warnings here
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. 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.
Once I issue the fastboot reboot command before the Nexus 6 shows anything on the display I press power and vol down and get into TWRP. It seems to what it's supposed to do (presumably patch the stock ROM) and then I reboot to Android.
But the next time I boot to recovery I end up with stock recovery again. I have tried this a number of times and while I can get TWRP installed it always reverts to stock recovery after the next restart.
Is there something else I have missed here in the instructions? They seem fairly clear.
Not that I think it matters but I am running 7.1.1 (flashed with the OTA image since I was not getting OTA updates)
Thanks
Instead of using the fastboot command to reboot to recovery after you have flashed TWRP do it manually. Been a while but I believe that should work.
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
TMG1961 said:
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
Click to expand...
Click to collapse
I have done that several times. This is the screen I see when TWRP is loading for the first time.
Not sure if those red messages are fatal or not
When I am in TWRP I can reboot to recovery and it gets back to TWRP but if I reboot to system and then try to enter TWRP on a reboot (holding power and volume up/down it boots into the Fastboot and when I choose Recovery mode I send up with stock recovery again.
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
TMG1961 said:
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
Click to expand...
Click to collapse
That is pretty much what I have been doing. The only difference is, the first time I did this (before I realised it wasn't working), I rebooted from adb and I did see the swipe to allow changes. But since then if I boot from abd or boot from the bootloader, I don't see the TWRP option to swipe to allow changes anymore.
I wonder if it's because the data is encrypted (standard on a N6?)
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
TMG1961 said:
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
Click to expand...
Click to collapse
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
lchiu7 said:
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
Click to expand...
Click to collapse
After using fastboot to flash TWRP, use the volume and power buttons​ to boot into TWRP, and allow modifications, then make a backup and reboot system. Go back to recovery and if all is well, then flash your ROM. Make sure you've got your TWRP issue fixed first though.
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Depending on what your doing, typically you have to manually boot into recovery after flashing twrp (from fastboot), don't use fastboot reboot xxxx. Use the power/volume key combo to reboot. Then accept either system modification or flash a systemless root solution. This will enable custom recovery to "stick". Otherwise, stock android will overwrite recovery on boot.
The TWRP thread has discussions about this. Starting at post 1044 should help.
mrcreativity said:
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Click to expand...
Click to collapse
Is your device encrypted before you flash TWRP?
Yes it is encrypted.
Anyway, I tried all the various methods and combinations but ended up going back to stock recovery. What worked was flashing SU after TWRP.
I'm running pure nexus now and enjoying it.
I can only seem to get into fastboot mode with a Menu saying:
Restart Bootloader
Unlock Bootloader (Unlocked)
Wipe Userdata
Exit
I haven't been able to get to any download mode at all, just this menu and stock recovery, can someone please give me instructions on this? I've gotten different files and ways to root this from many different threads and I'm confused as hell.
Never rooted this RP2 before, it's on latest OTA MR2-RC001-RZR-190914.3123. Got it unlocked before and it's been unlocked for a while but didn't go further with rooting because I got confused and didn't want to brick my expensive phone. Last phone I rooted was back on kitkat or lollipop before I switched to iPhone, so I'm not a total noob just rusty. But Razer got me back to Android and it''s changed alot. I need detailed advice please. :good: And if my instinct is telling me correctly I'd assume something is changed about the bootloader in MR2 thats affecting me right now?
That menu is the bootloader/download mode.
DarkestSpawn said:
That menu is the bootloader/download mode.
Click to expand...
Click to collapse
My issue was not having Bootloader interface installed. Fixed
MarkusGingles said:
My issue was not having Bootloader interface installed. Fixed
Click to expand...
Click to collapse
Have you unlocked critical partition?
https://developer.razer.com/razer-p...6.1692205032.1582602359-1206928491.1581902985
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
THE CABLE THAT CAME WITH THE PHONE WILL NOT WORK.
If you have everything unlocked then make sure you do this
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Or install using this tool
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
If you make it this far then it's a matter of typing in the correct path in fastboot.
fastboot flash boot "arter97 name here".img
Then from the fastboot menu scroll down to boot to recovery or type fastboot reboot recovery
TWRP should boot if you installed the correct kernel.
In TWRP hit cancel then swipe to make modifications and install magisk 20.3
Profit
JDBarlow said:
Have you unlocked critical partition?
https://developer.razer.com/razer-p...6.1692205032.1582602359-1206928491.1581902985
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
THE CABLE THAT CAME WITH THE PHONE WILL NOT WORK.
If you have everything unlocked then make sure you do this
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Or install using this tool
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
If you make it this far then it's a matter of typing in the correct path in fastboot.
fastboot flash boot "arter97 name here".img
Then from the fastboot menu scroll down to boot to recovery or type fastboot reboot recovery
TWRP should boot if you installed the correct kernel.
In TWRP hit cancel then swipe to make modifications and install magisk 20.3
Profit
Click to expand...
Click to collapse
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
MarkusGingles said:
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
Click to expand...
Click to collapse
Have you tried the format data partition ?
MarkusGingles said:
Okay so I couldn't flash anything originally simply because i didn't have Bootloader Interface installed. Figured that out and had everything working, unlocked, Arter Kernel 12, Magisk 20.3, EdXposed, and now after I edited build.prop to enable my regular hotspot without carrier permission and reboot. Well now I really can't flash sh?t. Even though I can get into bootloader & Recovery, when I try to fastboot flash MR1 Stock or MR2 stock just to get back into the phone it freezes on the razer logo and eventually reboots and repeats. Then i have to Reflash arter to get back into TWRP after I try to flash anything else which otherwrites Arter97.img. Finally read the red text in TWRP and /data was refusing to mount, fixed that by a basic ass wipe (DUH) Hoping that might have been the issue, my data folder was corrupt or my old data folder was mismatching with the rest of the new roms i tried to flash? Idk someone smarter plz tell me. So far my next attempt is going to be downloading a flashable Stock Deodoxed ZIP to see if flashing from within TWRP now that /Data will mount makes a difference compared to Fastboot. Tried fastboot flashing MR1 and MR2 Normal Razer Stock Rom after data remounted and now i can get to the green vortex/visualizer screen instead of just the Razer Logo before it STILL loops and then when it loops again a second time it sends me to TWRP automatically.
Click to expand...
Click to collapse
Will it not let you flash stock using flash_all.bat file while in fastboot mode?
I would definitely try and start over for sure if possible