Develop Bugs

[Q] Can anybody help me out, please?

I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!

you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root

NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!

luck has been wished

Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?

still won't not into any rom? did you get errors?

NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.

what happens when you reboot the phone not going into bootloader?

Just the HTC EVO 4G splash screen. Over and over and over...

does it show the boot animation or just stuck on splash?

Just the splash. No animation.

pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation

Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App

Wrong button..

xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?

never do OTA when rooted, use unrevoked to root, unrevoked.com

NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?

Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...​
2) Anyone know how to turn S-(back)ON in my current situation?​
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )

run the ruu to s-on then trade for another

NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.

[Q] Can't get EVO to unroot =(

Hi All,
I'm trying to unroot my evo and can't... I do NOT remember what unrevoke method I used for it, its been 8 months... I've tried the many different tutorials posted online, which has been complete epic fail.
The Specs:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041F
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Aug 19 2010,14:29:08
ClockwordMod Recovery v2.5.0.7
I've been able to turn S-ON but whenever I try to flash the PC36IMG, it gives me the error "main version is older". After that failure, I tried the method of installing HTC Sync and running running "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed" which started though failed half way in with a communication error.
What the hell am I doing wrong here guys? I need to get this in the mail to send back to Asurion tomorrow, so i'm offering a $5.00 paypal bounty to the first person that can help me out and get me back to a stock rom. Thanks!

asurion could not possibly care less that your phone is rooted. You dont even have to send them a phone back, you can just report it lost, but you dont have to cuz they wont care. So you dont really need to worry.
Basically your getting the "main version is older" error because of your bootloader. HTC/google wont let you flash older versions of certain image files, its another stumbling block to make gaining root harder. I havent had this problem in a while, but it definitely started when you flashed s-on.
The solution is going to involve fastboot. I believe your going to have to flash an engineering bootloader, maybe a new misc partition. I took a quick look for solutions but theyre all for rooting, not unrooting. I cant tell you exactly what is wrong, but for future reference just run an RUU while you have s-off. It will save a lot of complications.
But really, why go through that trouble? Asurion wont care that your phone is rooted.

So you need to either flash a PC36IMG.zip that is the same version or newer than your current ROM, or flash mtd-eng.img to the misc partition.
the newest pc36img should be here:
http://forum.xda-developers.com/showthread.php?t=874091
as for toasts mtd-eng.img, that should be easy enough for you to find.

Thanks for the bit of info, I finally found someone else who had the same problem and was helpful enough to post the stuff online.

I've been having trouble unrooting my evo due to outdated PC36IMG.zip files. Every time I've tried a new one, it won't complete the flash, it says abort. So if this is the newest...all I do is download http://rapidshare.com/files/4370996....651.1-3.30.651.3_releasekobxwrvtv9q86pp0.zip and just rename the file to PC36IMG.zip right? Should work out?

[Q] Evo 4G Boots to 4G Screen then turns grey

Well, I've come across an embarassing situation. My problem is in the title, and for those with a keen eye, yes, I'm a Sprint tech so laugh about that if you will, don't care. Gotten that on several other forums and no help. Apparently people hate us lol. Point is, telling me I need to take the phone in isn't really much help since I'm the person you'd normally go see. Anyway on to the issue.
A while ago I came across a phone that the owner didn't want anymore, and lo and behold it turns out the reason for that was a soft brick (I can't think of what else to call it.) I'll boot the phone, it loads up to the splash screen, and at different points will just flash grey and stop loading, then after a while of being left alone try and boot up again and then freeze up. I've pretty much exhausted the range of my knowledge (Owned samsung all my life, my rooting journey has been pretty much strictly that), so I come to you guys. Below I'll list what I've tried and my specs, hopefully I don't have a paperweight with a kickstand on my hands.
Things I've tried:
RUU's out the ass, had trouble getting them to even connect to the phone (triggered it at certain points during the boot til I found the sweet spot), and when it did its thing, simply gave me Error 132 (Signature Verification failed), which apparently is fixed with s-off. Leading me to...
Revolutionary. This I did really not expecting it to work, since the last time I've used this for someone else I had to enable USB debugging and everything, meaning I need to boot into the OS. No dice here.
ADB push I'm pretty new to this particular bit, so I tried to push a custom recovery onto the device, which failed due to S-ON. (At my wits end at this point, figured, "what the **** maybe I'll get lucky.")
Specs:
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.10.0001
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
And the date and time, which is incorrect so here
Oct 15 2010, 12:07:00
I don't think I need to point out yes, I've tried hard resetting and all the basic BS most normal users are surprised to find out they can do themselves. I'm fresh out of ideas, so before I begin the painstaking process of using other peoples solutions to other problems and hoping it works for mine, I've come for some direct advice/help. I think ADB might be my best bet at this point, but I have no real idea how, and after 7 hours reading through other peoples' stuff, you can imagine I'd rather just be told if it is or isn't going to work.
tl;dr, bricked evo, pls help.

Since ur the techy guy take a old evo that might have been smashed or something but the mother board still works swap the mother board and ur good to go I guess bcuz the other evo is now just trash
Sent from my PC36100 using xda premium

lreyes15 said:
Since ur the techy guy take a old evo that might have been smashed or something but the mother board still works swap the mother board and ur good to go I guess bcuz the other evo is now just trash
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Easier said than done; phones i send in have to match the ESN on the sticker as well as on the board, so no luck with that. ALso bump.

Have you tried unlocking it with unrEVOked?
EDIT: Well that won't work if you can't get the phone to boot up. Will the phone stay on in Bootloader or Fastboot modes? You cam flash an RUU while in Fastboot. If it stays on, either that or a PC36IMG.zip might work.

Captain_Throwback said:
Have you tried unlocking it with unrEVOked?
EDIT: Well that won't work if you can't get the phone to boot up. Will the phone stay on in Bootloader or Fastboot modes? You cam flash an RUU while in Fastboot. If it stays on, either that or a PC36IMG.zip might work.
Click to expand...
Click to collapse
It'll stay on in either of those two modes. I've tried a PC36IMG as well as the RUU for the phone's Radio, and neither works. I get error 132 for the RUU and PC36IMG doesn't get detected, unless I'm doing something wrong. It's in the root of the SD card and when I boot into the bootloader it tells me nothing's there on that initial check.

psych0r3bel said:
It'll stay on in either of those two modes. I've tried a PC36IMG as well as the RUU for the phone's Radio, and neither works. I get error 132 for the RUU and PC36IMG doesn't get detected, unless I'm doing something wrong. It's in the root of the SD card and when I boot into the bootloader it tells me nothing's there on that initial check.
Click to expand...
Click to collapse
Try a newer PC36IMG, like the one from the 4.54.651.1 ROM.

Bricked While Flashing To Metro

I bricked my evo 4g while attempting to flash to metro (on my own, couldnt find a exact guide). I had written a metro prl, donor flashed, and I was changing the NAM settings. All this went fine and then I was attempting to write the NVRAM file from whiterabbit site exactly as it told me. It wrote successfully but when I turned on my phone it was bricked.
I can access boot loader but it wont load into recovery. I get the white htc screen over and over again when I normally turn it on or when I attempt to access recovery.
Any help would be appreciated Im super frustrated .
Here are my bootloader specs
Unlocked
supersonic evt2-3 ship S-ON
HBOOT-2.16.0001
MICROP-041F
TOUCH PANEL-ATMEL224_16ab

tenfour1 said:
I bricked my evo 4g while attempting to flash to metro (on my own, couldnt find a exact guide). I had written a metro prl, donor flashed, and I was changing the NAM settings. All this went fine and then I was attempting to write the NVRAM file from whiterabbit site exactly as it told me. It wrote successfully but when I turned on my phone it was bricked.
I can access boot loader but it wont load into recovery. I get the white htc screen over and over again when I normally turn it on or when I attempt to access recovery.
Any help would be appreciated Im super frustrated .
Here are my bootloader specs
Unlocked
supersonic evt2-3 ship S-ON
HBOOT-2.16.0001
MICROP-041F
TOUCH PANEL-ATMEL224_16ab
Click to expand...
Click to collapse
Lol duude calm yooouur nips duude...
Now on to your thing......first your not hard brick which is good and look up how to unroot EVO 4G and reroot it where its HBOOT 2.16 S=OFF then try your method of going to metro or somthing lol
Sent from my PC36100 using xda premium

You can try and take your SD card out of the phone stick it on your computer and download a recovery place it on your of the SD card rename it to PC36IMG.zip ,place the card back on the phone and go to your bootloader and see if it finds the update
Sent from my PC36100 using xda app-developers app

Will unrooting unbrick my phone? And i have a recovery I just cant reach it because when i press recovery it boots to the white screen again. I tryed reflashing my recovery and same thing keeps happening.

A little update at where Im stuck. I reflashed my recovery in hope that it will work but nothing and now it will not let me flash using Cmd prompt anymore. I cannot flash using cmd because it says waiting for device. Putting roms or recoverys in my sd card and renaming as PC36IMG comes out the same, it stops at Parsing zip and never moves forward. I cannot reach recovery because when I click it I just get the white splash screen again.
Apparently my messed up NV items are not as simple to fix as other bricks. There was a solution posted here by cutthroat but the file is no longer downloadable. Here is the link.
http://forum.xda-developers.com/show...6&postcount=54
Any further help on how to fix my NV files or stop this bootloop/brick would be appreciated. Thanks

Well I looked through all those old links and trying to get those files now looks *really* hard.
You could try what someone did in this post:
http://forum.xda-developers.com/showpost.php?p=31931866&postcount=49
And hope that it works.
Maybe afterwards flash a stock rom like nitrous rom and ##3282# reset and ##786# reset
**edit**
This one looks interesting too:
http://forum.xda-developers.com/showthread.php?t=1885208
If you could actually manage to find the nv.img file that would restore your evo, all you need to do is load the engineering hboot aka eng hboot,
then "fastboot flash nv nv.img" ( Without the quotes )
**edit #2**
Supposedly you can get a nv.img file from a PC36IMG.ZIP file, ruu maybe?
Anyways, this thread looks helpful too:
http://cdmagurus.com/archive/index.php/t-4567.html

Thanks for the advice. I'll look into these. I gave up for a few weeks cause Ive gotten too busy lately but hopefully it will be fixed soon

tenfour1 said:
Thanks for the advice. I'll look into these. I gave up for a few weeks cause Ive gotten too busy lately but hopefully it will be fixed soon
Click to expand...
Click to collapse
No problem. I actually had to fix a friend's evo a week ago that had this same problem. It already had S-OFF so I found an eng hboot that was inside a PC36IMG.zip file
After it had flashed, I put it back in bootloader and executed the fastboot command in my post above with the nv.img file you can find by searching google for "mik mik evo radio"
You want the one that says: Baseband 2.15.00.12.19, PRI 2.33_003, WiMax 27243 & NV 2.15_003
After I flashed the nvitems, it worked fine afterwards. Reflashed back to the carrier and all was well.

So Ive tryed a few things and Im stumped. I tryed to fastboot flash my nv.img and it never works. I tryed to put an original signed ruu into my sd card and it never flashes. I looked at trying to s-off but i cant seem to find a guide where I can do it with a bricked phone. Dont really know what to try next.

[Q] Stuck in a loop please help

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?