Related
Hi everyone I'm an experienced rooter and am having trouble finding a method to root the Google Play Edition HTC One. Can anyone link me to a method or let me know how to do it?
If you have the HTC ge ...I asumme since you're experienced you have knowledge of adb and fastboot...if so all it takes is fastboot oem unlock
Then flash recovery of your choice and so on
Nxxx said:
Hi everyone I'm an experienced rooter and am having trouble finding a method to root the Google Play Edition HTC One. Can anyone link me to a method or let me know how to do it?
Click to expand...
Click to collapse
I've mine unlocked with "fastboot oem unlock", but I'm not able to root the phone. In fact, I think I've lost my stock recovery, I didn't check it before unlock, so I'm not even sure if the recovery had been missing before the phone was unlocked. When I try to boot into recovery now, all I get is an android robot on its belly with a red warning triangle on it. I also can't boot/flash custom recovery either, adb seems the phone just fine, but it tries to push the recovery, the phone just freeze up.
Someone else on android central forum also has his stock recovery missing right out of the box, getting the same belly-up robot as mine, very strange.
mickey4mice said:
I've mine unlocked with "fastboot oem unlock", but I'm not able to root the phone. In fact, I think I've lost my stock recovery, I didn't check it before unlock, so I'm not even sure if the recovery had been missing before the phone was unlocked. When I try to boot into recovery now, all I get is an android robot on its belly with a red warning triangle on it. I also can't boot/flash custom recovery either, adb seems the phone just fine, but it tries to push the recovery, the phone just freeze up.
Someone else on android central forum also has his stock recovery missing right out of the box, getting the same belly-up robot as mine, very strange.
Click to expand...
Click to collapse
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
mdandashly said:
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
Click to expand...
Click to collapse
can you post the link to stock recovery you found? I couldn't flash the stock recovery image I found on the forum, says "different signature".
mickey4mice said:
can you post the link to stock recovery you found? I couldn't flash the stock recovery image I found on the forum, says "different signature".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358781
Got it from this post. I also used to stock factory image from that post as well.
I'm frustrated because my battery life is pretty bad and when I check stats, the kernel is consuming 25% of battery. Any idea what gives?
mdandashly said:
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
Click to expand...
Click to collapse
Also, did you get "FAILED (status read failed (Too many links))" when unlock? Mine unlocked just fine but I don't if that error msg at the end of the process effected anything else.
mickey4mice said:
Also, did you get "FAILED (status read failed (Too many links))" when unlock? Mine unlocked just fine but I don't if that error msg at the end of the process effected anything else.
Click to expand...
Click to collapse
Yeah it may have said failed. But everything seems to have worked. I'm just trying to get back to stock bc I may need to RMA.
You do know the Android on it's back is the stock recovery?...
EddyOS said:
You do know the Android on it's back is the stock recovery?...
Click to expand...
Click to collapse
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?
---------- Post added at 08:32 PM ---------- Previous post was at 08:17 PM ----------
mickey4mice said:
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?
Click to expand...
Click to collapse
Arrrhhh...never mind. I finally brought up the recovery menu by pressing the power+vol up/down buttons REALLY REALLY HARD! I tried this combo for 3 days without success, I think the vol up button is finally loosening up, weird I don't have any problem using it on the phone, just in the recovery mode.
Stock recovery really doesn't have anything you can do In it
a box of kittens said:
Stock recovery really doesn't have anything you can do In it
Click to expand...
Click to collapse
Yes, but all I need is gain root and keep stock for OTA, don't want to flash back and forth every time an update comes in.
Sideloading CWM "fastboot boot recovery-clockwork-touch-6.0.3.1-m7.img" isn't working for me, keep stuck on downloading...nothing happens.
mickey4mice said:
Yes, but all I need is gain root and keep stock for OTA, don't want to flash back andrth every time an update comes in.
Sideloading CWM "fastboot boot recovery-clockwork-touch-6.0.3.1-m7.img" isn't working for me, keep stuck on downloading...nothing happens.
Click to expand...
Click to collapse
A bit confused on what command you're trying...do you want to flash cwm? Then " fastboot flash recovery recovery.img"
a box of kittens said:
A bit confused on what command you're trying...do you want to flash cwm? Then " fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
I don't want to permanently flash a custom recovery like CWM, only want to sideload it to flash SuperSU and gain root. The command I use is "fastboot boot recovery.img" where recovery.img being the name of CWM. Don't know why it's not working though.
mickey4mice said:
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?.
Click to expand...
Click to collapse
Yes, that's the stock recovery. You then have to press power + volume up (in the case of the Nexus 4, for example). You have to manually flash CWM as you would for the normal One
e.g. fastboot flash recovery recovery.img
You apparently can no longer 'boot' into CWM - you have to flash it
My Moto X now refuses to boot. With stock recovery it'll get past the bootloader, then blink an image of a dead android with the message "Error" briefly, and keep doing so every ~10 seconds. If I flash TWRP, any attempt to boot takes me to TWRP, with log messages reading "unable to mount..." for a bunch of partitions (/data, /cache, storage, etc.)
Can I recover my device?
The short sequence of events: I rooted my phone (T-Mobile phone, unlocked it via Motorola's website) and installed TWRP. Later I tried to accept the 4.4.2 OTA update, but the phone wouldn't take the update, because TWRP. Flashed stock recovery tried again, got stuck in bootloop. Tried flashing back the 4.4 / 140.44.3 images from here, now I'm stuck with a blinking error message.
I see there are a bunch of image files bundled into the 4.4.2 / 161.44.25 update - would flashing those do any good?
What version is your bootloader?
Steve-x said:
What version is your bootloader?
Click to expand...
Click to collapse
Version 30.B2.
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Fast boot erase cache should work . its trying to flash the it's ,so you need to delete the cache where the ota file downloaded to
Sent on my Gummy running Lenoto X
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
that is the file you need to flash with RSD Lite or Fastboot and it should get you 100% back up and running.
But then if you want to go to 4.4.2 after you flash the firmware before you add anything or install TWRP just update the phone to 4.4.2 then install the custom recovery and SuperSU.
Steve-x said:
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Click to expand...
Click to collapse
I have tried both RSD Lite, and applying all of the commands from the XML file manually, following the directions from here. Both ways, I still get the blinking error message
The "can't mount..." log messages I get if I flash back to TWRP suggest it could be some sort of partitioning problem, but I'm not sure how to diagnose that.
And the flashing of all files completes successfully?
Steve-x said:
And the flashing of all files completes successfully?
Click to expand...
Click to collapse
I could have sworn that I wasn't getting any errors previously. Now, however, after trying to flash system.img (making sure to use mfastboot, of course), I get an error on the phone, "sp space is not enough". Not sure what it means, and Googling around doesn't turn up any answers.
dray_jr said:
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
Yep, that's exactly what I flashed. Made sure the md5sum matched my download and everything.
flashallthetime said:
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Click to expand...
Click to collapse
Yep, cleared the cache, no luck
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
So I guess more warnings into my noobs guide to accept an ota thread
Maybe I should put a notice not to accept the ota and only flash your carriers sbf firmware when available?
Sent on my Gummy running Lenoto X
Steve-x said:
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
Click to expand...
Click to collapse
Code:
C:\Users\spiffytech\Documents\sdk\platform-tools>fastboot erase system
(bootloader) Variable not supported!
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.101s
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
spiffytech said:
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
Click to expand...
Click to collapse
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
flashallthetime said:
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'll go with that plan What is it that makes flashing from sbf safer?
So if you perform a full factory reset the phone will boot up normally now? If that is the case then I don't see any problem with accepting the OTA to 4.4.2.
Help PLZ
I had the exact same problem as OP, took the same course of action, and got a successful boot. I do some minimal stuff, check if everything is working, turn on dev mode, etc. I put in my wifi password.
I wanted to check if my bootloader was back to stock, so I turned off my device, and then tried to power on. Pressing the power button does nothing.
So I get into fastboot, and select factory (reset) again. It boots up, but it doesn't seem like it actually did a factory reset, because it automatically connected to my wifi..
Have you any idea what's going on, and how perhaps to solve this weird dilemna?
EDIT: I'm not sure if I actually did anything, but after a couple reboots it just started working normally. I installed the update to 4.4.2 and everything is smooth thus far.
Eventually the phone prompted me to apply the 4.4.2 update so often the phone was actually unusable - it'd go back to the "do you want to update?" screen as soon as I backed out of it. I was thus forced to apply it OTA. Fortunately, the update went through fine this time, and my phone continues to work fine
Thanks for your help, folks!
I am 100% stock.
I did the update using Minimal ABD and Fastboot. Once that was finished, the phone booted up (after optimizing all my apps) and gave me a System UI error and would never get past that (even if I hit OK or Report). I turned it off and then went it came back on, it went straight to the Google Logo. It didn't even vibrate like it usually does when it boots up.
If I hold down all 3 buttons, it will boot to the bootloader screen, but anything I do from there, just goes back to the Google logo and that's it. I had to go to Recovery and get another error, then hit power + volume up, and I did a factory wipe. However, after that, it still does the same thing. Goes to the Google Logo and nothing else. I've wiped it a few times now and no luck.
Any suggestions on what to do?
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
edit: Didn't realize update file was sent out through OTA. Try flashing factory 5.0.1 then flash the update which is in the cache folder. Extract and save that 5.1 OTA file somewhere else before flashing 5.0.1, if not its gone. Best suggestion is to wait go back to 5.0.1 and wait for 5.1 factory image.
DevilMR said:
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
Click to expand...
Click to collapse
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
mikebio said:
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
Click to expand...
Click to collapse
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
meest said:
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
Click to expand...
Click to collapse
This is correct. I also can't get my computer to recognize my Nexus anymore. Any tips on that?
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
DevilMR said:
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
Click to expand...
Click to collapse
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Nevermind, got it... I am going to reflash factory image... I tried 5.0.1 and it failed.
mikebio said:
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Click to expand...
Click to collapse
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
meest said:
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
The issue is, it comes up Fastboot Shamu and it isn't recognized. Only when I put in into Apply update from ADB does it show up Nexus 6 on Windows... Not sure what to do. I can't flash right now because of this.
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Edit: I have a feeling its due to a driver issue... during the downgrade the required driver probably changed... and thus disconnected in the middle of flash. If this is the case, then I feel like an idiot
diabl0w said:
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Click to expand...
Click to collapse
Try setting up another computer. You should be able to go into bootlader mode by pressing power and volume down buttons at the same time. Hopefully you have enought battery. If that doesnt work someone should be able to help you out.
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
r3pwn said:
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
Click to expand...
Click to collapse
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
diabl0w said:
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
Click to expand...
Click to collapse
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
r3pwn said:
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
Click to expand...
Click to collapse
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
diabl0w said:
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
Click to expand...
Click to collapse
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
r3pwn said:
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
Click to expand...
Click to collapse
I realized that after I downloaded the file and took a look at it further... thanks for your help and for bearing with me. It worked!
How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?
Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o
Did you flash userdata too? Tried factory reset on top?
pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.
I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk
530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.
I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.
dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.
PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.