So this has been mind breaking for me. I failed to flash the blackrose hboot everytime i trie and on every rom. It gets to the point where it has sent it files and then it says <waiting for device>. This happens on stock, BuglessBeast, rcadsmixhd 2.3 & 1.6 and hypersense (i like sense ). Anyone has any advice . Btw it did not brick it.
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
m0_t3 said:
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
Click to expand...
Click to collapse
Ehm, usb debugging is enabled and detected by the software at first. It gets to the point that it sends its hboot and after that it says something like error: deviceoffline and then stuck on waiting for device forever.
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
m0_t3 said:
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
Click to expand...
Click to collapse
well maybe htc sync but that was closed and its process was killed by taskmanager. No other programs i can think of.
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
m0_t3 said:
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
Click to expand...
Click to collapse
SO without my sd card it did not make any difference, apart from that it now mixes the message: adb server is out of date. Killing... and then waiting for device again.
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
m0_t3 said:
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
Click to expand...
Click to collapse
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
m0_t3 said:
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
Click to expand...
Click to collapse
WOW you are awesome sir thank you now it works i wish you could click the thanks button 30.000 times.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Awesome.
Glad to help ^_^
Sent from my Nexus One using xda premium
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
bassmadrigal said:
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Click to expand...
Click to collapse
It gives me attached device: Ht9 and thencq lot of numbers
Sent from my HTC Nexus One using XDA App
race55 said:
It gives me attached device: Ht9 and thencq lot of numbers
Click to expand...
Click to collapse
Well, that definitely means that your device is recognized. Did you get it working?
bassmadrigal said:
Well, that definitely means that your device is recognized. Did you get it working?
Click to expand...
Click to collapse
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
race55 said:
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
Click to expand...
Click to collapse
If you throw a post at the end stating what you had to do, he would probably update his original post.
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
Click to expand...
Click to collapse
ICS is too big for the stock ROM space on the N1, so you need to make those alterations so it can fit. texasice did make a striped down version that works on stock though.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
If you are like me, you have been flashing ROMS on your phone for years before you ever unlocked the bootloader. I didn't do it until about 6 months ago because I needed to flash Blackrose. Also, don't bite the hand that is trying to feed you.
Related
Hi! I am unlocked my nexus one and now tried to root it.
I tried with Win XP and Win 7 with the same result.
I can see the device. If i go to the command promt and enter
"adb devices" it shows me the serial - So, usb is not the problem.
I also successfully unlocked it the same way.
Dev. Mode USB is also activated.
As soon I try to root it i.e. with superboot, Android SDK etc. I get the message
"waiting for device" (stays there for ever)
also when I want to lock the device again - same result.
Something must have happened preventing me to access the phone.
Also did a hard reset - without success.
Bottemline I am STUCK. The phone works, but no root .
Versions: ERE27 with 2.1update1
Someone an idea?
Thanks
Try a different USB Port. You can't relock the device.
MatMew said:
Try a different USB Port. You can't relock the device.
Click to expand...
Click to collapse
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Oh really?
Can you provide link proof on how to re-lock the bootloader?
Lol - he thinks you can "re-lock" it.. hahaha..
did u debug ur usb....?
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
pjcforpres said:
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
Click to expand...
Click to collapse
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
You have to install the correct adb drivers
http://forum.xda-developers.com/showthread.php?t=613217
Eclair~ said:
Lol - he thinks you can "re-lock" it.. hahaha..
Click to expand...
Click to collapse
glad ur soooooooo much smarter
congrats ! A+
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
can you post the video link
helipilotx said:
glad ur soooooooo much smarter
congrats ! A+
Click to expand...
Click to collapse
Out of all the people that basically implied, or thought, what I said you - had to have a 'comeback' to me.. guess its because I said "hahaha," and "lol". If we really could re-lock the bootloader though... i'd be all over that..
TFJ4 said:
You have to install the correct adb drivers
Sorry, this is not the problem. These drivers I downloaded and installed already
As I said I can see the device and was able to unlock it.
- Any other ideas?
Thanks.
Click to expand...
Click to collapse
chronzz said:
can you post the video link
Click to expand...
Click to collapse
Have to look for it again. I saw it on my research to solve this problem I am having. When I find it again i will let you know for sure.
Anymore ideas anyone?
Thanks!
I had this problem yesterday (my first ever ROM flash!). I'm sure you didn't make this mistake, but my phone had to be on the boot (white) screen before it was recognized. When the phone was turned on normally, or off normally, I got the "Waiting for device" message.
FYI: I'm using Linux Fedora Core 12 on my PC.
Just had this problem. Jade this stupid mistake of not doing it while on the bootloader screen.
helipilotx said:
but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
That is THE best post i've ever read... just see the confidence
Perhaps the video he saw was of a holiday phone, in which case
Code:
fastboot oem lock
does work.
No good on our retail ones (yet) though.
helipilotx said:
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Love this post!!! +1 for post of the year!!!!
I first want to thank everyone at UnrEVOked for what they've done. I'm posting this because the UnrEVOked post doesn't really give any instructions. Its an easy enough root, but I know I've been there before and even the simplest things can be tough if things aren't laid out. So here's a step by step tutorial.
Due to some bugs, Unrevoked 3.2 was taken down shortly after being released, but the updated version is now LIVE! So obviously we're going to bring you a video tutorial on how to do it! Thanks to the guys at Unrevoked for giving us this simple solution to rooting the Droid Incredible.
LINK TO VIDEO WALKTHROUGH FOR HOW TO ROOT THE DROID INCREDIBLE
◄●REQUIRED DOWNLOADS●►
EVERYONE: Unrevoked3. Download the version for your OS.
WINDOWS USERS: unrEVOked modified USB driver
◄●How to Install HBOOT Drivers (Windows Users ONLY)●►
If you're using Windows, you're going to have to install the HBOOT drivers first. You can follow this video tutorial:
How to Install HBOOT Drivers
and follow along with these written instructions provided by the Unrevoked team:
Download the unrEVOked modified USB driver and expand it somewhere you will remember.
Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
Open Device Manager.
Click Start, then right click on Computer, then click Properties, then click Device Manager.
Under Other devices, you should now see the Android 1.0 device.
Right click on Android 1.0 and click Update Driver Software:
Click on Browse my computer for driver software.
Click on Browse and select the Android USB Driver folder on on your computer, click ok, then click next.
You should get a status bar indicating that the driver is installing. If you get any warnings, just click Ok.
Your driver should install.
Click Close and make sure Android Bootloader Interface is listed under Android Phone.
◄●Instructions●►
Make sure you downloaded Unrevoked3 for your OS.
If you're on Windows, make sure you "uninstall HTC Sync or any other program that might talk to the phone over USB (doubletwist, etc). They will cause problems" (Unrevoked.com).
Plug your phone into your computer with USB.
Drag down from the notification bar on your phone and select "Charge Only" and "Remember this"
Make sure your phone has USB Debugging turned on by going to Menu>>Settings>>Applications>>Development and checking USB debugging.
Run the Reflash application that you downloaded.
Unrevoked will run its processes. Follow the few instructions it gives and thats it!
You're now rooted!
PS - Others have asked elsewhere if it flashes a custom recovery. Yes, it flashes Clockwork
Be sure to wait for S-OFF to install before unplugging phone!
shoman24v said:
Be sure to wait for S-OFF to install before unplugging phone!
Click to expand...
Click to collapse
Thanks for reporting that
thanks, one question, maybe more later.
after this is done, then what. do i really need to do anything else. is this where the fun begins, like i really only want to remove the bloatware. but if i want, can i just leave it rooted and do nothing with it. i am a total noobie and even this "one click" thing has me scared and confused. thanks for the post.
Once you're done, you can remove bloatware. And yes, if you so choose, you can do nothing at all
So that mean's that Unrevoked for the Incredible automatically applies S-OFF?
imaqine said:
So that mean's that Unrevoked for the Incredible automatically applies S-OFF?
Click to expand...
Click to collapse
Yes.
The message you have entered is too short. Please lengthen your message to at least 10 characters. FU
imaqine said:
So that mean's that Unrevoked for the Incredible automatically applies S-OFF?
Click to expand...
Click to collapse
Yeah the Incredible is one of the phones that it does S-OFF for.
Anybody having any troubles?
djR3Z said:
Anybody having any troubles?
Click to expand...
Click to collapse
ive had root from way before the one click method ..the hard way
my bro just got a incredible and went thru everything and it all,
it kind of worked out for him
except it didnt give him clockworkmod icon at the end
...he has s-off and super user
i told him to get rom manager and look and see and it says it is there 2.5.0.5 but when he robots into recovery it goes to a black screen white lines on sides ..same with manual
any ideas?
chrisloveskaos said:
ive had root from way before the one click method ..the hard way
my bro just got a incredible and went thru everything and it all,
it kind of worked out for him
except it didnt give him clockworkmod icon at the end
...he has s-off and super user
i told him to get rom manager and look and see and it says it is there 2.5.0.5 but when he robots into recovery it goes to a black screen white lines on sides ..same with manual
any ideas?
Click to expand...
Click to collapse
Thats odd, but you should be able to just flash a custom recovery separately. Did ROM Manager ask to install clockwork recovery?
edit: fixed my problem on my own xD
chrisloveskaos said:
it says it is there 2.5.0.5 but when he robots into recovery it goes to a black screen white lines on sides ..same with manual
any ideas?
Click to expand...
Click to collapse
Search for SLCD recovery.
Sent from my ADR6300 using XDA App
devlp1213 said:
edit: fixed my problem on my own xD
Click to expand...
Click to collapse
Sweet haha
Which version of Android needs to be on the phone? 2.1, 2.2, or does it not matter?
enigmatl said:
Which version of Android needs to be on the phone? 2.1, 2.2, or does it not matter?
Click to expand...
Click to collapse
It doesn't matter.
djR3Z said:
It doesn't matter.
Click to expand...
Click to collapse
just not the latest one with the v-cast app store.
Unrevoked is not working with the latest OTA as of this posting.
ncwildcat said:
Unrevoked is not working with the latest OTA as of this posting.
Click to expand...
Click to collapse
Yea I just got my refurb and now I am stuck at........sToCk....eeewww
You can find it on:
http://alpharev.nl/
HBOOT 1.0+ is NOT supported
MOD EDIT: No shouting please!
Boot from ISO and follow instructions yea? Is it safe to boot from USB?
i have 1.0
it works
Damn, why not at my device....?!
http://forum.xda-developers.com/showpost.php?p=10176241&postcount=130
aikon96 said:
Damn, why not at my device....?!
http://forum.xda-developers.com/showpost.php?p=10176241&postcount=130
Click to expand...
Click to collapse
Nand backup CM 6.1, pull the backup to your PC (just to be sure). Install a rooted stock ROM, then try.
ogo2 said:
it works
Click to expand...
Click to collapse
I can't get it to work.. can't access fastboot in step 1 tried power for several minutes..
whitetigerdk said:
I can't get it to work.. can't access fastboot in step 1 tried power for several minutes..
Click to expand...
Click to collapse
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Suppe123 said:
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Click to expand...
Click to collapse
Jeeeezz-US! You were lucky...
Ok maybe we should use this thread
Suppe123 said:
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Click to expand...
Click to collapse
Same problem, haven't been able to find a solution so far
when cell is in hboot usb plug, before turn in fastboot try to navigate with vol+ and vol - and when you see it isn't freeze, push anykey of pc and when it says turn your phone into fastboot do it.
juanporrero said:
when cell is in hboot usb plug, before turn in fastboot try to navigate with vol+ and vol - and when you see it isn't freeze, push anykey of pc and when it says turn your phone into fastboot do it.
Click to expand...
Click to collapse
Tried that, even tried going into fastboot, and back to HBOOT doesn't work either
I've got bootloader 0.43.001 I had the keep it simple froyo rom installed when trying. I'll try the keep it simple eclair rom now
JonasDroid said:
Tried that, even tried going intofastboot, and back to HBOOT doesn't work either
I've got bootloader 0.43.001 I had the keep it simple froyo rom installed when trying.
Click to expand...
Click to collapse
Same thing is here
does this mean we can now change the partitions sizes?
eclair rom didn't help either, didn't really expect it to help but it was worth the try.
Any other suggestions? looks like much off us have this problem
How did you burn the iso (the ones with the fastboot problem)?
I burned it using the build in windows image burner onto a CD. I might try a USB later on but I'll stop trying for now
i do it with azure
Threadstarter,
Can you provide us a complete steps (Tutorial)on how to S-OFF the Hboot ? I totally do not understand, as i have never flash such thing before. I'm using the rooted HTC official Froyo ROM found in xda forum
foosoomin said:
Threadstarter,
Can you provide us a complete steps (Tutorial)on how to S-OFF the Hboot ? I totally do not understand, as i have never flash such thing before. I'm using the rooted HTC official Froyo ROM found in xda forum
Click to expand...
Click to collapse
Burn the iso and boot from it. The rest of the instructions are given to you as you go
Swyped from my HTC Legend
Is it normal that you need to press the power at the right time 2ce?
I managed to get past the first by some pretty stupid method which I'm not going to make public if I'm not sure that it works (cause it's pretty risky)
But that same method doesn't work the second time in step 2/3.
Or isn't it supposed to ask for that a 2nd time?
So I had to pull my battery out in the 2nd step and it showed a message that it was unable to flash the HBoot but luckily the old was still intact.
S-OFF on first try
I used unetbootin to make a usb boot pen, then boot into tiny core, followed instructions and S-OFF
A couple of days ago I thought it would be a GREAT idea to install a GSM ROM (Android Revolution HD) on my Sprint HTC One. I am now able to go into the recovery and flash a different ROM, but the ROM will boot up but shut down several seconds after reaching the home screen. I have been told that using an RUU might help, but will that work even if my computer doesn't recognize my phone as a USB device? All help is appreciated
EDIT: FIXED THANKS TO BIGDADDY619'S GUIDE ON THE SECOND PAGE
Spadman1234 said:
A couple of days ago I thought it would be a GREAT idea to install a GSM ROM (Android Revolution HD) on my Sprint HTC One. I am now able to go into the recovery and flash a different ROM, but the ROM will boot up but shut down several seconds after reaching the home screen. I have been told that using an RUU might help, but will that work even if my computer doesn't recognize my phone as a USB device? All help is appreciated
Click to expand...
Click to collapse
Maybe you screwed your radio but i'm not sure this is the answer to your problems... To be able to run a RUU your pc MUST recognize your phone in fastboot mode.
I repaired a friends device that did the same thing. When it boots you will see a lock screen with no wallpaper and then it will shutdown.
An RUU is the ONLY way to fix it.
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
An RUU is the ONLY way to fix it.
Click to expand...
Click to collapse
There's nothing special about an RUU, it's just a self extracting archive that uses fastboot to flash stuff.
It can be done by hand, such as with a nandroid backup.
Spadman1234 said:
A couple of days ago I thought it would be a GREAT idea to install a GSM ROM (Android Revolution HD) on my Sprint HTC One. I am now able to go into the recovery and flash a different ROM, but the ROM will boot up but shut down several seconds after reaching the home screen. I have been told that using an RUU might help, but will that work even if my computer doesn't recognize my phone as a USB device? All help is appreciated
Click to expand...
Click to collapse
Pm me i can help you fix it I'm on Sprint and have helped several members fix their phones
Sent from my ElipticNexus7
matt95 said:
Maybe you screwed your radio but i'm not sure this is the answer to your problems... To be able to run a RUU your pc MUST recognize your phone in fastboot mode.
Click to expand...
Click to collapse
Okay, I'll try to get my compooter to recognize it in fastboot (that's from the bootloader right?)
altimax98 said:
I repaired a friends device that did the same thing. When it boots you will see a lock screen with no wallpaper and then it will shutdown.
An RUU is the ONLY way to fix it.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Alright thanks I'll try the RUU.
bigdaddy619 said:
Pm me i can help you fix it I'm on Sprint and have helped several members fix their phones
Sent from my ElipticNexus7
Click to expand...
Click to collapse
PM'd, thanks a lot
Spadman1234 said:
Okay, I'll try to get my compooter to recognize it in fastboot (that's from the bootloader right?)
Click to expand...
Click to collapse
Yep
bigdaddy619 said:
Pm me i can help you fix it I'm on Sprint and have helped several members fix their phones
Sent from my ElipticNexus7
Click to expand...
Click to collapse
You should explain how you fixed it here so everyone with that issue can check your method without opening thousands of threads about it
matt95 said:
Maybe you screwed your radio but i'm not sure this is the answer to your problems... To be able to run a RUU your pc MUST recognize your phone in fastboot mode.
Click to expand...
Click to collapse
When I go into fastboot, my compooter makes that duh-doo sound for connecting a USB device, but it never shows up as a device on my computer that I can transfer files to. Is this normal and/or is this good enough for the RUU to work?
Spadman1234 said:
When I go into fastboot, my compooter makes that duh-doo sound for connecting a USB device, but it never shows up as a device on my computer that I can transfer files to. Is this normal and/or is this good enough for the RUU to work?
Click to expand...
Click to collapse
Yeah that's enough, run the RUU while your phone is in fastboot mode and you'll be ok
matt95 said:
Yeah that's enough, run the RUU while your phone is in fastboot mode and you'll be ok
Click to expand...
Click to collapse
Alright thanks a lot I'll tell u if it works
Spadman1234 said:
A couple of days ago I thought it would be a GREAT idea to install a GSM ROM (Android Revolution HD) on my Sprint HTC One.
Click to expand...
Click to collapse
Don't do that!
but it's ok to eat fish cause they don't have feelings.....
raptoro07 said:
Don't do that!
but it's ok to eat fish cause they don't have feelings.....
Click to expand...
Click to collapse
Lol
matt95 said:
Yep
You should explain how you fixed it here so everyone with that issue can check your method without opening thousands of threads about it
Click to expand...
Click to collapse
I most definitely will once we get it going
Sent from my ElipticNexus7
matt95 said:
Yeah that's enough, run the RUU while your phone is in fastboot mode and you'll be ok
Click to expand...
Click to collapse
I've heard that there's no new version of the Sprint RUU or something, will whatever I have work for it anyway?
Spadman1234 said:
I've heard that there's no new version of the Sprint RUU or something, will whatever I have work for it anyway?
Click to expand...
Click to collapse
If you have S-OFF it will...
These instructions are for the Sprint variant only
You will need to be unlocked and have twrp installed for this to work (I'm posting this here because of my work schedule if you need further assistance PM back hopefully you and Matt can get it working )
1. Follow this guide Guide - Get s-off on 1.31 HTC One (Sprint) Update:
You will get a failed warning after issuing the echo blah blah command this is normal and nothing to be worried about and after the echo command type exit to exit the adb shell and continue.
2. Get the RUU here click the first link in the thread(extract it to your desktop/open it and click setup it will scan your device,go thru the various screens reading the warnings and checking the boxes, once it starts it will take 10-20 minutes to complete) once it's done you will be back to completely stock.
Optional:
Use revone to gain s-off (if you go with this option once you are s-off you won't need to use HTC-Dev to unlock your bootloader because revone does it for you) A sidenote about revone it will fail several times just press the UP arrow on your keyboard to issue the same command and press enter.Watch the cmd window for instructions to reboot and continue.
or flash a Sprint rom from the Sprint forum
Any other questions or concerns post here or PM me
Good Luck
BD619
bigdaddy619 said:
These instructions are for the Sprint variant only
You will need to be unlocked and have twrp installed for this to work (I'm posting this here because of my work schedule if you need further assistance PM back hopefully you and Matt can get it working )
1. Follow this guide Guide - Get s-off on 1.31 HTC One (Sprint) Update:
You will get a failed warning after issuing the echo blah blah command this is normal and nothing to be worried about and after the echo command type exit to exit the adb shell and continue.
2. Get the RUU here click the first link in the thread(extract it to your desktop/open it and click setup it will scan your device,go thru the various screens reading the warnings and checking the boxes, once it starts it will take 10-20 minutes to complete) once it's done you will be back to completely stock.
Optional:
Use revone to gain s-off (if you go with this option once you are s-off you won't need to use HTC-Dev to unlock your bootloader because revone does it for you) A sidenote about revone it will fail several times just press the UP arrow on your keyboard to issue the same command and press enter.Watch the cmd window for instructions to reboot and continue.
or flash a Sprint rom from the Sprint forum
Any other questions or concerns post here or PM me
Good Luck
BD619
Click to expand...
Click to collapse
This ^^^^ is gold thank you thank you thank you I'll do this tomorrow when I have time I'll tell you if it works (which it will)
FIXED!!! Thanks to bigdaddy616 and matt95! I used the guide from bigdaddy and it worked after a few minor problems (all from me not following directions.)
Thanks to all you guys!
Spadman1234 said:
FIXED!!! Thanks to bigdaddy616 and matt95! I used the guide from bigdaddy and it worked after a few minor problems (all from me not following directions.)
Thanks to all you guys!
Click to expand...
Click to collapse
Lol great news
Sent from my HTCONE using xda app-developers app
Bigdaddy please push to make this a separate sticky in here.
Also, could you post a warning/guide in the international forum?
Would be appreciated.
so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing
Bfitz26 said:
so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing
Click to expand...
Click to collapse
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?
Bfitz26 said:
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?
Click to expand...
Click to collapse
What exactly did it say?
TheOriginalKyle said:
What exactly did it say?
Click to expand...
Click to collapse
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.
Bfitz26 said:
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.
Click to expand...
Click to collapse
1. I believe our bootloader is locked, I don't think safe strap is necessary just make a backup before you flash anything too risky
2. For the custom recovery this method seems to work the best http://forum.xda-developers.com/showthread.php?t=2449670 it also explains #1 better. You can also flash Clockwork Recovery the difference is mainly personal preference. To get the latest TWRP on you'll need to flash the .img then when it's all set up flash the .zip.
3. For the failed efs partitions here's a link to back that up (I had no idea that was a problem). http://forum.xda-developers.com/showthread.php?t=2451390 I only used this when I flashed a different radio, also the only brick that I know of is with FreeGee on 12b but that's the lazy way and who knows maybe he fixed it.
4. ROM's will usually tell you what is compatible and what isn't, if you have the latest TWRP or CRP you should be fine on 12b just read the instructions and scan the comments for issues.
Glad I could help
Thanks!
Sent from my VS980 4G using Tapatalk