Develop Bugs

problems and questions with unlocking bootloader

Will this void my warranty even if the HTC developer site supports it and if it does is there a way to lock it? I also have problems while getting the codes I must send to HTC it just gets stuck on Waiting for device... Can anyone help me
Sent from my Galaxy Nexus

Hi
This may help you answer your first question
http://forum.xda-developers.com/showthread.php?t=1709782
To your second question:
No. If you unlock the bootloader you can never go back to
the same "Locked" state as before. So looking at the bootloader
it is always visible that the bootloader has been unlocked once.
And the third one:
Is your device listed when youn run
fastboot devices
If not - recheck your USB connection (e.g. Drivers)
More tips are found here
http://forum.xda-developers.com/showthread.php?t=1598964
My first try also failed on Win7 so I went back to my old PC with Vista where it worked
regards
max

That was great thanks a lot very informative. I followed the unlock bootloader tutorial but i don't remember any drivers.. can you link the drivers to me please ?
EDIT: Yes i have windows 7 but no older pc.. Ideas?
Also is there a way to remove sense and have stock ICS can't find any ROM that does that
Sent from my Galaxy Nexus

JamesInsights said:
That was great thanks a lot very informative. I followed the unlock bootloader tutorial but i don't remember any drivers.. can you link the drivers to me please ?
EDIT: Yes i have windows 7 but no older pc.. Ideas?
Also is there a way to remove sense and have stock ICS can't find any ROM that does that
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
http://www.htc.com/www/help/
"HTC Sync for all HTC Android phones", driver comes with Sync. Just make sure to disable the actual software after your install, it's kinda annoying and largely useless.

clxcoltz said:
http://www.htc.com/www/help/
"HTC Sync for all HTC Android phones", driver comes with Sync. Just make sure to disable the actual software after your install, it's kinda annoying and largely useless.
Click to expand...
Click to collapse
Great, Thanks!

Help with unlocking and rooting

I can't seem to get this to work. I'm trying to unlock my phone using the nexus toolkit but when I put my phone into fastboot mode and click the unlock option on the toolkit I just get '< waiting for device >'. Every video I watch just shows them plugging the phone in and then having the program unlock it for them. It's not doing the same for me. Any suggestions?

Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.

063_XOBX said:
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
Click to expand...
Click to collapse
Every guide and video I find uses that method. Do you have a link to the other method?

http://forum.xda-developers.com/showthread.php?t=1529058

063_XOBX said:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
I still get the 'waiting for device' when I do it this way too. I have the most current samsung drivers. I also did everything to set up ADB.

uninstall the drivers and reinstall using the naked drivers.

[Q] Uhh... How do you root 4.2??

I just got this phone and the guy who had it accepted the OTA to 4.2 It's the sprint variant. I've skimmed a few threads and checked out the toolkit but it only seems to go to 4.1.2
Any help??

Can't_Live_Without_My_Evo said:
I just got this phone and the guy who had it accepted the OTA to 4.2 It's the sprint variant. I've skimmed a few threads and checked out the toolkit but it only seems to go to 4.1.2
Any help??
Click to expand...
Click to collapse
Same instructions apply. Knock yourself out!
Sent from my Nexus 10 using Tapatalk HD

Efrants guide is stickied in the general nexus thread. Will tell you everything you need to know

Alright maybe we can help with this lol
I have the drivers installed, It says Samsung ADB device or whatever in device manager.
I have usb debugging enabled.
I hold the up and down button and power
Should it say "fastboot usb" or just fastboot, On my evo it said fastboot usb when connected.
I have the galaxynexusroot package from the asian guy which simply contains fastboot.
I open command window where it's at.
And type "fastboot oem unlock"
And it just says waiting for device. I'm certain the drivers are there.
What's my problem?

If boss don Efrant's guide can't get you there then try Google or use the search bar in xda.
I believe in you little buddy

namtombout said:
If boss don Efrant's guide can't get you there then try Google or use the search bar in xda.
I believe in you little buddy
Click to expand...
Click to collapse
I've utilized all 3, Now after installing the drivers from PDAnet which we're suggested by Efrant it just says Android 1.0 under device manager and I can't seem to update it.
And still no luck the unlocking. obviously due to the drivers.

I have the Samsung ADB interface installed. Do I need another driver? It seems I do, But I can't get anything to stick when I go into Fastboot.

http://forum.xda-developers.com/showthread.php?p=25477039
Follow instructions

namtombout said:
http://forum.xda-developers.com/showthread.php?p=25477039
Follow instructions
Click to expand...
Click to collapse
... I don't want to return to stock.
I am stock...
I want to unlock/root.

You can flash whatever rom you want after doing this.
Not sure if substituting the rom you want instead of the stock image will work. Try it and find out.

namtombout said:
You can flash whatever rom you want after doing this.
Not sure if substituting the rom you want instead of the stock image will work. Try it and find out.
Click to expand...
Click to collapse
We seem to be miscommunicating.
I have a new Galaxy Nexus from Sprint updated to 4.2.1
I'm trying to get the drivers installed properly to be able to unlock the bootloader.
I'm in no shape to be flashing any rom I want, Without the drivers installed first.

From efrant's guide, which seems to apply in all situations: "Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). "

bodh said:
From efrant's guide, which seems to apply in all situations: "Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). "
Click to expand...
Click to collapse
I've done this, But it still just shows "Android 1.0" with an exclamation mark while in fastboot.
I've uninstalled everything and I'm about to try again and see if something goes right this time.

Uhh, the guide suggests using universal naked drivers, not pdanet.. http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1

bodh said:
Uhh, the guide suggests using universal naked drivers, not pdanet.. http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
I'm trying to install the Universal Naked drivers right now, Window's find it but gives an error, It actually showed bootloader drivers too
It's saying
windows found driver software for your device but encoutered an error while attempting to install it.
google galaxy nexus bootloader interface.
the hash for the file is not present in the specified catalog file. the file is likely corrupt of the victim of tampering.
if you know the manufacter of your device, you can visit its website and check support section for driver software.
So.... What now.

Are you on windows 8? There are links to full write ups on the drivers in efrant's guide, pertaining to many different situations. With all the driver issues i've heard of, i'm glad to not need any!

bodh said:
Are you on windows 8? There are links to full write ups on the drivers in efrant's guide, pertaining to many different situations. With all the driver issues i've heard of, i'm glad to not need any!
Click to expand...
Click to collapse
Yeah I am on Win8 Which is bull****.
I'm not as new to this game as it may seem, And it barely makes any sense.
I've rooted many many HTC phones in my time.
I'm tempted to install windows 7 just to get this taken care of. But that's soooo much of a hassle.

Hope you found this and it does the trick: http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109

I'm now typing this message from Windows 7.
I'm willing to endure the hassle to get this beautiful device off from the stock rom
And I had already done that last thing you posted before anything else as soon as I realized that the drivers wouldn't even open to install

FINALLY got it thanks to Windows 7.

[Q] Received Ebay Phone, am I screwed?

Ok, I bought a galaxy nexus SCH i515 off ebay. The phone was listed as verizon, all the information behind the battery came up as sch i515. However when I powered it on. The phone said activate samsung account. The phone matches verizon info on the back. I contacted verizon and they said most likely the phone was rooted and that the phone could not be switched back even after a hard reset (which i did). I have wifi so used that to get on play store and downloaded rootchecker.... it says phone is not rooted.. (did original owner just unroot phone) am I screwed or is there anything I can do to get verizon able to activate it?

1) wrong section
2) follow this: http://forum.xda-developers.com/showthread.php?t=1626895
after step 2, check in the phone status menu for the model number.

So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)

loopers said:
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
Click to expand...
Click to collapse
I appreciate your quick informative answer but if i've already called verizon and they have informed me that the imei is not in their data base.... if i do all these steps and flash back to complete stock the imei still will not be in there data base correct? I mean I'm still stuck on this.... if I need to start asking somewhere else please let me know. Thanks

Just flash the factory images from Google. And make sure the ESN is good you can check it just Google search
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2

where is the factory images from google? Sorry i've been back and forth with seller and verizon and DO NOT want to screw this up

I see nothing specific from google search that says from a google site to flash these files to phone with steps

loopers said:
I see nothing specific from google search that says from a google site to flash these files to phone with steps
Click to expand...
Click to collapse
sorry found files

well found everythhing i need and loaded into the bootloader.. can't get it unlocked because it won't recognize fastboot devices..... it recognizes nothing. tried multiple ports.usb ports that is.... comes up with error code 214dfddsf i can't remember.... googled error.. no one really knows a fix.. if anyone knows of a toolkit for 4.1.1 or similar for samsung galaxy nexus let me know.... i've been trying to get my wifes phone activated for 6 1/2 hours and i'm done with it less you guys have a clear cut alternative.. i don't expect anyone to jump up and say here ya go but if ya do i'd greatly appreciate it.... i've googled the error to death.. no clear cut fix.... and i'm not trying to load up a rom.. i neeed to get the phone completely factory reset so i can get it activated from verizon..

oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....

loopers said:
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
Click to expand...
Click to collapse
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever

Pirateghost said:
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Click to expand...
Click to collapse
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb

loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Try wugs nexus root toolkit. More friendly for new users. Just Google the name and it'll come up.
Sent from my Galaxy Nexus using xda premium

loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL

as is strewn throughout these forums....ADB and FASTBOOT use different drivers. just because you have adb working doesnt mean that fastboot is setup properly

Sandman-007 said:
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
Click to expand...
Click to collapse
those are the drivers i have installed i think someone completely fudged this phone

those are all google nexus don't say anything about samsung version :\

fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope

loopers said:
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
Click to expand...
Click to collapse
No need to root, just install drivers, unlock bootloader and flash stock image, then lock the bootloader up..

Got it fixed. Tool kit worked. Txx
Sent from my SCH-I535 using Tapatalk HD

[Q] Unlocked on Day One...now stuck with S-ON! Help :-/

I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance

figaro1418 said:
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
Click to expand...
Click to collapse
ok so what you'll need to do is make sure you have working ADB and Fastboot on you PC and make sure they can see the phone.
First you want to get:
http://forum.xda-developers.com/showthread.php?p=42407269
once you have this loaded on your pc we are going to want to make sure it works. for simplicity im going to this a certain way once you get the hang of paths and how this all works you can choose to do it a different way.
first make a folder on your c drive fastboot
once you have that folder place all the contents of ADB and Fastboot from the link above into the folder.
from windows open up a command prompt. (search CMD.exe)
once opened we want to get to that directory so we type this :
cd c:\
once that is done lets plug phone into the pc
run command
adb devices
(output should look something like this)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\>
this means no devices are seen by the pc. This is okay, for now.
with the phone you are going to need to enable develop mode. to do so go to
settings > about > software information > more > click the build number on the screen about 10 times in a row.
if done correctly it will call you a developer in a toast notification.
back all the way out to settings and go to the bottom. you should see developer options now. accept the warrning and get into the options. you will see the option for USB debugging, we want to have this enabled now.
once this is all done run this command from the CMD.exe you had to open above
adb kill-server
then run
adb devices
(output should look something like this)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
***device name here***
you are now talking to the phone via ADB congrats.

...next step
Perfect! I'm up and running in adb. Thanks for the great instructions Now what should I flash?

I'm running bonestock and it's amazing. Haven't found the need to change. It runs awesome, everything works, simply amazing.
Sent from my iPhone 5s using Tapatalk 4

figaro1418 said:
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
Click to expand...
Click to collapse
Why do you say you're stuck with S-On? You can still S-Off, just so you know.

karn101 said:
Why do you say you're stuck with S-On? You can still S-Off, just so you know.
Click to expand...
Click to collapse
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.

Lock your bootloader?
Sent from my iPhone 5s using Tapatalk 4

Look at the HTC one toolkit by squabbi on the HTC one general forum ,it helped me get root back after taking the ota
Sent from my GT-P3110 using xda app-developers app

I was in the same situation as you in regard to HTC Dev unlocked on day one but still had S-On. What I did was flashed the Odexed Full ROM version: 1.10.605.10 from santod040 (http://forum.xda-developers.com/showthread.php?t=2485319) and then flashed the stock boot.img and signed-recovery.
However, after doing that I had one hell of a time with rumrunner, even though I was using the download for 1.10.605.10. It turns out, even though I was on the stock ROM I flashed above with the correct version my OS was showing 1.10.605.02 because I had one of the weird phones that shipped with that version instead of .08. Luckily for me since I had the stock boot.img and signed-recovery, I just did the OTA update to 1.10.605.15 and then used rumrunner for that version.
Also, no you don't need to lock your bootloader before doing that. I didn't.

bloodiedwraith said:
I was in the same situation as you in regard to HTC Dev unlocked on day one but still had S-On. What I did was flashed the Odexed Full ROM version: 1.10.605.10 from santod040 (http://forum.xda-developers.com/showthread.php?t=2485319) and then flashed the stock boot.img and signed-recovery.
However, after doing that I had one hell of a time with rumrunner, even though I was using the download for 1.10.605.10. It turns out, even though I was on the stock ROM I flashed above with the correct version my OS was showing 1.10.605.02 because I had one of the weird phones that shipped with that version instead of .08. Luckily for me since I had the stock boot.img and signed-recovery, I just did the OTA update to 1.10.605.15 and then used rumrunner for that version.
Also, no you don't need to lock your bootloader before doing that. I didn't.
Click to expand...
Click to collapse
synisterwolf said:
Lock your bootloader?
Sent from my iPhone 5s using Tapatalk 4
Click to expand...
Click to collapse
figaro1418 said:
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Click to expand...
Click to collapse
I had mine unlocked on day one as well. When RomRunner came out, I was able to run it just fine (unlocked).
Are you on a stock ROM? You can always make a backup, move those files to your computer, RUU to be completely stock, and then run RomRunner.
Once that's done, just bring over your backup and restore it in recovery.

figaro1418 said:
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Click to expand...
Click to collapse
It won't recognize it because that's what fastboot is for in the folder your adb is in. Don't type adb devices. Type fastboot devices. Then you'll see your mistake
Sent from my One using Tapatalk

karn101 said:
I had mine unlocked on day one as well. When RomRunner came out, I was able to run it just fine (unlocked).
Are you on a stock ROM? You can always make a backup, move those files to your computer, RUU to be completely stock, and then run RomRunner.
Once that's done, just bring over your backup and restore it in recovery.
Click to expand...
Click to collapse
He can't run the RUU because you have to be S-OFF to do that, hence why I put what I needed to do since I was in the same situation.

bloodiedwraith said:
He can't run the RUU because you have to be S-OFF to do that, hence why I put what I needed to do since I was in the same situation.
Click to expand...
Click to collapse
You don't need to be S-Off to do it. The signed RUUs are up.
Here's a link.
http://flyhalf205.com/?dir=RUU
Regardless, flashing a stock ROM is most likely the easiest route to go. I was just throwing up an alternative.