Related
I was wondering if anyone could help me.
First i rooted my phone, then S-off'd with sunshine.
then i tried to update my firmware from 1.32.xx.xx to 1.40.401.8 so i could install ViperONE rom
First, i flashed a no-wipe zip 1.40.401.8 and it worked but after rebooting the phone, it would restart on each screen-off.
so i figured that there was something wrong with the versions and did a full wipe install.
now i can't install any zip. It hangs at the part where it starts the install and freezes, then goes into a boot loop.
I cant see any file system at all.
I've tried putting ADB sideload mode in, but it doesn't recognize it
Please, does anyone know what i should do?
Gordon-B said:
I was wondering if anyone could help me.
First i rooted my phone, then S-off'd with sunshine.
then i tried to update my firmware from 1.32.xx.xx to 1.40.401.8 so i could install ViperONE rom
First, i flashed a no-wipe zip 1.40.401.8 and it worked but after rebooting the phone, it would restart on each screen-off.
so i figured that there was something wrong with the versions and did a full wipe install.
now i can't install any zip. It hangs at the part where it starts the install and freezes, then goes into a boot loop.
I cant see any file system at all.
I've tried putting ADB sideload mode in, but it doesn't recognize it
Please, does anyone know what i should do?
Click to expand...
Click to collapse
The problem with Viper makes it sound like you installed the 1.40 base rom on the 1.32 firmware, so are you sure the 1.40 firmware flashed? You can check this in download mode.
So Aroma is crashing during install? Are you able to save the installation log? Which version of TWRP are you using?
I hope that 1.40 installed... it says so in download mode.
im using TWRP 2.8.6.4
the reason i decided to start over with a full-wipe zip is because of the problem with the constant rebooting.
should i try to do a RUU like shown here?
http://forum.xda-developers.com/one-m9/general/hima-stock-rom-collection-htc-one-m9-t3095746
Gordon-B said:
I hope that 1.40 installed... it says so in download mode.
im using TWRP 2.8.6.4
the reason i decided to start over with a full-wipe zip is because of the problem with the constant rebooting.
should i try to do a RUU like shown here?
http://forum.xda-developers.com/one-m9/general/hima-stock-rom-collection-htc-one-m9-t3095746
Click to expand...
Click to collapse
TWRP 2.8.6.4 is a beta version. You should use the official version 2.8.6.1 (here: http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720)
what ROM(s) are you trying to install? And what errors are you getting in Aroma installer? If download mode says 1.40, then that's probably accurate.
i've tried ViperROM and android revolution.
Neither work. Both crash as soon as it gets started after configuration... I don't see any "error codes" or anything, just reboots and starts a boot loop.
i can try again with 2.8.4.1. but at this point, i just want to have my phone working again.
Gordon-B said:
now i can't install any zip. It hangs at the part where it starts the install and freezes
Click to expand...
Click to collapse
I'm trying to understand what you mean here. That's why I'm asking about Aroma logs.
Gordon-B said:
i've tried ViperROM and android revolution.
Neither work. Both crash as soon as it gets started after configuration... I don't see any "error codes" or anything, just reboots and starts a boot loop.
i can try again with 2.8.4.1. but at this point, i just want to have my phone working again.
Click to expand...
Click to collapse
So...you begin the ROM install in TWRP, the Aroma installer starts, you go through your options, press install, and what? Do you see wiping data? system? Does it show progress percentage? Or right after you press install in aroma, aroma FCs, and the phone reboots?
essentiallly yes.
In aroma, i go thru the options about installing the ROM.
then it asks if i want to wipe before install, then install starts.
in Android Revolution, it gets to 30% right away, then crashes.
in ViperONE it gets to 1%, hangs, then crashes.
i'm sorry i dont have a log to show.
Gordon-B said:
essentiallly yes.
In aroma, i go thru the options about installing the ROM.
then it asks if i want to wipe before install, then install starts.
in Android Revolution, it gets to 30% right away, then crashes.
in ViperONE it gets to 1%, hangs, then crashes.
i'm sorry i dont have a log to show.
Click to expand...
Click to collapse
Install the latest version of TWRP (2.8.6.1) and boot into recovery.
Go into Mount
If "Only mount system read-only" (at the very bottom) is selected, deselect it. If it's not selected, select it, and then immediately de-select it.
Try to install again.
did it. exactly the same result.
if i look at the terminal results, it says E: Unable to mount '/cache'
Gordon-B said:
did it. exactly the same result.
if i look at the terminal results, it says E: Unable to mount '/cache'
Click to expand...
Click to collapse
Are you able to mount cache in the TWRP mount menu?
Are you positive you have good ROM downloads? Are you able to unzip them on a computer?
I'm running out of ideas. You might want to post in this TWRP thread. http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
Who is your carrier? If there's an RUU for your specific carrier, you could try running it. You know it will wipe your SD card, though, right?
I ended up installing the RUU from the link I posted. It worked like a charm.
"You are aware it will wipe your SD"
DUDE! I literally had a blank phone. It showed 32gb free space. There was NOTHING on it.
The RUU worked though.
I kinda want to try again, because I have no idea what went wrong or why... At least I know how to fix it now.
Thanks for the help.
Sent from my HTC One M9 using XDA Free mobile app
Gordon-B said:
I was wondering if anyone could help me.
First i rooted my phone, then S-off'd with sunshine.
then i tried to update my firmware from 1.32.xx.xx to 1.40.401.8 so i could install ViperONE rom
First, i flashed a no-wipe zip 1.40.401.8 and it worked but after rebooting the phone, it would restart on each screen-off.
so i figured that there was something wrong with the versions and did a full wipe install.
now i can't install any zip. It hangs at the part where it starts the install and freezes, then goes into a boot loop.
I cant see any file system at all.
I've tried putting ADB sideload mode in, but it doesn't recognize it
Please, does anyone know what i should do?
Click to expand...
Click to collapse
for flashing the no-wipe I had no problems but I did go into the 3 android-info.txt files and change the cid and mid to match my device. also had to flash it twice as the first flash always fails. Recently I learned about changing the cid to supercid and I think that solves having to go into the files. If your phone is still not working you can always go to the link below and download the RUU for your device and then run the .exe file from your pc and return to stock (I'd look for the specific instructions for that because I did leave some steps out).
EDIT--just looked at full wipe file and it's not an RUU must have been another thread I was thinking of.
http://www.htc.com/us/support/rom-downloads.html
Gordon-B said:
I ended up installing the RUU from the link I posted. It worked like a charm.
"You are aware it will wipe your SD"
DUDE! I literally had a blank phone. It showed 32gb free space. There was NOTHING on it.
The RUU worked though.
I kinda want to try again, because I have no idea what went wrong or why... At least I know how to fix it now.
Thanks for the help.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, well now that you know the RUU works to restore I think you'd be safe to try again.
Just install the latest TWRP (2.8.6.1) and flash the NO WIPE 1.40.401.8 firmware. The wipe version contains the stock recovery and you don't want that.
Or, if you want to use Viper, there's an option in Aroma to install it with the 1.32 kernel so you could just skip the firmware update.
bigp951 said:
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
Where are people getting the 1.40 RUUs? All that I see on the HTC website are 1.32 versions. Even the Unlocked/Developer rom is 1.32.617.30
Do I need to look on the international site?
Sent from my HTC One M9 using XDA Free mobile app
tyr this---
http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571
Sent from my HTC One M9 using XDA Free mobile app
Gordon-B said:
Where are people getting the 1.40 RUUs? All that I see on the HTC website are 1.32 versions. Even the Unlocked/Developer rom is 1.32.617.30
Do I need to look on the international site?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Go ahead to the M9 general forum, there you will find what you need.
Sent from my HTC One M9 using XDA Free mobile app
I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Jerry060599 said:
I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Click to expand...
Click to collapse
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
LLegion said:
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
Click to expand...
Click to collapse
tks for the help . will be trying it out.
Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance
LLegion said:
Of u still have issues i can give whatsapp and help you with further assistance
Click to expand...
Click to collapse
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance
Jerry060599 said:
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Click to expand...
Click to collapse
Look at post 3 in this thread. Best is you read all information in the first three posts.
Here u havebaccess to my personal folderhttps://drive.google.com/folderview?id=0B--58xBx8PTOfmYyeDdXeFJ1ZnRSdGJTVnVhQTJQZUZiMG5uRWl0blNackNWMVU1NUNoVjg&usp=sharing
Flippy498 said:
Look at post 3 in this thread. Best is you read all information in the first three posts.
Click to expand...
Click to collapse
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Jerry060599 said:
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Click to expand...
Click to collapse
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
dragonesdenano said:
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
Click to expand...
Click to collapse
Sorry for the (extremly) late reply. I had not been home for the past week. I tried restoring to stock system image and flashin su binaries before. It didnt work. At this point, I suspect that the only reason why I can't flash supersu is because of my firmware version. So I'll be wimpering in a corner untill some kind devs at htc decide to release the source for my version.
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
cloves said:
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
Click to expand...
Click to collapse
Restore your boot partition or dirty flash rom
Fixed
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
cloves said:
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
Click to expand...
Click to collapse
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
willardwellls said:
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
Click to expand...
Click to collapse
Flashed via twrp 3.0.0-2
This is the file:
https://download.chainfire.eu/752/SuperSU
FYI, if you are flashing a ROM, sometimes they have superSU already built in. So no need to flash your own superSU. That is the case with Viper ROM. Also make sure your firmware matches the firmware that the rom is using.
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Just had the same problem. Put on 2.65 and it's now booting into the OS. Thanks!
Thanked God i found this post, tried latest stable also beta seems bootloop never ends. Try v2.6 all become alive. Many thanks Sir
Same problem after installing latest SuperSu version from TWRP recovery: eternal bootloop. I didn't know what was wrong and tried different supersu versions but I became reluctant to keep trying that method after the second time... Gladly, I found your thread before doing anything else (even posting myself a thread) and now I can continue my evil rooting plans :victory: Thank you for asking and thanks for replying you prevented me to re-lock my phone and do everything from scratch. It's my first root
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
cloves said:
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I beg to differ about xposed. One wrong mod and you're phone is bricked.
Beamed in by telepathy.
I have not had any problems with exposed and that's why I said make a backup on your card. I have installed multiple Xposed modules and have not had any issues I have not seen anybody break the phone either. As I mentioned make a trip back up what is the point of rooting your phone if you're not going to use it to its full potential that's just me
Sent from my HTC One M9 using Tapatalk
Me too - Bootloop
I have an AT&T HTC One M9. Bootloader is HtcDev Unlocked, S-On, and TWRP is installed...
I previously messed up my phone bad by trying to install a OS ROM that didn't work right... So, I used my PC to overwrite it with the HTC OTA version, and that worked. I went into the M9 and tried to download and run SunShine, to get S-OFF, but it said it couldn't temproot, I don't know why, it's pissing me off, and SunShine suggested I root the device with another means. I downloaded SuperSU 2.69 and tried that, it installed okay (I guess) and said it might loop a few times. Try 100! Infinite loop. I tried SuperSU 2.65, but it said, "it's already patched!" and the system ROM had not been backed up. (I'm assuming SuperSU patches whatever is in the system partition?)
Anyhow, it's currently stuck in an infinite loop. I'm going to try re-putting the HTC OTA system ROM on it (great, I lose another half-day at this), and then re-try SuperSU 1.65.
Any idea why SunShine won't S-OFF a device? Why won't temproot work? Any other (good) way to root it?
Twrp question?
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
thanks dude
Skorpyun812 said:
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Click to expand...
Click to collapse
i am stuck and say my phone going to crab but your post save me
cheers
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
White91 said:
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
Click to expand...
Click to collapse
i think your s-on on bootloader mape it off then install recovery
I've been running cm13 nightlies on my OP3. I haven't updated in a couple weeks and last night i got a notification that there was some new updates. Since it's been a while i decided to do the update so i let the cmupdater do it's thing and went to bed. This morning i wake up and was greeted with a very cranky phone. I noticed i was having trouble with any google related app, and also popups of google apps crashing. So i go to settings and I see that my phone has been updated to CM14!
well that would explain the Google apps pproblem. I was going to flash gapps for 7.0 but i couldn't get into recovery. I had twrp installed but now i couldn't get into it. the phone reboots, shows the oneplus logo then shuts off. Then i decide to reflash twrp. i put the phone into fastboot mode and from my pc command prompt, tried the fastboot flash recovery. img. it says it was successful but i still can not boot into recovery. I made sure debugging was on and I also accepted my pc key when asked on the phone before booting into fastboot mode. I realise this is a dirty flash but is there anyway of recovering from this ? i usually flash the nightlies myself from the recovery,i don't know why last night i used the cmupdater.
You probably got it going by now but in case. Which version of twrp are you trying? I would try the latest twrp-3.0.2-23-oneplus3.img. Make sure OEM unlock is checked in device manager, root is allowed as well, try an app like flashify or something that can flash an image from within the OS and see if you have better luck.
Ducter said:
You probably got it going by now but in case. Which version of twrp are you trying? I would try the latest twrp-3.0.2-23-oneplus3.img. Make sure OEM unlock is checked in device manager, root is allowed as well, try an app like flashify or something that can flash an image from within the OS and see if you have better luck.
Click to expand...
Click to collapse
Thank you for your help. I couldn't try the flashify route as it would not install. Something about parsing the package failed. I did manage to fix it by downloading the latest twrp you suggested and flashing that. After that I was able to boot into recovery and flash pico gapps 7.1. Unfortunately that wiped out all of my apps but at least i didn't lose any of my files. Thanks again.
pdrift said:
Thank you for your help. I couldn't try the flashify route as it would not install. Something about parsing the package failed. I did manage to fix it by downloading the latest twrp you suggested and flashing that. After that I was able to boot into recovery and flash pico gapps 7.1. Unfortunately that wiped out all of my apps but at least i didn't lose any of my files. Thanks again.
Click to expand...
Click to collapse
Glad you got it going, I see now that I mentioned device manager... No clue where that came from lol, was suppose to be developer options. Regardless, you got it and that was the goal.
Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?