Alright so I'm not new to rooting... I've rooted my Incredible off and on for the year I've had it, tried out several roms, etc... Well I wanted to try out Gingerbread so I went through the whole unrooting process to get it, tried it, realized it wasn't my cup of tea. So while running 2.3.4 I tried to use Unrevoked (didn't realize they hadn't released a gingerbread update at the moment), then tried a method to root I found on the Android forums. Well after doing that I got the DONE prompt on my Unrevoked 2.2 program. Well I restarted my phone and it was stuck in a boot loop on the HTC Incredible splash it just continuously restarts on that screen. I went in to boot loader I believe is what it's called (vol down + power) to try and just run my PB31.img and get my phone into a working order. Well when it checks the img it says the MAIN VERSION IS OLDER I guess since it's a Froyo PB and I'm on Gingerbread. I also occasionally get the white screen with the black box in the middle... I can't get onto my phone at all. I have literally no clue what to do and I will be in someone's debt forever if they can accurately get me through this problem. The S is still on and the phone is not rooted in the least. HELP ME!!!!!!!!!!!
Also I do not have insurance so a replacement phone is out of the question. I just really need to get this one fixed and make it last me till October.
Just did a check. I get the white screen black bars when going to anything within the (vol down + power screen). Can not do system reinstall.
what do you mean by this? are you no longer able to access hboot? that is the white screen with the information at the top, 4 options and then 3 skateboarding androids at the bottom. If you are able to get into hboot still, could you please tell us what it says? for example mine says:
Incredible XC Ship S-off
Hboot-0.92.0000
Touch Panel-ATMEL224_16ab
Radio-2.15.00.12.19
We mainly need to know which hboot version you have in order to get you in the right direction in terms of rooting and so forth.
Incrediblec XD Ship S-On
Hboot-0.92.0000
Microp-0417
Touch Panel-Atmel224_16ab
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Like I said I can get to that main screen I can choose any of the options. Problem is when I choose them it immediately goes to the white/black screen. When I normally try to turn on my phone it still goes into the boot loop. I have a PB31 I used last time I had the black/white screen issue when I rooted my phone, but I'm expecting the same result as my actual PB31 since I downloaded them both during Froyo times. I could care less in the end if I actually root my phone lol right now I just want a working phone. -_____-
On a side note... Seeing as how S is on I could take it to a Verizon store and try and point the finger at Google because of a botched 2.3.4 upgrade. Only problem with that is there's an app that Unrevoked installs that would be seen if they can get into the phone.
Alright another update... I tried the Black Screen Froyo fix PB31 I had and HBoot won't even recognize it.
If you take a look at my guide, maybe it will be of some assistance. You are still at step one and you need to begin following the steps set out by scotty85 after you download all of the components if you haven't already. You should be able to connect with adb since you can still get into hboot but let us know if you can't.
http://forum.xda-developers.com/showpost.php?p=26146567&postcount=15
this is the original guide by scotty85, He has an account on xda too with the same guide but it isn't sticky so it's not as easy to find...
http://androidforums.com/incredible...ot-2-3-4-downgrade-get-s-off.html#post3308718
I know this may seem like a lot to ask, but do you maybe have a skype or something so you can verbally talk me through this? I've already messed it up by reading, so it'd be awesome if we could respond back and forth. I have no clue what any of the adb stuff even means -_-
ZachRoberts_ said:
I know this may seem like a lot to ask, but do you maybe have a skype or something so you can verbally talk me through this? I've already messed it up by reading, so it'd be awesome if we could respond back and forth. I have no clue what any of the adb stuff even means -_-
Click to expand...
Click to collapse
Well, right now I have to go to work and if someone else is able to help you before I get back, then great! but I will do my best to walk you through it when I get home, around 5
I have all the files from your post, and the ZergRush thing from Scottys post is broken... So I just need someone to calmly talk me through it lol.
Is that 5 EST? I'm CST and don't go to work until 5:30 CST... but it'll probably be super close to midnight till I get home after I go into work...
alright guys so this is partly a bump to get Zach a little help and partly to fill you in so we can get his problem solved.
This is his hboot:
s-on
AMOLED screen
hboot: 0.92
radio: 7.07
He has his incredible with stock 2.3.4 installed
He tried to use unrevoked 2.2 to root and got the response "done" from unrevoked
When trying to boot the phone it freezes at the splash screen
--Not sure how long he tried waiting for that, I would suggest he tries waiting at least ten minutes at that screen to see if it will ever get past that, patience is a virtue, after all.
When trying to enter recovery or even trying to do a factory reset through hboot it goes to splash like normal and then goes to a black screen with vertical white bars on the sides. I tried to google this symptom, which you would think would be pretty easy to find something but apparently not.
His goal is to just get the phone back to working in stock 2.3.4 but I don't think he would be opposed to getting it rerooted and get a ROM back on it.
My suggestion to him was that the easiest way to try to save his phone would be using fastboot. that being said, I am not proficient in fastboot but I know there are a lot of people around here that are and their assistance would be highly appreciated.
EDIT: Never Mind, I can see that the folks over at androidforums got him straightened out.
To Zach, If you still want help to root later, I will still be available.
ZachRoberts_ said:
I have all the files from your post, and the ZergRush thing from Scottys post is broken... So I just need someone to calmly talk me through it lol.
Click to expand...
Click to collapse
just an fyi,zergrush is included in the "mini-adb_inc" download:
mini-adb_inc(contains misc image,flash image,and some basic adb tools) *link removed
mirror:miniadb_inc.zip
mirror md5: 7c5211686a20b558ccd660c782f82e2b
*clockwork and zergrush included in mirror
and the link to revolutionarys zergRush page here on xda is still working fine for me... http://forum.xda-developers.com/showthread.php?t=1296916
glad youre up to a working phone again,when youre ready to root,you might check out my hctdev unlock guide. it doesnt use unrevoked,or any other root programs,wich seem to be "finicky" on some incredibles
as long as the phone is out of mfg warranty(it prolly doesnt even matter for that,you can get back to .92 hboot) htcdev may be a little more reliable:
http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html
sorry i was unavailable earlier,holler if you have questions
nschiwy... I just want to go ahead and thank you for spending all day on skype with me getting my phone set up. Everything is in working order and am loving it. Kudos ma... Kudos!
Related
Hi, hoping someone can help me. My phone seems to have bricked itself. A few weeks ago i had CM6 on my phone then i reverted back to the stock rom from HTC. The phone worked fine for a few weeks then about a week ago i started having random data connection issues, yesterday the phone started resetting by itself, after the third or fourth reset the phone stopped booting at all. all i get now is the white HTC EVO 4G screen or the bootloader when i hold the volume down button.
Here are the version numbers on the bootloader screen.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
i can only get windows to recognize the phone through usb by using the HBOOT USB option and installing the android bootloader interface driver. I don't really know how to use ADB and i'm not even sure if it is seeing the phone. All i want to do it get this back to official firmware.
any and all help is appreciated
thanks.
Well, it's not bricked if you get into that menu. Can you get into your recovery? If so, try wiping everything and reflashing the rom.
No i can't get into recovery, i even tried reapplying clockwork recovery trough there and all it does is install it, say it's installed ok then i reboot and try to go to recovery mode and it just goes to the white HTC EVO 4G screen
What version of hboot do you have?
*Nevermind* Apparently I can't read. xD
What root method did you use?
that's if i even installed it right.
i'm not sure if it even is rooted anymore because i had put the official firmware back on, when i had CM6 installed i used clockwork recovery and unrevoked
well if you were able to install a custom rom like cm6 then you are more then likely rooted. you say that you cant get into recovery? you should just try running the ruu.exe and returning to complete stock and then reroot if you want.
the official RUU.exe doesn't see the phone. when i connect hboot in the bootloader, device manager see's the phone as android bootloader interface and it i let the boot normally and let it crash at the evo 4g screen it show's up as "Qualcomm CDMA Technologies MSM" and doesn't have a driver. I am running Windows 7 x64
maybe you should try slashing the stock pc36img.zip maybe that will get you back on track.
Edit: this is the link to the thread with the stock pc36img.zip
http://forum.xda-developers.com/showthread.php?t=791019
and just for future reference. it is not that hard to do a search of the information that is needed. while i was here posting these things i found with the search all the info i hae given. just food for thought.
What caguirr4 said. With that file (or since you have s-off you can TRY getting a rom zip and renaming it to pc36img.zip) your phone will read it automatically when you boot using the volume down technique. That should at least get your phone to boot up and you can continue trouble shooting from there if you have more problems.
Remember: Conserve your battery! You don't want the juice to run out while the phone is in the middle of flashing something. THAT is how bricks are made.
i ran the update you gave me, the phone said that all the stages of the update were sucessful and asked me to reboot, i did so and now my phone won't power on and when i plug it into the wall it won't show any charging lights.
zerozr1 said:
i ran the update you gave me, the phone said that all the stages of the update were sucessful and asked me to reboot, i did so and now my phone won't power on and when i plug it into the wall it won't show any charging lights.
Click to expand...
Click to collapse
You ran the updates that who gave you? Various things were suggested on this thread.
sorry for not clarifying,i ran the original stock image that was linked to me by caguirr4 in post #9. According to the update it ran fine but after that the phone died when it had me reboot.
zerozr1 said:
sorry for not clarifying,i ran the original stock image that was linked to me by caguirr4 in post #9. According to the update it ran fine but after that the phone died when it had me reboot.
Click to expand...
Click to collapse
Ok, so you press the power button, and it does nothing? That doesn't sound good at all. Hopefully, your battery is just dead and the drivers for the USB port didn't install right. In which case, you need this:
http://forum.xda-developers.com/showthread.php?t=695243
Do you have any extra batteries you can try to make sure that battery isn't just dead?
I ended up taking it to a sprint service center, they tested the phone with thier own battery and the phone was dead. they are replacing the phone for me now. thanks you everyone for trying to help.
You could of just overwritten the ENG bootloader u had installed...
I am having the exact same problem. I can get to the bootloader but not recovery. Here's my specs
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.21
I had cyanogen 6.1.1 installed on it and it was was working fine. I just felt the thing vibrate and took it out of my pocket to see the "htc EVO 4G" screen and it just keeps rebooting unless I hold the volume button to get into the bootloader.
I REALLY don't want the stock firmware back on here and would like to avoid loosing root if possible.
I tried putting the PC36IMG.zip from here and at first it asked me if I wanted to flash it and after the first thing it restarted and now gives an error Main Version is older!
Update Fail!
Any ideas? I would really like to keep this phone.
Thanks,
Justin
I've tried basically everything I can think of. After attempting to flash the first PC36IMG.zip file I get the main version error for every other one.
Is there somewhere I can get the latest PC36IMG that will be newer and I can try to flash? At this point I don't really care if I lose root (if I haven't already) I just want my phone back.
embmicro said:
I've tried basically everything I can think of. After attempting to flash the first PC36IMG.zip file I get the main version error for every other one.
Is there somewhere I can get the latest PC36IMG that will be newer and I can try to flash? At this point I don't really care if I lose root (if I haven't already) I just want my phone back.
Click to expand...
Click to collapse
Just run the ruu.exe and get it back to stock.
Sent from my PC36100 using XDA App
I tried that. I even tried flashing the stock PC36IMG.zip (which flashed successfully) but I had the same problem. I finally gave up after like 8 hours of working on it and took it into Sprint. I am going to pick it up at 7. They said if they couldn't fix it they would give me a new one for $35 since I'm out of warranty which doesn't seem bad.
I'm currently stuck in a boot loop, with no way to access my rom or recovery. I can only access bootloader. The boot loop began happening soon (around 2hrs) after flashing MIUI; The rom was running, and out of nowhere it just began cycling. Any ideas on how I can get out of this boot loop?
Edit: I'm no longer in a boot loop after installing a different full system PC36IMG.zip. Instead after the initial splash screen my evo goes black and vibrates 5 times, then my green LED starts flashing. It stays this way until I remove the battery.
So far I have tried:
Flashing RA's recovery image using fastboot. (The flash was successful)
Using RA's recovery PC36IMG.zip. (The installation was successful)
Using an RUU file renamed to PC36IMG.zip (The installation was successful)
Using a Sprint Lover's file renamed to PC36IMG.zip (The installation was successful)
For all of these the process of installing and flashing went fine. Yet when I would turn on my phone it would just go right back into the boot loop.
*I've been editing this post as I've tried new things, so you don't need to read through the thread to help me.
Anyways I'm at my wits end here, pretty worried, and phoneless, so any help would be amazing.
Have you tried ADB from bootlaoder or fastboot. May be able to get recovery that way.
I'm trying to do a bit of research, but am a little confused on what adb is. It's part of the android sdk? I can't seem to find it, or know how to launch it. Is there a thread somewhere that covers it? I'll keep doing my research, thanks for the tip.
Its a command terminal but if you are not familiar with it you probably wont get it right away! I am just starting to learn this myself. VERY VERY useful tool though! Here a link.......
http://forum.xda-developers.com/showthread.php?t=502010
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
thanamesjames said:
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
Click to expand...
Click to collapse
Jeez sounds like you have a better grasp on this than me already! LMAO
haha, well i'm not too sure. Have you gotten you're evo to be found? Right now while using adb, I'm just told "device not found." All my drivers should be properly installed because I had to install them when I used unrevoked. So I choose fastboot on my evo, and then it shows up on my computer as "android 1.0" under devices and printers... but adb doesn't find it.
I was told to get rid of my drivers and re install the recommended ones before starting. It recognized mine right away. YouTube also has nice how to videos on ADB.
Is there any way you can point me to the recommended drivers? I think that second link you gave me is the same as the first also.
Edit: Every single guide I see on the internet about adb, says use debug mode within the actual rom. However I'm obviously not in a rom, i'm in bootloader, and for the life of me can't get adb to find my phone.
Edit2: Ok, so maybe I can only use fastboot. Right now when trying fastboot it just says "waiting for device," even if it didn't say that, what would i need to do to get on the road to recovery?
So I'm starting to get scared. At first I figured this was something I could fix... and now I'm not positive it is. I've used fastboot from terminal, trying to flash recovery and it says "FAILED (remote: not allowed)" I'm starting to get desperate, does anyone have any ideas?
I'm sorry to bump this, but I'm really struggling here... because I'm phoneless and all , I worked at this for 5 hours last night from 9-2, and now I'm at it again... and very worried. I've read that theres almost no way to completely brick your phone, but I'm starting to feel like I did. It seems like no matter what I flash it just keeps boot cycling. Thanks for the help.
go to the bootloader and ruu it
I have... I took the ruu file and renamed it PC36IMG.zip, went into bootloader and it went through all the steps with "OK"s, rebooted, and went right back into the boot loop.
Specifically I used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip" from here,
http://goo-inside.me/evo/stock/RUU/
Is there a specific number version of RUU I should try? I just tried the most recent.
You have to use the ruu that matches your radios/software etc. How did this boot loop start? Give us all your phone info, rom, hboot version, radios etc.
Sent from my iphone slayer 4G
I flashed a CM7 nightly, from CM, about 2 weeks ago. Yesterday, still using the same nightly (build 1 or something) my phone seemingly out of nowhere rebooted - I wasn't even using it at the time. When it went back into CM7 it acted as if I had never linked a google account to my phone. The first thing that came up was the android google apps screen. Anyways, I decided I wouldn't stick with CM7 until at least an RC was out, so I wiped data, cache, and davlik and flashed MIUI. I used it for about two hours, didn't do anything out of the ordinary, and once again seemingly out of nowhere it rebooted... except when it did it went into a cycle and never reached MIUI, and wouldn't go into recovery, I could only access bootloader.
Anyways, I'll tell you what bootloader says my phone versions are, but I do believe the info all changed this morning when I flashed the ruu file.
SUPERSONIC EVT2-3 SHIP S-off
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Check your pm
Sent from my iphone slayer 4G
Are there any other thoughts on how to get on my feet?
In addition to booting an RUU file as PCIMG36 I've also tried a Sprint Lover's image as PCIMG36. Even though both installed properly, my phone still staid in the boot cycle afterwards for both.
I've been suggested, and have seen other users suggest on other threads, to try adb commands, but I don't know if i can access adb while the phone is in bootloader. I have however accessed fastboot, are there any commands that might help me? If not, can I use adb while in bootloader? Thanks.
Well I tried a new PC36IMG.zip file and I'm no longer stuck in a boot loop... instead as soon as the HTC EVO 4G splash disappears my phone goes black and vibrates 5 times, and my green LED flashes.
Good? Bad?
This would be the 300th something thread I've read on this subject and this is exactly were I'm at with my EVO minus the last post... I was using warms2p2 with the hdmi kernal everything working fine then I went to change my notification ringtone and bam went into boot loop and never came out. SOOO! it would be nice to save this unit... any help forum members would be great I've tried every RUU out there from fastboot from sd card nothing.
Very intesting that this thread ended this way... please share if you think you got this whooped. Thank you in advanced.
Love the revival of old threads...but did you try changing the kernel?
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip 3.70 RUU, just rename to PC36IMG and flash in the bootloader if you want to run the RUU.
I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.
Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.
Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.
darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!
Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?
So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.
I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..
With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option
darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.
So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.
Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.
to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?
yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates
its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,
ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.
goood luck hope you get your phone back up and running
well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
I had an issue with my phone before, and I gave it back to sprint rooted and everything, but then when I got the new phone, I checked to see what hboot version and radios were on it.. and I saw that it had
-Revolutionary- at the top
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-6.16.1002
Alright, so I am posting because I don't know where to go from here. I have been trying to find FAQ's about this for a little while now, but I don't know where to look. I just want to get this unrooted and flashed to stock so I can redo everything I did to my last phone again. Anyone know where to start?
p.s.
I tried to boot to recovery from hboot and got a black screen with a picture of a phone and a red exclamation point, so I don't know whats up.
(Before that, sometimes, it'll give me this green symbol instead of the red. It looks like a synchronization sort of thing, but I'm unsure.)
The phone just doesn't have a recovery, fastboot a recovery image to the phone and then you'll be able to boot into recovery successfully. I'm sorry, I don't know how you would go along undoing everything but why go through the hassle if it is all done.
Its not so much that I want to just restart everything from square one, I just don't know anything about what's on there right now.
Farr93 said:
Its not so much that I want to just restart everything from square one, I just don't know anything about what's on there right now.
Click to expand...
Click to collapse
Are you actually wanting to fully return to stock? If so check this thread it has instructions on rooting and unrooting for Revolutionary
http://forum.xda-developers.com/showthread.php?t=1245649&highlight=unrooting+evo4g
Farr93 said:
I had an issue with my phone before, and I gave it back to sprint rooted and everything, but then when I got the new phone, I checked to see what hboot version and radios were on it.. and I saw that it had
-Revolutionary- at the top
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-6.16.1002
Alright, so I am posting because I don't know where to go from here. I have been trying to find FAQ's about this for a little while now, but I don't know where to look. I just want to get this unrooted and flashed to stock so I can redo everything I did to my last phone again. Anyone know where to start?
p.s.
I tried to boot to recovery from hboot and got a black screen with a picture of a phone and a red exclamation point, so I don't know whats up.
(Before that, sometimes, it'll give me this green symbol instead of the red. It looks like a synchronization sort of thing, but I'm unsure.)
Click to expand...
Click to collapse
I would not worry about what is on it. The exclamation point just means there is no custom recovery installed. This also means they couldnt have installed much of anything or screwed anything up.
Just go to this thread:
http://www.google.com/url?q=http://...ds-cse&usg=AFQjCNFl8ge3sBGVpGuSjNeTBfRjqDxdnw
and download the PC36IMG of AmonRA. Put on the root of your SD card and restart to bootloader (the white screen where you choose to go to recovery). It will automatically find the PC36IMG and ask if you want to install. Select Yes and you will get AmonRa recovery installed.
You can then install any ROM you want or flash a completely stock rooted ROM for that fresh feeling.