yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] swiperrat:
lol busted......
[EVO 4G Android Development] 94tbird:
who the hell cares what post number you are? do you win prizes?

I modified one of the themes for the Evo3D and made it work for the Evo. Took a few tries, but came out perfectly. Its the ocean blue one
[EVO 4G Android Development] Goobertime:
Someone should start a themes page...

Sent from my Classic EVO
[EVO 4G Android Development] noname580:
MTD Partitioning

I just recently bricked an EVO trying to partition the nand using the MTD partitioning post. All of a sudden it flashed black after several attempts with troubleshooting. Only booted to bootloader say S-ON, thank god. Got my new one today. Having trouble with it as well. Worked fine with the amonRA styled recovery, 3.07. Only thought left is possible issue with the recovery. I have tried both the original release of 2.0 and the new RC0.2. Anyone else having an issue with partitioning?
[EVO 4G Android Development] POWerSUrgeSW3:
Have you tried any other scripts for partitioning? Me personally I never mess with the phones internal partitions. Ever received any errors when running any of your partition scripts?

~Max

This Message Sent From My CM7 HTC-Evo4G
[EVO 4G Android Development] picklerick:
this is the best thing since slice bread. thanks! although flashing large roms was a no go, kept giving me some error about not enough space on E:/ or something
[EVO 4G Android Development] PhxkinMassacre:
WARNING TO ALL USERS!!!! BRICKS WILL BE MADE!

ok i have spent all day trying to fix this to no avail.

i flashed a theme made in zipthemer (have used before with no problem) and after the flash it gave me the option to reboot system so i clicked it. when i clicked it i got screen tear and the phone would not boot. i don't mean a boot loop either. i mean it will show the splash then go to a black screen vibrate 5 times and then just have a green blicking notification light.

i have spent all day ruu'ing trying to fix it and nothing. i don't know if it was the theme or the recovery but since i have used zipthemer plenty before im gonna go with recovery.

this truly is a great recovery but it just f***ed me hard and im 14 days past the 1 year manufacturer warranty so im gonna have to break out the money and buy a new one :( :( :( :(

edit: and incase anyone was wondering this was not a noob error. i have been around this for plenty of time and know what i am doing. just to rule out the "oh your a noob" posts (not trying to sound like a smartass/****)
[EVO 4G Android Development] Redneck Trash:
How is it you've used this theme before? This is a new version of the recovery. Maybe I missed something but it sounds odd.

Sent from my PC36100 using Xparent Red Tapatalk
[EVO 4G Android Development] Goobertime:
i think he means he has flashed the same theme for a rom before.....also you arent bricked if you can get into boot loader......so i dont think you need to buy a new phone...
[EVO 4G Android Development] PhxkinMassacre:
what i meant by theme is a rom theme that is flashed through recovery. and thats the thing. the bootloader is all i can get to. believe me i have tried it all. phone wouldn't boot (black screen vibrate 5 times and blinck green led) so i ruu''d multiple times and it and now it is stock unrooted. it will boot for about 2 minutes and then go black screen vibrate 5 times and have a green flashing led.

i cant flash a recovery because im not rooted.

i cant root because not only does the phone not stay up long enough to accomplish it but it also will not be detected by any of my computers.

before i unrooted i also tried flashing recovery and the sd card would not mount in the bootloader to scan it. it wouldn't even check the sdcard it just skips it. not text that signals its scanning or anything

trust me when i say i know what i am doing and i tried it all. it is and irreversible problem i have here. i have literally spent 6 hours today trying to fix this. it is toast. im thinking it messes up some blocks in one of the partitions in the nand and that = your S.O.L.
[EVO 4G Android Development] Redneck Trash:
I misunderstood. I though you themed the recovery. I'm going to bow out now since this is over my head.

Sent from my PC36100 using Xparent Red Tapatalk
[EVO 4G Android Development] PhxkinMassacre:
its ok haha no harm done. but yeah themeing the recovery is way over my head haha :P i didn't even make the theme i flashed before my phone had its nuclear meltdown haha
[EVO 4G Android Development] noname580:
I havent tried any other scripts except for the ones posted by caulk that were originally made by someone else. Weird that only twrp 2 doesn't like the scripts. Both amonRa 2.something and the other modified amonRa recovery by I can't remember, like 3.07 or so, work fine with the partitioning zips. I need to starting learning the code to android. And no I have never recieved any errors in TWRP 2.0 while using the scripts, just bootloops and reboots to recovery.

---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------

The black screen, vibrating, and blinking green light is what happened to my phone while trying to partition the nand memory. It said S-ON so I brought it back to sprint and got a new EVO. You nand memory is fried. Can't even hard reset.
[EVO 4G Android Development] PhxkinMassacre:
that what i thought. thanks for the info. but the wierd thing is, is that it turns on and is fully operational but only stays on for about 2-3 minutes...
[EVO 4G Android Development] likeurface:
Is it required to repartition the sd card if coming from another recovery?

Econ teacher: "what happens if we shift LRAS to the right?"

Random other student in class:"we all die of starvation"

Teacher: "and this, students, is why none of you will ever lead this country" and proceeds to walk out of class.
[EVO 4G Android Development] POWerSUrgeSW3:
To tell you the truth I think he partitioning with v2.0 messes the SD card up. I had issues mounting the card correctly after I did. But it was weird. It would show up in my ROM for awhile then act like it wasn't there. Thought it was the card so finally went messing with it yesterday. Ended up reverting my recovery back to v1.1.1 and partitioning my SD Card again. All seems well now. Back to v2.0.

Oh the other thing that caught my eye was when I went into v2.0 recovery the log would say that it could not read /sdcard, yet I could still install zips from my SD card. Weird.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] Goobertime:
Is anyone working on themes? Cause there are a million for the 3d and I'm getting jealous...Haha

Sent from my Classic EVO
[EVO 4G Android Development] TorxT3D:
how safe is it to use this to wipe and flash small and large sense 3.5 roms?

partition ext as well for the larger sense roms.. ??
[EVO 4G Android Development] FusionX:
Booting Issue

I am having a problem booting my phone...

Background: A couple days ago I flashed TWRP2 to my evo... it worked fine but as I've seen reported it did hang for 60 seconds or so before entering recovery. At that point I checked the "terminal" output in recovery and it said it was having problems mounting my SD Card... however, I was still able to access my files on the SD card in recovery.

I wasn't going to flash anything until this morning. As usual, I performed a nandroid in preparation to flashing... TWRP backed up my phone to the SD card, I wiped cache and dalvick cache, flashed a kernel, wiped cache and dalvick once more and went to reboot as normal.

I came back to my phone about 15 minutes later and it was stuck on the white htc screen... I let it go for another 15 minutes but still no luck.

Problem: I went to go back into recovery, which I can do, but now it can't mount the sd-card at all, or read any files on it... I put the sd-card in my buddies phone and it reads just fine so I know the card is good.... I powered off and then entered the bootloader, which I can get into fine... I tried to reflash TWRP via PC36IMG.zip... it reads the zip but then instead of asking me to flash it, it jumps back to bootloader.. I tried to flash Amon RA back on but same thing, it reads the zip but wont offer me the option to install it.

I tried then to use fastboot to flash my recovery.img file but fastboot in my terminal in linux won't recognize any devices, even when the phone says fastboot usb.

Does anyone have any ideas as to what I can do to fix this?????

I am assuming that this is likely related to the recovery and not the kernel I was trying to flash but I guess that could be, but one would think that a kernel wouldn't have an effect on how or if recovery can read my sd-card...

Any help is MUCH appreciated!!!!
[EVO 4G Android Development] Notorious:
Are you still s-off? Also try a ruu
[EVO 4G Android Development] HDRules:
Fusion: Were you flashing the new Anthrax kernel? It has a problem with Hboot 0.76 and will not reboot. Flashing a different kernel will allow you to boot properly.
[EVO 4G Android Development] POWerSUrgeSW3:
I would pull the SD Card out and put it in a PC computer and run a full scan disk on the card. It might be about read to kick.

I get the same error in recovery with the SD Card not mounting but still being able to read files off of it. I've formatted my care a few times and still the same. Never had an issue until this recovery, wondering if that might just be a part glitch in the current version of the recovery. And maybe the two issues are not related.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] FusionX:
Wow, I just looked and S-on... First time that's happened since June 2009.. nice catch! Guess I'll have to re-root tonight. Do you think that would cause issues with the sd-card not being readable in recovery?

Yes, it was the Anthrax kernel and I do have Hboot 0.76, damn I guess I should have read more about that in the thread before flashing that bad boy! I wonder why it would cause an issue in recovery with the sd-card and the issue of turning S-on?

Yeah, I checked the card on the computer and it comes up clean with a scan... I'm wondering if like you said, that's just something with the current version of the recovery...

Thanks All!
[EVO 4G Android Development] Notorious:
I'm warning you MIGHT have a brick. One member was using this recovery he flashed one of the themes then it mysteriously went back to s-on and he could not reach recovery and a ruu didn't help. He ended up taking it back for a replacement

Edit:his phone just bootlooped
[EVO 4G Android Development] Kekoh:
All these issues are making me weary of keeping TWRP...
[EVO 4G Android Development] FusionX:
Interesting.. I'm hoping that going through the root process will help but the one thing that has me concerned is that the bootloader sees that I have a PC36IMG.zip on the sd-card, but it doesn't give me the opportunity to install it... if that's the case I think I'm at a loss.

I never flashed any themes to the recovery and I can get into it, but I can't really do anything in the way of installing anything from inside of it because it can't see my sd-card...

Guess I have some terrible homework for the night.
[EVO 4G Android Development] HDRules:
Have you tried a nandroid restore?
[EVO 4G Android Development] FusionX:
Keep an eye on the thread...

My issues may not even be related to TWRP for certain... I posted here because logically when taking into account I just started using this recovery and the fact I flashed the Anthrax kernel I thought it was more likely related to the recovery. However as posted above it sounds like there are reports of the Anthrax kernel causing issues with hboot 0.76..

When I get to the bottom of this I'll be sure to update what I find... If I am not bricked then I'll flash Amon RA and try the kernel again to see if it causes the same issue. I'll also flash known good kernels with TWRP to try and rule the recovery out too.
[EVO 4G Android Development] POWerSUrgeSW3:
I do not see how flashing a recovery would redo the bootloader on its own. Plus if it did, what was going on around the same time that the phone did go S-ON. But this is a question more for the Devs.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] FusionX:
Can't do a restore b/c recovery can't see my sd-card... maybe I can do a manual restore but that would require fastboot to recognize my device which it doesn't so that might not be an option presently.
[EVO 4G Android Development] Notorious:
If you.go back a few pages the guy that replaced his phone posted what happened and he made a thread but we could not help him
[EVO 4G Android Development] POWerSUrgeSW3:
Just saw this too... so getting an unlocked bootloader should be even easier now...

RT @DroidTweak #android #mobile HTC EVO 4G and myTouch 4G Slide now supported by HTC Dev... http://t.co/lnbRafZo http://t.co/AEpRfLOS #droidtweak

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] Captain_Throwback:
You need to follow evo's suggestion to use an RUU to flash your device. The only other thing you can do is flash an HTC-signed PC36IMG. I have some links to a few on my Dropbox if you need them. I'd recommend the latest Froyo, since it's easier (IMO) to root with unrEVOked than with Revolutionary.
[EVO 4G Android Development] Notorious:
Thank you throwback :)
[EVO 4G Android Development] Notorious:
Also I just checked and that's only for the Korea version
[EVO 4G Android Development] POWerSUrgeSW3:
True I did miss that. Sorry for the excitement. But worth keeping an eye on regardless.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] whiterider13:
I believe the reason the bootloader does not give you the option to update when it sees the PC36100.zip is because you are S-on.

*Don't take life too seriously, you won't get out alive.*
[EVO 4G Android Development] Captain_Throwback:
This is correct. If the PC36IMG doesn't have an HTC signature, then it won't be recognized by the bootloader when you're S-ON. Fortunately, there are fully sotck versions that can be used. I provided a few links to the poster via PM. Hopefully that'll get it working.
[EVO 4G Android Development] FusionX:
Ok, so I flashed the RUU... I am able to boot into the rom but it will randomly reboot... also, I cannot go through the rooting process.. the computer is detecting the device as "Qualcomm" something or other, I think this is related to the Anthrax kernel... I can get fastboot commands working via Hboot USB but I don't think I can root the phone this way, correct?

Any thoughts???
[EVO 4G Android Development] Captain_Throwback:
The Anthrax kernel can't be the issue anymore, as you should now be completely stock. Try flashing the stock PC36IMG again, and see if that helps. You only need it to be on long enough to root the device. It's also possible the device got corupted and/or you have some bad blocks.

Or you can try upgrading to Gingerbread and see if that stabilizes the device. Then you can root via Revolutionary.
[EVO 4G Android Development] FusionX:
that's what i would have thought! My computer, in several OS's (ubuntu, windows 7 and xp) won't recognize the device when it's up and running... it identifies it as a qualcomm device which i have never seen before. I'm going to keep messing around and see what I come up with.. The title of the Anthrax kernel thread made me think it was related...

[KERNEL] [SENSE] 12-25 - AnthraX - BEATS - USB HOST MODE - QUALCOMM 'B' VER

also, when I hook up my phone to the PC while it is running the stock froyo rom, it doesn't register as being plugged in, no charge light, nothing.
[EVO 4G Android Development] Captain_Throwback:
Try the Gingerbread update and see if that helps.
[EVO 4G Android Development] killacamoh9:
Same problems as FusionX, except the only similarity we have is that we were using TWRP 2.0 recovery. I love the recovery, but it looks as though amon-ra is still old faithful. I've thought I've bricked my evo a thousand times, but I've spent more time trying to fix this than any other time. Hope is dying.
[EVO 4G Android Development] aikeru:
Thanks!

Thanks for making this and releasing it into the wild! :)

My Dad's EVO has a busted volume rocker (been using an app to control volume). The warranty is out since it has 'water damage'. :(

This could allow him to use CyanogenMod or other cool ROMs that he hasn't been able to flash before!
[EVO 4G Android Development] FusionX:
Same Sh*t different build... still rebooting on gingerbread RUU... can't see phone via PC so can't root.... pretty much losing hope that this can be fixed... if anyone has any ideas?

edit: in fact, i cannot get into hboot usb anymore after using the RUU for GB... I seem to be worse off now.
[EVO 4G Android Development] Captain_Throwback:
Well, at this point, you should be able to take the phone in for service. It's unrooted and S-ON, so you shouldn't have any trouble getting it serviced. Sorry I couldn't help more :(.
[EVO 4G Android Development] FusionX:
unfortunately the phone is 18 months old so it's out of warranty... i guess i'll just try a few more things tonight and then tomorrow if need be I'll get an upgrade... although there isn't any sprint phone out that I want right now :(
[EVO 4G Android Development] Goobertime:
Well, my brother had an issue with his phone and his warranty was well up, and they still got him a refurbished phone for like 30 bucks, so its worth taking in, just play stupid

Sent from my Classic EVO
[EVO 4G Android Development] POWerSUrgeSW3:
Out of warranty? I would take it in anyway. My phone is 18 months old as well. My phone ended up having bad blocks and kept rebooting after booting into the OS for a few minutes. After the tech messed with it for 20 minutes said they would replace it. No charge or anything just a simple signature and wait for a new phone.

There is a back order with Evos from Sprint though. Probably due to the big sale Sprint just had. I got lucky and the tech at my store swapped my board with one they had there.

Big thing is as long as the phone is S-ON and looks stock, that's all they care about. I told then that I was having boot issues and went back to a factory reset and it made it worse.

So give them some speal like that and you might get lucky. Because the random reboots on a stock ROM sounds like some bad blocks on the NAND memory.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] Lacedaemon:
Upgraded from TWRP 1.1 to TWRP 2.0 and it still won't flash MIUI updates. :mad:

UPDATE: The update installed with Amon Ra. Are there certain types of .zip files that TWRP can't install? :confused:
[EVO 4G Android Development] FusionX:
Heading to the store in a few... If they can't fix it... the debate is between:

Samsung Galaxy S II Epic 4G

or

HTC Evo 3D

EDIT: They are replacing the Evo at no charge as it is a known issue (random reboots...) Also, the Epic looks nicer than the 3D
[EVO 4G Android Development] Novarider:
I just tried to flash a rom and it said there was a md5 error but the md5 for the rom matches what it's supposed to be. Is there a way around this problem?
[EVO 4G Android Development] Redneck Trash:
Is there a toggle option for checking md5?

Sent from my PC36100 using Xparent Red Tapatalk
[EVO 4G Android Development] Novarider:
Not that I could find.
[EVO 4G Android Development] POWerSUrgeSW3:
Agreed. Plus the Epic II has a bigger screen :-)

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] POWerSUrgeSW3:
Have you used an MD5 checker on a computer to verify the downloaded file was correctly download? Could be a bad download? Have you tried flashing your recovery back to v1.1.1 to see if the update worked? Or did you flash RA after to verify the file would work?

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] Captain_Throwback:
Well, at least one positive came out of this . . . though I'm sorry you got stuck with an EVO :rolleyes:.

Now you can get that replacement home, rooted, and flashed with that Anthrax kernel (you shouldn't have any problem with that now).
[EVO 4G Android Development] ECrispy:
Does RC2 have any issues with sdext partitions, wiping/creating them etc?
[EVO 4G Android Development] whiterider13:
Nope. The sd ext issues were fixed for RC0.2

*Don't take life too seriously, you won't get out alive.*
[EVO 4G Android Development] kf2m:
Had that happen to my Launch Day EVO earlier this week. Using RC0.2, and was flashing CM7.1 Nightly 256. No SDCARD, ADB or Fastboot access via USB. Wasn't the SDCard since it works fine with the replacement EVO. Followed the instructions in the x5 vibrate, green notification light issue. YOu could get back into Recovery if you have the USB cable connected, but no access via USB. The old Evo was a 002 with the Engineering HBOOT.
[EVO 4G Android Development] Diablo67:
Works great for me,love the touch,instead of the volume rocker.Alot easier to use.
[EVO 4G Android Development] Goobertime:
I love it too, I'm just afraid if I keep using this recovery something will get messed up, like what happened to some others that have posted

Sent from my Classic EVO
[EVO 4G Android Development] POWerSUrgeSW3:
Well I haven't had an issue due to the recovery. Ithink a lot of us are hitting the wall with just general hardware failures due to age/factory known issues.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] Captain_Throwback:
Well that, and people are trying to use this recovery to flash things that it will not flash, like HBOOTs, Radios, etc. The versions of those from Calkulin's thread that were made to flash via recovery WILL NOT flash with TWRP. That's by design, as has been posted previously, since these are better flashed through the Bootloader. I think that's where quite a few people have been hitting a roadblock (to be fair, I don't see that noted in the OP or on the site anywhere).
[EVO 4G Android Development] POWerSUrgeSW3:
I guess I miss that. As it was ground into my head by maybe threads on forums... HBOOT, Radios, and a few others should ALWAYS be flashed through the bootloader and not recovery. Due to the fact of a much less risk of messing up the phone.

But I guess goes to show everyone has got to read read read to make sure they are aware of risks as well as proper procedures when it comes to the art of rooting/customizing of their phones.

~Max

• Sent Via My Rooted & Customized Evo4G •
[EVO 4G Android Development] gunfromsako:
+ 1
[EVO 4G Android Development] Novarider:
Yes the md5 matched what it was supposed to be so the download was good. I switched back ra recovery and the rom flashed fine.
[EVO 4G Android Development] Goobertime:
The dalvik cache wipe doesn't wipe everything other recoveries wipe does it ?

Sent from my Classic EVO
[EVO 4G Android Development] whiterider13:
It does for me.

*Don't take life too seriously, you won't get out alive.*
[EVO 4G Android Development] Goobertime:
- Wiping Dalvik Cache Directories...

Cleaned: /data/dalvik-cache...

Cleaned: /cache/dalvik-cache...

Cleaned: /cache/dc

I:Mounting /sd-ext

This is what it says it wipes, isn't it supposed to wipe SD ext. Cache? Idk I just feel like something is missing

Sent from my Classic EVO
[EVO 4G Android Development] whiterider13:
It only wipes sd ext and cache if you do factory reset which also wipes data. If I remember correctly, those 3 are the only ones that amon ra 2.3 wipes as well when you wipe dalvik cache.

*Don't take life too seriously, you won't get out alive.*
[EVO 4G Android Development] Goobertime:
Idk I just don't understand why twrp doesn't wipe as much as amon ra...i just remember reading that's why AR was a better recovery than cwm because AR wiped everything correctly....Idk I'm just being paranoid, I do like this recovery a lot, I'm just confused about little things

Sent from my Classic EVO
[EVO 4G Android Development] POWerSUrgeSW3:
What is it not wiping that RA is? I thought they both had very similar wipe options.

~Max

• Sent Via My Rooted & Customized Evo4G •