Develop Bugs

Need help with root

I just got a replacement evo and I updated it to 3.30.651.3 and my hardware ver. is 003..And i can not get root Please any help would be great ..thanks

i am ALWAYS open to helping people root. it seems the tutorial to do would be here
http://forum.xda-developers.com/showthread.php?t=829045
the problem is, all the files are for 0004 hardware so it would screw up your 0003. better just sit tight until they release the 0003 ruu cracked, patched, and engineering files. once again, open to help people.
dk

Thank you i can wait i tell you running stock isnt bad my battery life is crazy long...

Just as a last check, you might want to search the threads to see if any of the methods work for 0003. I might recommend just waiting though because the other methods seem a little shotty. The one I linked makes perfect sense and sounds foolproof. I doubt htc could have thought out that loophole.

Yeah cool thanks for your help

What is the manufacture date of your phone did it come with 3.30?
Sent from the edge of hell

there is now a method for rooting hardware 003 running hboot 2.02.

dkdude36 said:
there is now a method for rooting hardware 003 running hboot 2.02.
Click to expand...
Click to collapse
Send link please?

its in the dev section. zi(something) wrote it up. the only thing missing was a tweaked custom recovery. if you need help pm or email/ichat me ([email protected] for all of them)
good luck ot you all
dk

I have hardware 0003, and the method you linked got me rooted. Took a couple attempts on a few of the steps, but end result is s-off, amon-ra recovery, still using hboot 2.02 however. I didn't see the need of downgrading hboot. Be careful when flashing roms though, as only htc kernels will allow the camera to work at the moment. (to the best of my knowledge). I'm more than happy to help, too, if you have any other questions.
Feel free to gtalk me or email me. [email protected]
Sent from my HTC SuperSonic 4G using the XDA app.

the point of downgrading is to allow unsigned pc36img.zips, and to have fastboot commands. these can be used for major developing, or simply changing your splash screen. not much of a purpose, but a purpose.

edit
I realized you meant changing splash through adb, my fault. Good point about the fastboot, though. I haven't tried the .zips either. I may downgrade yet.
Sent from my HTC SuperSonic 4G using the XDA app.

Be careful when downgrading. You could be bricked. I would recommend not downgrading until you do something that requires it. How do you flash splash screens without adb?

Flashable zips through recovery. Shift has a thread around here somewhere I got the one I'm using atm.
Sent from my HTC SuperSonic 4G using the XDA app.

I didn't know that was possible. Well it makes sense because wimax, radio, pri, nv, and boot .img are all installable with some tricky coding through recovery. Why not the splash1 partition too...

stock device, can I RUU to older updates?

Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks

Is the phone s-off?
Sent from my PC36100 using XDA App

badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.

animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?

badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.

badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.

pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?

pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?

animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk

badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.

pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.

pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk

tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk

tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...

@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.

badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App

GB OTA and the new hboot 0.82.0008- lots of questions

I haven't flashed the new hboot yet. I'm currently running CM7 and have the eng hboot 0.76.2000 with s-off.
As promised, here are the questions:
1) Has anyone flashed the new hboot and tried to restore a custom rom?
2) If I flash the new hboot (0.86.0008) will I be able flash back to the eng hboot?
3) What are the differences between the two? I usually use cwm/recovery, but if I need the hboot, I would like to be able to flash all the partitions. Is this still possible with the SHP version?
4) the nb0 files seem like I could flash them via "flash hboot" and skip the zip or disk destroy. Does this make anyone nervous?
5) I lost track of all the rooting going on... I rooted with gfree before there was a version number. Is there a root method that unlocks even more?
Thanks in advance... I've been playing with the ASUS transformer lately which has an unlocked, unbrickable bootloader, so I know I should slow down before getting to flash happy with hboot.

Why do you want to flash a new hboot? Something wrong with your device or something?
Sent from my HTC Desire Z using XDA Premium App

This is one of those "If it ain't broke, don't fix it" things.
Sent from my T-mobile G2 using Tapatalk

The more you tell me not to do it, the more I want to flash it!
I'm just curious....

Same as u gee one, I wanna know. If no one ever tried new things cause what we had was "good enough" we would be years behind in progress in about every level of life.
Sent from my HTC Vision using XDA Premium App

Stick with the ENG HBOOT -- it has more of the fastboot commands enabled.

I think we all plan on sticking with eng hboot. Still doesn't answer the question about what is different with the new one.
Sent from my HTC Vision using XDA Premium App

Hboot changes are typically to add security (i.e., take away your freedom), not add new features or make anything better. Unlike the radio, it will NOT affect performance. This is just a bootloader, like GRUB or LILO. Once it hands the CPU off to the Linux kernel, its life is over. As long as it does that correctly, there is no reason to change it.

Thank you 234 I think that is the kind of answer we were looking for I would hit thanks but am on the mobile app.
Sent from my HTC Vision using XDA Premium App

I have flashed the htc desire hboot on the G2 and so far I'm still able to flash any rom for both the G2 and the htc desire .
Sent from my T-Mobile G2 using XDA Premium App

What "features" are missing from the existing hboot? If it aint broke dont fix it, definately a case of theres a new version must flash it must be better, think will stay on my old boring hboot that does what i need it to do until the wiki is updated.
Sent from a htc desire z

Hold my beer, I'm gonna flash the new hboot!
There's nothing wrong with hboot- I'm just asking about what differences there are. I never asked if it was better. I understand that it's not an engineering hboot, but I don't know what features are "missing" from it. This is the exactly the question that I'm asking. I know that flashing a new hboot will not increase my battery life or improve my radio reception. I know that flashing hboot can be dangerous and lead to bricked devices. I know that flashing hboot will not solve world hunger, resolve the world debt crisis, or bring peace in the Middle East.
I think if I asked about a new ROM, people would just tell me to flash it and find out for myself.
Flashing hboot can be dangerous and possibly brick your device. I do not recommend it. This thread is for entertainment purposes only!

gee one said:
There's nothing wrong with hboot- I'm just asking about what differences there are. I never asked if it was better. I understand that it's not an engineering hboot, but I don't know what features are "missing" from it. This is the exactly the question that I'm asking. I know that flashing a new hboot will not increase my battery life or improve my radio reception. I know that flashing hboot can be dangerous and lead to bricked devices. I know that flashing hboot will not solve world hunger, resolve the world debt crisis, or bring peace in the Middle East.
I think if I asked about a new ROM, people would just tell me to flash it and find out for myself.
Flashing hboot can be dangerous and possibly brick your device. I do not recommend it. This thread is for entertainment purposes only!
Click to expand...
Click to collapse
No offence buddy but why do you want to flash a new hboot then? You mention different ways to root but as far as I am aware the wiki is the "official" recommended way, will stick with what Ive got until such times as the wiki recommends changing my hboot,that is the only guide to rooting that I need.

I never said I wanted to flash it. I just asked what was different about it. What changed from the old stock hboot? Maybe the partition layout is different and there is more memory allocated to data? I don't know, hence the questions.
As some people have asked, if it ain't broke, then why fix it? Then why would HTC/T-Mo change it? I'm just curious about the changes.
I agree, for most users, they would never need hboot. The zipped up roms and radios are just fine for flashing in recovery.
sent from my cyanogen(mod) vision

I agree with you. There's nothing wrong with wanting to know what does the new hboot do. Furthermore, the only thing "wrong" with knowing more is that you get more awesome stuffs, kinda painful isn't it?
And, "if it ain't broke, then why fix it", why are we using HTC Vision here, not Nokia 1100, or better yet, smoke signal?

Holy thread resurrection, Batman !
Sent from my Desire Z running CM7.

He's got a good point though.

[Q] Stuck in limbo, need help!

I have posted several stuff about a situation I am having with my phone.... and I still cannot get it solved fully. I hope I can do it here.
I will try and summarize the situation with some key points.
First here is my current info....
Android Version 2.2.1
Baseband Version 2.15.00.03.04
Kernel Version [email protected]#2
Build Number 1.05.970.1 CL339957 release keys
Software number 1.05.970.1
PRI version 2.11_01c
PRL version 01001
Model Number PC36100
Supersonic DVT1 Ship S-ON
HBOOT-6.17.0001
MICROP-041f
TOUCH PANEL-ATMEL224_20aa
RADIO-2.15.00.03.04
Now I first rooted using revolutionary and got s-off properly.... I played with some roms and found it fun but not enough time to keep at it..... so I decided to s-on and go back to stock using un-revoked. That semi worked.... I got s-on.... but never lost the root. I still have recovery and everything still shows I have root except s-on.
Additionally, I tried to run the stock kddi ruu and i have gotten every error from 140, 170, 171 and even at one time 130...lol still no luck there. In doing all of that I figured out that the image version on my phone is 4.24.651.1 and I need to get to 1.05.970.1 (the stock kddi evo 4g) but cannot get it done.
Also I am HBOOT-6.17.0001 which is confusing in itself. xhausx helped me by giving me a nanadroid version of my kddi rom but that doesn't allow me to update anything and finding updates here is impossible unless I am running stock without root.
I am not sure if I need to flash a new misc partition, wipe my nand or something else and so not know how to do all of that..... can someone please please please help? I am willing to toss a small reward your way if we get me back to when I bought it.

I think you need to run the RUU for your phone; get it back to out of the box, stock, and just start over.

HipKat said:
I think you need to run the RUU for your phone; get it back to out of the box, stock, and just start over.
Click to expand...
Click to collapse
didnt you see this in my message????
Additionally, I tried to run the stock kddi ruu and i have gotten every error from 140, 170, 171 and even at one time 130...lol still no luck there.
if you have another RUU that I do not know about please let me know... because the one that I have from kddi is not working.
my current one is.... RUU_SuperSonic_K_KDDI_JP_1.05.970.1_Radio_2.15.00.03.04_NV_2.11_release_176711_signed.exe

You have a Japanese Evo, right?
Since it's a different phone, most of the people here will not be able to help you. I could tell you what to do if you had a American Evo, but it would probably either error out or further your problem.
Is there a forum for your specific version? Do things generally work the same as our Evos... like can you use the same RUU that I would use?
Sent from my Evo + MIUI using Tapatalk!

I was thinking if this will work somthing I might do if everything fails? Maybe you could try rooting it again and unroot?
Sent from my PC36100 using XDA App

plainjane said:
You have a Japanese Evo, right?
Since it's a different phone, most of the people here will not be able to help you. I could tell you what to do if you had a American Evo, but it would probably either error out or further your problem.
Is there a forum for your specific version? Do things generally work the same as our Evos... like can you use the same RUU that I would use?
Sent from my Evo + MIUI using Tapatalk!
Click to expand...
Click to collapse
The fact that I have a Japanese evo doesn't mean that anyone will not be able to help me. This is actually the place where the developers made the first RUU for the Japanese evo to begin with. There are plenty of pro's here.... we just need to find the right solution for me. Additionally, most everything works the same.... I cannot use the same RUU as you because the cid will come up different and cause me more probs.

culua said:
I was thinking if this will work somthing I might do if everything fails? Maybe you could try rooting it again and unroot?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have tried to run the root process again and it says in revolutionary that you already have s-off..... which in fact I do not.... and when I do the opposite process it just acts like its running the s-on and does nothing.

AgentTabasco said:
I have tried to run the root process again and it says in revolutionary that you already have s-off..... which in fact I do not.... and when I do the opposite process it just acts like its running the s-on and does nothing.
Click to expand...
Click to collapse
Sorry can't help you. I guess just flash stock Rom for now untill you found an answer for problem. Sometime it fix it self? Lol.
Sent from my PC36100 using XDA App

Fixed
I have fixed my phone since I last posted this thread... thanks to all those that helped me solve my issues.

[Q] Just Got DINC2. Need a little advice.

Just got a DINC2 replacement after 2 years with original dinc. My hope was to root and S-off ASAP. After a little searching I am not sure how to proceed. I have 0.98 bootloader with Android 2.3.4 and 5.10.605.9 software version.
I see that revolutionary does not have option for my bootloader. I also see a thread with a downgrade tool. I also saw a sticky saying not to download the bootloader.
Where do I go now with this?
Thanks.

If you have a way to get a xtc clip to get s off you will be ok. There are people that have been able to get s off with your software version but then have bootloop issues with sense roms. For some reason aosp roms are ok. There are many threads on this make sure you read up before deciding what to do. But I did read with the clip to get s off no issues with sense roms.
http://forum.xda-developers.com/showthread.php?t=1695414
http://forum.xda-developers.com/showthread.php?t=1659256

Thanks for the reply! This is very disappointing. I really do not want to shell out $50 on a clip. It seems all I can do otherwise is wait for an OTA or a fix.

If he's on the 5.x version he can downgrade, and then use revolutionary.
Sent from my vivow using Tapatalk 2

marcmarshall said:
Just got a DINC2 replacement after 2 years with original dinc. My hope was to root and S-off ASAP. After a little searching I am not sure how to proceed. I have 0.98 bootloader with Android 2.3.4 and 5.10.605.9 software version.
I see that revolutionary does not have option for my bootloader. I also see a thread with a downgrade tool. I also saw a sticky saying not to download the bootloader.
Where do I go now with this?
Thanks.
Click to expand...
Click to collapse
With the 5.x software, use the downgrade tool in development, and s-off with revolutionary.
Edit: sorry, just noticed tyler's post says almost exactly the same thing.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

Sorry looks like yours is not the newer software so you should be able to downgrade with revolutionary. Sorry if I miss guided you. There is a lot of people with the newer version having problems.

ok so what ive read here is if the phone is
SOFTWARE version 5.10.605.9
then downgrade + revolutionary. Hboot is .98, for what it's worth.
Also, another question, if the phone is past the 1 year warrenty, is it worth while to just use the HTCDev unlocking, or does this not 'fully' unlock the device to community needs?

gi812 said:
ok so what ive read here is if the phone is
SOFTWARE version 5.10.605.9
then downgrade + revolutionary. Hboot is .98, for what it's worth.
Also, another question, if the phone is past the 1 year warrenty, is it worth while to just use the HTCDev unlocking, or does this not 'fully' unlock the device to community needs?
Click to expand...
Click to collapse
Software version 5.x you should downgrade. It'll give you a lot more freedom.
Sent from my vivow using Tapatalk 2

Sorry for miss leading you at first. I downgraded with revolutionary and everything went great. There are some helpful videos on you tube on the downgrade process if you get stuck.