Related
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
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.
Hello all.
I rooted my G2 using the gfree method and all went well(I have S-Off). It was much easier then the process for my G1.
Current setup
HBOOT-0.82.0000
RADIO 26.03.02.26_M
Cyanogenmod 6.1.1
So my question is should I bother to update my bootloader? A friend of mine with a similar setup said I should upgrade but what additional functionality would I get? Anyway I hope this does not seem like a stupid question.
The Eng HBoot gives you fastboot capabilities. That's about it. If you don't really use fastboot, then there is no reason to flash it.
Thank you for the reply but Im confused.
When I go into the boot loader it says fastboot and it shows up if I do 'fastboot devices' from the command prompt. I thought that meant I have fastboot capabilities? Or am I misunderstanding something?
If you have the stock bootloader, you don't have privileges like "fastboot flash" capabilities. It will show up with "fastboot device" because you have the phone in fastboot. It's like in adb, doing "adb devices" will show it up, even if you don't have superuser privileges.
Hope that clears things up a bit.
Ok now I understand. Thank you for your patience.
Looking back on the root instruction on the cyanogen site now I see the section referring to replacing the bootloader.
Now I hear alot about flashing the wrong radio and bootloader versions. How do I know for sure the file on the cyanogen site (0.76.2000) is the correct one?
That's the one that I have on my G2
Side note. I was looking at the wiki on XDA and it has the Eng HBoot for the G2 listed as 0.84.2000 and the DZ HBoot as 0.76.2000 that are hyperlinked to download.
Correct me if I'm wrong, but aren't those two supposed to be switched? My G2 has 0.76.2000, which is what I used when I first achieved perma root using the rage method before gfree. This is also listed on the CM wiki. I am by no means an expert, but I thought the two HBoot's were not interchangeable between the two devices.
Anyone care to chime in on this to share some light? I would hate to start a thread for this question of mine to be answered.
Yes I noticed the same thing. XDA has 84.2000 and CM has 76.2000. Relevent links posted below.
http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
tazz, what radio version do you have? Id like to update my radio as well, hopefully it will clear up some issues.
My radio version is the one dumped from the RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.14 0f_26.06.02.27_M_release.
It's found in this thread http://forum.xda-developers.com/showthread.php?t=959488
The instructions to flash with fastboot are there, as well as an update.zip, so you should have no problems there.
Regarding the engineering hboot;
The ONLY known brick was made by scotty2 by playing with hboot commands that are only available in the engineering hboot. In other words, it allows you more freedom to control the device, but at the expense of potentially REALLY f-ing it up if you mess with things that you don't understand.
With a radio s-off phone, you can save the phone from literally anything, even without the engineering hboot. As a matter of safety, the engineering hboot is *not required*. In terms of convenience, it is nice, as long as you don't go playing with things you don't understand.
Tazz. Thank you for the info. but should I upgrade the SPL before that installing that radio?
If you want to upgrade the radio through fastboot then yeah, you need to upgrade the spl first.
Otherwise, you can just update the radio through the update.zip in bootloader the pc10img.zip way, then you can do the spl upgrade.
Its really a personal preference.
Sent from my thumbs
tazz9690 said:
Side note. I was looking at the wiki on XDA and it has the Eng HBoot for the G2 listed as 0.84.2000 and the DZ HBoot as 0.76.2000 that are hyperlinked to download.
Correct me if I'm wrong, but aren't those two supposed to be switched? My G2 has 0.76.2000, which is what I used when I first achieved perma root using the rage method before gfree. This is also listed on the CM wiki. I am by no means an expert, but I thought the two HBoot's were not interchangeable between the two devices.
Anyone care to chime in on this to share some light? I would hate to start a thread for this question of mine to be answered.
Click to expand...
Click to collapse
santaclaws said:
Yes I noticed the same thing. XDA has 84.2000 and CM has 76.2000.
Click to expand...
Click to collapse
You were right I updated the XDA Wiki to reflect the correct info on the ENG. Hboot for the G2 which is 0.76.2000 and the DZ which is 0.84.2000. Good Catch.
joemm said:
You were right I updated the XDA Wiki to reflect the correct info on the ENG. Hboot for the G2 which is 0.76.2000 and the DZ which is 0.84.2000. Good Catch.
Click to expand...
Click to collapse
You're a good man joemm. Thanks for fixing things.
I went ahead and upgraded to the Eng hboot. No Brick. Yay!
tazz. occasionally my phone loses data connectivity. i can still make phone calls but no data. i notice if i kill the radio process internet works after the signal comes back. do you think an update to my radio would help this issue?
Yeah it could help it. I upgraded my radio and I get better data reception now than I did with the older radio version that I had.
I had the same problem, where I would have to reboot the phone to regain data. It still happens once in a blue moon, but not like it did before.
At least I am not the only one having that issue. Its a bit annoying.
The only "solution" I found was to make a simple gscript to kill all radio processes. Its quicker then a reboot. Not sure if killing the radio process has any negative effect but the phone seems fine after.
I just leave the shortcut on the desktop and use it whenever I need it.
dhkr234 said:
Regarding the engineering hboot;
The ONLY known brick was made by scotty2 by playing with hboot commands that are only available in the engineering hboot. In other words, it allows you more freedom to control the device, but at the expense of potentially REALLY f-ing it up if you mess with things that you don't understand.
With a radio s-off phone, you can save the phone from literally anything, even without the engineering hboot. As a matter of safety, the engineering hboot is *not required*. In terms of convenience, it is nice, as long as you don't go playing with things you don't understand.
Click to expand...
Click to collapse
Thanks for the info here, I had been searching this forum for at least 2 days now, looking for information on the eng-hboot and was it needed or not.
Being new to all this, could this eng-hboot vs hboot be on the wiki somewhere? My thoughts are that once I got my phone rooted and backed up I was trying to figure out what the next step was before flashing any ROM. I really don't want to mess up my phone.
From what I gather the main thing with the eng hboot is that it lets you do the fastboot commands.
and apparently it has other stuff that can also brick your phone lol
I am wanting to get Fastboot commands working on my Evo, Currently when I try a command they do not work. I read that I need a different H-Boot for fastboot to run correctly on my phone. So searching I found the correct H-Boot, but it seems my partitions are wrong for the H-Boot. Here is what my set up is...
CM7
Hardware 0003
H-Boot 2.10.0001 S-OFF via Unrevoked
Baseband 2.15.000.11.19
PRI 1.90_003
Software 3.70.651.1
When I run "cat /proc/mtd" in shell I am 00040000 for erasesize
Is there a work around I can do? I found a way to fool H-Boot into thinking its .76 BUT it says NOT to use the method if I have new partitions, erasesize 00040000, which I have
Could I RUU to a earlier software, then apply the .76 H-Boot, or will my 0003 hardware cause conflicts? So much dev for the Evo, but so many restrictions on what you can and cant do, depending on hardware, h-boot, baseband, its crazy! lol If it is possible please give as much info as you can. I dont want to get even more confused on what I can and cant do to get fastboot up and running
Thanks
If you've fooled HBOOT, kudos to you. But the latest HBOOT isn't downgradable, and if you RUU on your current software, it'd take you back to stock blah blah, but I think on the current HBOOT. I don't have all the answers, but I think you may be stuck on this one...
teh roxxorz said:
If you've fooled HBOOT, kudos to you. But the latest HBOOT isn't downgradable, and if you RUU on your current software, it'd take you back to stock blah blah, but I think on the current HBOOT. I don't have all the answers, but I think you may be stuck on this one...
Click to expand...
Click to collapse
No, I havent fooled it. I found a thread on how to, but not with my partitions sizes, I have the 40k partitions. So that being said I can not as of yet downgrade my H-Boot to ENG .76 I thought to myself, I am still S-OFF so I should be able to flash simple splash screen, nope!
c:\android-sdk\tools>fastboot flash splash1 evosplash1.rgb565
sending 'splash1' (750 KB)...
OKAY [ 0.350s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.354s
Seems I cant do that because of the way I rooted, Unrevoked. I had the HTC Hero a while back and that phone was so easy to mess with. Then I played with a Intercept, trash! I got a LG Optimus S, another phone that is a PIA! Now I got my dream phone, been wanting a Evo since it cam out, 2 months after I got my Hero, grrrrrrrr Anyway, now that I have a Evo I cant do as I was able to do with my Hero. I thought because it was HTC it would be the same. The other 2 phones not being HTC was the problem, lol. I guess these phone companies are doing more and more to try and lock the end user out of rooting the device. Sucks for us who want to be flashing this or that, in any method we choose.
Now that I am done ranting, lol It looks like most of the stuff i want to do can be done via PC36IMG.zip's. Flashing recoveries, flashing splash screens, radios, all that junk. Is there a good thread explaining how to create these zip's and what they can and cant be used for?
Thanks
teh roxxorz said:
If you've fooled HBOOT, kudos to you. But the latest HBOOT isn't downgradable, and if you RUU on your current software, it'd take you back to stock blah blah, but I think on the current HBOOT. I don't have all the answers, but I think you may be stuck on this one...
Click to expand...
Click to collapse
My replacement evo came with 3.70, hw003, hboot 2.10, 2000 erasesize and I still downgraded my hboot to .76. It's the newer block sizes and hw004 that have problems downgrading.
cordell12 said:
No, I havent fooled it. I found a thread on how to, but not with my partitions sizes, I have the 40k partitions. So that being said I can not as of yet downgrade my H-Boot to ENG .76 I thought to myself, I am still S-OFF so I should be able to flash simple splash screen, nope!
c:\android-sdk\tools>fastboot flash splash1 evosplash1.rgb565
sending 'splash1' (750 KB)...
OKAY [ 0.350s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.354s
Seems I cant do that because of the way I rooted, Unrevoked. I had the HTC Hero a while back and that phone was so easy to mess with. Then I played with a Intercept, trash! I got a LG Optimus S, another phone that is a PIA! Now I got my dream phone, been wanting a Evo since it cam out, 2 months after I got my Hero, grrrrrrrr Anyway, now that I have a Evo I cant do as I was able to do with my Hero. I thought because it was HTC it would be the same. The other 2 phones not being HTC was the problem, lol. I guess these phone companies are doing more and more to try and lock the end user out of rooting the device. Sucks for us who want to be flashing this or that, in any method we choose.
Now that I am done ranting, lol It looks like most of the stuff i want to do can be done via PC36IMG.zip's. Flashing recoveries, flashing splash screens, radios, all that junk. Is there a good thread explaining how to create these zip's and what they can and cant be used for?
Thanks
Click to expand...
Click to collapse
There's a thread on Android Central HERE that explains how to make a flashable PC36IMG.zip splash screen. i assume the process for any other PC36IMG.zip is similar.
lovethyEVO said:
My replacement evo came with 3.70, hw003, hboot 2.10, 2000 erasesize and I still downgraded my hboot to .76. It's the newer block sizes and hw004 that have problems downgrading.
Click to expand...
Click to collapse
I have hardware 0003 but its is equipped with new partitions 40k size. Are you saying I can downgrade Hboot?
Sent from my PC36100 using Tapatalk
EndlessDissent said:
There's a thread on Android Central HERE that explains how to make a flashable PC36IMG.zip splash screen. i assume the process for any other PC36IMG.zip is similar.
Click to expand...
Click to collapse
Thanks for the link!
Sent from my PC36100 using Tapatalk
cordell12 said:
I have hardware 0003 but its is equipped with new partitions 40k size. Are you saying I can downgrade Hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You could try and theoretically it "could" work but I can't say for sure because there haven't been much reports of the 40k sized 003hw's having success with it.
lovethyEVO said:
You could try and theoretically it "could" work but I can't say for sure because there haven't been much reports of the 40k sized 003hw's having success with it.
Click to expand...
Click to collapse
I see, so theoretically it could also brick me. I am within my 30 days, and have a dead pixel. Thing is they know I root my phones, they were checking out my wifes LG Optimus S with 2.3 and were really interested on how to root. One of the reps wants to root his Evo but is scared due to all the versions and what not. Cant say I blame him, but you think working for sprint they can easily get a replacement phone, no?
Has anyone had success with hardware 0003 and NEW partitions (40,000 block size), or have anyone bricked while trying?
Thanks for input
cordell12 said:
I see, so theoretically it could also brick me. I am within my 30 days, and have a dead pixel. Thing is they know I root my phones, they were checking out my wifes LG Optimus S with 2.3 and were really interested on how to root. One of the reps wants to root his Evo but is scared due to all the versions and what not. Cant say I blame him, but you think working for sprint they can easily get a replacement phone, no?
Has anyone had success with hardware 0003 and NEW partitions (40,000 block size), or have anyone bricked while trying?
Thanks for input
Click to expand...
Click to collapse
My girl got her Evo in December. It's an 003 model but I'm not sure about the partition size as that is news to me. I rooted with whatever version of Unrevoked was out at the time, and simply grabbed the .76 hboot from Toast's part 2 thread and flashed it. It worked without any issue.....in this case. After I did that, I read that a lot of people were having trouble downgrading to the engineering SPL and were bricking, and I breathed a heavy sigh of relief that it didn't happen to me and my girl's 4 hour old Evo. lol
Come to think about it, I don't even know why I did it to her phone. I always experiment with my own phone before flashing anything new on hers, so in retrospect, downgrading to that hboot in her phone just for fastboot commands was a risk not worth taking.
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2