Database Info

Shell Root? And Hboot

What is this? I tried to root my phone with unlock root and it says failed shell root permission. How am I supposed to get this and another question, I have hboot 1.45.... But my software number is diff. Is that a problem?
Sent from my myTouch_4G_Slide using xda premium

Try unlocking through HTCdev.

Unlock using HTCdev, flash CWM, flash superuser.zip. Done, you're rooted.

HappyKhicken said:
Unlock using HTCdev, flash CWM, flash superuser.zip. Done, you're rooted.
Click to expand...
Click to collapse
This is very true. There's a couple stickys in the dev section about this. Blue has a huge guide on how to do this, there's even a tool that'll do it all. Try using Hassons Toolkit. Simple as hell, best tool for any HTC phone.
Sent from my MIUI V4

I also suggest gaining S-off. It'll eliminate a couple steps when flashing new ROMs.

HELP!!!! Please

Hey Guys,
My phone is stuck on the HTC logo with the little red message about development blah blah blah........... What do I do????

That depends on what you did or what you were trying to do.

You gotta give us more than that. Are you rooted? Unlocked boot loader? Can you reach recovery (hold down bottom volume rocker and power button)? If so, go to recovery, and use the 1.85 RUU found in the development section. Make sure your phone is in recovery.
Sent from my HTC One X using xda app-developers app

ethomas94 said:
You gotta give us more than that. Are you rooted? Unlocked boot loader? Can you reach recovery (hold down bottom volume rocker and power button)? If so, go to recovery, and use the 1.85 RUU found in the development section. Make sure your phone is in recovery.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ok tried running 1.85 RUU while in Recovery (TWRP) still erroring out. I'm unlocked and rooted. Any ideas??????????????

nonono. dont do the ruu when you are in recovery. instead of going to recovery in bootloader, go to fastboot. then on pc fastboot oem lock and run ruu, this will most likely fix your problem. whether or not you're problem can be fixed with an easier solution i do not know.

ethantarheels123 said:
nonono. dont do the ruu when you are in recovery. instead of going to recovery in bootloader, go to fastboot. then on pc fastboot oem lock and run ruu, this will most likely fix your problem. whether or not you're problem can be fixed with an easier solution i do not know.
Click to expand...
Click to collapse
Thanks man finally!! Now how would i go about rooting again and flashing a rom since the phone is not rooted and locked again??? Sorry for newb questions iphone user for 6 yrs.... Thanks for all your help!!

do you still have the unlock_code.bin file from when you unlocked it? if not on your computer check your email cuz htc emailed them to you. then boot phone into fastboot and fastboot oem unlock with the unlock code. then look in some of the stickies for how to root 1.85 to get a batch file that flashes cwm for you automatically. once you flash cwm, flash the super user root file to root it. then you're good to go!! however i recommend you immediately install twrp over cwm.

ethantarheels123 said:
do you still have the unlock_code.bin file from when you unlocked it? if not on your computer check your email cuz htc emailed them to you. then boot phone into fastboot and fastboot oem unlock with the unlock code. then look in some of the stickies for how to root 1.85 to get a batch file that flashes cwm for you automatically. once you flash cwm, flash the super user root file to root it. then you're good to go!! however i recommend you immediately install twrp over cwm.
Click to expand...
Click to collapse
I updated to 4.0.4 is their root for this???

ealvinito said:
I updated to 4.0.4 is their root for this???
Click to expand...
Click to collapse
There's not gonna be root for 4.0.4 for a while. But sit tight.
Sent from my HTC One X

Unlock the bootloader again install twrp recovery. Then install root. Done.

gunnyman said:
Unlock the bootloader again install twrp recovery. Then install root. Done.
Click to expand...
Click to collapse
Done. Unlocked and rooted running illuminati 4.0.4 and loving the smoothness. Thanks for the input.
Sent from my HTC One X using xda premium

gunnyman said:
Unlock the bootloader again install twrp recovery. Then install root. Done.
Click to expand...
Click to collapse
Yeah I don't know why in the age of TWRP people still use CWM. Unless your ROM requires it that is. Swiping vs messing around with the volume button, nuff said

TWRP doesn't load (stuck at htc screen)

Hi there,
just got a One X and wanted to install a custom Rom. Did bootloader unlock and installed TWRP with Toolkit. As I'm on Windows 8 I couldn't do the root part, if I'm not mistaken this is not needed and the custom ROM will be rooted anyway..? So TWRP installed successfully and I cleaned Cache but it doesn't start when i select recovery in HBOOT it stucks at the green HTC logo.. Is there any advice? Thanks in advance..

Edit: also just noticed that you did not root. You really need to do that before trying to install a ROM. I know you unlocked the boot loader but rooting is still needed to access system files. With out that, it is pointless. Find a Linux or windows 7 mention.
Better yet just run a live USB within Linux. That should work. Ooh, I wonder can you boot using your phone since it can be considered a mass storage device....probably not. Sorry off topic.
My guess is that windows 8 probably isn't reading your phone correctly. But you said you unlocked the boot loader. Try to manually install twrp
Sent from my Carbon-ize Evita using xda-developers app

TacoLoco said:
Hi there,
just got a One X and wanted to install a custom Rom. Did bootloader unlock and installed TWRP with Toolkit. As I'm on Windows 8 I couldn't do the root part, if I'm not mistaken this is not needed and the custom ROM will be rooted anyway..? So TWRP installed successfully and I cleaned Cache but it doesn't start when i select recovery in HBOOT it stucks at the green HTC logo.. Is there any advice? Thanks in advance..
Click to expand...
Click to collapse
Just download the latest HTC sync from HTC website and it Will install drivers you need, you can then leave sync or uninstall it and drivers will remain.
Sent from my HTC One X using xda premium

How are you going to access twrp if you do not have root and super user?
Good luck with that.
Sent from my HTC One X using xda premium

If the bootloader is unlocked, there's no need to root. They are independent of each other.
Check md5 on your recovery file and reflash. Then do fastboot erase cache and try going to recovery.
Sent from my One X using xda app-developers app

I thought unlocking the BL and root was co-dependant. You can root but can't install ROMs until the BL is unlocked. Or you could unlock boot loader but can't touch system files until you gain root access.
Or did I miss understand? Which is why rooting alone nor unlocking the BL alone is not the only step in installing a ROM.
Sent from my Carbon-ize Evita using xda-developers app

Herc08 said:
I thought unlocking the BL and root was co-dependant. You can root but can't install ROMs until the BL is unlocked. Or you could unlock boot loader but can't touch system files until you gain root access.
Or did I miss understand? Which is why rooting alone nor unlocking the BL alone is not the only step in installing a ROM.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
I will explain further.
For ATT One XL root was needed prior to unlocking the bootloader to allow you to write to system files(which is no longer possible as of 3.18), and be able to change the CID in order to allow HTCDEV to provide the Unlock_code.bin to unlock your bootloader. This is probably where your confusion stems.
IF, like every other carrier, ATT allowed you to unlock the bootloader, you would not need to have rooted to be able to unlock your bootloader, you could have just unlocked it and then flashed TWRP. At that point you could flash a rooted rom or allow TWRP to root your rom for you. (For some rom versions, I believe anything under 3.18)
Hope this cleared some stuff up for you! :good:

Ah makes perfect since now. Darn AT&T and their lock downs.
So basically Rogers and Telstra can root just by unlocking and that's it. No exploit needed. And of course flashing twrp and a rom
Sent from my Carbon-ize Evita using xda-developers app

Herc08 said:
Ah makes perfect since now. Darn AT&T and their lock downs.
So basically Rogers and Telstra can root just by unlocking and that's it. No exploit needed.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Correct!

Phone won't get past boot screen

Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?

mikel.canovas said:
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
Click to expand...
Click to collapse
Can you get to bootloader? Fastboot access? You were soff previously correct?
Sent from my One Xl using Tapatalk 2

jrior001 said:
Can you get to bootloader?
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel

mikel.canovas said:
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/evita
From twrp's site grap the 2.6.3 recovery.IMG and with phone in bootloader where you see "fastboot usb" type in cmd promt fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
And the fastboot reboot-bootloader
Then navigate and try to get to recovery again
If you get that far flash ROM again, just that for now and relax for a bit
Sent from my One Xl using Tapatalk 2

Getting an error after writing recovery. Saying FAILED (remote: not allowed)

mikel.canovas said:
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
Click to expand...
Click to collapse
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2

jrior001 said:
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
No bootloader is "relocked". I was in fastboot when I ran the RUU since ADB is not being recognized when in bootloader. RUU was successful, didn't seem like anything went wrong

Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.

redpoint73 said:
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
Click to expand...
Click to collapse
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work

mikel.canovas said:
Bootloader says relocked.
Click to expand...
Click to collapse
You need to unlock bootloader again to flash TWRP.

unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel

mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
Click to expand...
Click to collapse
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2

mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Click to expand...
Click to collapse
Using the unlock token is known to sometimes fail and require repeated attempts, just keep trying.
Not sure why the RUU didn't work, that is weird.

jrior001 said:
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
I've done the RUU twice now. Same results. Was s-off with 2.14 hboot

mikel.canovas said:
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
Click to expand...
Click to collapse
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita

timmaaa said:
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader

mikel.canovas said:
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
Click to expand...
Click to collapse
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita

timmaaa said:
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
Click to expand...
Click to collapse
Then why has it failed 3 times? RUU is reporting successful. So what's the error?

Which error code is it giving you?
Sent from my Evita

timmaaa said:
Which error code is it giving you?
Sent from my Evita
Click to expand...
Click to collapse
RUU gives no error. It shows that it's successful

[Q] Brick?

I am trying to restore my device to stock but i am unable to. Im trying to use the ruu. but i keep getting the 155 error. I relocked my bootloader but its not working. im using a telus htc one. My hboot is: 2.15.000 and radio 1.13.50.05.31. No os btw
But i can get to the bootloader

I might be wrong, but as far as I'm aware, it can't work on a locked bootloader, so you'll need to unlock it again.
Make sure you're using the correct ruu, double read the instructions for flashing it...
That's the most I can say, I don't really have that much experience in this.
Also, another option will be to send the stock ROM.zip to the phone using adb, flash a custom recovery, and boot into recovery and flash the ROM.

i could have swore that it needed to be locked. and to do adb,i need a os

still doesnt work

izzyisawesome said:
i could have swore that it needed to be locked. and to do adb,i need a os
Click to expand...
Click to collapse
If you already have a custom recovery, you can use adb there without an os
Sent from my XT1032 using XDA Free mobile app

The suggestion to relock the bootloader seems to be confirmed by this post: http://forum.xda-developers.com/showthread.php?t=1655832
If you didn't do it, you also need to restore the stock recovery.
Do you still have error 155?

tzzeri said:
If you already have a custom recovery, you can use adb there without an os
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Whenever i install a custom recovery, it doesnt show up

kdd998 said:
The suggestion to relock the bootloader seems to be confirmed by this post: http://forum.xda-developers.com/showthread.php?t=1655832
If you didn't do it, you also need to restore the stock recovery.
Do you still have error 155?
Click to expand...
Click to collapse
I relocked the bootloader. I installed the stock recovery,from another post. i am pretty sure its the right one. yes i keep getting that error

If you want to be sure of the recovery you can find the good one in the RUU. You'll find guides to get the firmware.zip from the RUU on XDA.

Same problem here. Anyone have a android backup I can try?