I've done my searches here, and keep finding dead threads, or no real answers. My friend has an evo(me too, but I got mine rooted), and he wants to root. He is running 1.47 and hboot 0.79. I keep getting main version is older. I've used simpleroot to do this twice, so I know I'm using it correctly. Also switched SD cards. Another friend had the same thing, but his rooted. Is there anything I can do? Help me get root on his phone, and I'll donate a case of beer/dinner/whatever up to $20. First right answer gets it. Thanks! FOrgot to mention, I've been using simpleroot OTA, and it worked on mine and one another phone, but not this one
I had the same issue, when doing simple root it asks you to visit the flash website. When you do make sure to refresh the page again after the flash game loads. Once I did that I was able to fully root.
here this would work its way faster and easier
http://forum.xda-developers.com/showthread.php?t=720565
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=F8UN6Z3V93DL6
jacc1234 said:
I had the same issue, when doing simple root it asks you to visit the flash website. When you do make sure to refresh the page again after the flash game loads. Once I did that I was able to fully root.
Click to expand...
Click to collapse
Been down that road about twenty times. No dice. Thanks for the suggestion, though
jonathanflores: Forgot to mention, simpleroot is what I've been using. Doesn't work.
are you wanting to just get back to 1.32 or trying to root 1.47?
Yellowcard8992 said:
are you wanting to just get back to 1.32 or trying to root 1.47?
Click to expand...
Click to collapse
I'm trying to gain root access for wifi tether. That's all that matters is wireless tether, and not paying $30 a month for it.
Make sure you wipe the phone and reset it back to stock before attempting the simple root method. he may have loaded something that is messing with the flash bug used to gain access.
Make sure you dont' get a write error on step 3 when it asks you to go to the flash site. If you do start at step 1 again. The flash part is the key since that's the exploit they're using to get the old HBoot onto the EVO.
I got a write error at first. I put back in my 8gb card formatted it, started from step 1 followed every step to a T and was fine.
jahouse said:
Make sure you wipe the phone and reset it back to stock before attempting the simple root method. he may have loaded something that is messing with the flash bug used to gain access.
Click to expand...
Click to collapse
This was done multiple times. At least 8 times, and that's minimum
donatom3 said:
Make sure you dont' get a write error on step 3 when it asks you to go to the flash site. If you do start at step 1 again. The flash part is the key since that's the exploit they're using to get the old HBoot onto the EVO.
I got a write error at first. I put back in my 8gb card formatted it, started from step 1 followed every step to a T and was fine.
Click to expand...
Click to collapse
Hmmm...I'll check. Thanks
samfreese said:
This was done multiple times. At least 8 times, and that's minimum
Hmmm...I'll check. Thanks
Click to expand...
Click to collapse
The Write error in step 3 appears briefly in the command window that pops up and it still lets you hit enter and continue like it worked.
I had some issues on a friends evo with simpleroot. I found that the issue was not all files were being pushed properly to the device. I checked after step 1 (booting into Windows, checking the SD card.) I noticed that the flash file was not on the SD card some of the times. Check that, make sure you have all the files.
Once I verified that all the files were on there, it worked perfectly.
Phyllip J FRy said:
I had some issues on a friends evo with simpleroot. I found that the issue was not all files were being pushed properly to the device. I checked after step 1 (booting into Windows, checking the SD card.) I noticed that the flash file was not on the SD card some of the times. Check that, make sure you have all the files.
Once I verified that all the files were on there, it worked perfectly.
Click to expand...
Click to collapse
That's a good piont the writing step in step 1 can take longer. You gotta make sure it showed everything go through. One file takes 5 minutes and shows nothing on the screen as it's copying. You may want to check the SD card afterwards that all the files it said it copied are present on the card.
Use the manual method I posted originally (simpleRoot is based off of it). It works, I've done 4 EVOs with it personally.
Have you tried Unrevoked3? unrevoked .com/recovery
Related
I'm guessing I'm just stupid. I'm trying to root my Evo 4G and it isn't working.
When I run this:
[Program] SimpleRoot .1 ---- 3 Click Root w/ nand unlock!!
(i cant post links apparently so ive mangled it)
ht tp://forum.xda-developers.com/showthread.php?t=706411
Step one seems to work: I go
On step 2 there are permissions errors:
(i cant post links apparently so ive mangled it)
ht tp://img153.imageshack.us/img153/9895/fails.png
and at the end of step 2 the instructions say 'once you see the white screen with the androids...'
However my phone is just sitting here on, not rebooting from step 2.
I originally tried the manual steps for rooting and nand unlocking but also ran into permission errors, which made me think I should use the automatic method.
What version number are you running? 1.47? If so then you'll need the new version of Simple Root.
I just got the phone yesterday and updated everything fully.
However I just downloaded all the files for this rooting tonight, so they should be the newest versions as well. Also I was under the impression that I was supposed to lose my apps from doing the rooting. I still have them all.
1.47.651.1 is the software number.
You need the newest simple root the poster above linked, the one you downloaded is for the previous un-updated software.
OK I got you.
I'm following these steps now then:
ht tp://forum.xda-developers.com/showthread.php?t=715915
at this point I'm totally lost.
The instructions say,
Note: This process will only work if you already have the engineering HBOOT. (If you have NAND unlocked, you already have it and can proceed confidently.) If you'd like to check the actual version, you can boot into HBOOT and look near the top of the screen: it should say HBOOT-0.76.2000, not 0.79.0000. If you have 0.79.0000, you will need to do Toast's Part 2 first before starting here.
Click to expand...
Click to collapse
I checked and mine says 0.79.0000 so I need to do Toast's Part 2 first.
Toast part 2's first step is:
go into the recovery provided in the PART 1 root method and do a nandroid backup before u begin this. we will use this nandroid at the end of this tutorial to get u back where u were.
Click to expand...
Click to collapse
Toast's part 1 part about nandroid backup says:
adb reboot recovery
- this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to.
For Windows XP ~~> Run recovery-windows.bat
For Vista and Windows 7 do it as Admin
- at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system.
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard.
Click to expand...
Click to collapse
When I do adb reboot recovery, it brings my phone to a symbol of a phone with a red triangle and exclamation mark, with no option to choose anything.
n4th4nr1ch said:
at this point I'm totally lost.
The instructions say,
I checked and mine says 0.79.0000 so I need to do Toast's Part 2 first.
Toast part 2's first step is:
Toast's part 1 part about nandroid backup says:
When I do adb reboot recovery, it brings my phone to a symbol of a phone with a red triangle and exclamation mark, with no option to choose anything.
Click to expand...
Click to collapse
Use pongoface's method of Simpleroot OTA pg. 70 post 691.
http://forum.xda-developers.com/showthread.php?t=720565&page=70
I have the same issue, I am following these directions here... Ill post my results. Same boat as op though.... had it at onepoint, lost it while trying to fix 4G...
Fail, My issue appears to be different than n4th4nr1ch's though. I am not seeing the skateboarders. I can see them with a volume down/power off, however selecting recovery produces the red triangle. I have the old 0.79.0000 as well. What sucks is that i had it at one point. I think I read somewhere that I am bjorked Do it manually during ota causes a Main old version error and fails to update Also I get this during the flash hack step 3
/sdcard/part3: cannot create
/data/app-cache/com.android.browser/BEC48C17295CAF9F550BCD500A0A6F03
/data/app-cache/com.android.browser/BEC48C17295CAF9F550BCD500A0A6F03/foo directory non existant
Something i did broke the flash hack i fear
In my case from above, Trying to get to Ra or Clockwork from the OTA simpleroot produces the same red triangle....
Again,
on step 2 of the auto installer I get errors: permission denied.
OK it looks like you were talking about a slightly different auto installer called Simple Root which has 4 steps. I followed the post and everything succeeded as far as I can tell.
Now on to figure out how to get fresh rom working
n4th4nr1ch said:
OK it looks like you were talking about a slightly different auto installer called Simple Root which has 4 steps. I followed the post and everything succeeded as far as I can tell.
Now on to figure out how to get fresh rom working
Click to expand...
Click to collapse
unfortunately I failed at the other installer as well
mrloserpunk said:
unfortunately I failed at the other installer as well
Click to expand...
Click to collapse
make sure you have all the requirements on your pc and do a factory reset of your phone before you start.
First and formost, I'd like to thank ya'll for creating these awesome guides/ROMS/walk throughs and tools for rooting. That's a talent i'll unfortunately never have.
But to get to what I'm peeved about, everytime I try to root my EVO (I have the OTA update, 1.47.**.**.**), I get to the portion of the flash hack. I load the site/sites the first time. The command line tells me to refresh the page, but never tells me it's complete and to move onto the next step. I've performed every method I could find, each several times, and get caught with the same error everytime. OTA Simple, the other one written by the same author, another method with a batch file that automates it, etc. I'm at my whit's end!!
Any insight could help.
Also, SuperUser is installed from a previous failed attempt. I'm not sure if that would affect anything. Thanks guys, and keep up the awesome work!
Try using the original 1.32.xx... RUU and going back to stock then use the other Simple Root app for that version.
bm1322 said:
First and formost, I'd like to thank ya'll for creating these awesome guides/ROMS/walk throughs and tools for rooting. That's a talent i'll unfortunately never have.
But to get to what I'm peeved about, everytime I try to root my EVO (I have the OTA update, 1.47.**.**.**), I get to the portion of the flash hack. I load the site/sites the first time. The command line tells me to refresh the page, but never tells me it's complete and to move onto the next step. I've performed every method I could find, each several times, and get caught with the same error everytime. OTA Simple, the other one written by the same author, another method with a batch file that automates it, etc. I'm at my whit's end!!
Any insight could help.
Also, SuperUser is installed from a previous failed attempt. I'm not sure if that would affect anything. Thanks guys, and keep up the awesome work!
Click to expand...
Click to collapse
I had the same problems.....
best thing to do is wipe all your root files and start back at step one with simple root. When you get to step 3 and it tells you to continue to step 4 refresh the browser one more time just to be safe.
I kept getting stuck but deleting the root files and starting fresh worked for me.
firsttimer44 said:
I had the same problems.....
best thing to do is wipe all your root files and start back at step one with simple root. When you get to step 3 and it tells you to continue to step 4 refresh the browser one more time just to be safe.
I kept getting stuck but deleting the root files and starting fresh worked for me.
Click to expand...
Click to collapse
Awesome. I'm definitely gonna give this a try.
Anyone else have any other suggestions?
Still the same dam results
Hey ive been trying to root my evo all day it is on version 2.1-update1. I was able to root my brothers perfectly fine using the downloads and tutorial from the idiot-proof guide to rooting by thebiles. But on mine I get stuck right at the beginning, when i try to flash the PC36IMG my bootloader says main version older. I feel like ive tried everything if anyone can help I'd reallly appreciate it thanks.
Try simple root, and keep trying. I got that same error even with simple root on my buddies 3 times before it worked. Don't know why. Maybe try copying the pc36img to the sd card instead of letting simple root push it...gl!
I agree with the simple root approach. Not trying to highjack your post but I have a question back at you if I may. You say you have one root EVO and one not root? If so the the root has PRI 1.34 and the nonroot 1.40? Could you perhaps do a data speed comparison on these and post the results? I am real curious...
sorry man i saw your post like 2 minutes too late the simpleroot worked right before i refreshed this page thanks for the help though guys appreciate it
one more quick question while PC36IMG was flashing the 2nd "tp" file said bypassed next to it rather than OK like all the others and the first tp had a blank next to it...is this a problem i should look into before unlocking the nand and all that other good stuff?
No problem glad you got it working. This was kinda like going to the casino...getting up to go to the bathroom...coming back to see someone hit the jackpot on your machine....hahaha!!!
That is normal....mine did that.
thanks man appreciate it...one more question for anyone that can help, im using the idiot proof guide and im on step 56 but when i try to enter the adb shell i get an error from command prompt saying "error: more than one device and emulator" i entered the shell perfectly fine like 2 steps before that and used it to flash the new pc36img rom but now i get this error to enter shell again how do i fix this error?
Okay I came here thinking this might finally be it... but nope I tried all the solutions mentioned here but to no avail. I am frustrated and still getting the main version is older. Does anyone know what is causing this error. Please I'm using usb debugging I wiped and backed my SD and have ota that came out in June. I installed Microsoft net frame and htc drivers. I updated simple root and the update log said this was to fix the error but still getting the same error. Any suggestions
I have the same issue, pretty much have tried everything with no luck, kind bummed at the moment, hope someone can help
Thanks
I got to work FINALLY!!!!!
So finally i got the main version error older NO MORE. So i decided to share what i did in hopes that it will work for all of you frustrated out there.
1) Download simple root from xda forum, dont download it anywhere else. The first time i tried i downloaded it at another android forum and even though it may seem the same, this version for some reason was not pushing the files as it suppose to. So again download from forum. Search for it on XDA.
2) Be patient and prepare yourself.
3) Make sure you on the 147 ota version. Not froyo. or before any version before ota because you can use old simple root.
4) After you download it extract it to a folder. Choose whatever location suits you i like desktop so i can delete file after i use it and keep zip. Be sure to update the program. Open it and let it search for downlaod or go to root folder and search for the updater.
5) Before running the program check the obvious. Is usb debugging enable, Do i have microsoft netframe, Are my phone drivers correct. Is the usb cable correctly connected to my computer and phone. Did i choose charge only when connected to the computer.
6) Now on your phone, and this step did it for me, go to Settings>SDandPhoneStorage>FactoryDataReset. Brace yourself this will wipe data it will not change your version. But if you want do a backup the folder of your contacts and whatever you have in your SD card, this is the time to do so. Mount as disk drive, and remember to change back to CHARGE ONLY. I skipped this because rooting was more important than my girlfriends phone number.
7) Now youre noobiness is ready connect phone double check Step 5. In case you missed something.
8) Run the simple root downloaded from XDA forum. Wait for it to push files is wont take long but me patient. Think of it passing 180mb to sd card so it takes some time.
9) Phone will reboot in a screen with skating androids Push power button and WAIT. It will find file and you shouldnt be getting "main version older" reboot error you where getting if you paid close attention to detail. Now update push volume up.
10) Why so impatient wait for it to update files. Once its down just push volume up for reboot. First time it reboots after root or when u flash a rom it usually takes longer, enough to get u nervous but dont be WAIT.
11) Easy sailing now but youre not done yet. Hit recovery once your phone reboot. Choose the method you want i chose Clockwork it works just fine for flashing roms.
12) Congrats your fully root and can flash that cool rom youve been reading about. Suggestions: DamageControl or Cyanogen but go ahead and try whichever you like.
13) YOURE DONE WOOF
If for some reason, it happened to me with AvaFroyo, when you flash your rom it goes on a loop and keeps rebooting dont panic that is what the recovery is for just put your microSD on a card reader delete the rom that is giving you problem and place another one and Reflash. Read how to flash rom you have to wipe on Recovery menu everytime you flash a different rom.
I hope this helps...Its in plain english not Dev English so...
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?
OK, I posted in the Q&A section, but not finding much love. Hopefully someone here might be more help.
The first thing to put out there is that I did not accept the Gingerbread OTA. Still on 2.2.
Here's the story: A couple of days ago I tried running unrevoked on my Evo. One month old, HW version 0004. I'm pretty sure I did everything as instructed, but the procedure failed. Machine would run for 30 seconds or so then drop into diagnostic mode (5 vibrations & lock).
So I tried re-flashing back to stock. The first stock image I tried screwed the phone up in that: (1) it would no longer see USB connections (2) no longer saw my Micro SD card (3) would no longer charge when the phone was on.
So I tried flashing a newer stock image, the third one on this page:
http://forum.xda-developers.com/showthread.php?t=884060
That only made matters worse, as now I've lost bluetooth, too.
Keeping in mind that I cannot communicate with the phone via USB (unrevoked now just keeps waiting for me to plug the phone in, as does HTC Sync, which I installed after everything else as a last shot) and am not rooted, what are my options here? I really want to get this device back to stock, because I need a phone that works.
If I take it back to a Sprint repair store will they even look at it? Can they flash it back to stock for me or am I SOL there?
I've been thinking that I could let the OTA install and if everything's still broken take it to Sprint and tell them the OTA screwed up my phone, but I'm worried I've left traces that would tell them I'm bullshitting.
Hell at this point I'm willing to pay $$ to get this thing fixed, motherboard swap or whatever, but I'm not sure Sprint will even do that.
Gotta have my phone back guys, any help greatly appreciated.
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
TF1984 said:
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
Click to expand...
Click to collapse
I'm not rooted, though, so I doubt any files I could e-mail myself would do any good.
I am considering taking the phone back to Sprint, but I don't know whether to accept the OTA then make up some story about losing Bluetooth, SD Card access and USB, or just being honest and telling them what I did.
At this point I just want to get my phone back to stock and working as it should. I'll leave the rooting adventures to others. Rooting my Nook Color is one thing, since it's basically a $250.00 toy, but I can't live without my phone.
Try this:
http://forum.xda-developers.com/showthread.php?t=695243
However, will need root to fix the USB problem. You should look into some temp root options that will allow you to use a terminal emulator to fix the USB issue. I've never tried a temp root method, so you're going to have to do some digging around for that. Maybe someone who knows more about temp root can chime in and help.
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
TF1984 said:
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
Click to expand...
Click to collapse
So, accept the GB OTA, then?
My Sprint store is also a repair facility. Do they have hardware and tools that can re-flash the device to stock regardless of what you've done to it? because that's what I'm thinking of doing at this point.
My biggest problem with attempting to fix it myself is that not being rooted and not having USB access I seem to be SOL.
BTW: I just testes WiMax and it works, so at least my WiMax key is good.
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
plainjane said:
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
And unfortunately I don't have insurance, but I'll pay the repair fee if they ask me to.
dsf3g said:
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
Click to expand...
Click to collapse
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
rugedraw said:
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
Click to expand...
Click to collapse
Thanks, I'll try that. I saw that thread earlier, and I just noticed that someone answered my question about fastboot. So I'll see if I can fix USB using that.
What really bugs me now is the lack of Bluetooth!
XDA search is down right now so I can't see if there are any others who have experienced this.
Please note that with the link I gave you, you can fix the SD card not being detected issue, but to fix the USB port using those instructions, you need root. Since Unrevoked won't work without the USB, you would have to either try a temp root method (I've never used it so I can't offer you much help there) or some other manual root method where the USB port isn't needed.
Step 1, Go into Device Manager
Start Device Manager.
Windows 7
Click Start > Control Panel > System and Security > Device Manager. Windows Vista
Click Start > (Settings) Control Panel > (System and Maintenance) > Device Manager. Note If prompted, click Continue. Windows 2000 / XP
Click Start > (Settings) Control Panel > (Performance and Maintenance) > System > Hardware > Device Manager.
Step 2, These Devices are typically installed when you Install HTC Sync or Just connect your Android Device, If their are no conflicts uninstall all of them and restart your PC, Then Reconnect your android Device
The following devices are normally installed:
If a red X, yellow ! or yellow ? is displayed to the left of a listed device, a conflict is present and the drivers must be updated or reinstalled.
Note Driver conflicts may also be indicated by a device entry labeled Other Devices or Unknown.
Android USB Devices
My HTCDisk drives
HTC Android Phone USB DeviceModems
HTC Modem (if using as a tethered modem)Portable Devices
E:/ (Where E represents the assigned drive letter.)Universal Serial Bus controllers
USB Composite Device USB Mass Storage Device
kingakuma said:
Step 1, Go into Device Manager
...
Click to expand...
Click to collapse
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
dsf3g said:
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
Click to expand...
Click to collapse
are you using the same usb cable for the charger?
if so try a different usb cable
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
DomSim said:
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
Click to expand...
Click to collapse
Thanks, but how can I download or install this without an SD card mounted?
dsf3g said:
Thanks, but how can I download or install this without an SD card mounted?
Click to expand...
Click to collapse
ok, we can't help you if you do not follow directions. read my post, and those of the others who posted. one contains a link to a thread to fix the sdcard. you have been told to do this several times. i told you to do this first then get z4root. im done helping you, good luck.
Use z4root in order to achieve temp root for previous mentioned fixes.
Wohooo! I've fixed the SD Card issue! Thanks all, even DomSim, who's apparently given up on me in frustration. Give a noob a break, DomSim. I'm new to all this and am trying to balance reading this stuff with a family that also needs my attention.
I've got Z4Root installed and verified root, too. I'll probably fix the USB issue at work, since I don't need a computer connection for that and it's getting late (yeah, I usually leave for work just after 5:00 AM).
Once I've got the USB issue sorted I'll have to take a look at the bluetooth issue. I'm hoping its related to the USB situation and will be cured at the same time, but suspect that's just wishful thinking on my part.
Just completed the USB repair portion and.... SUCCESS!!!!! BEYOND MY WILDEST DREAMS, actually, as Bluetooth now works also.
I was hoping that the bluetooth functionality depended on USB (I think I recall that the bluetooth module on my Dell Mini 9 was USB based) and lo and behold, it does!!!!
Thanks again to everyone who helped out. You guys are first class!