5,594,653 Members 32,774 Now Online
XDA Developers Android and Mobile Development Forum

[Q] bootloader help

Tip us?
 
freckzula
Old
#1  
Member - OP
Thanks Meter 4
Posts: 43
Join Date: Oct 2013
Default [Q] bootloader help

im in bootloader menu on my htc. i lost superuser access, and all root apps wont work either. im tryin to update superuser but cant get anything to work. please help
 
projektorboy
Old
#2  
Senior Member
Thanks Meter 88
Posts: 404
Join Date: Sep 2010
Location: Phoenix, AZ
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM

If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?

For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.

Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?

If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.

Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en

ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu

Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053
 
freckzula
Old
#3  
Member - OP
Thanks Meter 4
Posts: 43
Join Date: Oct 2013
Quote:
Originally Posted by projektorboy View Post
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM

If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?

For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.

Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?

If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.

Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en

ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu

Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053


i ran rummer a month or so ago. i had s-off and on bootloader menu it says unlocked. when i click on recovery it just reboots. when i first did this i never flashed twrp. i did a root check when i did rumrunner it said root access granted. now when i check it it says no root access, and my superuser is gone. i tried dl all sdk again, but i cant get comp to find phone in cmp. i also tried to launch rumrunner again ,, it rebooted phone few times then ended with stupid problems with phone press enter to exit. im about to throw in towel after hours of trying different things..
 
freckzula
Old
#4  
Member - OP
Thanks Meter 4
Posts: 43
Join Date: Oct 2013
Quote:
Originally Posted by projektorboy View Post
It sounds like perhaps you took an OTA and it replaced a lot of things, including removing root access and possibly placing you back on Stock Recovery instead of TWRP or CWM

If you're actually at the bootloader menu, does it say "UNLOCKED" at the top? I assume you've also done Rumrunner's S-OFF at some point, right?

For you to ever have had root access at some point, it means that you flashed in a custom recovery and flashed in a Superuser package ZIP file.

Being at the bootloader menu gives you the option to go to fastboot, or to go to recovery. What happens when you go to Recovery?

If you have a custom recovery (TWRP or CWM) then you'll have the option to ADB Sideload a ZIP file for installation to your phone.

Koush keeps his Superuser.zip in the description of his app on the Play Store: https://play.google.com/store/apps/d...uperuser&hl=en

ChainFire keeps his SuperSU.zip here: http://download.chainfire.eu/supersu

Don't forget to get more info about SuperSU from his official thread at http://forum.xda-developers.com/show....php?t=1538053


this also all started after verizon came out with update and phone automatically updated but unsuccusfully
 
projektorboy
Old
#5  
Senior Member
Thanks Meter 88
Posts: 404
Join Date: Sep 2010
Location: Phoenix, AZ
Thank you for re-affirming my suspicion that an OTA put you in this position.

Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.

Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.

The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\

Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)

Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.

If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.
The Following User Says Thank You to projektorboy For This Useful Post: [ Click to Expand ]
 
freckzula
Old
#6  
Member - OP
Thanks Meter 4
Posts: 43
Join Date: Oct 2013
Quote:
Originally Posted by projektorboy View Post
Thank you for re-affirming my suspicion that an OTA put you in this position.

Rumrunner wasn't ever going to help you in your situation. Rumrunner is purely for achieving S-OFF. Since you're still S-OFF, it didn't have anything to do with your phone. Your root access is gone because the OTA wiped it out. It's important to always be careful about OTA updates because OTA updates assume that you NEVER modified your phone and will write whatever they want to wherever they want.

Since you can at least get to the bootloader, your phone can be saved. You said that you tried to update your SDK so that you could have the fastboot files available. When you run the SDK updater (I assume you're on Windows) you have to right-click and run as Administrator to make it work.

The files you want for fastboot are hiding in c:\program files (x86)\Android\android-sdk\platform-tools\

Take adb.exe, fastboot.exe, adbwinapi.dll, and adbwinusbapi.dll and copy them to a separate folder. (Such as C:\adb\) Navigate to that folder and do shift+right-click in a blank area of the folder so you can run a command prompt. You will want to put a ROM and a recovery file in this same folder too. (You sound like you want the stock ROM)

Use the command 'fastboot devices' to see if the phone shows up. If the phone doesn't show up, then you need to go to the HTC Website so you can install HTC Sync, then remove Sync (while leaving the drivers behind) so that your phone has the correct drivers to make it show up in fastboot.

If 'fastboot devices' ends up revealing a device, then you can grab a custom recovery image file and do "fastboot flash recovery filename.img" to put a custom recovery in your phone. Then within the custom recovery you can do adb sideload romname.zip to install a ROM and that should put your phone back into a usable state.


Ty for walk through! Will try tomorrow! I wanna get kit kat on here. I think some problems were from files on comp in wrong folders. Hope this works
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


TRENDING IN THEMER...