So I decided to root, and got through unlocking the boot loader and getting TWRP installed, but once I installed SU, I get stuck at the big M screen before the animation stiches. I can power off and boot into recovery mode, and have tried wiping all that I could and reloading SU, but I still can't get past the Motorola logo.
Any help would be greatly appreciated!
FYI, the version of SU I installed is "UPDATE-SuperSU-v2.76-20160630161323.zip"
*UPDATE*
found this in another post:
- In TWRP, go to Advanced - Terminal
- Enter "echo SYSTEMLESS=true>>/data/.supersu"
Once I did that, I was able to reinstall SU and got everything working.
nolatech said:
So I decided to root, and got through unlocking the boot loader and getting TWRP installed, but once I installed SU, I get stuck at the big M screen before the animation stiches. I can power off and boot into recovery mode, and have tried wiping all that I could and reloading SU, but I still can't get past the Motorola logo.
Any help would be greatly appreciated!
FYI, the version of SU I installed is "UPDATE-SuperSU-v2.76-20160630161323.zip"
Click to expand...
Click to collapse
If you made a TWRP backup before you flashed supersu restore it, that will get you booting again. If you don't have one, then your best bet is probably to get a backup from one of the firmware threads.
Before you flash supersu you have to force it to install systemless. Enter this in an adb shell or TWRPs built-in terminal:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
That will force if to flash systemless. Another option is to start from supersu 2.62. That one always flashed systemless.
jason2678 said:
If you made a TWRP backup before you flashed supersu restore it, that will get you booting again. If you don't have one, then your best bet is probably to get a backup from one of the firmware threads.
Before you flash supersu you have to force it to install systemless. Enter this in an adb shell or TWRPs built-in terminal:
Code:
echo "SYSTEMLESS"=true > /data/.supersu
That will force if to flash systemless. Another option is to start from supersu 2.62. That one always flashed systemless.
Click to expand...
Click to collapse
I didn't make a backup prior, but I also didn't force the install to be systemless. Once I did that and reinstalled supersu, everything started working again.
Thanks!
nolatech said:
I didn't make a backup prior, but I also didn't force the install to be systemless. Once I did that and reinstalled supersu, everything started working again.
Thanks!
Click to expand...
Click to collapse
Good to know. SuperSU must have cleaned up after the first attempt once you flashed it systemless. Nice feature.
Related
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
common issue at this point. It appears recovery isnt sticking for some reason.
kokotron said:
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
Click to expand...
Click to collapse
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Click to expand...
Click to collapse
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
kokotron said:
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
A solution for auto swpan defualt recovery, the file is there only rename it
DJBhardwaj said:
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
Click to expand...
Click to collapse
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
Just Install a Custom Kernel with modified ramdisk. Install Hellscore kernel and then install SuperSU. You will be able to experience Root.
I think unleashed kernel has also been updated with the same, but I can only confirm it with Hellscore.
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
kokotron said:
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
Click to expand...
Click to collapse
It is weird. I am pretty much sure you're either missing something or using a corrupted img file. Confirm that the file has been downloaded completely by verifying the md5 checksum and I am sure it will mismatch
hp420 said:
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
Click to expand...
Click to collapse
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
kokotron said:
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
Click to expand...
Click to collapse
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
Ok thank you, this seems to have worked. When I booted back into Android though root didn't work any more. I re-rooted using your link (which was what I used the first time as well), and I guess I'll know how it goes the next time I reboot the phone.
hp420 said:
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
Click to expand...
Click to collapse
Not the boot loader because I have the new bootloader that came with L and TWRP working perfectly, so both can coexist.
The problem comes from within the rom as I said, the file is in /system/etc/install-recovery.sh is responsible to clear the custom recovery and return to default android recovery. The solution is to remove (or rename) that file, what I saw is that the TWRP and SuperSU (both try to) can not rename it, and the solution was to rename it manually from the file manager included in the TWRP (mounting /system as explained before).
The same problem to can not overwrite files (should be modified in any command in library ) prevents install from a flashable zip SuperSU, so the solution http://forum.xda-developers.com/nexu...- root-t2025274 initiating its own operating system booting own image solves the problem that can not be overwritten (or modified) files from the TWRP (at least until a specified version for L see the light).
Probably whoever the new bootloader prevents TWRP modify files in /system, but bootloader not erases the custom recovery. Surely people of TWRP is working to fix this issue (or sleeping sometimes you have to sleep) but the problem can be solved by keeping the new booloader.
Conclucion, I have stock L Last bootloader, root and TWRP everything working perfectly and hellsCore Kernel
sidVici0us said:
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
you installed via the SuperSU binaries from flashable zip in TWRP or use the method http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274 ?
With the CF-auto-root you should have no problems, I did so and I read that many people do so, use this method to root.
On the other hand, I was thinking that having a recovery that can not flash zip is not something useful
---------- Post added at 03:16 PM ---------- Previous post was at 02:52 PM ----------
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
You can not use the superSU flasheable zip, the recovery is not working to modify /system partition, use the other method.
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
CF autoroot works perfectly!! http://www.xda-developers.com/android/chainfire-releases-cf-auto-roots-for-nexus-line/
Okay so I am on a LG G2 LS980 and I finally found a way too install a CM13 ROM which took me hours of bricking my phone and rebuilding using .ToT files, but I installed TWRP and completely wiped the phone (except for the the data part so my zips weren't deleted) then after wiping I flashed an exotic bootstack.zip and rebooted back into recovery, then I wiped everything again except for the data which contained my other zips, after that I flashed my CM13 ROM and Gapps for android 6.0.1 and then I rebooted and finally success, so everything was perfect and working so I flashed the latest closed firmware (after I created a nandroid backup of course) and still I rebooted with success and everything still worked, then I tried to flash SuperSu 2.57.zip and then I bricked my phone once again so I restored using my backup (thank god) and I do know in the developer setting I can enable Super User permissions to APPS/ABD (don't know what ABD does but I chose them both, I opened a terminal emulator and typed SU and it asked to grant permission and all that so it does work, but I don't know how reliable the developer setting SU that's packaged into my ROM is and I'm wondering if their is anyway I could change from using the devolper setting SU to the SuperSu app with SuperSu 2.57.zip? Is the developer settings SU as reliable as SuperSu or is SuperSu better? Those are my two questions, please help, thanks!
Paentherax said:
Okay so I am on a LG G2 LS980 and I finally found a way too install a CM13 ROM which took me hours of bricking my phone and rebuilding using .ToT files, but I installed TWRP and completely wiped the phone (except for the the data part so my zips weren't deleted) then after wiping I flashed an exotic bootstack.zip and rebooted back into recovery, then I wiped everything again except for the data which contained my other zips, after that I flashed my CM13 ROM and Gapps for android 6.0.1 and then I rebooted and finally success, so everything was perfect and working so I flashed the latest closed firmware (after I created a nandroid backup of course) and still I rebooted with success and everything still worked, then I tried to flash SuperSu 2.57.zip and then I bricked my phone once again so I restored using my backup (thank god) and I do know in the developer setting I can enable Super User permissions to APPS/ABD (don't know what ABD does but I chose them both, I opened a terminal emulator and typed SU and it asked to grant permission and all that so it does work, but I don't know how reliable the developer setting SU that's packaged into my ROM is and I'm wondering if their is anyway I could change from using the devolper setting SU to the SuperSu app with SuperSu 2.57.zip? Is the developer settings SU as reliable as SuperSu or is SuperSu better? Those are my two questions, please help, thanks!
Click to expand...
Click to collapse
Well, for Android 6.x.x, always flash the latest SuperSU (Latest BETA) as the boot image is now patched to obtains root access, not the /system.
Concerning builtin su (I think it's Superuser in CM), it does the same as SuperSU, so flashing it isn't mandatory.
Hi. So, I had TWRP on stock rom and my phone was rooted. was messing around trying to install viper4android and i think i clicked wipe data, etc in recovery mode. Phone rebooted and im un-rooted now with SuperSU installed but it says "there is no binary SU installed and superSU cannot install it. This is a problem! "
What do I do now? I can still boot into recovery.
If I have to flash to a stock firmware, is that easy to do? Thanks in advance
AdrMXP said:
Hi. So, I had TWRP on stock rom and my phone was rooted. was messing around trying to install viper4android and i think i clicked wipe data, etc in recovery mode. Phone rebooted and im un-rooted now with SuperSU installed but it says "there is no binary SU installed and superSU cannot install it. This is a problem! "
What do I do now? I can still boot into recovery.
If I have to flash to a stock firmware, is that easy to do? Thanks in advance
Click to expand...
Click to collapse
1. Flash Rom You Want To use in your Device .
2.Download Supersu Binary Zip File from Here http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash it through TWRP recovery
4.Now reboot your cell phone and install SuperSU.
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Shakedbuk said:
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Click to expand...
Click to collapse
Update your twrp, there's no need to use that old version... my phone reboots when it wants when it has opd twrp versions
Download twrp 3.1.1-0
Put it on your phone, maybe via adb or through mtp if you have it
Go to Install -> hit the button on the right that says 'Install image'
Find the TWRP.img and install it, it will prompt you where to install it, put 'recovery'
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Shakedbuk said:
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Click to expand...
Click to collapse
Don't use axon7tool for this... you already have TWRP, the only thing you have to use axon7tool for is to install twrp when you have the stock recovery. after you have twrp on the phone just try not to use the PC except for maybe miflash
I tried both of this options.
Flashing new version of twrp through the old twrp resulted in black screen when i try to get to recovery.
So I flashed the old twrp from the pc, tried to flash the new one using the same method but it the same as i flashed it through the old twrp. (which mean that when i get to the recovery i get black screen)
ATM the situation is the same, system wont boot stuck on zte logo, twrp is 3.0.2.2 (there is another method to flash newer twrp?)
There is another option?
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Shakedbuk said:
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Click to expand...
Click to collapse
Wait, what did you do? Did you install everything again after wiping system?
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Shakedbuk said:
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Click to expand...
Click to collapse
You installed SuperSU without a system, and the phone did not boot up? Amirite?
what i did was wipe system dalvik cache, cache, after that install bootstack and the system files, and after that the supersu.
before i wiped the system, when i tried to install the supersu the twrp collapsed, after that it installed it but did not helped to make the system boot.
UPDATE - Did not manage to find a way to get TWRP installed permanently but did manage to install Lineage OS 16 (which was my end goal) via hotboot of their recovery IMG, so happy with that at least! Appreciate any help given!
Not sure what I am doing wrong. have never come across this before!
I just completely reset my phone to stock via MiFlash
I then boot into TWRP recovery from Fastboot
I then install the TWRP installer in TWRP
I then reboot to recovery but get 'The System has been Destroyed'
I can still boot into the stock ROM
I can still boot into Fastboot
I just can't seem to get TWRP to install, I can only access it in hotboot
Any help would be amazing!
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Oh well damn, I will give that a shot thank you!
Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Never install twrp on stock pie. You'll get the same message. Hotboot it only.
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
From what I have tried it seems that it is a bug with stock pie, custom roms with pie and stock oreo don't have this problem.
Anyway, you can basically get the same functionality by hotbooting but it's less convenient.
I have TWRP installed and resurrection remix. Maybe their TWRP works for you, just check the instructions and give it a try.
I think you should install TWRP in both slot A and B for it to work.
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Weird, it used to work for me when I was on stock pie.
I'm on a custom rom right now so I cannot test if it still works.
Sorry
I also have the same problem but now I'm on a custom rom and the TWRP without magisk works, but I would like to try an sGSI, on a custom rom does the procedure work?
Try another twrp
I'm here also had the same problem on mi A2 lite
But Rom run smooth and stable for a long time that I even forgot I have no twrp. Instead I backed up with titanium bk just in case. So ,Hotbooted with adb.... less convinient but u get to where u wanna flash though