Database Develop

HTC One root that really works

hey everyone !!
firstly, apologies if this should be somewhere else or if ive repeated someone else's problem.
hope you can help. ive got an HTC One and im trying to root it because i want to install a custom rom. ive tried lots and lots of ways including rom manager, superuser, fastboot, superboot. TWRP, CWM and your all in one toolkit but everything fails.. i was wondering if i have a problem with the internal storage. i tried to transfer a jpeg to the phone using HTC sync manager. i left it to transfer and went to work. 8 hours later the progress bar hadnt moved. i tried to transfer a boot image and it keeps timing out. rom manager comes back with errors when i do anything. for example if i try to go into fix permissions i get "an error occured while attempting to run privileged commands" im beginning to think that rooting this mobile is an impossibility. please help !!!

Did u unlock the bootloader?
Sent from my EndeavorU using Tapatalk 2

shiningarmor said:
Did u unlock the bootloader?
Sent from my EndeavorU using Tapatalk 2
Click to expand...
Click to collapse
hey shin hows it going ?
the bootloader is unlocked but i have noticed that the mobile is s- on. im guessing that i need to switch to s- off. is that possible ?
thanx matey !!

graemebonny said:
hey shin hows it going ?
the bootloader is unlocked but i have noticed that the mobile is s- on. im guessing that i need to switch to s- off. is that possible ?
thanx matey !!
Click to expand...
Click to collapse
You won't have S-Off unless you have it unlocked from the get go, ie a developers phone.
All you need to do is follow everything from this thread and youre good to go.
http://forum.xda-developers.com/showthread.php?t=2182792&highlight=how+to+root
The whole process should take about half an hour max as if you haven't made an account with HTC dev unlock then you will have to, they will send you a key once you send them the read out from your phone.
It's a really easy procedure to be honest.

dladz said:
You won't have S-Off unless you have it unlocked from the get go, ie a developers phone.
All you need to do is follow everything from this thread and youre good to go.
http://forum.xda-developers.com/showthread.php?t=2182792&highlight=how+to+root
The whole process should take about half an hour max as if you haven't made an account with HTC dev unlock then you will have to, they will send you a key once you send them the read out from your phone.
It's a really easy procedure to be honest.
Click to expand...
Click to collapse
hey dude
as i said the bootloader is already unlocked so i dont have to do all that again. the method u suggest is one of the many i already tried and it didnt work. its info is all wrong. it keeps referring to the SD card. The HTC one doesnt come with an SD card ??? it has internal storage.
Graeme

Don't forget to erase cache after you flashed your recovery, this can cause many problems.
fastboot flash recovery recovery.img
fastboot erase cache
If you don't erase cache, this could be your problem.
Possible solution :
Did you try this method? Don't use any All-in-One tool to do this, do take the time to do this manually via an SDK/ADB command window (see my signature if it is not installed on your computer)
Download the boot.img HERE made by Paul O'Brien and the CWM recovery by Flyhalf205 HERE place both files in your platform-tools of your SDK folder.
Reboot into Bootloader mode
Plug your USB cable and make certain that FASTBOOT USB is highligted
At the prompt type>fastboot flash boot boot.img
Success message
Again at the prompt type>fastboot erase cache
Success message
At the prompt type>fastboot reboot-bootloader
Your phone will reboot in Bootloader mode
At the prompt type>fastboot flash recovery recovery.img
Success message
Againt at the prompt type>fastboot erase cache
Success message
At the prompt type>fastboot reboot
Once rebooted check if you have the Superuser application in the app Drawer

Did you manage to get recovery installed ok?

graemebonny said:
hey everyone !!
firstly, apologies if this should be somewhere else or if ive repeated someone else's problem.
hope you can help. ive got an HTC One and im trying to root it because i want to install a custom rom. ive tried lots and lots of ways including rom manager, superuser, fastboot, superboot. TWRP, CWM and your all in one toolkit but everything fails.. i was wondering if i have a problem with the internal storage. i tried to transfer a jpeg to the phone using HTC sync manager. i left it to transfer and went to work. 8 hours later the progress bar hadnt moved. i tried to transfer a boot image and it keeps timing out. rom manager comes back with errors when i do anything. for example if i try to go into fix permissions i get "an error occured while attempting to run privileged commands" im beginning to think that rooting this mobile is an impossibility. please help !!!
Click to expand...
Click to collapse
The sd card Nens referring to is the internal storage
Sent from my GT-I9300 using Tapatalk 2

[Q] One is stuck in bootloader

I just got my HTC One less than a week ago, rooted and flashed my first ROM with no issues. Decided to try out a different one today, but after flashing it, my phone rebooted into bootloader and has been stuck there. Anytime I try to reboot the phone or reboot into recovery, it just goes back to the bootloader screen. Same thing when I attempt a factory reset. I've tried reinstalling TWRP recovery and although it says the install is successful, it's still stuck in bootloader. I also tried to install my previous ROM via fastboot command (which is failing), but to no avail. I got the following output:
sending 'zip' (994092 KB)...
OKAY [ 38.486s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 54.083s
I'm on the Sprint version, and I'm aware that 4.2 ROMs don't work on Sprint yet so I'd be using older versions of them for the time being, but I guess I inadvertently used an incorrect version.
Any ideas?

hmm...must really be bricked. :-\

if it is booting into bootloader, it is not bricked...
try connecting your USB cable , select fastboot in bootloader... it should show the FASTBOOT USB
now on your PC, where you have the ADB/Fasboot files, SHIFT+RIGHT CLICK on that folder and select Open command window here.
In command window, enter FASTBOOT ERASE CACHE
and try booting again...it might work.....

mathrania said:
if it is booting into bootloader, it is not bricked...
try connecting your USB cable , select fastboot in bootloader... it should show the FASTBOOT USB
now on your PC, where you have the ADB/Fasboot files, SHIFT+RIGHT CLICK on that folder and select Open command window here.
In command window, enter FASTBOOT ERASE CACHE
and try booting again...it might work.....
Click to expand...
Click to collapse
nope, no luck I also tried flashing recovery again in addition to it, still going straight to bootloader.

nsuviolin2005 said:
nope, no luck I also tried flashing recovery again in addition to it, still going straight to bootloader.
Click to expand...
Click to collapse
Try using the HTC one AIO toolkit to flash a new recovery and see if that helps.
It uses the FASTBOOT method to flash. Plus you have options to try CWM and TWRP.
If that works you should be able to flash a different rom to get your device up and running

gazlufc said:
Try using the HTC one AIO toolkit to flash a new recovery and see if that helps.
It uses the FASTBOOT method to flash. Plus you have options to try CWM and TWRP.
If that works you should be able to flash a different rom to get your device up and running
Click to expand...
Click to collapse
When I click to flash a recovery, it gives me a prompt that there will be 2 screens and to close the 1st one once I'm in bootloader...I do that, then the 2nd screen comes up but nothing happens. Same thing for both the Sprint options

You need to be in the fastboot menu not bootloader menu.
Sent from my HTC One using xda app-developers app

gazlufc said:
You need to be in the fastboot menu not bootloader menu.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I was...FASTBOOT USB mode, my phone is booting into that menu by default

nsuviolin2005 said:
I was...FASTBOOT USB mode, my phone is booting into that menu by default
Click to expand...
Click to collapse
hmmmmm thats strange.
What you could try is download one of the recoveries and unzip the file so you get the .img file of that recovery.
Then try to flash your own recovery option. see if that works

gazlufc said:
hmmmmm thats strange.
What you could try is download one of the recoveries and unzip the file so you get the .img file of that recovery.
Then try to flash your own recovery option. see if that works
Click to expand...
Click to collapse
Is this supposed to be automated or something? All I get with any option is an command line screen that's in the folder but nothing's happening.

nsuviolin2005 said:
Is this supposed to be automated or something? All I get with any option is an command line screen that's in the folder but nothing's happening.
Click to expand...
Click to collapse
could you post screenshots so I could see what happening?
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
The only other thing I could think of is to try an RUU if all else fails but I can't guarantee that it will work
Sent from my HTC One using xda app-developers app

gazlufc said:
could you post screenshots so I could see what happening?
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
The only other thing I could think of is to try an RUU if all else fails but I can't guarantee that it will work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Profit! Turns out the flash your own recovery option worked, I just didn't follow it all the way through, initially...after I closed the command prompt screen, the Open file menu came up and I was able to pick my TWRP recovery and boot into it. I restored my backup I made right before flashing the bad ROM and the phone is booting past the bootloader now
But.....next issue is that it's booting to a black screen instead of the regular lock screen, and after sitting there in that state for a few minutes, it reboots. :-\ I'm wondering if this is just because I deactivated the phone and switched back to my EVO LTE while trying to fix the One...that would be a first, though, as the phones are usually operational even if they don't have service.

nsuviolin2005 said:
Profit! Turns out the flash your own recovery option worked, I just didn't follow it all the way through, initially...after I closed the command prompt screen, the Open file menu came up and I was able to pick my TWRP recovery and boot into it. I restored my backup I made right before flashing the bad ROM and the phone is booting past the bootloader now
But.....next issue is that it's booting to a black screen instead of the regular lock screen, and after sitting there in that state for a few minutes, it reboots. :-\ I'm wondering if this is just because I deactivated the phone and switched back to my EVO LTE while trying to fix the One...that would be a first, though, as the phones are usually operational even if they don't have service.
Click to expand...
Click to collapse
Glad to hear the recovery worked. As for the phone staying on black. I would just advice to flash a nother rom if the problem still persists mate

gazlufc said:
Glad to hear the recovery worked. As for the phone staying on black. I would just advice to flash a nother rom if the problem still persists mate
Click to expand...
Click to collapse
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.

No problem man glad I could help
Sent from my HTC One using xda app-developers app

nsuviolin2005 said:
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
Click to expand...
Click to collapse
\question i am having the same problem you have but i think its due to water damage i am going straight into the bootloader are sometime i can get it into safe mode

nsuviolin2005 said:
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
Click to expand...
Click to collapse
To be S-ON again you need to reboot into bootloader
Then FASTBOOT USB
then run fastboot and write "fastboot oem writesecureflag 3" and enter. Now you will be S-ON

But do NOT S-ON unless you absolutely need to.

[Q] Remote: not allowed when trying to flash TWRP/CWM

My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?

Try the tool kit in development.
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse

redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
Are you in bootloader/fastbootusb?

BD619 said:
Are you in bootloader/fastbootusb?
Click to expand...
Click to collapse
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.

redmanjoey said:
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
Click to expand...
Click to collapse
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP

joshuaw84 said:
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.

Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...

redmanjoey said:
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
Click to expand...
Click to collapse
It could be outdated.
Do you have android sdk on your PC?
If so make sure it's up to date.
If not get it HERE

redmanjoey said:
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Click to expand...
Click to collapse
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP

joshuaw84 said:
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Sorry if I sounded mean or anything I was literally just asking which one you meant lol. I now realize "are you implying" does sound kinda snarky. Anyway, it must have been something with my computer because I did it on another computer and got it to work.
So the thread doesn't go to waste, if anyone is having issues try on another computer.

Okay, now trying to flash the stock recovery to get the phone exchanged for radio issues, I am running into the same problem. I tried both computers now. Hopefully I figure it out soon, had to activate an old blackberry for the time being.
"sending 'recovery' (16472 KB)...
FAILED (remote: not allowed)
finished. total time: 0.007s"

I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.

{ParanoiA} said:
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
Click to expand...
Click to collapse
To flash a recovery? Just rename the recovery as a radio file?

Yes. Go to http://forum.xda-developers.com/showthread.php?t=2696652 and all the info you need is there along with directions.

[Q] Flash back to Stock

Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.

samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.

samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.

samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.

samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.

Awesome!

samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!

boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:

samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app

Help with Nexus 6 possible Brick

Alright I am looking for some help here. I was attempting to unroot to update my Nexus 6 to Android M. Not sure how this happened but here it goes. I can boot the phone into recovery TWRP and into boot loader but the OEM is locked....In recovery I have no backups or ROMs o flash and my mac is not connecting with the Nexus 6. It seems like there is no ROM on the phone at all and I cant use Terminal commands I keep getting Failures. I have run the 1 click root and unroots for mac and still nothing. I also have no access to Developer options since I cant load into a ROM...So I cant select allow OEM unlock... Please let me know if there is anything I can do to fix this. Thanks for your help everyone!

Try to uninstall all drivers then re install to see if mac recognizes your phone then sideload a rom to recovery or adb

Had this before. I believe when connecting to your computer, you have to delete every nexus 6 previous connections so it would be as if your phone never connected to your computer before. Then after you do that, it should install drivers and recognize your phone. I'm not sure if I remember correctly but I believe its from your toolbar on your computer where it normally pops up "eject USB " warnings. Sorry if I couldn't help

Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.

or fastboot wipe user data and cache.

nhizzat said:
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
Click to expand...
Click to collapse
I have been working on this since last night 7pm... I tried adb push and it just sits there and says starting adb sideload for about 10 min then vibrates with a cancellation. I tried removing Android File Transfer and reinstalling it and I still get the can not find device error. Im thinking this might be a loosing battle.

simms22 said:
or fastboot wipe user data and cache.
Click to expand...
Click to collapse
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....

ibaldwin85 said:
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
Click to expand...
Click to collapse
did you have any roms on your phone before all this? if you did, did you try to search if they are in a different location in your storage now?

Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
he has no rom and bootloader locked. nrt cant do anything.

simms22 said:
he has no rom and bootloader locked. nrt cant do anything.
Click to expand...
Click to collapse
But if he has TWRP......he can transfer a ROM from the PC and flash it......

paclaco said:
But if he has TWRP......he can transfer a ROM from the PC and flash it......
Click to expand...
Click to collapse
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"

simms22 said:
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
Click to expand...
Click to collapse
True, but have a Mac, and it is rare that being in recovery and connected to the Mac, do not recognize ....
then wait a Windows computer then ....

FIX! we got it!
Thanks for all the responses guys! We spend another 4 hours on this Sunday and finally got it! We ended up using this forum step by step. http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
While my friend was installing all of the ADB drivers on his PC I attempted the steps on my mac. It made it through the first to lines of code but when rebooting into Boot loader it came back with a fail notice to unlock the OEM.
When he got all drivers installed we used the same lines of code (modifying C: for the location he had the ADB drivers) and it accepted all codes. Seeing that screen change into the OEM unlock select yes screen was a GREAT moment lol. After that we used NRT to flash Marshmallow...
All in all it was fun trying to figure this out! Not so much fun thinking I had to drop another $300 to get a new phone! Again thanks everyone for the help!

BladeRunner said:
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
Click to expand...
Click to collapse
Agreed, but its convenient as all hell.
Sent from my Nexus 6 using Tapatalk