how do I root 3.28.1540.6 - One (M8) Q&A, Help & Troubleshooting

I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.

samanbabah said:
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
Click to expand...
Click to collapse
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.

samanbabah said:
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
Click to expand...
Click to collapse
Try "adb reboot fastboot", and understand what you're doing before you mod your phone. I've seen you with issues lately that you wouldn't have if you read all of the instructions for what you are trying to do and followed then exactly. You are going to end up with a brick of you don't.

jshamlet said:
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
Click to expand...
Click to collapse
yeah I just don't want to write over the stock recovery so I can get OTA updates in the future. I guess I'll wait for devs to update their recoveries.

samanbabah said:
yeah I just don't want to write over the stock recovery so I can get OTA updates in the future. I guess I'll wait for devs to update their recoveries.
Click to expand...
Click to collapse
Yeah, I failed to realize there was a way to get around that, and blew my stock recovery away.
That said, I think that you could use Sunshine, assuming it's temp-root feature still works, and abort before running the compatibility test. Then, use a local terminal to backup the stock recovery. There is a dd command to pull the recovery block to a file around here somewhere. Unfortunately, I didn't think of that in time to back mine up.
I have posted a request for the new Developer Edition recovery in another thread, though, so hopefully someone can extract it and post it.

jshamlet said:
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
Click to expand...
Click to collapse
This has to be Dev Ed specific, because I have no problems, and I really haven't heard of many others having problems either.
Plus, "recoveries are having problems booting from fastboot *right now*"? It isn't like an online service where the website is down.
Flash a backup and fix your sh*t.

xunholyx said:
This has to be Dev Ed specific, because I have no problems, and I really haven't heard of many others having problems either.
Plus, "recoveries are having problems booting from fastboot *right now*"? It isn't like an online service where the website is down.
Flash a backup and fix your sh*t.
Click to expand...
Click to collapse
Dude, seriously, there are many brands of decaf on the market that are just as tasty as the real thing.
The issue with recoveries not booting correctly is a noted issue, and started with WWE users. I got a hard lock on TWRP 2.8.0.3, and Philz seemed to running, but with no video. It is interesting that not everyone is having that issue, though. Right now, the only "workaround" is to actually flash. When I say "not working right now", I mean that the developers haven't found/fixed the issue yet, but you knew that, so I'll move on.
Also, it's not like I don't know how to get a stock recovery. It's just I'd rather not have to go through the hassle if I don't have to, especially since it's not exactly time-critical. There probably won't be another OTA for a while, and I have no doubt someone will post a copy of the updated recovery before then.

jshamlet said:
Dude, seriously, there are many brands of decaf on the market that are just as tasty as the real thing.
The issue with recoveries not booting correctly is a noted issue, and started with WWE users. I got a hard lock on TWRP 2.8.0.3, and Philz seemed to running, but with no video. It is interesting that not everyone is having that issue, though. Right now, the only "workaround" is to actually flash. When I say "not working right now", I mean that the developers haven't found/fixed the issue yet, but you knew that, so I'll move on.
Also, it's not like I don't know how to get a stock recovery. It's just I'd rather not have to go through the hassle if I don't have to, especially since it's not exactly time-critical. There probably won't be another OTA for a while, and I have no doubt someone will post a copy of the updated recovery before then.
Click to expand...
Click to collapse
I actually have heard of problems with CWM and Philz (CWM based)on the ViperOne thread. They state in OP and several times in the thread when screw ups happen to only use TWRP. I always thought it was ROM specific, and because of all the USE TWRP! posts, I haven't heard of recovery problems like this.
Maybe a switch to TWRP will fix his problem?

I'm not really seeing the issue here....you just can't boot the custom recovery from a command prompt(temporarily most likely). You can still flash twrp, do what you need to do(i.e. root,etc), then flash the stock recovery back in less than 5 minutes. You could probably just extract the recovery from the OTA or the rom you flashed. It literally took you more time to post your replies here than it would have taken you to do that....just saying.

Here's the stock recovery image that was posted in another thread: http://goo.gl/KsKQvk
I went through the same thing yesterday being unable to temporary boot to trwp. Sunshine didn't work giving me temp root and Weaksauce and Towelroot didn't do it either.
Custom recovery and Supersu flash worked as always.
HTC One M8

Related

[Q] Soft brick now I can only flash nightly?

I soft bricked my M8 and wiped the phone with twrp then tried to sideload the GPE rom I was using again and it wouldn't work. In fact I can't flash any rom that isn't cyanogen mod nightly for the m8... Also my bootloader changed from the white screen with the droid bots on a skateboard to a black screen with a single droid on it. Any idea why I can't flash anything besides cyanogen?
Rye Cribby Tree said:
I soft bricked my M8 and wiped the phone with twrp then tried to sideload the GPE rom I was using again and it wouldn't work. In fact I can't flash any rom that isn't cyanogen mod nightly for the m8... Also my bootloader changed from the white screen with the droid bots on a skateboard to a black screen with a single droid on it. Any idea why I can't flash anything besides cyanogen?
Click to expand...
Click to collapse
Did you try pushing the rom instead of sideloading it? Apparently sideloading in TWRP doesn't work, or doesn't work like it should
Try pushing it to the correct path and flash again.
Are you S-OFF?
BerndM14 said:
Did you try pushing the rom instead of sideloading it? Apparently sideloading in TWRP doesn't work, or doesn't work like it should
Try pushing it to the correct path and flash again.
Are you S-OFF?
Click to expand...
Click to collapse
Yeah, once I got the phone fixed I tried to load it normally. However it still didn't work. I tried other recoveries like Philz Touch too. Unfortunately firewater doesn't work for me.
Rye Cribby Tree said:
Yeah, once I got the phone fixed I tried to load it normally. However it still didn't work. I tried other recoveries like Philz Touch too. Unfortunately firewater doesn't work for me.
Click to expand...
Click to collapse
Try flashing the boot.img file that comes with the ROM first, then re-flash the ROM of your choice.
Code:
fastboot flash boot boot.img
fastboot reboot-bootloader
Go back into recovery of choice, wipe cache, dalvik-cache etc Then go to installed zip and select the ROM of your choice and flash the ROM.
Firewater won't work anymore for "later released" models that gets shipped with latest firmware. HTC patched it, you "MIGHT" be lucky if you still have an older device.
The developers of Firewater did however create another method to S-OFF the device. [Android][HTC S-OFF] SunShine for modern HTC devices
Sunshine is $25 but it works. It first checks your phone for compatibility before you pay for anything. That way if your device "isn't" compatible then it won't make you pay $25 for something that "won't" work.
Something to look into if you have $25 to spare :good:
BerndM14 said:
Try flashing the boot.img file that comes with the ROM first, then re-flash the ROM of your choice.
Code:
fastboot flash boot boot.img
fastboot reboot-bootloader
Go back into recovery of choice, wipe cache, dalvik-cache etc Then go to installed zip and select the ROM of your choice and flash the ROM.
Firewater won't work anymore for "later released" models that gets shipped with latest firmware. HTC patched it, you "MIGHT" be lucky if you still have an older device.
The developers of Firewater did however create another method to S-OFF the device. [Android][HTC S-OFF] SunShine for modern HTC devices
Sunshine is $25 but it works. It first checks your phone for compatibility before you pay for anything. That way if your device "isn't" compatible then it won't make you pay $25 for something that "won't" work.
Something to look into if you have $25 to spare :good:
Click to expand...
Click to collapse
I tried flashing the boot.img and it didn't work sadly. It fails as soon as I swipe to flash.
Rye Cribby Tree said:
I tried flashing the boot.img and it didn't work sadly. It fails as soon as I swipe to flash.
Click to expand...
Click to collapse
Did you flash in fastboot?Try to download twrp from its officical site.Also maybe you have downloaded a bad version of the rom.
Jyotirdeb said:
Did you flash in fastboot?Try to download twrp from its officical site.Also maybe you have downloaded a bad version of the rom.
Click to expand...
Click to collapse
There is no offical twrp for the AT&T version of the m8 and I did flash in fastboot. The ROM I used worked in a previous installation as well. It soft bricked after updating so I completely wiped the phone now it wont install.
I had a similar problem, I had to use the format option in twrp and then used RUU
gonzo237 said:
I had a similar problem, I had to use the format option in twrp and then used RUU
Click to expand...
Click to collapse
Do you have a link? Or something I could look up and find on my own?
Rye Cribby Tree said:
Do you have a link? Or something I could look up and find on my own?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2727831
Now this one is for the Verizon HTC, but maybe this will help you.
gonzo237 said:
http://forum.xda-developers.com/showthread.php?t=2727831
Now this one is for the Verizon HTC, but maybe this will help you.
Click to expand...
Click to collapse
Ah, I can't s-off, thank you for the reply though I'm sure someone else with this problem will find this helpful.
Rye Cribby Tree said:
Ah, I can't s-off, thank you for the reply though I'm sure someone else with this problem will find this helpful.
Click to expand...
Click to collapse
I'd still give the format option a try, I wasn't able to flash any roms except for the CM nightly as well, then I made it worse by trying to wipe the internal data which led to not being able to mount the internal partition, and couldn't even get into the bootloader until my phone battery died. I remember reading that the format would allow me to mount the internal storage. You may be able to fix the issues with a format and then try flashing a rom.
Did you try converting your phone over to GPE? That's what it sounds like you tried to do. If so then that is why nothing is working because the partitions are layed out differently from a stock sense M8. You need to wipe everything and run whatever RUU is available for your device and pray to god it works because you are s-on... You seriously should have been s-off before doing all of this. Being s-on is really going to complicate things for you bro... That's also probably why you can't fastboot the kernel. Find a RUU for your phone and run it. Post back here if you get any "main version" errors cuz then some tricks will need to be done.. Feel free to PM me, maybe I can assist directly getting you back up and running...
gonzo237 said:
I'd still give the format option a try, I wasn't able to flash any roms except for the CM nightly as well, then I made it worse by trying to wipe the internal data which led to not being able to mount the internal partition, and couldn't even get into the bootloader until my phone battery died. I remember reading that the format would allow me to mount the internal storage. You may be able to fix the issues with a format and then try flashing a rom.
Click to expand...
Click to collapse
Great news, your suggestion worked! I'm able to flash the sinless GPE 4.4.4 rom! No more nightly's for this guy.:good:

phone stuck on HTC boot screen and other stuff

I recently got a htc one m8 that is stuck on the boot screen.
i can get into the bootloader and fastboot seems to work.
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
if i reboot normally it goes back to the bootscreen with the green htc logo.
if i try to go to hboot adb doesn't recognize the device.
so i'm stuck now. i've read several tutorials and tried various things but have no idea where to go from here.
i can tell you that the bootloader says its unlocked and that its set to s-on and there is no os installed.
help
jodahall said:
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
Click to expand...
Click to collapse
Try fastboot erase cache, and flash TWRP again with fastboot.
What is your hboot number, and what TWRP version are you trying?
Also, was your phone recently updated OTA for the Stagefright patch? If so, its a known issue that this recent update does not work with TWRP for some folks.
jodahall said:
if i try to go to hboot adb doesn't recognize the device.
Click to expand...
Click to collapse
This is as it should be. adb doesn't work in hboot. You need to be booted into OS to use adb, possibly will work in recovery (but you can't boot into recovery, so that doesn't really matter).
my hboot version is 3.19.0.0000
i am trying to flash the latest twrp
I have not gotten the ota, this phone has been sitting in a drawer for about 6 months so nothing new has been applied.
I will try erase the cache and reflash the twrp
jodahall said:
i am trying to flash the latest twrp
Click to expand...
Click to collapse
What number TWRP exactly? And you're sure its the TWRP file for the M8, right?
I ask for the number, since I've seen at least a couple times where the person claims they are trying to use the "latest" or "current" TWRP. But when I ask for more info, it turns out the version is not even close to current.
Best to be specific when talking about version numbers.
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
I also tried your advice and from a command window erased the cache and then reflashed. It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Sent from my A0001 using XDA Free mobile app
oh, it worked. I am one step closer as it booted into the custom recovery.....whoohooo
I ran the command "fastboot format cache" from a dos prompt a couple of times, there were errors the first two times, then the 3rd time it created it without error.
ok onto the next steps that are in Vomers guides....
thanks for all your help
jodahall said:
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
Click to expand...
Click to collapse
You are correct, that is latest version (and correct one for the M8). You might re-download just to eliminate the possibility the file wasn't corrupted.
jodahall said:
It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
Click to expand...
Click to collapse
If you are still intending on doing this, don't try any version older than 2.8.4.0 or so. TWRP versions much older than that, won't work on hboot 3.19. TWRP will install and seem to work fine, but after you flash the ROM, the ROM won't boot.
jodahall said:
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Click to expand...
Click to collapse
In the technical sense, the emmc chip does have a finite number of times it can be flashed.
But in reality, I think the number of times the emmc can be flashed before failing is (supposedly) something in the thousands.
Of course, things sometimes fail before they are supposed to, and every extra flash may put you closer to that point (in theory). But I don't let that stop me from flashing what I want, whenever I want to. And flashing recovery a few extra times is not going to hurt anything much IMO.
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
jodahall said:
thanks for all your help
Click to expand...
Click to collapse
There's a button for that!

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

Does the "fastboot boot" command work for anyone here?

I'm using the fastboot binary from HTC's website. I tried to use it to boot TWRP without flashing it, but in download mode, it just hangs forever after saying "Flash images success (1/1)" and "Start downloading", with the cursor stuck on the second of those. The fastboot command is also hung, after printing "booting..." I eventually have to force reset the phone using all 3 buttons.
I also tried it from the bootloader screen and that just fails immediately, saying "booting... FAILED (remote: unlock device to use this command)" even though I'm unlocked (and S-OFF).
The reason I'm doing this btw is so I can try to back up the stock recovery before overwriting it with TWRP, but I don't know how to do that without root, for which I need TWRP... so if anyone knows another way, that'd be great too!
supeRUUser said:
I'm using the fastboot binary from HTC's website. I tried to use it to boot TWRP without flashing it, but in download mode, it just hangs forever after saying "Flash images success (1/1)" and "Start downloading", with the cursor stuck on the second of those. The fastboot command is also hung, after printing "booting..." I eventually have to force reset the phone using all 3 buttons.
I also tried it from the bootloader screen and that just fails immediately, saying "booting... FAILED (remote: unlock device to use this command)" even though I'm unlocked (and S-OFF).
The reason I'm doing this btw is so I can try to back up the stock recovery before overwriting it with TWRP, but I don't know how to do that without root, for which I need TWRP... so if anyone knows another way, that'd be great too!
Click to expand...
Click to collapse
You can't. Read twrp FAQ.
yldlj said:
You can't. Read twrp FAQ.
Click to expand...
Click to collapse
I don't see anything at twrp.me/FAQ about this...
Are you saying there is no way to make a backup of the stock recovery, at all? How do the ones posted here get made?
supeRUUser said:
I don't see anything at twrp.me/FAQ about this...
Are you saying there is no way to make a backup of the stock recovery, at all? How do the ones posted here get made?
Click to expand...
Click to collapse
You need 2 phones.
Taken from twrp faq
6. How do I backup stock recovery prior to flashing TWRP? You can't. The "fastboot boot" command appears to be disabled on the 10's ABOOT, so TWRP must be fastboot flashed over stock recovery. You can however, extract the stock recovery.img from the OTA firmware.zip when it's received and use that to install the OTA.
[*]An alternate method to obtain a stock recovery is listed below, but it requires 2 devices (either owned by you, or help from someone else in the forum):
Someone fastboot flash twrp and immediately make a backup of boot and upload it to XDA.
Once the above is available, someone else download that boot.img to their device, and fastboot flash twrp to the BOOT partition of their device.
Once the above is done, reboot the device, which will bring up TWRP, and then backup stock RECOVERY in TWRP, and upload to XDA.
Then, from within TWRP, use the Image install feature in TWRP to flash the stock boot.img
They're probably pulled from the RUUs.
Barracuz said:
They're probably pulled from the RUUs.
Click to expand...
Click to collapse
Yep. That's how I get stock recoveries for people who need them.
---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------
supeRUUser said:
I don't see anything at twrp.me/FAQ about this...
Are you saying there is no way to make a backup of the stock recovery, at all? How do the ones posted here get made?
Click to expand...
Click to collapse
Download the latest RUU for your model, and use nkk71's RUU decrypt tool to extract the firmware (with the -f flag). The stock recovery will be in there.
Duh, OK, that should have been obvious. Thanks.
supeRUUser said:
Duh, OK, that should have been obvious. Thanks.
Click to expand...
Click to collapse
It's not obvious if you don't know about the decrypt tool, and a lot of people don't. You're welcome

Categories

Resources