New phone, new issues. Unable to root!?! - Desire General

Ok, so I got my new Eris today, the trackball quit on my old one, so VZW sent me a replacement. I get the phone, boot it up, and it's already running 2.1. Never thought anything about it, but a little while later when I tried to root the phone, I kept running into the same problem.
I've tried two versions of PB00IMG.zip, the first release, and the more recent post on XDA from Ivan. Neither have worked, the phone just keeps giving me the following message:
Main Version is older!
Update Fail!
Do you want to reboot device?
<Action> Yes
I've also tried the MR2 RUU downgrade method, which also failed. Anybody have any idea what to do here?

Try moving this over to eris android development, I think they are working on a root for 2.1, I would head over there to ask them.
Sent from my ADR6300 using Tapatalk

Related

[Q] Can Someone please help me! :/

Okay, so I installed a leaked OTA on my phone which gave it 720p and yadi yada..its not the FroYo update. Anyway, so i want to downgrade, but i cannot get my phone rooted at all. I tried doing the Unrevoked method, and heres the mutiple things that happened...It will stay stuck saying pushing recovery...or it will reboot completely and stay stuck saying waiting for reboot, or it will say communtications lost(or something like that), or it will say waiting for system to settle. But it WILL NOT root...at first i thought it was my computer, but i tried it on another one and got the same results. Not only do i want to get rid of the update, but before i installed the OTA, i installed the Droid Incredible official boot animation on there and i cannot get it off nor can i get any other boot animations on there.....in general, i want it to be factory fresh. PLEASE HELP!
Dod you uninstall htc synch
Sent from my ADR6300 using XDA App
no i didnt, was i suppose to?
Yes. That will mess up root process
Sent from my ADR6300 using XDA App
schwartzman93 said:
Okay, so I installed a leaked OTA on my phone which gave it 720p and yadi yada..its not the FroYo update. Anyway, so i want to downgrade, but i cannot get my phone rooted at all. I tried doing the Unrevoked method, and heres the mutiple things that happened...It will stay stuck saying pushing recovery...or it will reboot completely and stay stuck saying waiting for reboot, or it will say communtications lost(or something like that), or it will say waiting for system to settle. But it WILL NOT root...at first i thought it was my computer, but i tried it on another one and got the same results. Not only do i want to get rid of the update, but before i installed the OTA, i installed the Droid Incredible official boot animation on there and i cannot get it off nor can i get any other boot animations on there.....in general, i want it to be factory fresh. PLEASE HELP!
Click to expand...
Click to collapse
If your having trouble with unrevoked make sure you have the bootloader driver installed and that you have htc sync removed along with the my htc driver uninstalled
Yes and the drivers too!
Sent from my ADR6300 using XDA App
thankyou guys so much, it worked!

[Q] Problems flashing custom roms

I've got a fully rooted, fully NAND unlocked evo4g and I've been having a lot of trouble flashing custom roms.
Right now I'm trying to flash Cyanogen 6.0.0 and i'm getting the following error (check the attachment for a pic of the error).
I've googled the problem and all I could draw from my research was that I needed to download a new PCM132.IMG.
Tried that, and I still get the same error message.
What am I doing wrong?
Any help is appreciated...
Cyanogen roms need the .76 bootloader.
This site has the right one you need:
http://theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
Sent from my PC36100 using Tapatalk
Thanks for the quick response. I'll try that right now and let you know how it goes.
Now I seem to be having a whole new slew of problems...
I followed the instructions, finished it, then went to check if I had the 0.76 bootloader.
Nope, still running 0.93. So i figured I would try reinstalling the drivers using the USBDeview.exe that he said to use.
But, when I unplug and plug my phone back in, no drivers install. I'm assuming I'm going to have to do it manually, but where can I find the drivers for my EVO?
The second problem is that I can't go into recovery through bootloader or quick boot.
I'm hoping that's just a problem because the drivers aren't installed, otherwise I'm boned.
Thanks for your help..
Did you go through every single step they had? Or did you just flash the pc36img file?
Sent from my PC36100 using Tapatalk
Fixed it, everything worked out perfectly. Except for now my CM6 doesn't have the google market....
downlikealedzep said:
Fixed it, everything worked out perfectly. Except for now my CM6 doesn't have the google market....
Click to expand...
Click to collapse
thats because you must download and flash GAPPS from here
http://mirror.kanged.net/gapps/gapps-hdpi-20100817-signed.zip
and another question. any specific reason you are flashing a cm6 nightly for 7-19? the final release of 6 is out and there are new nightlies.

[Q] Problems Rooting Incredible

I tried searching for a solution to this but am having a hard time finding anything.
Basically, I am trying to root my friend's Incredible for him with unrevoked and I'm having some trouble.
First I got a message that there was a problem with the CID backup. I talked to some people from the unrevoked team and they gave me a fix but they then said that he had a weird unusual file they would have to look into.
So then I tried again for the hell of it and instead of that error message I got one saying that root failed perhaps my firmware version isn't supported.
Does anyone know if a firmware version isn't supported and if there is a manual method using adb?
Thanks for any help
I am also trying to root a friends right now. I have the hboot drivers installed, but it just says "Pushing Recover" forever and never does anything. Sucks!! I have rooted quite a few Evo's without a hitch........this is a realy bummer
I've rooted my incredible without any issues in the past, that seems kind of strange.. hopefully unrevoked team can get that figured out for you.
Yeah, I've rooted a bunch of Evos and I don't think any of them went through with out a flaw and I had to use adb for all but one.
Is it a SLCD incredible? I had an unusually hard time with my lady's inc. Meanwhile mine was rooted first time. Wonder if changes between the 2 shipments happened? I just kept trying and eventually it went. Hardest part was to get her computer to accept the ADB Drivers...
I'm not sure, would that be in the about phone setting or is it associated with a certain hard ware version? How many times did you try it cause I think we did at least five haha.
Also were you getting similar error messages?
You can tell by the screen itself. If there's a backlight its an SLCD. But sadly I have no idea if it really makes a difference. It took me 3 tries and it randomly worked. I changed nothing in my method.
You don't remember the error messages you got were do you?
I personally don't know how you could tell which one you had. Maybe google search your phone's model number or hardware version to see there are any answers out there.
I used a Mac to root my Inc and it went smoothly after two tries haha. The Mac version does not require you to install drivers, so if you want to try that method have at it.
if you go into settings/about phone/hardware, and if under hardware version it says 0002 its "amoled" and if its says 0003 its "slcd".

Replacement EVO has the OTA...

compliments of the local repair center.
Needless to say, I'm not rooted. What's my options?
Unfortunately for you, you have to wait until a root method is available for the newest firmware. Or find someone with an evo that hasn't taken the ota update, and doesn't care about rooting and trade phones
Vinchenzop, I don't mean to steal someone's thread with this question but it looks like you answered his question with what might just be the answer to mine so I'll ask it here. I think (I know) I did something very stupid yesterday after I uploaded to 2.3.3 on my rooted phone. I did it from here, not the official update and when I was done I know I was still rooted because I restored everything with Titanium backup. Well, seems Titanium on the auto backup didn't back everything up every night like I set and some of the backups missed data or some programs just weren't there so I did a restore of my programs from My Backup Pro. Something in there must've unrooted me because now when I open Titanium it says, after the request for approval to use it pops up, Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and includes BusyBox, and try again.
When I open Wireless tether it says it's been granted superuser permission but then says unable to start tethering, is your devise rooted?
Help please.
If you have s-off in bootloader you're still rooted. Try going to recovery and flashing this superuser fix/reboot and your permissions should work again.
http://db.tt/9D4X8hg
Sent from my PC36100
Just a quick reply, I'm on the road (pulled over) can't see my previous response but after that didn't work I went back into recovery and saw the option to reset permissions. You're a miracle worker. THANK YOU SO MUCH. I'm back to root.
RickMG said:
Just a quick reply, I'm on the road (pulled over) can't see my previous response but after that didn't work I went back into recovery and saw the option to reset permissions. You're a miracle worker. THANK YOU SO MUCH. I'm back to root.
Click to expand...
Click to collapse
Glad you got it fixed man!
Sent from my PC36100
Rick, check your pm
dirkyd3rk said:
If you have s-off in bootloader you're still rooted. Try going to recovery and flashing this superuser fix/reboot and your permissions should work again.
Sent from my PC36100
Click to expand...
Click to collapse
dirkyd3rk said:
Glad you got it fixed man!
Sent from my PC36100
Click to expand...
Click to collapse
dirkyd3rk, I just noticed my response and it was for anyone else having the problem that I had. I just wanted to say the response was meant to say that I downloaded the file you mentioned above which eventually is the reason I was able to get back my root. I just needed the one more step I listed above about going back into recovery after doing your instructions and that is when I saw the option to "Reset Permissions" which I never saw before your fix and that did the final trick. Thank you so much again.
p.s. I had to delete your link above because I do not have enough posts but all those who might need it can see it in your original response to me.
RickMG said:
dirkyd3rk, I just noticed my response and for anyone else having the problem I had I just want to say the response was meant to say that I downloaded the file you gave me which eventually is the reason I was able to get back my root. I just needed the one more step I listed above about going back into recovery after your instructions and then I saw the option to "Reset Permissions" which I never saw before your fix and that did the final trick. Thank you so much again.
p.s. I had to delete your link above because I do not have enough posts but all those who might need it can see it in your original response to me.
Click to expand...
Click to collapse
No problem man either way you're back in business that's all that matters lol.
Ok, posting in this thread bc its the closest subject to what i have going on.
I got my evo replaced last night for antenna issues. Old one had Fresh on it, and i want it back.
I am using the same memory card as was in my old evo
current phone has 2.2 build 3.70.651.1
this thread says there isnt a way to root with latest OTA. But the read first thread under Q&A says that my build is supported.
So i followed the instructions under xHausx guide and im getting stuck.
When i run my autoroot.bat file as administrator it opens up dos prompt and says
'res\ini.cmd' is not recognized as internal or external command, operable program or batch file.
ERROR Cannot load init file! Make sure you extract everything out of the zip!
I downloaded the autoroot 2.5 file through the mirror linked on the guide and extracted it. I have HTC sync 2.0.35. (i know there is a new version 3.0 available but as it just came out yesterday i am assuming that the version is not needed for this method)
Debugging is checked
Phone was in charging mode
Any thoughts?
Im trying not to get discouraged. This is what happens when you let someone else root it the first time and dont pay attention.
I think i posted almost all details that i could think of.
Randomsilliness said:
Ok, posting in this thread bc its the closest subject to what i have going on.
I got my evo replaced last night for antenna issues. Old one had Fresh on it, and i want it back.
I am using the same memory card as was in my old evo
current phone has 2.2 build 3.70.651.1
this thread says there isnt a way to root with latest OTA. But the read first thread under Q&A says that my build is supported.
So i followed the instructions under xHausx guide and im getting stuck.
When i run my autoroot.bat file as administrator it opens up dos prompt and says
'res\ini.cmd' is not recognized as internal or external command, operable program or batch file.
ERROR Cannot load init file! Make sure you extract everything out of the zip!
I downloaded the autoroot 2.5 file through the mirror linked on the guide and extracted it. I have HTC sync 2.0.35. (i know there is a new version 3.0 available but as it just came out yesterday i am assuming that the version is not needed for this method)
Debugging is checked
Phone was in charging mode
Any thoughts?
Im trying not to get discouraged. This is what happens when you let someone else root it the first time and dont pay attention.
I think i posted almost all details that i could think of.
Click to expand...
Click to collapse
Your phone luckily wasn't updated to the 2.3 OTA, so you can still root it. I have no experience with the Autoroot method, so unfortunately I cannot help you there. I can recommend using unrevoked instead to root your phone.
You'll need to uninstall HTC Sync, and download the modified drivers from the unrevoked site & install them. Download the latest version (I believe it's called reflashpackage.exe once it downloaded). Everything else you should already have covered - debugging on, charge only, etc. There are video walkthroughs of unrevoked on YouTube, if that helps you.
Once you've installed the drivers, plugged the phone in, and started unrevoked, it should only take about five minutes or so. The phone will reboot a couple of times, wait for it to say "done", then you're rooted. Unrevoked installs ClockworkMod, if you'd rather use Amon Ra you can get it from Rom Manager or from xda.
I'm sure that Autoroot is a great program, I just don't have experience with it. I've rooted with unrevoked once, and it was the easiest process I've seen for fully rooting/nand unlock.
Good luck!
...oh, and don't restore any nandroid backups from your old phone. User apps backed up with Titanium are fine, but nandroid backups are a baaaad idea.
(from... Evo/MIUI/Tapatalk)
Uninstall HTC sync would be my first thought...then start again with just the usb drivers.
Thanks, gonna try that method now. What better way to spend an evening right???
LOL
Ok.
Followed the instructions on Unrevoked.
Downloaded unrevoked 3.
installed drivers.
restarted phone,
opened unrevoked 3.
Program ran, then kicked off error “Error: failed to get root. Is your firmware too new?"
Looked up a few forums that says boot to bootloader and clear storage.
While doing this i noticed it says S-Off now.
Cleared storage, rebooted and ran unrevoked. It went through its little speal and rebooted the phone a few times.
now unrevoked says "done" However, i still have stock HTC Sense.
*slams head on laptop*
Ok, so i found a thread that suggested downloading root checker.
it says i have root access.
So if im thinking correctly i just need to install a rom that i like?
Randomsilliness said:
Ok.
Followed the instructions on Unrevoked.
Downloaded unrevoked 3.
installed drivers.
restarted phone,
opened unrevoked 3.
Program ran, then kicked off error “Error: failed to get root. Is your firmware too new?"
Looked up a few forums that says boot to bootloader and clear storage.
While doing this i noticed it says S-Off now.
Cleared storage, rebooted and ran unrevoked. It went through its little speal and rebooted the phone a few times.
now unrevoked says "done" However, i still have stock HTC Sense.
*slams head on laptop*
Click to expand...
Click to collapse
Ya...depending on what was imaged in the process, you will probably have a stock rom installed afterwards. I've done two EVO's (004) in the last day using this:
http://www.multiupload.com/HSWSV16NU0
when you are done..your will have a stock rooted sense.
But it sounds like you got through everything well, so no need to redo anything..happy flashing?
I still haven't got my replacement, apparently EVOs are backordered. I told the Sprint store to NOT update it to gingerbread. Told them I use Netflix too often and to leave it alone They said no problem.
Stuke00 said:
I still haven't got my replacement, apparently EVOs are backordered. I told the Sprint store to NOT update it to gingerbread. Told them I use Netflix too often and to leave it alone They said no problem.
Click to expand...
Click to collapse
I did notice when I picked the one up for my son yesterday at Best Buy, they were updated the two customers before me. Did the same thing...just took the box without him even opening it and did my own thing.
After 2 replacements in a week on mine..today the third one came in and had the same solar flare in the middle of the screen. The guy at the sprint store was now a little more sympathetic and went and got a new 004 out of the back and let me do the activation myself...whew..no update done on that one either!
Randomsilliness said:
now unrevoked says "done" However, i still have stock HTC Sense.
*slams head on laptop*
Click to expand...
Click to collapse
It's normal to have stock HTC Sense after you root (at least with unrevoked). Do you have Superuser in your app list?
bkrodgers said:
It's normal to have stock HTC Sense after you root (at least with unrevoked). Do you have Superuser in your app list?
Click to expand...
Click to collapse
Yes i did have it. I copied my rom zip file over and installed it ... so i think everything is good.
Fresh 3.5
Tho my antenna is now going in and out a lot (which it didnt before the root, thats why i got the old one replaced due to it going in and out)
and 3g is SUPER slow.
Any ideas?

[Q] Bricked Evo Help!!!

So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Do you have htc sync installed? It won't work unless you have the actual htc sync suite installed. Just google it won't cost you anything. I semi bricked my phone but I fixed it. Maybe some things I done in this thread could help you. Just skim through a few of my posts'.
http://forum.xda-developers.com/showthread.php?t=1100781
Sent from my PC36100 using Tapatalk
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
My last tip would be to put the phone in fastboot and then run the 3.29 ruu exe. It worked for me, here's the link. Just make sure you have htc sync installed and it's not running when u try to run the ruu (from fastboot in bootloader).
http://goo-inside.me/supersonic/sto...0.09.01_NV_1.77_CNV_release_150224_signed.exe
Sent from my PC36100 using Tapatalk
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
I selected the old one because that one never gives me issues, the 3.30 and 3.70 never work for me
Sent from my PC36100 using Tapatalk
k2buckley said:
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
Click to expand...
Click to collapse
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
lokoalex said:
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
Click to expand...
Click to collapse
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
A1Lonestar said:
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
Click to expand...
Click to collapse
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
lokoalex said:
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
Click to expand...
Click to collapse
Just make sure that the file is named PC36IMG.zip (exactly that).
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
k2buckley said:
Just make sure that the file is named PC36IMG.zip (exactly that).
Click to expand...
Click to collapse
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
linsalata28 said:
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My brother is impulsive and he didnt like the fact that it bricked on him. If it was me I would have definitely taken it to sprint.
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
linsalata28 said:
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not a bad idea. Might have to find some of those guys.
k2buckley said:
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
Click to expand...
Click to collapse
I've been trying man. Im getting nowhere with this. I tried the RUU 3.70 and it just crashed asked me if I wanted to debug. So im gonna try one of the older versions. At least its seeing these with the HTC sync working.
lokoalex said:
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
Click to expand...
Click to collapse
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
k2buckley said:
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
Click to expand...
Click to collapse
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Maybe try to update or downgrade your hboot version.
Sent from my PC36100 using XDA App
*Assuming you're working on a windows machine*
Go to this site http://shipped-roms.com/index.php?category=android&model=Supersonic
and download ruu 3.70.
Without your phone connected, run the ruu until it gets to the first dialog box (it should have a checkbox that says "I understand the caution..." blah blah).
With this dialog still open, go to start > run and type "%TEMP%" without quotes.
Inside this folder look for a file called "rom" or "rom.zip" (you are going to have to go through all subfolders) depending on your windows settings (Hide extensions for known file types).
When you find it move it to your desktop and rename it to "PC36IMG" or "PC36IMG.zip" accordingly.
Get a card reader and take your sdcard out of your phone and place it in the card reader. Place the PC36IMG file you renamed on the root of the sdcard. Install your sdcard back into the phone and boot into bootloader. This should scan the card and find the PC36IMG and reinstall a bone stock non-rooted 2.2 rom.
If this method fails, it's possible the nand may have been corrupted in the update process. I'm better at troubleshooting if I have the device with me so this is the best I can do.
lokoalex said:
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Click to expand...
Click to collapse
That is frustrating. It sounds like there may be a problem with your current boot.img, and maybe that's why it won't let the RUU re-write the boot.img when it's trying. That would also explain you not being able to boot, because if your bootloader is corrupted somehow, then you won't be able to get anywhere at all. Unfortunately, the bootloader you're on (HBOOT-2.16)isn't downgradeable. I'm starting to suspect that you're getting the bootloader version error because when you run the older RUU, it will try to flash an older version of hboot. Since the version you're on is NOT able to be downgraded, it's probably erroring out when it tries to downgrade, but it can't. I would suspect that if the RUU for the 4.22 software was available and you were able to run that one, then it would succeed. The problem is that you're trying to downgrade, and you can't do that. I'm not sure what went wrong when the OTA was accepted, but it seems like something did, and now you're stuck. I would guess that the only way to fix it would be to reflash the OTA (which you can't because you can't boot), or run the RUU for 4.22, which isn't available yet. My speculations may not be accurate, but that's my guess!

Categories

Resources