yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] ECrispy:
This looks pretty amazing! A full GUI in recovery is like UEFI on pc's!
[EVO 4G Android Development] Kchitown1977:
was able to flash rom fine ....... tried checking md5 sum said no md5 sum
[EVO 4G Android Development] ViViDboarder:
Yea, for the md5 it looks for filename.zip.md5 with the checksum.
[EVO 4G Android Development] xadidas4lifex:
I am getting a loop of the boot animation when I try to flash some roms, like JaredTheGreat's ICS Port
[EVO 4G Android Development] vladthedog:
check the following link out. I recently lost s-off when flashing the gps fix in cyanogen. spent a while but its looking like i got it fixed tonight. i followed the advice and was able to get access to usb via my computer...

http://xdaforums.com/showthread.php?t=695243
[EVO 4G Android Development] POWerSUrgeSW3:
Personally I'd just RUU to the latest RUU and use the Revolutionary root method. The newest HBOOT, I think, loads faster to the ROM and seems more stable than any previous. If you're already S-ON sounds like a good time to do it.

Just a thought. Because then you can attempt to kill two birds with one stone. Upgrade and reflash the phone stock. And rerooting while having the latest version of HBOOT/radios.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] ocnbrze:
well for the usb fix my phone would have to be rooted first. i currently have s-on and thus terminal emulator will not work as i do not have the superuser app.

---------- Post added at 07:55 AM ---------- Previous post was at 07:52 AM ----------

well the ruu will not work. i have s-on and it will not let me update. it sees it and all and attempts to load it then when it checks PC36IMG it goes back to the hboot screen. it will not ask me for an update.
[EVO 4G Android Development] fifasarajevo:
I have the same issue right now exept i managed to lose my S-OFF by trying to update to the latest TWRP. I am able to boot completely but the SD card isnt detected and i get the same problem with H-Boot, where it detects but then it goes back to the bootloader screen...someones gotta know of a way to fix this:(
[EVO 4G Android Development] Craigerade:
I had the same issue. I lost s off and got the 5 x vibrate issue. I was able to get the sd card recognized again and flash an Ruu, but the the phone wouldn't stay booted. It would just do the 5 x vibrate. Since I got it back to stock sprint replaced it. I would stick with amon ra recovery.

I thought my phone breaking was a fluke untill checking back on this thread. If this recovery is breaking phones they need to look into it right away and probably pull the download.
[EVO 4G Android Development] whiterider13:
I just want to throw this out there. For those of you that have had major issues, are you sure you downloaded the correct file from the website? I know the website does not list our phone as evo 4G or supersonic, it is listed as evo CDMA. Just want to try to narrow down the possible issues.

*Don't take life too seriously, you won't get out alive.*
[EVO 4G Android Development] vladthedog:
look at my post above. I had this exact same issue (was fully rooted, and then lost s-off and bootlooping). in order to "fix" it I had to do both the sd fix and usb fix above. I was able to get it booted into the rom ONLY if I had it plugged into my windows computer. Very odd. it would just sit and bootloop, even when plugged into my linux machine. however it would boot into the rom so you could run the terminal commands if it was plugged into my windows machine. I also have access to fastboot and tinkered around with that some.

I'm not sure the "proper" steps on getting it fixed. I've been down for half a week now, and just last nite I got my phone back up and running. I was only successful after I was able to do the sd and usb fixes though.

EDIT: just wanted to add that until I could do the usb fix I wasn't able to successfully run an RUU. once I fixed the usb everything else came into place so didn't need to run an RUU.
[EVO 4G Android Development] ocnbrze:
so can you run adb commands on a phone that has s-on? looks like that is what you need to do for the sd and usb fixes.
[EVO 4G Android Development] FusionX:
Your pretty much out of luck unless someone comes up with a new root method that can be performed in fastboot...

I have the same problem as you... however, I have a replacement phone on the way.. I've still been trying to fix it until I get the new one...

I can boot into the GB OTA I flashed with the RUU.. however, it will reboot after 2 minutes of being loaded... also, the computer will not recognize the phone is plugged in (windows xp, windows 7, ubuntu....) most of the time... sometimes it will recognize it as a qualcomm device and not an android phone while in the ROM.... but even with qualcomm drivers installed, it still doesn't let adb work...

I'm still messing with things... I think if I was still on hboot .76 I might have been able to get toasts original root method to work but now I'm stuck on hboot 2.16 and have no real options left.

I will note that fastboot commands work when the phone is in fastboot from the bootloader but they always spit out errors... except mounting the sdcard or rebooting...

My issues also started after installing this recovery but at the same time as flashing the Anthrax kernel with TWRP... so I can't be 100% which one caused the phone to eff itself.

Does anyone know of a method or way to make a PC36IMG.zip appear to be signed by HTC?
[EVO 4G Android Development] Craigerade:
Gooinsideme has PC36IMG.zip ruu's
[EVO 4G Android Development] fifasarajevo:
i still havent managed any fix...so far this is where i have gotten

I can get into Bootloader fine

If i go to recovery i get the 4 vibrates and nothing works

I can boot the phone into the rom but i cant get it to connect to the PC in any way so i cant even charge it

When i boot up the phone the SD card wont detect or mount
[EVO 4G Android Development] Craigerade:
I made sure to download the proper one. I installed via hboot with the pc36img. The first time I used the recovery was too update koushdeck ics. I wiped cache and dalvik. Flashed the zip. Then when I went to flash gapps next the sd card wasn't recognized. I went to reboot and after the HTC screen the screen went black and vibrated 5x. When I got back to hboot I had s on. I could never get the phone to stay booted even after getting sdcard recognized and flashing a Ruu. Lucky sprint replaced it since I have insurance.

I had installed version RC 0.2
[EVO 4G Android Development] fifasarajevo:
i tried going through dropbox and flashing but you need the SD card to be mounted for it to work
[EVO 4G Android Development] FusionX:
I can flash an official RUU, but the problem is with the phone not working for adb and with s-on now I can't do any root without adb working...
[EVO 4G Android Development] vladthedog:
no you cannot. i had to get it to load the system (having it plugged into my windows system while booting allowed for it to load... not plugged in it just bootlooped) and then from terminal emulator
[EVO 4G Android Development] fifasarajevo:
So at this point there isnt really a fix for this so i think im just gonna get a new phone oh well.

BTW for people that want to prevent the problem this is what i did to create it lol

I used TWRP the touch screen one ...the original version and i did a full wipe and flashed a rom after i flashed the rom and restored some apps i went back into bootloader and tried to upgrade to the newest version of TWRP and thats when my phone vibrated 5 times and i got S-ON so yea just so people know.
[EVO 4G Android Development] FusionX:
This is exactly what happened to me.. Sprint is replacing my phone (without insurance) b/c it is a "known issue"... glad it made s-on in this case... seems that the recovery may be the problem after all these reports.
[EVO 4G Android Development] fifasarajevo:
Wait so youre not under warranty and have no insurance and they still replaced your phone.....Did you just call them and ask or go to a store?
[EVO 4G Android Development] FusionX:
the ONLY thing that i can conclude would be a fix given our scenarios would be a way to root solely from fastboot... if that isn't an option then say hello to your brick called evo.

---------- Post added at 11:03 PM ---------- Previous post was at 11:02 PM ----------

i flashed the gb ruu... since i had s-on i went to the store and said "my phone is dead" and he looked at it... said oh this is a known issue so we will replace it for free, normally it would cost $35.00... and he ordered it, transferred my number to my old POS touch pro 2 and i was on my way. so yeah, for free on an 18 month old evo.
[EVO 4G Android Development] fifasarajevo:
Yea ok thanks for the info mate im going to go to my sprint store tomorrow (if theyre open hopefully) or monday and see if theyll do that for me ...and if not ill just get a new phone.

Thanks for all the help.:)
[EVO 4G Android Development] FusionX:
just play stupid.. do not mention rooting or anything... i told them i needed my phone to conduct business and the fact that it was not working was costing me a lot of money b/c i couldn't take calls from my clients. a nice stupid person gets further than a rude, demanding smart person.
[EVO 4G Android Development] Craigerade:
Don't have anything root related on your sdcard or any root apps including xda
[EVO 4G Android Development] fifasarajevo:
i actually formatted my SD Card so theres nothing on it anyway
[EVO 4G Android Development] POWerSUrgeSW3:
That sounds like a NAND memory bad blocks issue.

Something just seems off here.... because recovery is separate than the bootloader. So even if the recovery fried, as I've learned from experience, HBOOT shouldn't be affected. Am I missing how a recovery could mess HBOOT up?

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] aaanadie:
I think this issue is related to HBOOT .76 and TWRP, devs are fixing it, so you should flash newer HBOOT to use TWRP.
[EVO 4G Android Development] ocnbrze:
i have had the same issue and i started out with hboot 2.10. but i flashed mikg3.0 with twrp rc01 and i now have s-on and no access to my sd card. so i do not know what the heck happened. i do have stock froyo booted up. but no sd card. not sure how to fix it since i have s-on.
[EVO 4G Android Development] Dees_Troy:
I think the issues are actually related to the kernel that's being used. I've got a new build ready for testing but I need a tester. I've pulled the kernel out of Amon RA 2.3 and packed it in with TWRP. Come to #twrp on freenode if you would like to help test. Thanks.

From a back-end standpoint, we're really not doing anything different than the other recoveries as far as the way that we back up and restore things, so I'm pretty sure that the issue has to be related to the kernel.
[EVO 4G Android Development] aaanadie:
Hello,

I loose my S-OFF a few mins ago:

I had twrp-supersonic-2.0.0RC0.2

- Wipe all

- Flash classic-v005-01-02-finale-senseless

- Flash SUPERSONIC-SENSE-AnthraX-2.6.38.8-REV_zzzTESTzzz009 kernel

- Wipe cache & dalvik

- Reboot

then I got S-ON. I had HBoot 2.16.0001 but now 2.10.0001:(

Any help?
[EVO 4G Android Development] FusionX:
Sounds familiar... go back and read my recent posts from over the past week... then enjoy your new phone as your current one is probably lost, unless you can access adb from a booted rom... can you?
[EVO 4G Android Development] aaanadie:
If I go to recovery I just got 4 or 5 beeps and the screen still black.
[EVO 4G Android Development] FusionX:
can you boot into the rom at all? if you can, are you able to access adb shell?
[EVO 4G Android Development] Goobertime:
I'm glad I stepped off this recovery before something happened to my phone, as much as I liked the interface of this recovery I honestly think the download link should be pulled till something is fixed....but that's just my opinion

Sent from my Classic EVO
[EVO 4G Android Development] aaanadie:
No, if I put battery and boot, then I got FASTBOOT menu (BOOTLOADER, REBOOT, BEBOOT BOOTLOADER, POWER DOWN)
[EVO 4G Android Development] cbond007:
With all the messing up of people's phones, I'm glad I removed it a couple of days ago. I hope you guys fix your phones
[EVO 4G Android Development] Dees_Troy:
I put a RC0.3 build out on the website. This build uses the kernel that we extracted from Amon RA 2.3 which should hopefully prevent any more weird behaviors. It should also fix any other issues with wiping during a nandroid restore.

I am waiting on delivery of another EVO 4G which I will punish with this recovery when I receive it.
[EVO 4G Android Development] whiterider13:
Hey Dees_troy, is the new build different than the one I tested for you last week?

*Don't take life too seriously, you won't get out alive.*
[EVO 4G Android Development] Dees_Troy:
Yes, it is different. This build uses the same kernel as Amon RA 2.3 instead of the kernel that we were using before that was in the Cm7 tree.
[EVO 4G Android Development] aaanadie:
Help, please

Please, I need help

I need my phone to work, really need it.

I posted previously:

I had twrp-supersonic-2.0.0RC0.2

- Wipe all

- Flash classic-v005-01-02-finale-senseless

- Flash SUPERSONIC-SENSE-AnthraX-2.6.38.8-REV_zzzTESTzzz009 kernel

- Wipe cache & dalvik

- Reboot

then I got S-ON.

If I boot normally I get 4 or 5 beep.

If I pull battery and boot keeping vol down I can see:

...S-ON

HBOOT 2.16.0001

...

RADIO 2.15.00.05.02

I buy my phone in ebay and put in on bmobile, so I cannot get a replacement.

Any help?
[EVO 4G Android Development] fifasarajevo:
well im done here just bought an evo 3d sooooo yeah

and aaaandie mate your pretty much done with that phone nothing u can really do to fix it

---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------

double post
[EVO 4G Android Development] Captain_Throwback:
Have you tried flashing a stock ROM and then re-rooting?
[EVO 4G Android Development] aaanadie:
Note that I have HBOOT 2.16.0001, RADIO 2.15.00.05.02 & S-ON, any hope yet? Can you post a link for the right stock rom?

Thanks
[EVO 4G Android Development] FusionX:
It's not going to work man... just take it in and get it replaced (EDIT: just saw this isn't an option, so upgrade), or upgrade. Your phone is truly a brick, as is mine. I have spent hour upon hour trying to fix it.... the ONLY way to possibly fix it is if there is a root method developed that can work solely from hboot/fastboot... otherwise, you are screwed. sorry. :(
[EVO 4G Android Development] Captain_Throwback:
Try this one, and see if you can boot or not:

http://db.tt/Ck6AB18E

If it stays booted, you should be able to re-root.
[EVO 4G Android Development] FusionX:
if it stays booted AND you can access adb, you should be able to re-root.
[EVO 4G Android Development] POWerSUrgeSW3:
This doesn't mean the phone is bricked my friend. It simply means the phone needs rerooted. Now getting a used phone to start with means that the life span of the NAND memory on the phone is shorted. As long as the phone isn't physically spent, as in bad blocks, there should always be a way to fix the problem. IE flashing the most recent RUU and rerooting the phone. I personally had a phone that was rooted with bad NAND blocks and was unable to S-ON with anything. Until I found a HBOOT work around to be able to properly execute the RUU.

---------- Post added at 08:50 PM ---------- Previous post was at 08:45 PM ----------

On another note... I just installed v2.0RC.03. Again I tried partitioning my SD Card with the newest version of the recovery (of course after backing all content of my SD Card to my computer). And I repeatedly kept getting errors with not being able to mount /sd-ext . SO I decided to load AmonRA v2.3.3 to partition with that. Then copied everything back and installed TWRP v2.0RC.03 again. No errors...

Will say as a PLUS though... thing loads SOOOOOOOOOOOOO much faster!!! So nice! Thanks for the hard work!!
[EVO 4G Android Development] Craigerade:
Make sure to rename the file PC36IMG.zip I was able to flash a zip through hboot when my phone crashed. I just still had the vibrate problem. On a good note sprint gave me a nexus s because they said the evo's are on back order.
[EVO 4G Android Development] FusionX:
I agree! But if he can't get into any rom (including an RUU) and access adb shell, he cannot root considering his hboot version.. unless there is a way I am missing, in which case I would be very pleased!!!
[EVO 4G Android Development] aaanadie:
My cousin works in a phone repair center, so I brought my evo there. He sent me an email today saying my evo cannot be repaired, then I went ebay, buy one and must wait for it. I have no phone right now, I am going to try that fix later today but no much hope.

Thank you very much

---------- Post added at 05:02 PM ---------- Previous post was at 04:55 PM ----------

I'll try it later...

---------- Post added at 05:26 PM ---------- Previous post was at 05:02 PM ----------

I had twrp-supersonic-2.0.0RC0.2

- Wipe all

- Flash classic-v005-01-02-finale-senseless

- Flash SUPERSONIC-SENSE-AnthraX-2.6.38.8-REV_zzzTESTzzz009 kernel

- Wipe cache & dalvik

- Reboot

then I got S-ON.

If I boot normally I get 4 or 5 beep.

If I pull battery and boot keeping vol down I can see:

...S-ON

HBOOT 2.16.0001

...

RADIO 2.15.00.05.02

Can someone tell me what I did wrong? or was an issue related to twrp-supersonic-2.0.0RC0.2 and was fixed in twrp-supersonic-2.0.0RC0.3 ?

I need to know to no repeat that on my evo replacement.
[EVO 4G Android Development] picklerick:
If you are able to get into the bootloader then i dont see a problem. Use the signed PC36IMG that captain posted and then use http://revolutionary.io/
[EVO 4G Android Development] FusionX:
The problem, or at least in my case, i believe is that either the recovery or the anthrax kernel altered some part of the phone that cant be repaired or at least not without a working rom that gives access to adb shell... I for example can flash an ruu but once in the rom the computer does not recognize the phone properly causing absolutely no access to adb... Then the phone reboots continuously... Cant root without that when on hboot 2.16. Perhaps a partition was affected that cannot be repaired with flashing an ruu?
[EVO 4G Android Development] wallaceb:
well, I have news, I installed the RC2 of TWRP and had no issues using all features including flashing MikG 3.0. because of the "issues" people have been having i returned my phone to RA 2.3. by using the PC36IMG.zip method, and upon rebooting my phone the screen was blank/black.

i pulled the battery and pressed power and Vol up and got a bunch of vibrations.

this was just like what everyone else was describing.

i pulled the battery and pressed power and vol down, and got into the bootloader and was able to get into RA 2.3. i still show S-off and i still have my 2.10 version Hboot.

i proceeded to flash MikG 2.56 (since it happened to still be on my SD card) and it flashed fine and booted fine. i verified that my SDcard is still recognized, and i can still access ADB. i am in the process of downloading MikG 3.0.

i am not sure what happened.... :confused: :confused: :(
[EVO 4G Android Development] aaanadie:
Be carefull!!! Read my previous post:

http://xdaforums.com/showpost.php?p=20958031&postcount=218

and other people post too. I have no phone now until get replacement by Saturday.

Update: I just checked TWRP website, selected HTC EVO CDMA, says: "Device Specific Known Issues: None", last version available is "RC0.2 [2011-12-22]", I don't know why was deleted "PC36IMG-twrp-supersonic-2.0.0RC0.3" (should have be fixed my issue in that version), so be carefull again.
[EVO 4G Android Development] jlmancuso:
So is everyone getting this after the anthrax kernel or is it random? I tried the recovery for a few mins but went right back to amonRA.
[EVO 4G Android Development] wallaceb:
it seems more random, when i removed TWRP and went back to RA 2.3, i had the stock theme and kernel on MikG 3.0, my phone as i said above experienced this "issue". that is all i did... remove TWRP and went back to RA. i never even used the recovery, i re-installed RA using the PC36IMG method and my phone still gopt messed up.... :confused:

i have gotten my phone to work now by re-flashing MikG 2.56 and verifying everything worked correctly. i then re-flashed MikG 3.0, performed all the setup and installed apps. i then flashed Freedom 0.9 universal, and a theme for MikG and my phone works fine.

i have no idea what happened with my phone since it seemed like other people have said they stopped using TWRP and did not appear to have issues reverting back to RA.

all i can say is i am going to stick with RA 2.3, i have used RA the entire time i have had my phone, never had issues, and am going with the idea of "if its not broken, why fix it?"

luckily as i said i appear to have gotten my phone to work perfectly fine now.

it is just strange how the phone got messed up in the first place
[EVO 4G Android Development] scottspa74:
good question. I'm not using either, but have been following this closely since yesterday, and does seem, from reading, that in most cases it was in conjunction with anthrax kernel.

Given that (which may be coincidence, due to popularity of anthrax kernel), and that anthrax kernel won't flash on .76.00 hboot , there is something very puzzling going on. Wondering if it has to do with partition sizes, or boot.img size or something (over my head, just trying to further the discussion and investigation).

My condolences to those who lost their beloved evos :(

Edit: my post was intended as reply to jlmancuso, but wallacebs' post came in while I was typing
[EVO 4G Android Development] aaanadie:
When my evo dead:( I had hoot 2.16.0001 but can be a bug of twrp-supersonic-2.0.0RC0.2 related to flash anthrax kernel.

TWRP have a very very good GUI, actually the best, so would be great be sure it is safe to use.

---------- Post added at 04:33 PM ---------- Previous post was at 04:24 PM ----------

This thread and TWRP website are updated for HTC EVO 4G showing latest twrp-supersonic-2.0.0RC0.3 that should be fixed.

When someone flash anthrax kernel with this recovery please post here. I want to be sure all is ok again.

Thanks
[EVO 4G Android Development] glennruel:
Very very cool!!

I have been an Android addict for about a year. I truly love working on a new project. In my circle I have become the phone guy. I will tell you this is the coolest custom anything I have had the pleasure of playing with. I am on disability so that means I have lots of time to play. I can't tell you guy's how impressed I am with this. I do have a question, does it keep its performance with a device partially bricked? Just had that thought, I seriously love the package. Great Work!!

---------- Post added at 04:57 PM ---------- Previous post was at 04:35 PM ----------

I flashed a Nocturnal Shooter ROM last night with an Anthrax kernel. No issues. I have been useing TW Vs 2.0.0 for a couple days. I have flashed at least 8 ROMs and several kernels in that time. I have been on a mission lately to find "the perfect" combo. Or just bored. I have had no issues at all. I will say, though, issues I have had with flashings going awry, have usually been in-compatibility. Some kernels just don't like some ROMs no matter what the description says. I have had a few issues with the "wipe" before a flashing. Not with TWs recovery though. I have also found with what we are doing sometimes S&*T HAPPENS! Luckily Linux is so tough, you really got to work at it to really ruin it. I love Android and spend a lot of hours with it. I learn from my mistakes. I guess what I am saying is don't look so hard for someone or thing to blame. Take that time and learn something from the event.