• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Messed-up 4G! Need advance help!

O

onesimus7

Newbie
First of all I thank you for reading this.

I wasn't sure about the history of this EVO 4G that I got from someone for a very cheap price. He said that he messed the rom.

As I read bunch of things from here, xda and other forums. I found out that there's a common way to flash in HBOOT. Using the PC36IMG.zip.

Unfortunately, I have no Idea why this EVO4G, can't read/detect either the SDCard itself or the contents of it. I already placed the PC36IMG.zip for a quite few times (more than 10) and still no luck.

On the other hand, I was able to execute the RUU.exe (3.70 and 4.54.651.1 from goo-inside.me) flawlessly. Yet, my phone still won't boot properly.

CURRENT STATE of the PHONE :
  • Phone won't Boot Properly (Won't pass htc EVO 4G screen, Either it loops on and off, hangs on the logo, or turns off itself)
  • Phone can't boot to Recovery, It can go to HBOOT though, but when I choose recovery, It'll show the logo, then turns off itself.
  • Phone is rooted (S-off) by Revolutionary. HBOOT version is 6.16
  • HBOOT can't detect/scan SDCARD(so I can't try flashing PC36IMG.zip or any zip files at all) therefore NO LUCK with updating hboot or anything at all.

P.S. I've read the things from ROOTING FOR DUMMIES both GingerBread Edition and the other one, Haven't help a bit since the state of my phone is a bit rare.

I'm wondering if the sdcard slot is the one which's not working, the reason it can't detect the content(pc36img.zip) of my sdcard.


HELP WILL BE MUCH APPRECIATED (been reading and researching for almost 2 days)
 
welcome to the forums!!!!!!!!!!!!!!!!

ok just to be sure with the PC36IMG file, are you naming it right? it needs to be exactly PC36IMG. does your pc hides file extnesions? or does it show the extensions? because you could be either adding to many ".zip" to the name or not one at all. if it is PC36IMG.zip.zip then that will not work and the same goes if there is no extension at all as well.
 
hi and along with OCN advice if that doesnt work maybe try a different micro sd card in case it failed but useually his advice about the added ext is what happens most of the time
 
Thanks for the response guys, I doubled checked the PC36IMG.zip, used both mac and pc. I'm 100% sure its PC36IMG.zip (including the file extension)
 
Update : I tried a sandisk sdcard (borrowed) and it worked (detected PC36IMG.zip, successfully flashed hboot 6.17 s-on), It seems that my 16gb strontium sdcard is too thin to be in contact with the sdcard tray. Now I need to purchase another one for this phone.

I'm just wondering, I tried flashing AmonRA 2.3, It was detected but after the scanning, It never asked me to update and skipped back to menu. Can HBOOT detect battery status? I mean, if its less than 30% it won't ask for permission to update?
 
onesimus7 said:
Update : I tried a sandisk sdcard (borrowed) and it worked (detected PC36IMG.zip, successfully flashed hboot 6.17 s-on), It seems that my 16gb strontium sdcard is too thin to be in contact with the sdcard tray. Now I need to purchase another one for this phone.

I'm just wondering, I tried flashing AmonRA 2.3, It was detected but after the scanning, It never asked me to update and skipped back to menu. Can HBOOT detect battery status? I mean, if its less than 30% it won't ask for permission to update?
Click to expand...
No - your problem is that you are now S-ON, meaning you can't flash any unsigned zips in the bootloader anymore (you should've flashed the Amon_RA PC36IMG, not the one to make you S-ON). And you won't be able to root without the use of adb, which you can't access without a phone that at least boots to recovery. All you can do now is finish flashing back to stock.
 
CapThrowback said:
No - your problem is that you are now S-ON, meaning you can't flash any unsigned zips in the bootloader anymore (you should've flashed the Amon_RA PC36IMG, not the one to make you S-ON). And you won't be able to root without the use of adb, which you can't access without a phone that at least boots to recovery. All you can do now is finish flashing back to stock.
Click to expand...

So if I manage to go back to stock rom, It'll boot properly? Then I can root it Again?
 
onesimus7 said:
So if I manage to go back to stock rom, It'll boot properly? Then I can root it Again?
Click to expand...
I don't know if it'll boot properly. If all that was wrong was the card, then I assume it would, but you won't know until you actually do it.

If it does, then yes, you can just re-root/unlock it.
 
ok so you have s-on now with hboot 6.17. lets try another ruu and see if you can get your hboot to be normal and fully back to stock. try the 4.54 ruu again and see if that will do.
 
ocnbrze said:
ok so you have s-on now with hboot 6.17. lets try another ruu and see if you can get your hboot to be normal and fully back to stock. try the 4.54 ruu again and see if that will do.
Click to expand...

I tried 3.70 and 4.54, both still can't boot properly (turns itself off after 20secs more or less). I'm such a noob.

Any other way? To be honest I'm losing hope, while reading posts / situations which is the same as mine. O_O

But I don't have anything to lose to though except for time to be wasted.
 
onesimus7 said:
Is there a way to flash a recovery, s-on?
Click to expand...
If you update to the latest ROM, you can unlock your bootloader with HTCDev, and flash a custom recovery. That sounds like your only option, but there's no reason to think that would get your device working, at this point.

Are you sure your battery is fully charged? It may not be charging in the device. If you have an external charger, you can use that to make sure the battery isn't also an issue.
 
CapThrowback said:
If you update to the latest ROM, you can unlock your bootloader with HTCDev, and flash a custom recovery. That sounds like your only option, but there's no reason to think that would get your device working, at this point.

Are you sure your battery is fully charged? It may not be charging in the device. If you have an external charger, you can use that to make sure the battery isn't also an issue.
Click to expand...

I tried doing that. But I can't get to the last step (get_identifier_token) part. It shows.

(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.010s

If there's nothing I can do about this phone, please tell me, thanks for all the help. :)
 
I have no Idea actually. It was sold to me for a very cheap price. Half of the refurbed price.

It was stupid of me to think that If i unroot it would reset everything to stock. The phone says I'm wrong though. :)
 
Hey~! I was unable to unlock the device after flashing ruu 4.67. I flashed Amon RA and CWM recovery, still can't boot to recovery though. What seems to be the problem now?
 
onesimus7 said:
Hey~! I was unable to unlock the device after flashing ruu 4.67. I flashed Amon RA and CWM recovery, still can't boot to recovery though. What seems to be the problem now?
Click to expand...
I don't think there's anything else you can do. If you can't boot into recovery, then you're likely stuck. You can try contacting the_plattypus over on XDA (here's a link to his Twitter). He has some experience with this type of thing, and he may be able to help you get unbricked. Besides that, I don't think there's anything you can do.
 
You must log in or register to reply here.
Back
Top Bottom