I am at a loss of things to try with this Evo which I have no history of.
After initially being stuck at 4-triangles. I managed to flash the ENG 0.76 bootloader. Found out that:
S-OFF
Radio: 2.15.00.09.08 -some sort of Chinese radio?
I've tried it many different ways with RUUs, fastboot and PH36IMG, but RADIO_V2 repeatedly fails to flash.
I can also flash any recovery, but it fails to load, getting stuck at the Evo splashscreen, so that is also a problem. Most partitions flash nicely in fastboot. A successful system flash will result in a stuck Evo splashscreen, though.
Is there any way out of this? Perhaps by using one of the elevated commands in the ENG bootloader? I don't know how to get ADB running either, since I'm stuck in fastboot and have no idea whether USB debugging was on earlier. I do have a Linux box if that helps.
Any help would be greatly appreciated. Thanks!
Its a PC36IMG* not PH36IMG
Sent from my SPH-L710 using xda premium
Typo, sorry.
Sent from my Galaxy Nexus using xda premium
I might need to clarify a little.
I have absolutely zero history of this phone. None whatsoever.
1. Currently on ENG 0.76. I received the phone with no access to the bootloader, stuck at the HTC screen with triangles in each corner. I flashed the ENG 0.76 hboot via fastboot and that's what I'm on right now. Works fine.
2. I have no idea how it got to this radio version. Seems like a Chinese UIM radio. Got the phone from a friend who got it from an auction in Burma.
4. Flashing any radio in hboot will result in [see attachment]. Flashing in fastboot- see 2nd screenshot above. Fails either way, and I've tried multiple radios. Tried under multiple hboots, too. No dice.
5. Stock or custom recovery will flash fine but will get stuck at the white splashscreen if I try to enter it.
6. Bootloader is perfect. Works like a charm.
The only idea I can come up with is using an elevated command in fastboot oem which could reformat my radio partition somehow. I don't know whether I have ADB either. I have some experience with diag mode and JET on the HOX.
Any ideas?
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Sent from my SPH-L710 using xda premium
death-by-soap said:
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Click to expand...
Click to collapse
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
temuryusuf said:
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
Click to expand...
Click to collapse
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Sent from my SPH-L710 using xda premium
death-by-soap said:
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Click to expand...
Click to collapse
Obviously this is not the only hboot I've tried. I've gone to 2.10, even 2.18, tried there, come back down to ENG, tried again; it's just repeatedly failing. I'm not giving up hope due to the simple fact that the bootloader works and there MUST be a way out. Like I mentioned earlier I'm thinking one of the high level commands, but I have no idea what to do with them. Could anybody lead me in the right direction?
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Sent from my SAMSUNG-SGH-I747 using xda premium
shortydoggg said:
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Click to expand...
Click to collapse
I've only recently put 0.76 on after trying the newer Hboot versions. I found out that I was on 2.02 initially when I had the 4 triangles- I had to RUU because there was no accessible Hboot to fall back upon anyway. I then found a 2.02 img and flashed that through fastboot, which is when the bootloader actually started working. I'm using 0.76 now because it just seems to work better with commands.
What exactly does "permanent damage" imply in this case? Because the problem remains either way- RADIO_V2 fails to flash. All other partitions have not a single problem between them.
Is there a way where I can completely clear out the emmc, repartition it correctly and take steps from there?
At this point of time I'm rather certain mine is an older HW revision. How do I find out anyway?
The newer hardware started with Hboot 2.02 while the old ended with 0.97. You would never OTA to 2.02 from 0.97, but have went directly to 2.10 unless you flashed a Hboot with 2.02 or ran a RUU with that Hboot version. I actually made a post about a year and a half ago on how to tell, so if you phone ever boots again, I could point you to that post.
Right now, it's good that Hboot 0.76 seems to be doing something, but I'm afraid the radio may have been flashed with something that did not want to be there.
Sent from my SAMSUNG-SGH-I747 using xda premium
Related
I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many
Where is Captain_Throwback to save the day and another evo once again
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium
evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven
You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .
jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.
Hate to say it, my friend, but I think it's the end of the road for that phone
HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.
thanks captain.
capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?
Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?
I have a bricked evo 4g that currently only boots to bootloader, The evo says " s-off ".......I have tried flashing RA recovery thats fails, Also tried running official Sprint 2.3.3 ruu, that also fails with usb error 17. I posted some screen shoots of the bootloader and what error i get after trying to flash custom reovery.. does anyone know of a fix... any help is always much appreciated thanks!
Hey,
well I can give you the new that your phone isnt bricked if it was it would not turn on and would pretty much be a "brick" hence the name. I am not good with this but captain throwback is the man on fixing borked devices. so you might want to look to some higher ups in the forum and ask for help!
kevo3000 said:
I have a bricked evo 4g that currently only boots to bootloader, The evo says " s-off ".......I have tried flashing RA recovery thats fails, Also tried running official Sprint 2.3.3 ruu, that also fails with usb error 17. I posted some screen shoots of the bootloader and what error i get after trying to flash custom reovery.. does anyone know of a fix... any help is always much appreciated thanks!
Click to expand...
Click to collapse
Rather than running an RUU from the computer, have you tried flashing a PC36IMG.zip through HBOOT? Try this one - it's the 4.54 Gingerbread stock ROM. If that flashes successfully (you might have to do it twice), then you can try flashing a custom recovery again.
Do you happen to know what hardware version you have? I notice you appear to have flashed my 0.76 ENG HBOOT modded to read 2.10 - if you did that on a newer hardware model, that would be bad. The block sizes on the newer hardware models are different than on the older versions, so you really can't use an HBOOT version prior to 2.10 on them (the one you have is actually 0.76).
Captain_Throwback said:
Rather than running an RUU from the computer, have you tried flashing a PC36IMG.zip through HBOOT? Try this one - it's the 4.54 Gingerbread stock ROM. If that flashes successfully (you might have to do it twice), then you can try flashing a custom recovery again.
Do you happen to know what hardware version you have? I notice you appear to have flashed my 0.76 ENG HBOOT modded to read 2.10 - if you did that on a newer hardware model, that would be bad. The block sizes on the newer hardware models are different than on the older versions, so you really can't use an HBOOT version prior to 2.10 on them (the one you have is actually 0.76).
Click to expand...
Click to collapse
Yeah I think the hardware version was 003 or 004, yeah even when i use the Pc36img in your post 1. Radio_v2 ok then 2-8 Fail-PU.
Kinda the same situation, but I think easier to fix
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
I had the same thong happen to me when I first unlocked my phone all you have to do is get a computer with a card reader and put that PCI36.img
On the root of your SD card and put it back in the phone and boot into the bootloader... And if the card still cannot mount then keep pulling it and turning the phone on and let it come on in bootloader everytime and adventully the bootloader will reconigze the SD card and install the recover.. this method has worked for me a fee times
Sent from my PC36100 using XDA
Other option is sometimes I do a factory reset and reboot my phone and the very first ROM I ever flashed reinstalls... Without going into the bootloader ofcourse
Sent from my PC36100 using XDA
Oh wait I just read that you said you CAN get into recovery.. well there is a option to mount SD card.. do that and then restart
Sent from my PC36100 using XDA
monty_python said:
Oh wait I just read that you said you CAN get into recovery.. well there is a option to mount SD card.. do that and then restart
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Thanks man, but here's th thing, it KEEPS saying "E: cant mount sd card" and "No such directory found". thats my proble that I am having. If only I can get the phone to pick up the sd card, my situation would be handled.
I have a fairly strange problem. My wife got tired of the Verizon bloatware on her Dinc2 so I offered to root and flash it to a nice rom. Her only requirements were that it work both as a phone and as a camera. After an uneventful downgrade, s-off, root and CWM, we tried aeroevan's unofficial CM9. We found that the camcorder was broken. Next we tried the MikRoms Incredible 2 HD Rls1. This worked beautifully in every respect except one: when I rebooted the phone, it went into a loop. The phone would boot to the opening lock screen.. in some cases I could even unlock it.. and then either turn off or reboot (which one seemed random). After getting back into the bootloader, I tried all the obvious things:
Wiping all partitions
Reloading the ROM
Trying a different ROM
Flashing back to a Stock ROM + root
Flashing back to stock 2.3.3.
In every case, the phone works perfectly with the new ROM up until it is rebooted, after which it goes into a loop at the lockscreen. The only ROM that DOES work is aeroevan's unofficial CM9. It reboots without any issues, but of course the camcorder and camera flash are busted there. At least it's usable as a phone again.
I've looked and looked, and either my google-fu is failing me utterly or this is a fairly unusual problem. Does anyone have the faintest idea what's going on here and how I can work at fixing it?
This is a well known issue with 605.05 software phones (and several other threads already about this). There is a PSA in Development warning this issue exists. Only guaranteed ROMs without issue are AOSP ROMs. If you want working camera, flash CM7.
I have also heard that flashing the radio packaged with the latest software may fix the issue, you can give that a try. You could also try flashing Condemned Soul's 6.xx ROM in development section.
Sent from my ADR6425LVW using Tapatalk 2
Yah, right after I posted this I saw this:
http://forum.xda-developers.com/showthread.php?t=1746490
Sorry about that. Thanks for the info!
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
I bet the biggest plus is the happy wife part huh?
Sent from my Incredible 2 using xda app-developers app
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
Glad flashing the new radio got it sorted out!
fsiddique said:
Glad flashing the new radio got it sorted out!
Click to expand...
Click to collapse
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
wexx2504 said:
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
Click to expand...
Click to collapse
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
prototype7 said:
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
Click to expand...
Click to collapse
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
wexx2504 said:
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
Click to expand...
Click to collapse
You can check the md5sum from the phone, just use terminal emulator (might need busybox installed). To check if you are S-OFF, boot into the bootloader and it should say S-OFF.
Sent from my Incredible 2 using Tapatalk 2
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
wexx2504 said:
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
Click to expand...
Click to collapse
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
wexx2504 said:
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
Click to expand...
Click to collapse
\
I am at this exact same radio, firmware version, hboot version and situation too any help would be greatly appreciated. Trying to help a co-worker fix his wife's device.
i thought I saw it somewhere that "Captain" was going to upload a PC36IMG for this specific version of ROM, but I now can't find it.
The reason I want to use it is because my phone currently has the 4.67 software and 2.18 HBoot. Every time I try to flash an older version, it gives me the "main version older" error. Plus, my phone's USB port is not working with diag mode on (although still charges). So PC36IMG seem to be my only chance. Please advise where to get it or if I am wrong with my understanding. Thanks!
are you trying to root you evo with hboot 2.18 ?
i am some what lost...forgive me if i am wrong about anything. do you need the pc36img for 4.67 and 3.18 hboot ?
Sorry. Not really. I bought this evo 4g from cl and it turned out to be flashed to cricket. I want to flash it back to sprint so I can use it. I've read a lot and tried a lot but nothing helps. It looks like my problem is that:
1) it is now unrooted, so I don't have access to terminal so fastboot is not an option
2) it has a bad USB. I don't know if it is the hardware, or because of the previous flash
So my only chance is to load the PC36IMG to SD card and flash it from there. For some reason, whenever I do it, it loads it, checks it and goes back to bootload. This happens to all PC36IMGs I tried (maybe 6-7 of them) EXCEPT the following one:
PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2 .15.00.11.19_NV_1.90_release_161482_signed.zip
However, this one does not work either. After it checks it, it gives the error that "MAIN VERSION IS OLDER"
I thought if I can find a newer version than what I have (4.67) I may have a chance. I found that the one in my title is newer. But it looks like it is not a PC36IMG.zip file (how do I tell BTW? It just failed on me).
I searched and found other solutions like downgrading, but all required USB port which I don't have. So is there anyway I can still revive this?
This is my info on top of phone.
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
Radio-2.15.00.12.19
Dec 21 2011, 12:50:32
XenonV said:
are you trying to root you evo with hboot 2.18 ?
i am some what lost...forgive me if i am wrong about anything. do you need the pc36img for 4.67 and 3.18 hboot ?
Click to expand...
Click to collapse
well you need USB to be able to flash the phone, + you wont be able to do anything unless its rooted :/
But question:
1) I was wondering if the USB problem I am having is due to the earlier flash (I read about some ROMs leads to bad USB). If I install a stock ROM (newest) with my microUSB, I may have my USB back. Is that correct? Do you think it might work? It still charges, just not recognized data-wise.
2)Am I correct that I can copy the newer version of software (like the one in the title) as a PC36IMG.zip to my microSD card, and have the phone load into bootloader and recover that way?
Thanks!
XenonV said:
well you need USB to be able to flash the phone, + you wont be able to do anything unless its rooted :/
Click to expand...
Click to collapse
Yes, roms can cause hardware issues, well not only roms, but kernels, and more. And for your second question I can't say no or yes, but give it a try
Sent from my PC36100 using xda app-developers app
I see! Thanks! So are you aware of any PC36IMG for 5.07 software? And you mentioned 4.67 Hboot 2.18. Do you have a link? I don't think I tried it since I was looking for a "newer" version. But may be it will work? Thanks!
And, do you suggest install a different kernel, radio, etc? If so, which one should I try? I don't think I can make it worse.
XenonV said:
Yes, roms can cause hardware issues, well not only roms, but kernels, and more. And for your second question I can't say no or yes, but give it a try
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
i may have solved your problem....http://d-h.st/jrt
Sorry for being ignorant. I think I tried this one. It went back to bootloader after it "checking PC36IMG" without any real changes.
I thought it was due to it is a file I need to install from computer, rather than directly rename and put onto SD. That is why I was asking for a PC36IMG.zip file. I guess I am wrong?
Again, sorry for the ignorance. Never done these before. Just trying to save this brick I just bought. Thanks!
XenonV said:
i may have solved your problem....http://d-h.st/jrt
Click to expand...
Click to collapse
you mean flashing...try this http://www.youtube.com/watch?v=CA0Xfjstk_U&feature=my_liked_videos&list=LLjr29qtQIqEr0PzGlm9JIqw the audio on that vid sucks so turn your volume all the way up
I kinda realize the way, but my phone USB port not working right now. So that does not help.
XenonV said:
you mean flashing...try this http://www.youtube.com/watch?v=CA0Xfjstk_U&feature=my_liked_videos&list=LLjr29qtQIqEr0PzGlm9JIqw the audio on that vid sucks so turn your volume all the way up
Click to expand...
Click to collapse
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?