Related
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.
Hi, I'm a complete noob here, so forgive me for my "stupidity".
Okay, so I downgraded my DHD from 2.37.707.3 to 1.32.405.3 by making a goldcard and then flashing it. After rooting my DHD (Visionary), I proceeded to S-OFF it. After playing around, flashing some ROMs (CWM), I decided to change my radio. I went to look for a ROM, then I downloaded its recommended radio. After getting ENG S-OFF, I went to flash my radio, then went to flash my ROM after wiping my data, dalvik cache, etc... But now, I am experiencing a horrible signal, and most of the time, the phone says: "Limited Service Emergency Calls Only". When I try searching for networks, I get:"The SIM card does not allow a connection to this network", even though this IS my home network! I am at my wit's end. I have tried many methods. I tried re-flashing the radio, switching back to S-ON, changing back to Stock CID and Stock ROM, and also simple stuff such as rebooting, factory reset, etc. I know it has nothing wrong with my SIM because it works with my other phones. I've tried searching online, but to no avail. My phone is not tied to any carrier.
Any ideas? Any help will be appreciated!
nicholas98k said:
Hi, I'm a complete noob here, so forgive me for my "stupidity".
Okay, so I downgraded my DHD from 2.37.707.3 to 1.32.405.3 by making a goldcard and then flashing it. After rooting my DHD (Visionary), I proceeded to S-OFF it. After playing around, flashing some ROMs (CWM), I decided to change my radio. I went to look for a ROM, then I downloaded its recommended radio. After getting ENG S-OFF, I went to flash my radio, then went to flash my ROM after wiping my data, dalvik cache, etc... But now, I am experiencing a horrible signal, and most of the time, the phone says: "Limited Service Emergency Calls Only". When I try searching for networks, I get:"The SIM card does not allow a connection to this network", even though this IS my home network! I am at my wit's end. I have tried many methods. I tried re-flashing the radio, switching back to S-ON, changing back to Stock CID and Stock ROM, and also simple stuff such as rebooting, factory reset, etc. I know it has nothing wrong with my SIM because it works with my other phones. I've tried searching online, but to no avail. My phone is not tied to any carrier.
Any ideas? Any help will be appreciated!
Click to expand...
Click to collapse
i see that you get ENG s-OFF, but did you get RADIO S-OFF (there are diffrent things) , before you get ENG s-OFF?????
http://forum.xda-developers.com/showthread.php?t=857537
the coreect steps are
Downgrade and permanent root
Radio S-off
eng S-Off
flsah recovery and ROM
yeah well, I did that. it worked initially, but after flashing radio, then it stopped working.
nicholas98k said:
yeah well, I did that. it worked initially, but after flashing radio, then it stopped working.
Click to expand...
Click to collapse
It's not obvious from your OP, have you tried to reflash your original radio?
ghostofcain said:
It's not obvious from your OP, have you tried to reflash your original radio?
Click to expand...
Click to collapse
yup, I've tried reflashing to original radio multiple times
nicholas98k said:
yup, I've tried reflashing to original radio multiple times
Click to expand...
Click to collapse
still you didnt answer ,...DID YOU HAVE RADIO S-OFF or only ENG S-OFF
second did the flashing process worked as it supposed to....
when you look in settings about phone,...do you see he new radio there ???
if you do have all these
and still doesn't works ..redo the DOWNGRADE process again with all the correct steps
Saluco said:
still you didnt answer ,...DID YOU HAVE RADIO S-OFF or only ENG S-OFF
second did the flashing process worked as it supposed to....
when you look in settings about phone,...do you see he new radio there ???
if you do have all these
and still doesn't works ..redo the DOWNGRADE process again with all the correct steps
Click to expand...
Click to collapse
I have both radio and eng s-off. okay i'll go try to reflash the radio and redo the downgrade and see how it goes
nicholas98k said:
I have both radio and eng s-off. okay i'll go try to reflash the radio and redo the downgrade and see how it goes
Click to expand...
Click to collapse
waitin for feed back
give a PM if works well
good luck
Re: Desire HD No Signal after flash
okay, so I tried to revert to stock rom (revert the CID, change S-OFF to S-ON, etc) so after I started up my phone, there seemed to be a signal, but it slowly died away and now I'm stuck with the same problem.
Now, my phone info is:
Android ver: 2.3.3
Sense: 2.1
Baseband: 12.54.60.25U_26.09.04.11_M2
Kernel: 2.6.35.10-g3bf3222 [email protected]#1 Mon Apr 11 22:46:37 CST 2011
Build number: 2.37.707.3 CL56018 release-keys
Software number: 2.37.707.3
CID: HTC_044
I radio S-ON and reverted my CID to my default one (HTC_044) before updating using RUU: RUU_Ace_Gingerbread_S_hTC_Asia_WWE_2.37.707.3_Radio_12.54.60.25_26.09.04.11_M2_release_188759_signed
did I do it correctly? before I started rooting and downgrading etc, my software version was 2.37.707.3, so that was why I changed back to this software. Am I doing this correctly?
the phone can suddenly get a signal, but after a while, it soon dies.
Well i've been working for the past 9 hours trying ever possible thing i could find trying to fix my issue without any progress. How do i get back to stock so i can start over?!
Supersonic EVT1 ENG s-off
hboot-2.10.0001 (pc36*****)
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.05.02
mar 30 2010, 11:24:04
I was rooted with unrevoked after reverting back from the newest OTA using a guide from the XDA forums. everything was working wonderfully but my dumbass had to try and downgrade to an ancient ENG Hboot. using thefredelement's guide to get back to ENG .76. NOT NOTICING i shouldn't try it with HW version 003/004. unfortunately my phone is HW 003. idk what i need to do to get this fixed or if i bricked my phone. I've got a warranty still so i can always just report it lost pay the 50 and restore from my backup sd card.
anyways, my computer is able to see my phone with fastboot but not adb. i get errors when trying to flash new recoveries or anything but radios (such as fail PU, image update error, data length too large, etc) Trying to do anything with adb shell just says "device not found" (yes, i have the correct drivers installed) I CANNOT get into recovery (i had CWM 5.0.2.2) it just reboots back to hboot or the screen with the three droids skateboarding when i try. sorry ahead of time if this is posted in the wrong section/i just killed some brain cells with my stupidity and lack of experience. thanks in advance for any help and advice i can get! (sorry for the double post, idk how to delete postings)
Xexus said:
Well i've been working for the past 9 hours trying ever possible thing i could find trying to fix my issue without any progress. How do i get back to stock so i can start over?!
Supersonic EVT1 ENG s-off
hboot-2.10.0001 (pc36*****)
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.05.02
mar 30 2010, 11:24:04
I was rooted with unrevoked after reverting back from the newest OTA using a guide from the XDA forums. everything was working wonderfully but my dumbass had to try and downgrade to an ancient ENG Hboot. using thefredelement's guide to get back to ENG .76. NOT NOTICING i shouldn't try it with HW version 003/004. unfortunately my phone is HW 003. idk what i need to do to get this fixed or if i bricked my phone. I've got a warranty still so i can always just report it lost pay the 50 and restore from my backup sd card.
anyways, my computer is able to see my phone with fastboot but not adb. i get errors when trying to flash new recoveries or anything but radios (such as fail PU, image update error, data length too large, etc) Trying to do anything with adb shell just says "device not found" (yes, i have the correct drivers installed) I CANNOT get into recovery (i had CWM 5.0.2.2) it just reboots back to hboot or the screen with the three droids skateboarding when i try. sorry ahead of time if this is posted in the wrong section/i just killed some brain cells with my stupidity and lack of experience. thanks in advance for any help and advice i can get! (sorry for the double post, idk how to delete postings)
Click to expand...
Click to collapse
Remain calm. Let's see if we can get you fully functional.
First, let's upgrade that HBOOT. That by itself might fix you up, if it'll flash through the bootloader. Try the PC36IMG.zip attached to this post. It's for HBOOT 2.15.
If it flashes successfully, it should reboot the bootloader for you. If it doesn't, choose the fastboot option that does, and when it comes back up, try getting into recovery. If you can get into recovery, the next thing you should do is retire CWM and flash RA-supersonic.
thx capt. I actually just filed a clain through asurion, and for my $100 deductible i've getting a brand new evo3d xD so jumping the gun for the replacement actually worked out for me this time!
Xexus said:
thx capt. I actually just filed a clain through asurion, and for my $100 deductible i've getting a brand new evo3d xD so jumping the gun for the replacement actually worked out for me this time!
Click to expand...
Click to collapse
A shame to send back a perfectly fine OG . But I'm glad it worked out for you. Personally I like the challenge of trying to rescue a soft-bricked device. But I guess we'll never know if it was possible, now . . .
i would have loved to have found out myself. but being on probation and in the process of finding a job I just didnt have the time to mess with it i've still got it so once i get some time i'm going to attempt to unbrick it still. although its useless now that it's been deactivated lol
Yet another bootloop thread. So I had HTC stock rom for 2 years and last saturday I rooted the phone and installed cyanogenmod 7.2.0 (all instructions from CM forums). It worked fine for 3 days until I enabled wifi. Wifi didin't connect ("network disabled") so I rebooted. After typing in the pin code the phone reboots. From this on the phone reboots after about 10-30 secs after booting cyanogen.
I got the wifi to disabled again but no use. I got logcat and dmesg dumps but there wasn't anything that points out (at least not to me).
Things I tried:
- I have checked that currently the wifi is disabled
- Factory reset in clockworkmod (didn't work)
- Re-flashing the cyanogen 7.2.0 stable (worked for about 30 minutes, then rebooted by itself) without any additional software installed (except google apps, of course)
- re-flashing the downgraded firmware from CM forums via hboot -> no reboot!
Versions:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
It says SHIP, shouldn't I have ENG as I installed the engineering hboot as in the CM forum instructions? I would like to use CM so what should I try next?
Also, should I update the radio? The thread at developer section has lots of radios but mine is (about phone) 12.28b.60.140eU_26.03.02.18_M3. All the radios in the thread are "e" but no "U". So just to make sure that I don't brick my phone, are those "e" radios ok?
I cannot post links so I can't link the CM forum instructions.
When downgrading again you lost your engineering SPL, just reflash it with fastboot
http://forum.xda-developers.com/showthread.php?p=27796375
As far as the radio goes its hard to say what is best, different for anyone but theoretically all should work to some degree, I would suggest to try one of the newer ones as it may be the cause to one of your issues
Sent from my Nexus 7 using xda premium
Hmm I tried to re-do the cyanogenmod wiki downgrade & root but after running
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
I get lots of errors "An error occurred while running the exploit (-1) (errno: 25)". Didin't flash the hboot yet with fastboot. Maybe I should try that next.
Actually that won't work as you don't have many fastboot commands available to you with current SPL, you'll need to flash via bootloader, go to the thread I linked and at the bottom of the op there is a link to a couple pc10img.zips I made, read instructions and flash one of those
Sent from my Nexus 7 using xda premium
demkantor said:
Actually that won't work as you don't have many fastboot commands available to you with current SPL, you'll need to flash via bootloader, go to the thread I linked and at the bottom of the op there is a link to a couple pc10img.zips I made, read instructions and flash one of those
Click to expand...
Click to collapse
OK, I downloaded DZ_PC10IMG.zip from dropbox. I see there's a radio.img in the zip. What version is it and/or should I use it (is it a "e" radio)? If not, any special instructions on how to remove it and repackage the zip? Oh and thanks for your help.
Just flash the whole pc10img.zip as is, don't remove for now as changing radio might also help you and kits easy to switch back as needed, follow directions in that post or read the readme.txt from the drop box link
Sent from my Nexus 7 using xda premium
thdaie mills
I've flashed the DZ_PC10IMG.zip and now I have VISION PVT ENG S-OFF and 4ext recovery touch. Radio is 12.62.60.27U_26.13.04.19_M. I've lost the "e" in radio version. I've heard that it needs to be "e" for Europe(?). Time for radio update? The stock android boots fine.
Try phone as is, if everything works well then leave of be, if you feel your old radio was better than use fastboot to flash it back
Sent from my Nexus 7 using xda premium
Well the stock android is the downgraded firmware from cyanogen wiki. It's useless, language is only english thai or singapore etc. I could use a stock android, just had to find out where to get one. Or try cyanogen again with the new radio. Any special instructions to flash via the 4ext?
Edit: Hmm virtuous ROM could be nice if I wanted a stock rom.
So at this point everything is working as it should? Just looking to change radios? Or just looking for a ROM that's stock and has your language?
Sent from my Nexus 7 using xda premium
With the downgraded stock rom I get full bars on cell reception but nothing on 3g, i.e. doesn't connect to the internet. I have no wifi at the moment to test it.
Edit. In the settings it says "mobile network, connection failed"
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?