Related
Greetings all.
I just recently semi-bricked my Desire, I was uing 'Oxygen 2 RC2' and tried to partition my sdcard through 'AmonRA Recovery' and something went wrong and I ended up with a semi-bricked phone. I couldn't establish any connection with my SIM or SD-card.
I was tipped to install a original RUU which after a few tries worked and I recived a phone with the latest official Sense rom, HBOOT-0.93.0001 and S-ON of course.
After 'fastboot oem enableqxdm 0' is fastboot mode I atleast had connection with my SIM and SD-card and now a I have a semiworking but not rooted phone.
Now I want to root my phone and take back my USB-connectitvity but after reading this I understand that I need root for the USB-brick fix, to work but how do a get root with 'HBOOT-0.93'? Paul O'Brians root method only works for 'HBOOT 0.80' and lower and 'UnrEVOked' only works when having USB connection.
So how do I go about getting root and fixing my USB-Brick on my phone?
Thanks /ZeD
I have found a couple of "downgrade" tools but they haven't helped me much since everyone workd from within a fully booted system with a working USB-link which I have not.
Can a downgrade be done with a simple but old RUU file?
An old RUU file will not work.. I have the same problem, and got the same guide on how to fix it. But I sent it in for repair just hourse before, so I didnt have the chance to try it out. I unrooted my Desire as well with no luck. But as I read the guide, a rootet phone is not necessary?
For me it was, I had a another kind of fault at first my USB-brick happend when installing the ariginal RUU. What I should have done was to install a old RUU with 'HBOOT 0.80', root that and do the USB-brick fix, but I didn't know that I would get one ^^.
Blubba10 said:
a rootet phone is not necessary?
Click to expand...
Click to collapse
From the first step in that guide .
1. Follow this r5 rooting guide to do Step 1 of the rooting.
That will give you a basic ROM to work with, with root capability.
Click to expand...
Click to collapse
Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..
Blubba10 said:
Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..
Click to expand...
Click to collapse
I don't fully understand what you mean but when you have that kind of USB-brick that I have you need a rooted phone to fix it and the old way of rooting a Desire where you don't need it plugged to the computer can only root phones with 'HBOOT 0.80' or lower, the 'unrEVOked' way of rooting a Desire can be used on phones with newer bootloaders but need 'USB Debugging' which can't be used when a USB-brick is in play.
This is what you call a catch22 .
I have now seen a thread where a dude fixed a USB-brick on a non-rooted phone but the exploit that was needed is nowhere to be found. Well, well the hunt is on.
the easiest way to downgrade.
http://forum.xda-developers.com/showthread.php?t=768256
mariosraptor said:
the easiest way to downgrade.
Click to expand...
Click to collapse
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.
if you use a card reader to put the PB99 file on the root of your sd card? boot into hboot it will recognize the PB file and prompt for doangrade.
no need to be rude as no intention were to make you feel offended.
if it is of no help no hard feelings,
cheer up and have nice holidays and a Happy New Year!!!
Freddan80 said:
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.
Click to expand...
Click to collapse
I'm just a bit tired of working with this **** all weekend and answering in my ' cry for help threads' with I don't have root so I cant do that or I don't have a usb connection so I cant do that.
For the USB-brick fix to work I need root and for the downgrade to work I need a connection, it's just one way around my problem which seem to work but I only get 'permission denied' or 'that location is nonexistent'.
If anyone with more knowhow than me wants to take a look, the only thing that would actually fix my issue is here.
My meaning was to say that I think i have the same usb-brick as you (phone is now sent in for repair). It was rooted, but I unrooted it to hboot 0.80 and innstalled updates, wich resulted in hboot 0.93 in hope for it to fix itself. It didnt. As you say, you need root to fix brick. The only solution wich seems to work is this: http://forum.xda-developers.com/showthread.php?t=879068.. It seems to work for some people, not for me... And not for you as well, if i understand your latest reply correctly..
Yeah that's one of the fix I have tried.
It's kind of strange that that doesn't work, cause we should be able to write to that folder but for me it's like it isn't there at all. I checked my spelling and checked with 'androlib' that the working folder for 'Android Terminal Emulator' was in fact 'jackpal.androterm.
SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .
Freddan80 said:
SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .
Click to expand...
Click to collapse
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate
godina said:
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate
Click to expand...
Click to collapse
I used 'Better Terminal Emulator' never could get 'Android Terminal Emulator' to work.
I then used the commands given in the link I posted but instead of using 'data/data/jackpal.androidterm/*', I used '/data/data/*.
and then I did what the other thread said, made them executableand ran the exploit and then flashed my modified USB-brick fix.
Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app
here it is http://forum.xda-developers.com/showthread.php?p=10058480#post10058480.
godina said:
Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app
Click to expand...
Click to collapse
Ok I give up
Tried to download Better Terminal Emulator Magic, but it has been removed from market, looked for Pro version, cant download because there is no paid app support in Slovenia, so I can not download any paid app...
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?
godina said:
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?
Click to expand...
Click to collapse
You can obtain a copy here, but I'm not to sure about support.
I was trying to update to the latest Myn Rom (RLS5) and I guess it went wrong because now when I boot up it loads up for a minute but then goes to black and then has 5 quick vibrations. then it just stays on black and blinks the green led. And that's it.
I can get to h-boot, but not recovery. I have:
S-On
Hboot: 0.93.0000
Radio 2.15.00.07.28
Since S-Off, it will need a signed PC36IMG.zip or something? I really don't know what to do here.
Thanks in advance for the help, you guys are great!
I would try flashing RA via bootloader as a PC36IMG.zip. If that doesnt work you could always run an RUU.
c-stam said:
I was trying to update to the latest Myn Rom (RLS5) and I guess it went wrong because now when I boot up it loads up for a minute but then goes to black and then has 5 quick vibrations. then it just stays on black and blinks the green led. And that's it.
I can get to h-boot, but not recovery. I have:
S-On
Hboot: 0.93.0000
Radio 2.15.00.07.28
Since S-Off, it will need a signed PC36IMG.zip or something? I really don't know what to do here.
Thanks in advance for the help, you guys are great!
Click to expand...
Click to collapse
Does you have s-on or s-off? If S-ON then your nand is locked and you are not rooted
So I should be able to rename the De-odexed in this thread to PC36IMG.zip and go that route?
http://forum.xda-developers.com/showthread.php?t=874251
xHausx said:
Does you have s-on or s-off? If S-ON then your nand is locked and you are not rooted
Click to expand...
Click to collapse
S-On. and I could have sworn that I had s-Off before the botched update. I have been using programs that require root such as wi-fi tether, root explorer, cpu tuner, etc.
dglowe343 said:
I would try flashing RA via bootloader as a PC36IMG.zip. If that doesnt work you could always run an RUU.
Click to expand...
Click to collapse
I assume you mean RA the recovery. Which file should I use to download and change the name? I've only used .img files to flash it as an alternate recovery.
Thanks in advance.
c-stam said:
I assume you mean RA the recovery. Which file should I use to download and change the name? I've only used .img files to flash it as an alternate recovery.
Thanks in advance.
Click to expand...
Click to collapse
Download the .zip file and just right click on it and select rename. Make sure its PC36IMG.zip exactly. Otherwise bootloader won't recognize it.
Sent from my HTC Supersonic
dglowe343 said:
Download the .zip file and just right click on it and select rename. Make sure its PC36IMG.zip exactly. Otherwise bootloader won't recognize it.
Sent from my HTC Supersonic
Click to expand...
Click to collapse
I did that just now. downloaded the latest from the forum post in your signature, renamed it exactly, put it on the root, held power and volume down, it read the file and said "Checking File" for a couple seconds then just went back to the regular menu. never asked me "Yes" or "No".
c-stam said:
I did that just now. downloaded the latest from the forum post in your signature, renamed it exactly, put it on the root, held power and volume down, it read the file and said "Checking File" for a couple seconds then just went back to the regular menu. never asked me "Yes" or "No".
Click to expand...
Click to collapse
Sounds like you lost root somehow. I just noticed in ur earlier post that you have s-on. You most likely have to root again.
Sent from my HTC Supersonic
c-stam said:
S-On. and I could have sworn that I had s-Off before the botched update. I have been using programs that require root such as wi-fi tether, root explorer, cpu tuner, etc.
Click to expand...
Click to collapse
If you have a custom recovery still flash unrevoked forever, that well unlock your nand. Once that is unlocked you should be ok to continue.
Dots that update the hboot as well? If so that is probably what did it, otherwise you may have had an incomplete unrevoked root.
Sent from my PC36100 using XDA App
dglowe343 said:
Sounds like you lost root somehow. I just noticed in ur earlier post that you have s-on. You most likely have to root again.
Sent from my HTC Supersonic
Click to expand...
Click to collapse
Is there a way to root without being able to get into the rom? I only have the hboot menu as an option of interacting with the system right now.
Still stuck here. I tried running Unrevoked3 again and there wasn't enough time for it to recognize the phone before it did the 5 vibrations and went to black and cut off the usb connection. I tried renaming the latest RUU from http://forum.xda-developers.com/showthread.php?t=874091 to PC36IMG.zip and it did the same thing as before, the blue vertical progress bar reached the top, it said "Checking" and then after a minute or so it just went back to the regular first menu.
It sounds like the solution would be to get it rooted, but I need to find a way to do that without being into the rom or recovery.
You guys are a lot smarter then me when it comes to Android and fixing borked installs and updates. I know you guys can come up with a solution here, so thanks in advance.
c-stam said:
Still stuck here. I tried running Unrevoked3 again and there wasn't enough time for it to recognize the phone before it did the 5 vibrations and went to black and cut off the usb connection. I tried renaming the latest RUU from http://forum.xda-developers.com/showthread.php?t=874091 to PC36IMG.zip and it did the same thing as before, the blue vertical progress bar reached the top, it said "Checking" and then after a minute or so it just went back to the regular first menu.
It sounds like the solution would be to get it rooted, but I need to find a way to do that without being into the rom or recovery.
You guys are a lot smarter then me when it comes to Android and fixing borked installs and updates. I know you guys can come up with a solution here, so thanks in advance.
Click to expand...
Click to collapse
The link in my sig has 3.29.651 in RUU and PC36IMG.zip form, you can use one of those to get a working rom. Afterward you should be able to use the quick method to get rooted and flash a recovery again
c-stam said:
I did that just now. downloaded the latest from the forum post in your signature, renamed it exactly, put it on the root, held power and volume down, it read the file and said "Checking File" for a couple seconds then just went back to the regular menu. never asked me "Yes" or "No".
Click to expand...
Click to collapse
When you renamed the file, did you actually add the ".zip" to the name? If so, the file is called PC36IMG.zip.zip and the bootloader won't see it. Just name it to PC36IMG and the .zip is added automatically.
rugedraw said:
When you renamed the file, did you actually add the ".zip" to the name? If so, the file is called PC36IMG.zip.zip and the bootloader won't see it. Just name it to PC36IMG and the .zip is added automatically.
Click to expand...
Click to collapse
I have "hide files extensions for known files" turned off in my folder options
But good thought and thanks for the info.
xHausx said:
The link in my sig has 3.29.651 in RUU and PC36IMG.zip form, you can use one of those to get a working rom. Afterward you should be able to use the quick method to get rooted and flash a recovery again
Click to expand...
Click to collapse
IT WORKED!!!
Wow, what a relief to see it get past checking the rom and asking me if I want to update. Thank you so much! time to unrevoke and then unrevoke forever, so I won't have so many issues if this happens again.
Thanks everyone for your help. You guys are the best.
I had this same problem and couldn't ever figure it out. It would power on and the go black and vibrate 5 times. I ended up clearing my phone and going to Sprint to have it replaced. Glad you got yours all figured out.
c-stam said:
IT WORKED!!!
Wow, what a relief to see it get past checking the rom and asking me if I want to update. Thank you so much! time to unrevoke and then unrevoke forever, so I won't have so many issues if this happens again.
Thanks everyone for your help. You guys are the best.
Click to expand...
Click to collapse
So, I got the stock rom loaded, however I can't mount either of my microSd cards. and also when I try and install the OTA update from Sprint, it goes to black and does the 5 vibrations again. Also, unrevoked3 isn't working. Also, when I plug it into my computer it won't let me mount as a storage device.
Any ideas guys?
Thanks.
c-stam said:
So, I got the stock rom loaded, however I can't mount either of my microSd cards. and also when I try and install the OTA update from Sprint, it goes to black and does the 5 vibrations again. Also, unrevoked3 isn't working. Also, when I plug it into my computer it won't let me mount as a storage device.
Any ideas guys?
Thanks.
Click to expand...
Click to collapse
Is there another RUU I could try or another way to root that would get me access to recovery? Really not sure what to do but I'd hate to take it to Sprint and have to get a new one for this.
Thanks.
Hi all
For the last few weeks I have been trying to fix my HTC Desire back to some sort of working state. After awhile, I managed to get back to stock (from CM7), but soon realised I had the USB brick and SD Card issue. For info I used the stock HTC 2.3 Gingerbread RUU and used Alpharev PB99IMG_downgrade.zip for HBOOT (I was using Alpharev S-OFF with CM7).
So, I followed this guide, http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ and managed to mount the SD Card. However, I could not get the update.zip file to apply because I was no longer rooted.
So I followed the guide linked in the USB brick article, http://android.modaco.com/topic/307...ide-now-with-hboot-080-and-os-to-121-support/ and soon realised that I did not have the HBOOT version required. Either 0.75 and below, or, 0.80 and below. I have 1.02.0001.
Not a problem, I thought. I will follow this guide to downgrade, http://forum.xda-developers.com/showthread.php?t=768256 as it specifically says that "...the downgrade does not depend on any version of HBOOT" which is what I need. However, first step is to get a working Goldcard. This is where I start to get into trouble and I'm already losing track of what I'm doing, but I soldier on...
How do I create a Goldcard? I followed this guide, http://android.modaco.com/topic/305672-creating-a-goldcard/ and got stuck at running the ADB command as because my USB is broken, Windows 7 (x64) refuses to see the Phone. Luckily, my father has the same phone, so I put my SD Card into his Desire and managed to create a Goldcard (he is running CM7 on his Desire too).
So Goldcard in hand, I go back to the downgrade guide and then spot my next issue. I can't get Windows to see the phone to use ADB commands and I also can't get Windows to see the phone when it is booted up (the charge light won't even come on now), meaning I can't run the downloaded application.
Not to be outdone I went back to the Rooting Guide and tried both of the downloads with the "step1-windows.bat" command just in case they did work, but both give an error, which on searching, is to do with the HBOOT version being incompatible.
I tried putting on the PB99IMG_downgrade.zip file from Alpharev again, then re-running the HTC 2.3 Gingerbread stock RRU and taking the ROM.zip folder and re-loading it on to the phone, but it hasn't changed the HBOOT version. So my cry for help is.... how can I downgrade HBOOT without using ADB commands or having to have Windows detect my phone? I'm basically stuck with Fastboot and my SD Card.
Even though my phone looks stock, I can't call people as it disconnects straight away, the USB is broken and the battery drains stupidly quickly.
Thanks for any help!
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
bortak said:
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
Click to expand...
Click to collapse
Hi bortak,
Thanks for the reply. It is a bit of a strange situation I agree. I've been putting off signing up and posting for help as I feel quite dumb for breaking my own phone, but I have to admit defeat on this one.
I saw your reply also in this similar topic, http://forum.xda-developers.com/showthread.php?t=1290391, so I will definitely try your suggestion and report back.
Appreciate you taking the time to post.
Thanks.
USB Brick on official GB 2.3.3 and HBoot 1.02
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
dexterm1 said:
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
Click to expand...
Click to collapse
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
bortak said:
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
Click to expand...
Click to collapse
I´ll have a try
just fixed my desire 1 hour ago and it works.
look at this http://forum.xda-developers.com/showthread.php?t=1296916
What I did:
I was able to connect my pc and phone through wi-fi and adb worked (adb connect phones-IP-address ) and then pushed, chmod'd 755 and executed zergrush. Gained root via cmd with adb shell in windows and after that I just pushed flash_image and mtd0.img to phone and ran it like you supposed to in the guides (chmod 755 and execute). Rebooted and voila! USB connection is working and now my phone signal isn't dropping anymore - phone fixed!
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
dexterm1 said:
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
Click to expand...
Click to collapse
Hi, pls. tell us how did you managed to connect your unrooted phone over wifi with adb? I get only "unable to connect to ... ip ..."
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
exocetdj said:
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
Click to expand...
Click to collapse
I can not install anything without root, and i can't root 2.3.3 software.
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
exocetdj said:
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
Click to expand...
Click to collapse
Ignore this, you can't root 2.3.3 with unrevoked
r5_alpine said:
I can not install anything without root, and i can't root 2.3.3 software.
Click to expand...
Click to collapse
Use revolutionary instead
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
eddiehk6 said:
Ignore this, you can't root 2.3.3 with unrevoked
Use revolutionary instead
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I can't do both of this, because my phone is not recognized by PC in any way, i must root it without PC.
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
matus.karahuta said:
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
r5_alpine said:
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
Click to expand...
Click to collapse
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
matus.karahuta said:
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
Click to expand...
Click to collapse
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
r5_alpine said:
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
Click to expand...
Click to collapse
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
matus.karahuta said:
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
Click to expand...
Click to collapse
The phone is not seen by pc in any statement, not in bootloader, or fastboot, or recovery. I need to either downgrade to 2.29 rom version, or to root it in some way.
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
raze599 said:
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
Click to expand...
Click to collapse
Ya it will just do that way and do the rooting again after following these steps.....
find the stock splash screen here: http://forum.xda-developers.com/showthread.php?p=15430340&highlight=stock#post15430340
Uncompress that and put the .img file in the same folder as your fastboot file (in the Android SDK, it used to be in the Tools folder but nowadays they put it in the Platform-Tools folder), then open a CMD window, (Make sure the file is called splash1.img) and type:
fastboot flash splash1 splash1.img
That will restore the stock splash screen.
To restore the software you have to:
1: Find a 1.32.405.6 RUU that matches the original state of your phone. 2: Flash that RUU 3: Use Visionary R14 to Temproot and then Permroot 4: The Jkoljo's Easy Radio Tool to change the CID back to stock (If you phone was unbranded it will be HTC__001)
Now its ready to root again...
Hope that helps.
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
raze599 said:
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
Click to expand...
Click to collapse
I honestly think people are just copying and pasting stuff they've read somewhere without thinking about what they're saying. The bulk of that is nothing to do with the query you asked (apart from maybe the line about the RUU); I mean, replacing the splash image?! How's that going to help with a corrupted bootloader? Let alone telling you to download the full Android SDK just for that
On topic: the RUU should do it, but I've never tried it myself so you're probably safer waiting for someone with some actual experience to confirm before you flash. I have seen that error mentioned in one of the guides I used back when I rooted (January time), so I'll see if I can dig that out.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
---------- Post added at 08:07 AM ---------- Previous post was at 07:42 AM ----------
Okay, found it: a few people were having "bootloader corrupt" issues using the One-click ENG S-OFF tool.
Try the advice in that post (or maybe search that thread a bit further for mentions of "corrupt") before you waste time flashing a RUU. IIRC you can do Radio S-OFF & ENG S-OFF in any order (the ENG S-OFF tool has a box to tick whether you have Radio S-OFF or not); I don't think that's the problem here.
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
raze599 said:
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
Click to expand...
Click to collapse
Yeah, that should be fine. If you didn't allow it root access when you ran it then it's not going to have been able to do anything. Reboot, clear the request in your superuser app and start again.
You don't mention it, but I assume you've already used Visionary to permroot before you tried the S-OFF tool? Just a thought when you mentioned you didn't get the su request on the phone.
raze599 said:
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
Click to expand...
Click to collapse
Lol this is quite funny. I was actually instructing him over skype and then when I left Skype last night he did something and it worked lol THANK GOD!
I have no idea what he did but wierd things happen when I'm not looking lmao
Still though, since we have had some major problems, do you recommend that we install an RUU and start again from scratch? Just to avoid any future problems?
EDIT: Yes it was Permrooted, the superuser came up when he tried it himself and it worked.
I wouldn't bother personally; as long as you're s-off it doesn't matter how you got there. It's not like the phone's going to be left half s-on or something.
Besides, why let him waste time redoing that when he should be using that time to flash a load of new ROMs
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Thanks very much
Hi! I bought this evo 4g from cl and it turned out to be flashed to cricket.
I want to flash it back to sprint so I can use it. I've read a lot and tried a lot but nothing helps. It looks like my problem is that:
1) it is now unrooted, so I don't have access to terminal so fastboot is not an option
2) it has a bad USB. I don't know if it is the hardware, or because of the previous flash
So my only chance is to load the PC36IMG to SD card and flash it from there. For some reason, whenever I do it, it loads it, checks it and goes back to bootload. This happens to all PC36IMGs I tried (maybe 6-7 of them) EXCEPT the following one:
PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip
However, this one does not work either. After it checks it, it gives the error that "MAIN VERSION IS OLDER"
I searched and found the solution, but all required USB port which I don't have. So is there anyway I can still revive this?
This is my info on top of phone.
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
Radio-2.15.00.12.19
Dec 21 2011, 12:50:32
Thank you for all the help!
zhuzhugun said:
Hi! I bought this evo 4g from cl and it turned out to be flashed to cricket.
I want to flash it back to sprint so I can use it. I've read a lot and tried a lot but nothing helps. It looks like my problem is that:
1) it is now unrooted, so I don't have access to terminal so fastboot is not an option
2) it has a bad USB. I don't know if it is the hardware, or because of the previous flash
So my only chance is to load the PC36IMG to SD card and flash it from there. For some reason, whenever I do it, it loads it, checks it and goes back to bootload. This happens to all PC36IMGs I tried (maybe 6-7 of them) EXCEPT the following one:
PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip
However, this one does not work either. After it checks it, it gives the error that "MAIN VERSION IS OLDER"
I searched and found the solution, but all required USB port which I don't have. So is there anyway I can still revive this?
This is my info on top of phone.
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
Radio-2.15.00.12.19
Dec 21 2011, 12:50:32
Thank you for all the help!
Click to expand...
Click to collapse
It doesn't look as if you are rooted...security is on...you are on the most recent hboot so flashing a prior RUU won't work. I think you will need usb, or pull the sd card out and put it in a computer and put any files you need on them...not sure what steps you found for fixing it.
Yes, that's what I did. I put PC36IMG.zip onto SD card with my computer. But still if either never goes out of the loop or gives the "older" error.
Are you suggesting I should look into downgrading hboot? I think I saw something like that while I was looking through internet. I hope it does not require usb port. though. any suggestion will be helpful.
klharalson said:
It doesn't look as if you are rooted...security is on...you are on the most recent hboot so flashing a prior RUU won't work. I think you will need usb, or pull the sd card out and put it in a computer and put any files you need on them...not sure what steps you found for fixing it.
Click to expand...
Click to collapse
I located that downgrade hboot thread. And it does require USB and it seems to be for old Hboot to downgrade to older version. Not sure if it applies to mine either. Experts please help!
zhuzhugun said:
Yes, that's what I did. I put PC36IMG.zip onto SD card with my computer. But still if either never goes out of the loop or gives the "older" error.
Are you suggesting I should look into downgrading hboot? I think I saw something like that while I was looking through internet. I hope it does not require usb port. though. any suggestion will be helpful.
Click to expand...
Click to collapse
zhuzhugun said:
I located that downgrade hboot thread. And it does require USB and it seems to be for old Hboot to downgrade to older version. Not sure if it applies to mine either. Experts please help!
Click to expand...
Click to collapse
HBOOT 2.18 is the most recent hboot so you would need to unlock the bootloader to downgrade with RUU. See this thread, it doesn't look like you can without usb http://forum.xda-developers.com/showthread.php?t=1542193
The error message I saw "main version" being newer. I thought it means the PC36IMG is older than what's on the phone. Am I wrong? Was it referring to the hboot? Could anybody explain to me?
klharalson said:
HBOOT 2.18 is the most recent hboot so you would need to unlock the bootloader to downgrade with RUU. See this thread, it doesn't look like you can without usb http://forum.xda-developers.com/showthread.php?t=1542193
Click to expand...
Click to collapse
zhuzhugun said:
The error message I saw "main version" being newer. I thought it means the PC36IMG is older than what's on the phone. Am I wrong? Was it referring to the hboot? Could anybody explain to me?
Click to expand...
Click to collapse
It means you are running the most current version either 4.67 or the one that just came out. Both 4.67 and the newest have HBOOT 2.18 which to revert back to an older version such as 4.54 with HBoot 2.16 you would have to unlock the bootloader. You will not be able to install an older RUU without usb port. With the PC36IMG zip, also comes the HBOOT version that gets installed during the process so you will keep getting the error because your phone has the newest version on it.
So do I have both the software version and the hboot version being old before I can do anything, OR I can recover with one of them being old?
Also, do you think my usb port is really bad, or it's the software?
Thanks Man!
klharalson said:
It means you are running the most current version either 4.67 or the one that just came out. Both 4.67 and the newest have HBOOT 2.18 which to revert back to an older version such as 4.54 with HBoot 2.16 you would have to unlock the bootloader. You will not be able to install an older RUU without usb port. With the PC36IMG zip, also comes the HBOOT version that gets installed during the process so you will keep getting the error because your phone has the newest version on it.
Click to expand...
Click to collapse
zhuzhugun said:
So do I have both the software version and the hboot version being old before I can do anything, OR I can recover with one of them being old?
Also, do you think my usb port is really bad, or it's the software?
Thanks Man!
Click to expand...
Click to collapse
Does your computer recognize the phone? if so, then no...its not bad. If its not bad then this gets way easier for you to do. Captain Throwback has a guide that details how to gain s-off on 2.18 (Google unroot 2.18 mikmik). If you are not wanting to root, and just get back on sprint network...try this thread and see if this works http://forum.xda-developers.com/showthread.php?t=937652 as it is a guide to get back to sprint from being flashed to cricket. You may not need to be unrooted (didn't look). Hope this helps
Edit: of course if the usb port is bad...get it fixed!
The computer charges it, but does not recognize either with HTC Sync or as disk drive. It does not make the little noise when connected either. Is that typical for real bad port?
And how do I fix the port? does it require soldering etc, or just unscrew everything carefully and put in the replacement port? Thanks!
klharalson said:
Does your computer recognize the phone? if so, then no...its not bad. If its not bad then this gets way easier for you to do. Captain Throwback has a guide that details how to gain s-off on 2.18 (Google unroot 2.18 mikmik). If you are not wanting to root, and just get back on sprint network...try this thread and see if this works http://forum.xda-developers.com/showthread.php?t=937652 as it is a guide to get back to sprint from being flashed to cricket. You may not need to be unrooted (didn't look). Hope this helps
Edit: of course if the usb port is bad...get it fixed!
Click to expand...
Click to collapse
Anyone help please!
zhuzhugun said:
Anyone help please!
Click to expand...
Click to collapse
Sorry about the delay...it makes me wonder if it is a SD card issue. You might try clearing/formatting the SD card through phone settings
Sent from my PC36100 using xda premium
Not a problem. I appreciate your help.
I did format the SD card once. But at that time, I might not be using the correct PC36IMG. I'll try it again.
But I am totally new on this. Could you suggest the best sequence to try things? And which PC36IMG I should use? (I downloaded many of the ROMs on XDA and only one of them gave me the hope of working but failed because of main version older error). I realize I might be totally using the wrong zip file. Also, should I worry about doing anything like flashing the kernal etc? Most instructions involve USB port and not sure whether my case will need additional tweaks.
Just quick reminder:
No USB. Not rooted. My software version is 4.67... And HBoot 2.18. S-ON.
I'll report back once I try it. Thanks a lot!
klharalson said:
Sorry about the delay...it makes me wonder if it is a SD card issue. You might try clearing/formatting the SD card through phone settings
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Up! Up!
zhuzhugun said:
Not a problem. I appreciate your help.
I did format the SD card once. But at that time, I might not be using the correct PC36IMG. I'll try it again.
But I am totally new on this. Could you suggest the best sequence to try things? And which PC36IMG I should use? (I downloaded many of the ROMs on XDA and only one of them gave me the hope of working but failed because of main version older error). I realize I might be totally using the wrong zip file. Also, should I worry about doing anything like flashing the kernal etc? Most instructions involve USB port and not sure whether my case will need additional tweaks.
Just quick reminder:
No USB. Not rooted. My software version is 4.67... And HBoot 2.18. S-ON.
I'll report back once I try it. Thanks a lot!
Click to expand...
Click to collapse
zhuzhugun said:
Not a problem. I appreciate your help.
I did format the SD card once. But at that time, I might not be using the correct PC36IMG. I'll try it again.
But I am totally new on this. Could you suggest the best sequence to try things? And which PC36IMG I should use? (I downloaded many of the ROMs on XDA and only one of them gave me the hope of working but failed because of main version older error). I realize I might be totally using the wrong zip file. Also, should I worry about doing anything like flashing the kernal etc? Most instructions involve USB port and not sure whether my case will need additional tweaks.
Just quick reminder:
No USB. Not rooted. My software version is 4.67... And HBoot 2.18. S-ON.
I'll report back once I try it. Thanks a lot!
Click to expand...
Click to collapse
do you have usb debugging enabled?
I'll try it again. Thanks for the suggestion.
Are you suggesting my computer not recognize the phone because usb debugging not on? Or is it needed for flashing with PC36IMG?
I tried it again and made sure the debugging is on, but the computer still does not recognize it. I haven't yet tried to flash it again.
ak074 said:
do you have usb debugging enabled?
Click to expand...
Click to collapse