hey,
I wanted to root my nexus 5x too, first I tried to do so with the nexus tool kit....
it was all working until it came to the root process:
it said in the log:
Rooting....
Waiting for your device....
and nothing else happened anymore.
So I tried it manually with a guide.
As the bootloader was already unlocked, I continued with flashing the recovery (twrp 2.8.7.2) in fastboot.
Then it rebooted into the recovery.
Then twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I allowed the system modification then... so then before rebooting, twrp wasn't asking me if I want to flash the SuperSu.
Since this I'm stuck in a bootloop.
I can boot into the bootloader and recovery, I also tried to do a factory wipe or also formating data. But none of them worked for me. I'm still stuck in the bootloop...
I have no idea what to do now....
I'm really thankfull for every kind of help!
sorry wrong subforum...
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Vulkaistos said:
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Click to expand...
Click to collapse
I have to add something which i forgot to mention.....after I flashed the recovery and booted into it for the first time, twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I'm not able boot my phone up anymore.... I can try to flash the recovery with fastboot again...if this is what you mean?
okay i pushed the supersu zip onto the phone, and just flashed it. And my phone is booting normally now
thank you very very much. you saved me and my phone
That's nice to hear.
Have Fun with your Phone!!!!!!!!!!!!!!
Related
so after i unlocked my bootloader, installed twrp 2.8.7.2, rebooted boot loader and went into recovery, i was greeted by twrp but it asked me for a decryption password (which i never set up) and Heisnberg said I wouldn't have worry about here under section 3 of how to decrypt the data partition "This is no longer necessary as long as you use TWRP 2.8.7.1 or newer". So I tried making a nandroid backup as normal, but that failed because twrp couldn't get to the data partition, unlike what Heisnberg said. So i just restarted the phone, and now I'm in a boot loop (about to flash factory image now).
So what I want to know is what twrp ppl use, do you have to do the decrypt data partition step, and the practical differences between systemless and nonsystemless root? why would anyone want to do systemless root if it doesn't work with all root apps?
Thank you so much for anyone who replies :angel:
I got an unlocked HTC one M9, (sim unlocked not bootloader unlocked), I unlocked my bootloader to prevent it from wiping my data later, installed TWRP, and installed superSU from TWRP and now my phone refuses to boot. I get the HTC logo, then it vibrates and dumps me back at the boot loader with...
reboot reason: 0x776655aa
message: RPM:APPS NS-WD!
I have absolutely no idea what is going on, I can't find reboot reasons anywhere and I'm stuck. Before doing the twrp and supersu install the phone booted to android just fine.
I used TWRP 2.8.7.2 and superSU 2.71
I have attempted to reflash the stock backup I took as soon as i got the device and it always causes the exact same error, I don't know what to do but I can't replace the phone.
Please any help is appreciated.
Destari said:
I got an unlocked HTC one M9, (sim unlocked not bootloader unlocked), I unlocked my bootloader to prevent it from wiping my data later, installed TWRP, and installed superSU from TWRP and now my phone refuses to boot. I get the HTC logo, then it vibrates and dumps me back at the boot loader with...
reboot reason: 0x776655aa
message: RPM:APPS NS-WD!
I have absolutely no idea what is going on, I can't find reboot reasons anywhere and I'm stuck. Before doing the twrp and supersu install the phone booted to android just fine.
I used TWRP 2.8.7.2 and superSU 2.71
I have attempted to reflash the stock backup I took as soon as i got the device and it always causes the exact same error, I don't know what to do but I can't replace the phone.
Please any help is appreciated.
Click to expand...
Click to collapse
Ok, so I got the device to boot again by flashing only the boot partition and then wiping the cache before restart. But it returned to the exact same state when I tried to flash superSU again.
Am I using the wrong version of superSU? or should I not install it through TWRP?
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
sukhwant717 said:
try TWRP 3.0.2.. after that boot normally. then factory reset. boot again. go back to recovery flash su clear cache and dalvik cache.. boot. phone mat bootloop at logo few times don't interrupt it let it boot itself.
Click to expand...
Click to collapse
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
dantekb43 said:
Apparently.... my phone refuses to install TWRP 3.0.2......
I'm doing all the steps that I'm used to.... Enable Debugging on dev. options.... adb reboot fastboot.... fastboot flash recovery "TWRP 3.0.2" and it's sucessful....
However... when i try to boot into recovery, the phone goes back to fastboot (although, i can boot it to system normally).
I tried flashing 3.1.1 back again and it worked, it went back to 3.1.1 .... so I'm back at square one.
Click to expand...
Click to collapse
which version of super su you are flashing?
dantekb43 said:
Hi everyone,
I found similar threads here on the forums, but none of them solved my problem!
My Zenfone 2 (Z00A/ZEE551ML) keeps bootlooping into TWRP, the cause of this issue is when i try to flash the SuperSU v2.8 zip!
My TWRP is 3.1.1, when i flash either Lineage 14 or AOSP/XOSP it boots normally into the OS, but the moment when I install SuperSU the bootloop happens (and yes, I've tried to flash it before and after the first boot of the OS, and it didn't work for either one of these methods)! The problem is that I want to use AOSP and I need Root access, and it doesn't come Rooted out of the box, unlike Lineage. Does anyone have any ideas how to solve this?
Thanks in advance!
Click to expand...
Click to collapse
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Vorstedt said:
Check the following topic and download VerifiedBootSigner-v8.zip
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Flash SuperSU and don't reboot yet.
Flash VerifiedBootSigner-v8.zip and then reboot.
Let me now if it worked. I had the same problem after installing Magisk. Resigning the bootimage fixed the problem for me.
Click to expand...
Click to collapse
I've had the same problem and your solution fixed it!
Thank you very much, sir! :good:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.
Mate SE, installed TWRP 3.2.1-0 Pretorian80 Edition then installed openKirin lineageOS beta 4. Went to do a factory reset and now TWRP starts on startup but does not get past the loading page. Tried rebooting into bootloader, using the button combo or adb reboot bootloader only brings TWRP back up with the same issue. Any ideas?
From what I understand, you need to flash lineage via fastboot. Did you do that??
coolchris305 said:
From what I understand, you need to flash lineage via fastboot. Did you do that??
Click to expand...
Click to collapse
Yeah I launched the bootloader and used fastboot to flash it. The flash went through fine, then it rebooted and asked if I wanted to factory reset the device and I selected yes. Now it won't shut off, it only reboots into TWRP's loading page and sits there.
I should mention I have access to some ADB commands now but rebooting into bootloader won't work.
EDIT: got it working, just had to time rebooting it and plugging it in and holding vol- and power correctly, took me 30 or so tries, fml
JakeBuck said:
Yeah I launched the bootloader and used fastboot to flash it. The flash went through fine, then it rebooted and asked if I wanted to factory reset the device and I selected yes. Now it won't shut off, it only reboots into TWRP's loading page and sits there.
I should mention I have access to some ADB commands now but rebooting into bootloader won't work.
EDIT: got it working, just had to time rebooting it and plugging it in and holding vol- and power correctly, took me 30 or so tries, fml
Click to expand...
Click to collapse
Directly from OpenKirin's install guide:
"TWRP and other custom recoveries are not supported! Please ensure you have your device’s stock recovery installed. If you install the ROM with a custom recovery, we cannot assist you with any issues which may arise."
olswede said:
Directly from OpenKirin's install guide:
"TWRP and other custom recoveries are not supported! Please ensure you have your device’s stock recovery installed. If you install the ROM with a custom recovery, we cannot assist you with any issues which may arise."
Click to expand...
Click to collapse
Yeah....I skipped over the sentence saying "please ensure you have your device's stock recovery installed" and thought installing it via fastboot without using TWRP it would be fine. It was not. IMO they should make the warning more dire.
All fixed and working now, thanks for your input.
How did you get it fixed?