Develop Bugs

Can't flash AOSP Roms

So I've been dealing with this for a few days or so and started posting about it in Cyanogen's Rom thread, but I figured its finally time to make a thread about this.
First and foremost, I'm rooted, got SU, S-off, and I can get to #. Radio - EVO_Radio_2.15.00.11.19, PRI - EVO_PRI_1.90_003, NV - EVO_NV_1.90_003, H-Boot 2.10, and I'm using AR Recovery v2.1.1 (I've tried 1.8.0, 1.7.x, etc.). I just formatted my SD card Fat32 the non quick way, and tried flashing Cyanogen, and Evervolv, and my HTC Evo 4G screen just loops. Comes on for a minute, turns off, and repeats. I've also tried rerooting, which was mentioned elsewhere, as well as trying to flash MUIU, which flashes fine.
Any help would be greatly appreciated.

Did you flash GAPPS along with the rom?

Yes with 11/14 HDPI and I've tried it without it. Also im doing full wipes + Format All everytime.
Sent from my HTC Evo 4G using Tapatalk

what hw revision do you have? 003? 004? also, did you accept an ota? or got the evo with 2.10?

003 and I updated to 3.70. I'm not sure if I had 2.10 prior to updating, but I kinda think I may have had 2.02 before. I bought my Evo last Wed.
Sent from my HTC Evo 4G using Tapatalk

Jocelyn said:
003 and I updated to 3.70. I'm not sure if I had 2.10 prior to updating, but I kinda think I may have had 2.02 before. I bought my Evolution last Wed.
Sent from my HTC Evo 4G using Tapatalk
Click to expand...
Click to collapse
excellent..
try this:
http://forum.xda-developers.com/showthread.php?t=883548
it will give you the engineering hboot, which has fastboot commands available and will probably be more useful than 2.10.

I thought it wasn't okay for people with 2.10 to flash back.
Edit: erred ok I'll try it.
Edit2: Op even says don't use with 003/004
If you're doing this on late hardware models 003/004 (with new partitions) then you should stop reading now and probably not do it. I'm not sure if the new recovery can fix up your stuff after you do this
Click to expand...
Click to collapse
Sent from my HTC Evo 4G using Tapatalk

If it helps any, when I run cat /proc/mtd my partitions are 40000. This tells me I'm on the newer partition and should stay away from the method mentioned above.

Jocelyn said:
If it helps any, when I run cat /proc/mtd my partitions are 40000. This tells me I'm on the newer partition and should stay away from the method mentioned above.
Click to expand...
Click to collapse
oh ok, gotcha.. thanks for clearing that up. troubleshooting continues.
btw, i'm suspecting bad nand blocks, but that's wild speculation at this point.

shift_ said:
btw, i'm suspecting bad nand blocks, but that's wild speculation at this point.
Click to expand...
Click to collapse
Does that mean I should unroot and exchange my phone?

Jocelyn said:
Does that mean I should unroot and exchange my phone?
Click to expand...
Click to collapse
Yea, it might be the next step.
Swyped from my EVO

Do aosp roms flash in a different place/sector?
Sent from my HTC Evo 4G using Tapatalk

Jocelyn said:
Do aosp roms flash in a different place/sector?
Sent from my HTC Evo 4G using Tapatalk
Click to expand...
Click to collapse
no, but kernel size differences may cause issues like that.

shift_ said:
no, but kernel size differences may cause issues like that.
Click to expand...
Click to collapse
K one last thing. I'm going to unroot following the thread linked below, but what about RA 2.1.1 being my current recovery? Will an RUU flash it back to stock recovery? I'm also going to unroot and try the rooting method in following the thread and if its still a no go when flashing aosp roms, I'll unroot and exchange. Btw thanks for all the help!
http://forum.xda-developers.com/showthread.php?t=829045

Jocelyn said:
K one last thing. I'm going to unroot following the thread linked below, but what about RA 2.1.1 being my current recovery? Will an RUU flash it back to stock recovery? I'm also going to unroot and try rooting in following the thread and if its still a no go when flashing aosp roms, I'll unroot and exchange. Btw thanks for all the help!
http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
yes, an ruu straightens you back out to unroot. what i suggest you do is flash a stock rom before doing so.
no problem, i'm still trying to figure out why your phone is being so selective, but bad nands is always creeping up as a possible cause.

shift_ said:
yes, an ruu straightens you back out to unroot. what i suggest you do is flash a stock rom before doing so.
no problem, i'm still trying to figure out why your phone is being so selective, but bad nands is always creeping up as a possible cause.
Click to expand...
Click to collapse
Yeah I just ran unrevoked forever s-on linked in zikronix's thread and I'm flashing back to stock with his PC36img Hboot method. Like I said, I might as well try unrooting with the method in that thread and try flashing Cyanogen again. If its a no go, I'll just repeat the s-on, flash back to stock, and exchange it. Prolly gonna tell them 4G didn't work when I was in Chicago or something lol.

Jocelyn said:
Yeah I just ran unrevoked forever s-on linked in zikronix's thread and I'm flashing back to stock with his PC36img Hboot method. Like I said, I might as well try unrooting with the method in that thread and try flashing Cyanogen again. If its a no go, I'll just repeat the s-on, flash back to stock, and exchange it. Prolly gonna tell them 4G didn't work when I was in Chicago or something lol.
Click to expand...
Click to collapse
yea, that's your best bet.

[Q] How do I update to Gingerbread? ROM Manager Causing Issues

I want to update my G2 to Gingerbread 2.3.3 but for some reason when my phone restarts for the update to take affect I see the little green android with the progress bar. It stops without reaching 100% and I get an installation error. Why wont it upgrade? Could ClockworkMod Recovery be the culprit?

I don't know for sure but I would think so. Manually push the stock recovery (find it on the forum somewhere) back via adb and try again maybe? Either that or just flash the entire pc10img and u definitely won't have a problem. You will lose all your data tho.
Sent from my HTC Vision using XDA Premium App

JosepHenry said:
I want to update my G2 to Gingerbread 2.3.3 but for some reason when my phone restarts for the update to take affect I see the little green android with the progress bar. It stops without reaching 100% and I get an installation error. Why wont it upgrade? Could ClockworkMod Recovery be the culprit?
Click to expand...
Click to collapse
So if you have ClockworkMod Recovery, that means you're rooted.
What are you trying to update to 2.3.3 with? Are you taking the OTA? You can't do this (or really really shouldn't) when you're rooted.
If you're rooted, head to the dev section and pick up a pre-rooted 2.3.3 OTA release. You'll keep your root and be upgraded to 2.3.3 like you want.
http://forum.xda-developers.com/showthread.php?t=1211143 I used this one. Its literally just the OTA, pre-rooted. No radio, just the ROM. Flash through ClockworkMod recovery. You should backup apps with something like Titanium Backup first, because its in your best interest to wipe all data through recovery before flashing.

Thanks guys. I honestly didnt know that I wasnt suppose to update/install official updates if my phone has been rooted. The pc10img ROM xsteven77x didnt work for me but the one martonikaj suggested did.
Once again. Thanks! Problem solved.

JosepHenry said:
Thanks guys. I honestly didnt know that I wasnt suppose to update/install official updates if my phone has been rooted. The pc10img ROM xsteven77x didnt work for me but the one martonikaj suggested did.
Once again. Thanks! Problem solved.
Click to expand...
Click to collapse
Yep no problem. Just know that when you're rooted, you can no longer take any official update. Gotta do it on your own manually with pre-rooted ROMs.
Feel free to click "thanks" for my post glad I could help you out.

[Q] Evo3d from Assurion?

Has anyone gotten an Evo3d replacement from Assurion(sprint insurance) anytime recently? I'm most interested if it has Hboot 1.5 for obvious reasons. Thanks!

bigupurself7 said:
Has anyone gotten an Evo3d replacement from Assurion(sprint insurance) anytime recently? I'm most interested if it has Hboot 1.5 for obvious reasons. Thanks!
Click to expand...
Click to collapse
I got one in october and it had 1.4!

Got one this week and it had 1.3. Had 1.5 on my last phone so at least i got something worthwhile for my insurance premium.
Vibrate mechanism on it is really weak though.

1.5 2 weeks ago

mine was 1.3
Sent from my SPH-D710 using XDA App

1.4 a month ago

I guess is random hboots i got mine last week and it was 1.4
Sent From My HTC EVO 3D ROOTED

Got mine back in November with 1.5.
Sent from my PG86100 using xda premium

Got mines early last month with 1.3
Evo 3D on Tapatalk

Mine was probably early November, I got HBoot 1.30.
Seems random luck w/ shipped phones.

damm some of u guys are lucky!!!! i got mines in november and it was 1.50

evod3 said:
damm some of u guys are lucky!!!! i got mines in november and it was 1.50
Click to expand...
Click to collapse
i have 1.5.... i have cyanogen 7 installed.... im not getting the point of this thread?

whats the big whoop with hboot 1.5? im getting a 3d today to replace my toasted og evo 4g and have heard about it being a pain in the ass. why is it so much worse than all the other hboots?

PhxkinMassacre said:
whats the big whoop with hboot 1.5? im getting a 3d today to replace my toasted og evo 4g and have heard about it being a pain in the ass. why is it so much worse than all the other hboots?
Click to expand...
Click to collapse
Read around, there is no full root method for phones with with hboot version. You can root, but you won't be able to flash ROM with custom kernels unless you jump threw some hoops via fastboot.
Sent from my PG86100 using Tapatalk

I got mine like a week ago and it had hboot 1.5. Like others have said there is no full custom root method, you have to use HTC's unlock tool which requires you to use some adb but it walks you through it. Basically once you get a recovery installed you can flash roms like normal, but kernels are a different story because the boot partition where it is stored is still locked. But its actually not that hard to flash them. Download the flash image GUI app and it can either extract kernel files from a ROM zip and flash that or pick a kernel zip and flash that directly. It clears cache and dalvik for you and must reboot immediately.
Sent from my PG86100 using XDA App

ncfastls1 said:
I got mine like a week ago and it had hboot 1.5. Like others have said there is no full custom root method, you have to use HTC's unlock tool which requires you to use some adb but it walks you through it. Basically once you get a recovery installed you can flash roms like normal, but kernels are a different story because the boot partition where it is stored is still locked. But its actually not that hard to flash them. Download the flash image GUI app and it can either extract kernel files from a ROM zip and flash that or pick a kernel zip and flash that directly. It clears cache and dalvik for you and must reboot immediately.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did did my unlock via the HTC method.. worked flawlessly... then flashed the customer recovery via Teamwin's process and i have been flashing kernels and roms non stop since... its really not hard.. just make sure you boot via adb to fastboot using the command... or else it wont work.. but its basically the same as any other hboot now.

Got mine almost 3 weeks ago and got HBOOT 1.30!

[Q] PC36IMG ERROR AT HBOOT.I think i have soft bricked my phone. NEED HELP. PLEASE!!!

HI. I AM FAIRLY NEW TO THE ROM FLASHING SCENE. HAVE BEEN SUCCESSFUL FOR THE LAST FEW MONTHS AT FLASHING ROMS. THEN I THINK I STEPED OUT OF BOUND AND BEGAN TO TRY FLASHING NEW KERNELS. HAVE BEEN SEARCHING WEB ALL DAY ON WHAT COULD HAVE HAPPENED. FROM WHAT I HAVE READ I MAY HAVE FLASHED A KERNEL FROM ONE MOD TO ANOTHER. OR POSSSIBLY INTERRUPTED THE ZIP INSTALL OR FLASH. NOW WHEN I TRY TO FLASH BACK UP ROMS THEY BOOT LOOP OR JUST STAY ON BOOT SCREEN. SAYS NO PC36IMG at the hboot screen. please help.

Are you using the newest HBOOT from HTC? I heard that you can't flash kernels on it...
Maybe the .zip didn't download completely. What kernel did you try to flash, can you even access recovery?

HBOOT 6.16.1002. i was flashing a tiamat kernel. didnt like it and when i tried another one is when it happened. not sure if i did all the wipes. was late and was getting tired

by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE

trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
well tiamat will not work on any mik rom that i know of because (all?) mik roms are sense roms. if its a sense rom then you need a sense kernel. aosp rom needs aosp kernel. go into recovery and flash a sense kernel. that should fix your bootloop

Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out

trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium

-EViL-KoNCEPTz- said:
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?

Damn it. So am i screwed or is their a solution

trevanti00 said:
Damn it. So am i screwed or is their a solution
Click to expand...
Click to collapse
did your s turn back on after the bootloop ?

What did he do to fix it. Do you have a thread on that

I am s off

No it is still off

trevanti00 said:
No it is still off
Click to expand...
Click to collapse
then TWRP most likely didnt cause it. His situation was different from what your experiencing so what he did will most likely will be different from what youll have to do. Also if TWRP caused it you would be back to s-on

Well could you give it a shot and trouble shoot with me. I been at it eveery since last night

trevanti00 said:
Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out
Click to expand...
Click to collapse
here is one...http://forum.xda-developers.com/showthread.php?t=1496488

Flash amon ra in hboot and get off of twrp b4 u end up screwed first and foremost then try wiping everything in amon ra except sdcard and battery stats and flash a new rom and see if it will boot up if you can't get recovery to load you may need to try running an ruu and starting from scratch
Sent from my PC36100 using xda premium

evo4gnoob said:
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?
Click to expand...
Click to collapse
Ppl not reading enough or rushing thru things is my guess *shrugs*
Sent from my PC36100 using xda premium

ok trying that now.

problem solved. thank you guys a million times. i knew i would run into a brick sooner or later. lesson learned. i have always read all the post before flashing but was tired and got lazy. will never happen again. again THANK YOU GUYS.

Problem with rooting (Stuck on reboot loop)

I got my incredible 2 almost two years ago, and spent the whole time having it be rooted and messing with different roms completely carefree. I was supposed to get an upgrade soon, but sadly that didn't happen and won't for another few months. Any ways, I returned my phone to stock for the trade in. Since I am stuck with this phone for awhile longer, the default stock is driving me mad with the slow bloatware and etc, so time to root again.
I downgraded to 2.3.3,which was the easy part, and then used revolutionary. It said I was already s off, and asked if I wanted to install a recovery. I said yes. Upon reboot of my phone it turned itself off and rebooted. Again. And again. In an infinite loop. I went back into recovery and wiped cache and installed the su zip from my sd card, flashed another Rom. Nothing. Installing another Rom has it stuck on boot animation. I have to restore stock and start all over.
I'm confused on what I am doing wrong. Any advice would be great. Thanks.
Sent from my ADR6350 using xda app-developers app

Flash the latest radio.
Sent from my SCH-I535 using Tapatalk 2

prototype7 said:
Flash the latest radio.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
how to flash the radio?

luciddreaming said:
how to flash the radio?
Click to expand...
Click to collapse
Basically the same as flashing anything else (ROM etc.), no?

Shawno7 said:
Basically the same as flashing anything else (ROM etc.), no?
Click to expand...
Click to collapse
No.
The instructions are in the radios sticky in the dev forum. Read up, backup, then go for it.

gtdtm said:
No.
The instructions are in the radios sticky in the dev forum. Read up, backup, then go for it.
Click to expand...
Click to collapse
Will do