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 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.
OK before i get SEARCH.. I did and here is what i have looked at so far (i am 3+ hours into my search)...
http://forum.xda-developers.com/showthread.php?t=838484
http://forum.xda-developers.com/showthread.php?t=842495
http://forum.xda-developers.com/showthread.php?t=905261
ANd a few others that link back to one of those 3.
This is not my phone. I am helping my buddy who attempted to perma-root his phone using Visionary+ 14. I have an evo, and several other android phones and understand the basics of ADB and how to do most this stuff.
After he applied the patch, we are stuck on the white HTC screen. The problem is, it does NOT have the ENG SPL, we are still s-ON and still have stock recovery.
Here is what i have attempted so far:
download and tried to have it reload PC10IMG.zip - Got an error that said the version i was trying to install was older than the one i already had. I downloaded the latest one i could find.
Since i can get into the stock recovery, i downloaded and tried to use update.zip to reinstall things correctly, but that didnt work. It didnt error out and looked like it installed correctly, but still just stuck at the white HTC screen.
I cannot access ADB (at least any way that i know how).
Yes, i have the correct USB drivers installed and ADB is working as i have accessed it for other phones.
Here is the phone stats:
VISION PVT SHIP S-ON
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_m
eMMC-boot
Sep 2 2010, 17:59:38
I cannot find the right RUU to give that a try either. I have found a few that MIGHT be right, but i dont want to mess it up more by flashing the wrong thing (if this would even help.. i dunno)
ANY HELP WOULD BE REALLY APPRECIATED!!!!
Anyone?? Help????
frettfreak said:
this is why people post in the dev forum when they arent supposed to.... cause NOTHING happens if you post in q&a...
Anyone?? Help????
Click to expand...
Click to collapse
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
ianmcquinn said:
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
Good point!! Sorry.. just a little anxious. Dont want to tell him his phone is bricked....
Also... maybe no one responded cause i am a tard.... its s-ON still, not S-OFF
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Sorry for the confusion and pushy-ness and thanks for your help!
frettfreak said:
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Click to expand...
Click to collapse
Well, like I said before, this is the type of semi-brick that people seem to be stuck in when Visionary fails and I haven't seen a working solution. When I said to leave it at the HTC screen, it was just something mentioned in the how to recover semi-brick thread you linked to in the original post. Unfortunately, if that didn't work, you might by out of options.
EDIT: And oh, I forgot to mention about fastboot. Although it might seem like fastboot detects the phone properly, you cannot actually use it to flash anything unless you have the engineering HBOOT, so that doesn't help any.
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
lainvalenajr said:
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hmmm how do I do that? Is there a different way other than adb? I will check again but pretty sure I don't have adb access (I think this is what the eng spl does but I am just guessing here) does fastboot allow Me to do anything like that?
Ok guys, first of all I'll explain everything from the start.
Back in November I used AAHK to root, ENG S-OFF etc. my phone so that I could flash a custom rom. Installed Android Revolution HD.
A month ago or so I found the IceColdSandwich rom so I NAND-ed my AR and fresh installed that. And I kept switching between the 2 of them from time to time.
Found that there's a free download of clockworkmod touch on their website, but I couldn't flash it via fastboot. Gives me this:
sending 'recovery' (3554 KB) ... OKAY [0.641s]
writing 'recovery' ... FAILED (remote: not allowed)
Same thing happened when I tried to flash a new radio.
Stupid me, I reinstalled the recovery from ROM Manager again in the process as a last resort (dunno why I thought it would work >.< ).
Now the problems start, I was running AR 6.3.1 last night and I wanted to update the ICS rom, so I made a backup to AR rom and wanted to restore the ICS one. Told me the md5 wasn't correct or something. I instantly thought "GAH, probably because I reinstalled recovery." so I decided to finally install the clockworkmod touch if I had allready ****ed it up. Got the same bloody error:
"FAILED (remote: not allowed)"
So what did stupid old me think then? "Yeah, maybe I didn't ace hack it right the first time..." so I decided to use AAHK again. Logged in Linux, started the kit. All fine and well, said there "Rebooting, please wait". I was like "MMkay, I guess it will take a bit, I'm gonna go do something else" and forgot about it for a couple of hours. 2 hours later, same message in terminal, my phone still had the white background with HTC logo on it.
Ok, don't panic, what to do, what to do...disconnected my phone, pulled out the battery, rebooted into h-boot, hit recovery. The horror of it not being there
Rebooted into bootloader again, tried to flash recovery again, still the same message.
While I was there, desperately tried "Factory Reset", shows me a screen with a loading bar or something and next to it a micro sd card with upload download arrows on it (up and down arrows). Afterwords it proceeds to rebooting my phone 3 times and then it dies. Do I need some kind of file on my SD card for it to work or something?
I think I bricked it. :-<
Sorry for the long post.
Any kind of help is apreciated. Thanks guys
PS: H-BOOT says:
ACE PUT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Apr 12 2011, 00:55:45
Hey dude.
Just a quick post, you have not bricked your phone so don't panic.
More in a mo.
Greg.
Sent from my Desire HD using Tapatalk
Search this forum for a stock PD98IMG.Zip ideally a 1.32 one.
Copy this to your sd card, then boot into hboot.
Hopefully hboot will recognise the image and install it on your phone.
Can anyone qualify/dispute this?
Cheers.
Greg
Sent from my Desire HD using Tapatalk
Thanks Greg. I'll find the image and tell you in a min if it worked
It has to be an RUU that fits your phone. Do NOT flash a froyo RUU on a phone that was shipped with stock gb. An RUU will revert the phone to stock. After that you should have no probs running AAHK again to gain s off.
Sent from my HTC Desire HD with Beats Audio using XDA App
Bought my phone in December 2010, it was shipped with Froyo 2.2. I updated it myself to Gingerbread (only later I found out how dumb that was) so I guess it's okay if I flash a 1.32, right?
Good Guy Greg, I love you man I can use my phone again, thank you so very much!
I have just a question though. Is it by any chance possible to create a PD98IMG.Zip to revert my phone to something more recent? Can I use it to create something like a NAND backup?
dragancla said:
Good Guy Greg, I love you man I can use my phone again, thank you so very much!
I have just a question though. Is it by any chance possible to create a PD98IMG.Zip to revert my phone to something more recent? Can I use it to create something like a NAND backup?
Click to expand...
Click to collapse
Glad to help dude.
I think that as long as your phone turns on, even if it bootloops etc... you haven't bricked it.
I think it is possible, but I'm not totally sure how to create a PD98IMG.ZIP.
But I'd suggest is you want something more recent, just flash a new ROM.
Once you are back to stock (this may have broken root) check to see if you're still rooted, if not re root and use CWM Recovery to flash whatever ROM you want.
Regards.
Greg.
Sent from my Desire HD using Tapatalk
Thanks again, mate I used the AAHK again and I flashed my old rom back, but I still can't flash a different radio or the touch recovery...same error: "writing 'recovery' ... FAILED (remote: not allowed)"
Oh well, glad to have my phone back :>
You can't flash a radio with the way you are doing it (ie fastboot) unless you have the engineering bootloader (Eng soff). For.those of us with just soff we flash them via a pd98img formatted zip. Much easier in.my opinion as you can flash a radio without a PC.
One thing to note is that if your phone cane shipped with gb, DO NOT install the engineering bootloader as it will mess you up big time and cause your phone to.take30 min to boot up. Its fixable but its a pita
dragancla said:
Thanks again, mate I used the AAHK again and I flashed my old rom back, but I still can't flash a different radio or the touch recovery...same error: "writing 'recovery' ... FAILED (remote: not allowed)"
Oh well, glad to have my phone back :>
Click to expand...
Click to collapse
Why not buy the Touch upgrade from ROM Manager?
Greg.
Sent from my Desire HD using Tapatalk
TeamDraven said:
Why not buy the Touch upgrade from ROM Manager?
Greg.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
It's not fun if I don't do it myself It's like saying "Yeah, you ****ed up your phone, better take it to the local repair guy" but thanks to you I learned how to downgrade my phone back to stock and start over, even if I dont have recovery installed any more. I consider learning from trial and error better than having people do it for you...that and I've always wanted to learn to flash .img files like recovery, radios, 4ext themes etc. But I'm glad to report that I have ENG S-OFFed my phone since then and flashed all I need :>
Thanks again, Greg :>
I get what you are saying dude.
But there's no harm in supporting a developer.
Cheers dude.
Greg.
Sent from my Desire HD using Tapatalk
Desire HD brick
Hi, I have similar problem as dragancla with small differences.
I did root my Desire HD too, but in Ace advanced hack kit. I di mSD card as goldcard, next a put PD98IMG.zip (1.32.X) on sdcard. Then I started with root first three steps going well. After succesfully installing root, clockworkmod and first radio start next step flash new radio and here was the problem. Connection with PC fell and flashing was stoped. Now I have only black background without any mark of starting of device. Only orange LED flashes.
I tryed to remove battery and wait 10 minutes but without any succes.
Please can you help me with this problem?
That sounds like a hard brick.
And what can I do with it?
DO you know?
Brick DHD
Today I have a small changes in the device settings.
When I pushed it to recharger then device start to recovery but only for a few seconds. I can install retore or update but I have so short time for it, then every installation ends in black screen.
If somebody know something about this problem, please help me.
Eltahrel said:
Today I have a small changes in the device settings.
When I pushed it to recharger then device start to recovery but only for a few seconds. I can install retore or update but I have so short time for it, then every installation ends in black screen.
If somebody know something about this problem, please help me.
Click to expand...
Click to collapse
Have you used a froyo RUU and your device was shipped with Gingerbread?? if you did that then you have messed your hboot....you need to fix that in order to have a normal phone!!
It's kinda hard to know what's going on with the information provided, but you can come and hit the Hack Kit IRC Channnel to see if we can help...
I am at a loss of things to try with this Evo which I have no history of.
After initially being stuck at 4-triangles. I managed to flash the ENG 0.76 bootloader. Found out that:
S-OFF
Radio: 2.15.00.09.08 -some sort of Chinese radio?
I've tried it many different ways with RUUs, fastboot and PH36IMG, but RADIO_V2 repeatedly fails to flash.
I can also flash any recovery, but it fails to load, getting stuck at the Evo splashscreen, so that is also a problem. Most partitions flash nicely in fastboot. A successful system flash will result in a stuck Evo splashscreen, though.
Is there any way out of this? Perhaps by using one of the elevated commands in the ENG bootloader? I don't know how to get ADB running either, since I'm stuck in fastboot and have no idea whether USB debugging was on earlier. I do have a Linux box if that helps.
Any help would be greatly appreciated. Thanks!
Its a PC36IMG* not PH36IMG
Sent from my SPH-L710 using xda premium
Typo, sorry.
Sent from my Galaxy Nexus using xda premium
I might need to clarify a little.
I have absolutely zero history of this phone. None whatsoever.
1. Currently on ENG 0.76. I received the phone with no access to the bootloader, stuck at the HTC screen with triangles in each corner. I flashed the ENG 0.76 hboot via fastboot and that's what I'm on right now. Works fine.
2. I have no idea how it got to this radio version. Seems like a Chinese UIM radio. Got the phone from a friend who got it from an auction in Burma.
4. Flashing any radio in hboot will result in [see attachment]. Flashing in fastboot- see 2nd screenshot above. Fails either way, and I've tried multiple radios. Tried under multiple hboots, too. No dice.
5. Stock or custom recovery will flash fine but will get stuck at the white splashscreen if I try to enter it.
6. Bootloader is perfect. Works like a charm.
The only idea I can come up with is using an elevated command in fastboot oem which could reformat my radio partition somehow. I don't know whether I have ADB either. I have some experience with diag mode and JET on the HOX.
Any ideas?
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Sent from my SPH-L710 using xda premium
death-by-soap said:
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Click to expand...
Click to collapse
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
temuryusuf said:
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
Click to expand...
Click to collapse
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Sent from my SPH-L710 using xda premium
death-by-soap said:
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Click to expand...
Click to collapse
Obviously this is not the only hboot I've tried. I've gone to 2.10, even 2.18, tried there, come back down to ENG, tried again; it's just repeatedly failing. I'm not giving up hope due to the simple fact that the bootloader works and there MUST be a way out. Like I mentioned earlier I'm thinking one of the high level commands, but I have no idea what to do with them. Could anybody lead me in the right direction?
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Sent from my SAMSUNG-SGH-I747 using xda premium
shortydoggg said:
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Click to expand...
Click to collapse
I've only recently put 0.76 on after trying the newer Hboot versions. I found out that I was on 2.02 initially when I had the 4 triangles- I had to RUU because there was no accessible Hboot to fall back upon anyway. I then found a 2.02 img and flashed that through fastboot, which is when the bootloader actually started working. I'm using 0.76 now because it just seems to work better with commands.
What exactly does "permanent damage" imply in this case? Because the problem remains either way- RADIO_V2 fails to flash. All other partitions have not a single problem between them.
Is there a way where I can completely clear out the emmc, repartition it correctly and take steps from there?
At this point of time I'm rather certain mine is an older HW revision. How do I find out anyway?
The newer hardware started with Hboot 2.02 while the old ended with 0.97. You would never OTA to 2.02 from 0.97, but have went directly to 2.10 unless you flashed a Hboot with 2.02 or ran a RUU with that Hboot version. I actually made a post about a year and a half ago on how to tell, so if you phone ever boots again, I could point you to that post.
Right now, it's good that Hboot 0.76 seems to be doing something, but I'm afraid the radio may have been flashed with something that did not want to be there.
Sent from my SAMSUNG-SGH-I747 using xda premium