Develop Bugs

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

Hboot questions

So it seems as there is still some uncertainty in terms of updating to new hboot. Read some people lost root by doing so and read some were successful possibly due to having unrevoked forever installed. I updated to latest radio, wimax and nv already. Has anybody been able to downgrade the radio? I ask as it seems if downgrading is possible than unrevoked could be installed and then the hboot could be updated without losing root s-off. I appreciate any information and all your help.
Sent from my PC36100 using XDA App

starkillers said:
So it seems as there is still some uncertainty in terms of updating to new hboot. Read some people lost root by doing so and read some were successful possibly due to having unrevoked forever installed. I updated to latest radio, wimax and nv already. Has anybody been able to downgrade the radio? I ask as it seems if downgrading is possible than unrevoked could be installed and then the hboot could be updated without losing root s-off. I appreciate any information and all your help.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Why would you want to upgrade the hboot?

Was reading a few threads that suggest we should. I believe calkulin posted saying that he would update the hboot if it weren't for the fact that he uses fastboot commands during his development. Page 110 of his thread.
xHausx said:
Why would you want to upgrade the hboot?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

From what I've seen the new hBoots are all backward compatible, and as long as you have already ran Unrevoked Forever you *should* keep S-OFF, but the new hBoot has been particularly stubborn when it comes to abiding by the S-OFF. The extended commands on the eng-hBoot may not be very useful to most people but they can be very handy if something goes wrong and you manage to fubar your phone. So as long as you retain S-OFF or a custom recovery you should be ok using the 2.02 hBoot but I would wait awhile to find out more about ver 2.10. Especially if you plan on upgrading your radio.

I have already upgraded radio, wimax and nv and I don't have unrevoked forever installed . My hboot is the original with fastboot commands.
xHausx said:
From what I've seen the new hBoots are all backward compatible, and as long as you have already ran Unrevoked Forever you *should* keep S-OFF, but the new hBoot has been particularly stubborn when it comes to abiding by the S-OFF. The extended commands on the eng-hBoot may not be very useful to most people but they can be very handy if something goes wrong and you manage to fubar your phone. So as long as you retain S-OFF or a custom recovery you should be ok using the 2.02 hBoot but I would wait awhile to find out more about ver 2.10. Especially if you plan on upgrading your radio.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

I have 0.79, and as long as everything else is working, I don't see why it should be necessary to upgrade. And now that I've already updated all my radio's with the latest combo pack, I'm apprehensive about doing it anyway.

DarkAudit said:
I have 0.79, and as long as everything else is working, I don't see why it should be necessary to upgrade. And now that I've already updated all my radio's with the latest combo pack, I'm apprehensive about doing it anyway.
Click to expand...
Click to collapse
Same here except I think I'm at even a lower version... 0.76
What would the point be to upgrading hboot to 2.02? It's one thing I don't really understand all that well.
Anyone care to explain?

[Q] Can't unroot, "Main version is older"

I'm trying to unroot, but I keep getting "Main version is older, update fail!" when I try to flash any of the pc36img.zip files I've found. My HBOOT is 2.02.0000
Any ideas?
Thanks.
-TM

You need to flash a pc36img or run a RUU that is the same software version or newer. You're trying to flash an older software version and that's why you're getting that error.

Thanks. Do you know where I can find a recent PC36img.zip? I've been looking for about an hour now, everything I try is apparently old because I keep getting that error.

Try this one. It will bring you up to the current OTA.
http://forum.xda-developers.com/showthread.php?t=874091

Thanks, that looks like it should do it, but now I'm confused. I had 2.10, and I was easily able to root it with unrevoked. Why does that thread say that OTA is unrootable? Is the OP just outdated?

Goodluck
Sent from my PC36100 using Tapatalk

Yeah it's an old OP. 2.10 is rootable now so you should be able to re-root if need be. Can I ask why you're trying to unroot?

_MetalHead_ said:
Yeah it's an old OP. 2.10 is rootable now so you should be able to re-root if need be. Can I ask why you're trying to unroot?
Click to expand...
Click to collapse
My screen is popping up, and I've got to take it in to be repaired. Even though rooting has nothing to do with a defective gasket, I don't want them making a big deal out of it.

or, if u want to flash an older one, just flash toast's mtd-eng.img to the misc partition and it will allow you to flash whatever the hell you want.

ffolkes said:
My screen is popping up, and I've got to take it in to be repaired. Even though rooting has nothing to do with a defective gasket, I don't want them making a big deal out of it.
Click to expand...
Click to collapse
Try downgrading your HBOOT to 0.76 and use fastboot cmds to load up a new RUU rom with a kernel or however it'll fix that path there though for you hopefully it works.

alekosy said:
Try downgrading your HBOOT to 0.76 and use fastboot cmds to load up a new RUU rom with a kernel or however it'll fix that path there though for you hopefully it works.
Click to expand...
Click to collapse
Phones that ship with 2.02 or 2.10 cannot be downgraded to 0.76 without serious risk of bricking the phone. The partition tables are different on the newer HW versions.

illogos said:
Phones that ship with 2.02 or 2.10 cannot be downgraded to 0.76 without serious risk of bricking the phone. The partition tables are different on the newer HW versions.
Click to expand...
Click to collapse
BUT phones that dont ship with 2.02 or 2.10 but just upgraded to them can downgrade with little or no risk of brick.

Evo Unable to downgrade Radio Baseband

Spring Evo 4g
HBOOT: 2.10.0001
Model: PC36100
Hardware:0003
Android：2.2
Kernel 2.6.32.17
Baseband：2.15.00.11.19
Software3.70.651.1
PRI:1.90_003
Rooted with Unrevoked.
After upgrade Baseband, I got very bad signal and want to roll it back.
1. Tried to use cm recovery 2.6 to install zip file containing radio image to 2.05.00.06.10, not sucessful. However, every time it turn to 2.15.00.11.19 after reboot. I fell 6 vibrations during flash, do not know why.
2. Tried to use fastboot flash radio image，but I got "remote not allowed" message!
Could any body help out?
Thanks.
请高手们指点一下吧！谢谢谢谢！

2.10.0001 radio is non-downgradeable on new hardware models.

Your phone has the new block size that is not compatible with the old radios and the remote not allowed error is because you are not using the eng hboot. Unfortunately it is not compatible as is either.
You can force it to downgrade and I believe I found a way to make it work with the new block sizes, but it's never been tested.

Ill test it. Got an extra new block size

snandlal said:
Ill test it. Got an extra new block size
Click to expand...
Click to collapse
If it doesn't work though you're pretty much guaranteed to be bricked. But if it's a phone you're not worried about I've been dying to find out if this will actually work.

Yes i will sacrafice. Gettin a nexus s 4g anyways...seriously will test tho

snandlal said:
Yes i will sacrafice. Gettin a nexus s 4g anyways...seriously will test tho
Click to expand...
Click to collapse
Right on, all you need to do is downgrade to the eng hboot from the hboot and before rebooting or doing anything set 'fastboot -n 4096'
That *should* let you use the eng hboot. You still won't be unable to downgrade your radio though, although afterward it may let you flash the old radios without so much as a warning.

Ok will do. Hboot usb or fastboot usb?

Tryed this but i still get six short vibrates when flashing the radio

snandlal said:
Tryed this but i still get six short vibrates when flashing the radio
Click to expand...
Click to collapse
fastboot USB, as I previously said you will probably never be able to downgrade the radio. Sorry but that's just how it is.
Are you able to at least use your phone with the .76 hboot?

its weird.. there should be a way!!

wolfort said:
Spring Evo 4g
HBOOT: 2.10.0001
Model: PC36100
Hardware:0003
Android：2.2
Kernel 2.6.32.17
Baseband：2.15.00.11.19
Software3.70.651.1
PRI:1.90_003
Rooted with Unrevoked.
After upgrade Baseband, I got very bad signal and want to roll it back.
1. Tried to use cm recovery 2.6 to install zip file containing radio image to 2.05.00.06.10, not sucessful. However, every time it turn to 2.15.00.11.19 after reboot. I fell 6 vibrations during flash, do not know why.
2. Tried to use fastboot flash radio image，but I got "remote not allowed" message!
Could any body help out?
Thanks.
请高手们指点一下吧！谢谢谢谢！
Click to expand...
Click to collapse
Instead of downgrading so far back, have you tried downgrading the baseband from 2.15.00.11.19 to 2.15.00.09.01? If not, give it a try. You can download it and all of the other EVO radios from the link below:
http://forum.xda-developers.com/showthread.php?t=715485
UPDATE: Disregard. The original post was dated April 8th.
posting & replying via the XDA Premium app.

If i wanted to go back and try Android 2.1 roms, do i have to downgrade the radios as well?

Trying not to make a new thread but....say if I am using a 2.2 Rom with the 2.15.00.11.09 radio and I want to flash to a 2.1 rom(I'm talking bout far back as the rooted shipped stock ROM from last June. Would I need to downgrade my radio? And does that stock ROM already come prepackaged with a kernel. I'm pretty sure the kernel needs to be downgraded for it to be compatible. When I got my EVO in Sept, I was already on 2.2. Never tried 2.1 but have always been curious to try it and see how much worse it is. Then I could say I've finally tried all three versions of Android on my phone and how far we have progressed

As you've stated, the problem would not necessarily be the rom itself not working with the new radios, but whether or not the default kernel would work properly. Give it a shot. The worst that *should* happen is bootlooping. At that point, you can either reboot into recovery and flash a different kernel or downgrade the radio, PRI and NV. Of course, this is my opinion. You can download the rom from here . By the way, according to the descriptions on the shipped roms, the radios appear to be included.
posting & replying via the XDA Premium app.

just read that i can't downgrade my radio because i'm running the 2.10 HBOOT and on HW003. but if downgrading the radio is not necessarily important to run a rooted 2.1 rom then i don't have much to worry about do i? also, those links you posted: i can flash those RUU's in recovery like i would any other rom? i don't want to go back to stock and be unrooted.
i was thinking of running the 1.32.651.1 rooted rom from Flipzmode, and if need to - download the appropirate kernel link next to it on the detailed ROM wiki thread maintained by Toast.

You cannot downgrade your HBOOT from 2.10 (not necessarily accurate) without a risk of problems, however, you can downgrade the baseband, PRI and NV. I've done it several times. I've downgrade from baseband 11.19 to 09.01. As well as upgrade to 04.08. I've also downgraded my PRI from 1.90 to 1.77 all while having HBOOT 2.10.
posting & replying via the XDA Premium app.

i've downgraded my PRI because of the wakelock issues.
so you can downgrade the baseband to a certain extent? only within the 2.15 radios? but you cant downgrade to the radios that were on Eclair? if i can run 2.1 roms on 2.15 radios then by all means i'm going to try it out. thanks for the info doug

[Q] Returning from the Dead

Hello Supersonic Community,
I come to you in my time of need, I have spend the last 3 days at work trying to downgrade an Evo 4g to 2.1. from 2.2.
Initially I ran unrEVOked3 reflash package as from what I read it would probably be the easiest place to start from an unrooted 2.2.
Once I was rooted on 2.2 I followed the guide from here
and used the RUU/Zip files from here
I currently have the phone in a state where it will only load into the bootloader and I do have a working amon ra recovery.
When I try flashing the RUU's PC36img.zip file from hboot I see that it "checks" the zip file however I am not prompted to run the update.
and when trying to run the RUU zip file from recover it says there is not update script.
My main question is if anyone knows why I am not prompted for the update from Hboot or if its possible to flash from recovery back to stock 2.1
I come from a Nexus S and HTC Desire background and have a bit of knowledge just kinda stumped right now on this one. I am currently trying different SD cards for the hboot flash as I have read that it can be a bit finicky.
Thanks in advance for any help.
PHone info
Android version 2.2
Baseband version 2.12.00.09.01
Kernel version 2.6.32.15-ge2fb08e
[email protected] #11
Build number 3.29.651.5 CL252548 release-keys
Software number 3.29.651.5
Browser version Webkit 3.1
PRI version 1.77_003
PRL version 60675
Hardware version 0003
h-boot 0.79.00

It all goes back to the Hboot version you have. I think it's anything over 2.10 you can't downgrade.
I think your best bet is to just flash a stock/Rooted 2.1 ROM or a custom Froyo ROM

Well my HBoot is .79 so I hopefully can recover to 2.1.
I basically can't have a rooted phone, I work in mobile QA and we can't test on devices that are rooted. Which I know is a bit retarded but thats how it works for us right now.
If I flash a stock 2.1 rooted Rom I should be able to unroot.... at the very least uninstalled su and my boss won't know hehe
Thanks for your reply.

Did your phone come with that hboot? If your hboot and radio match the ruu you are trying to flash, then it should be good to go. If you r s-off while trying, even better. Do you have 20k or 40k block sizes?
Sent From My Pocket

{ParanoiA} said:
Did your phone come with that hboot? If your hboot and radio match the ruu you are trying to flash, then it should be good to go. If you r s-off while trying, even better. Do you have 20k or 40k block sizes?
Sent From My Pocket
Click to expand...
Click to collapse
**********HBOOT VERSION IS .79 *************** TYPO IN OP
That would be the Hboot it came with these are testing devices at my work. they are ALL STOCK unless i personally change it as no one else here handles the android phones.
I am unsure of the 20/40 k block sizes you are referring too do you mean on my sd card?

So i have successfully flash a rooted 2.1 stock rom and am trying to uninstall super user. If anyone has any tips on this let me know

Issue resolved.
Set phone into recovery and used ADB to remove the Superuser apk
Thanks for the help