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.
Related
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
Tried flashfire to flash a zip rather than messing around in recovery (dnscrypt), now can no longer boot into twrp and get bootloops unless I disable xposed.
Volume down button activates the pink led as it should, momentarily, but phone then continues on into system boot sequence after entering password. No twrp logo/screen.
No files from the zip appear to have been flashed by flashfire.
Boot and keys still locked and untouched.
Reflashing twrp recovery via twrp manager or twrp app makes no difference and appears recovery is still there.
I have no access to a computer but still have root, titanium backup, couple of root file managers and terminal app etc.
Has flashfire messed with system boot scripts or something? How do I diagnose/fix?
Edit: guessing id need flashtool and computer again to roll back kernel with root and recovery (LB) on the chance that would work, S'pose I'm stuffed then, unless there's a way to live flash or find out what changed.
Edit#2: FIXED. at a friends and redid the process. Kernel.575 -> install recovery,flash root and xposed zips -> Kernel.291. Nothing lost. DO NOT use flashfire if on this recovery method, don't even be tempted. The zip I tried to flash earlier works so it was definately flashfire.
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.
Hi I'm a new Android user and don't know much about it :'( I recently got my OnePlus 3T and I wanted to root it
so I followed a tutorial video from YouTube successfully unlocked bootloader and flashed twrp recovery then I tried to install SuperSU... well it installed but the device got soft bricked when I rebooted after finishing the installation and wiping cache/dalvik
then I format/factory reset everything using twrp recovery and it's working now but the device isn't rooted :'( tried to install SuperSU again and it got bricked again
Also I'm getting these messages on the startup screen-
1st one: Your device has been unlocked and can't be trusted. If you don't want to see this screen please lock your device by "fastboot oem lock" and erase user data.
2nd one: The dm-verity is not started in enforcing mode and may not work properly.
(My os version is 4.1.7)
device OP 3t A3010
plz help me :'(
The 1st and the 2nd msg that gets displayed is shown because the bootloader is unlocked..
Bootloops are common while flashing su...when I flashed super su for the first time, I got 3 or 4 random reboots and took almost 7 to 10 mins for the phone to boot up..
I would suggest using Magisk as a rooting method instead of SuperSU. If you use SuperSU then some apps can detect root and object to you being rooted and Google's SafetyNet gets triggered. Magisk solves this by trying to hide root from apps and Google so that you can use your device as if it wasnt rooted at all (but in fact is rooted). Go the the Magisk forum and download Magisk 13.3 zip from there.
I am assuming you are using OxygenOS (Oneplus's software) and not a custom ROM. Download the Open Beta or Stable build from here/
These steps will erase all the data on your phone permanently (including internal storage) so please backup anything in there.
To fix the DM verity error youll have to follow the steps outlined here
Once you have fixed that, flash oneplus recovery via fastboot which you can download here
To flash it go to fastboot mode, and cd into the folder where you downloaded it. Run the command 'fastboot flash recovery <RECOVERY_NAME>'.
Then run the command 'fastboot oem lock' to lock the bootloader. After you confirm the prompt on screen, the phone will boot into the recovery and youll see a progress bar. Once the progress completes and the screen turns off, be ready to immediately go back to fastboot mode by pressing volume up and power.
When you enter fastboot mode again, run the command 'fastboot oem unlock' and follow the same steps as before.
Once you are in fastboot mode, the phone is now in a clean state with no OS.
Follow the steps outlined on the oneplus website to flash a clean OxygenOS build (stable or open beta as per your taste)
Once the flashing is complete you have to let the phone boot up completely once. When you get to the setup screen, go through it and reach the launcher.
Now we flash TWRP recovery. Reboot to fastboot again. Flash TWRP recovery (I personally use blu_spark's twrp but you can use one of your choice). When it is done, boot into the recovery. Youll now be able to copy magisk zip into the internal sd. Do that, and flash it. Reboot.
Youll now be rooted. If you have any problems holla at me.
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