I just recently tried to flash the Rom DeFroST using the Clockworkmod.
I can now not boot into the Rom (I get a looping splash, the cool colourfull nexus one X animation) and if I try boot into clockworkmod, it stalls at the Telstra splash (still image). I also cannot browse any files on the SD card, I have to remove it and insert it into the adpater.
I'm really afraid I've bricked it :/ Can someone help me? I can still get into HBOOT.
a1m said:
I just recently tried to flash the Rom DeFroST using the Clockworkmod.
I can now not boot into the Rom (I get a looping splash, the cool colourfull nexus one X animation) and if I try boot into clockworkmod, it stalls at the Telstra splash (still image). I also cannot browse any files on the SD card, I have to remove it and insert it into the adpater.
I'm really afraid I've bricked it :/ Can someone help me? I can still get into HBOOT.
Click to expand...
Click to collapse
your phone is not bricked.
did you root your phone first?
I have a Telstra phone and I had to flash an official WWE ROM first, then use gold card to root my phone and now I can flash any ROM.
My phone came unlocked, it was unlocked by the company from whom I ordered it from. Yes I did root it first. Atleast, I assume I did...
I used the linux version of rewvoked 3 and it completed with out errors. It has been trying to boot for approximately 13 minutes now and is still stuck on the animated nexus one splash...
It is now into its 21st minute, I somehow doubt it's going to boot
a1m said:
My phone came unlocked, it was unlocked by the company from whom I ordered it from. Yes I did root it first. Atleast, I assume I did...
I used the linux version of rewvoked 3 and it completed with out errors. It has been trying to boot for approximately 13 minutes now and is still stuck on the animated nexus one splash...
Click to expand...
Click to collapse
Unlocked and rooted are two different things. Is this your first flash of a custom ROM for the Desire?
Whenever you flash a ROM for the first time it does take a LONG time for it to process. I don't remember how long, can't tell you if 15 min is to long. You can always re-flash by putting the phone into recovery mode manually and using the USB method for flashing.
Yes this is my first ROM.
That's the problem, the phone stalls if I try and put the phone into recovery mode... :/ Unless that too is meant to take a very long time?
Ok, surely 1/2 an hour is beyond what it should take?
a1m said:
Ok, surely 1/2 an hour is beyond what it should take?
Click to expand...
Click to collapse
you need to start over.
did you read ALL of this before you started (not trying to insult you in anyway, just question) http://forum.xda-developers.com/showthread.php?t=696189
it will tell you how to put is into recovery mode and then how to flash using USB
Yes I did, although I did end up following separate guides as my boot loader was 0.83 as opposed to 0.8 and 0.75 or whatever those guides included. Ok, start over. Sounds good... I'll try that, but you'll likely hear back from me!
a1m said:
Yes I did, although I did end up following separate guides as my boot loader was 0.83 as opposed to 0.8 and 0.75 or whatever those guides included. Ok, start over. Sounds good... I'll try that, but you'll likely hear back from me!
Click to expand...
Click to collapse
My boot is .80, I am not sure if it changed when I flashed an official ROM first. I did that to get rid of all the Telstra stuff.
One thing you can try is to flash an official WWE ROM first. Then after you can go onto a custom ROM.
Ok, clockwork mod is working again, now to install thisWWE ROM, what exactly is it, where can I get it and what should I do?
Double post sorry
a1m said:
Ok, clockwork mod is working again, now to install thisWWE ROM, what exactly is it, where can I get it and what should I do?
Click to expand...
Click to collapse
here is the link to official ROM for the HTC Desire http://forum.xda-developers.com/showthread.php?t=695667
They may have a radio in them as well. Once you flash one make sure your desire works. Then try flashing your custom ROM. Many custom ROM's need to have the latest radio so make sure you follow the instruction for that ROM and the radio that ROM uses.
alwayslearning said:
here is the link to official ROM for the HTC Desire http://forum.xda-developers.com/showthread.php?t=695667
They may have a radio in them as well. Once you flash one make sure your desire works. Then try flashing your custom ROM. Many custom ROM's need to have the latest radio so make sure you follow the instruction for that ROM and the radio that ROM uses.
Click to expand...
Click to collapse
one more thing, once you get an official ROM working, go to market and download ROM manager, use it to flash a custom ROM, it might work better for you.
Ok thankyou! But to me a radio is a small transistor based device that uses variable capacitance in order to change frequencies... What is it in this case?
By the way, I thank you for your help, you've been of great assistance!
EDIT: One more thing, that's a lot of roms, which one do I want? Any? do I want signed or unsigned?
Ok I'm even more confused, they're mostly .exe's, how do I use them?
EDIT: It also says they're not rooted, does that mean I have to re-root my phone again?
Having the exact same problem as you, also a telstra phone.
Boots and gets stuck on the "X" colored animation.
If you get it going, please post here what you did
a1m said:
Ok I'm even more confused, they're mostly .exe's, how do I use them?
EDIT: It also says they're not rooted, does that mean I have to re-root my phone again?
Click to expand...
Click to collapse
A radio is the software that works your phone, GPS and wifi portions of the device.
use the first ROM on the list. Hold the volume down key and press the power key at the same time, hold them until you enter the recover screen. it will take about 30 sec to process, use the volume down key to select clear storage follow the instructions and this should set your phone back to factory setting (using the last ROM that worked on your phone). Your phone should be working and you should be able to boot-up.
From this point you will be able to connect your phone to your PC then click on the ROM (exe file) and follow the instructions to flash the official ROM
let me know what happens.
Ok so i need a windows PC? I'm on Ubuntu.
My Windows decided to implode after an update earlier this evening. Will probably leave that to download and go to bed. I'll post here tomorrow with how I get on tomorrow morning!
Related
Hello,
I was trying to flash a new Rom onto my phone (Superfly) and installed the .zip file from clockwork, however, when I try to boot the phone, it sticks at the Mytouch slide screen.
I cant load into the card nor the phone.
Is there any way to reverse this?
Thanks in advance!
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
sandpaperback said:
Hopefully you made a backup. You should still be able to boot into recovery and restore your backup or even flash a new rom.
Click to expand...
Click to collapse
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
dion20 said:
The problem the OP and myself are having is that we cant load Clockwork recovery, and I think its cause when we flashed the new rom, it did away with USB debugging mode, and now we cant get back into the OS to select it again. I too am stuck in this loop, and I might just have to bite the bullet and bring it in to tmo and tell em it just stopped working for no reason...
Click to expand...
Click to collapse
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
wipe everything on the phone, find the thread that walks you through that
cursexcore said:
I did do a nandroid backup, but the phone magically can not find it now. And It took forever to get to work, but I was finally able to get back into clockwork and tried to install another a different rom (Kanged CM6 ROM) but ended with the same results of sticking on the mytouch slide startup screen. Frustrating, because it probably took about 3 hours to get back into clockwork!
Any other suggestions???
Click to expand...
Click to collapse
As was noted previously, if you haven't flashed the ESPRIMG rom, you're basically looking at re-rooting your phone every time you want to install a different rom. This means going through the whole process again and again and again.
falken98 said:
The USB debugging option means nothing while booted in to recovery. If you haven't flashed the engineering rom before you will need to redo the loop/ota.zip/update.zip spoof to get back in to clockwork.
Click to expand...
Click to collapse
thats weird, cause before I could get into clockwork after 2 tries max, not I tried repeatedly for 10 mins and it didnt work, so I should just keep tryin to get into clock work then?
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
sandpaperback said:
Yes, keep trying. And when you do, please flash the engineering rom and keep the proper update.zip on your card! It will save you a lot of trouble in the long run.
Click to expand...
Click to collapse
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Now I know theres something that makes it so I dont have to go thru the pain of rooting to get into clockwork I'm def gna use it..
what method should I use? Ive been doing the following and no luck so far
1 - cd to android sdk tools folder
2 - vol down + power for recovery
3 - highlight recovery
4 - run loop in cmd
5 - plug usb into phone
6 - plug usb into pc, and before it changes to HBOOT from USB i hit power to select recovery
7 - adb devices sees it as an offline device for a few cycles, then it disappears.
after step 7 I've tried running update.zip
unplugging and plugging back in
ctrl+c to stop the script when its offline
unplug when its noticed as an offline device
whats the best way to get into it now?
======
EDIT - finally got it into recovery, i loaded up htc's recover with it plugged it to the pc so it loaded up HBOOT from USB
normally your are not bricked if:
1. you can boot into recovery
2. you can not boot into recovery yet you can boot into bootloader [HOLD (power + volume down) to boot]
Don't worry I got a black/blank screen of death the other day for flashing the wrong boot.img fortunately I was able to boot into bootloader and start from scratch using the ESPRIMG.zip
dion20 said:
will do, theres alot of assumptions around here tho, and newbs to android are kinda expected to know things without them being stated in the threads..
Click to expand...
Click to collapse
I agree to an extent, but if you take the time to read through things thoroughly (as in every post in the How To Root or Engineering Build or even Rom Bible thread), you'll be okay. This is my first Android device as well. I put off rooting for a solid couple of weeks while I read through everything I could. I was completely paranoid about bricking my phone. Eventually, I went for it. Even then I had a couple hiccups along the way (including have to re-root two more times), but all the information is here.
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
cursexcore said:
[blah blah blah....] My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
My question: did u search here?
http://forum.xda-developers.com/forumdisplay.php?f=660
And found items about the champion build and this little file named ESPRIMG.zip?
U can also check out the ROM BIBLE stickie post.
u can try this:
http://forum.xda-developers.com/showthread.php?t=713507
or you can try this:
http://forum.xda-developers.com/showthread.php?t=713507
now if you really searched you would of found your own question:
http://forum.xda-developers.com/showthread.php?t=744709&highlight=unroot
cursexcore said:
So an update:
I went to a Tmobile retail store to see if I could do a direct swap and am having a new phone sent out to me. I will definately take all the replies into consideration when starting the root process on my new one! My final question is, since I am afraid Tmobile will not find my phone valid to be replaced under warranty due to it being rooted, is there any way to unroot and go back to stock? I have googled it, but cannot find anything specific for the slide...
Thanks!
Click to expand...
Click to collapse
I had the same problem you did, and fixed my phone, so its possible. refer to my post on the first page and then refer to this post and use the mirror that Wes himself posted.
http://forum.xda-developers.com/showpost.php?p=7001053&postcount=7
Hi everyone,
I can't post in the developers section cos I'm a new user so I hope you guys can point me in the right direction.
Okay to give you a brief summary:
My phone was rooted by using the latest Unrevoked 3.32
Then I did a NADROID Backup of my files.
Then I took S-Off With AlphaRev 1.8 Custom HBOOT.
Everything was successful and it said S-OFF.
Now when I boot up my phone normally all I get is the "Why So Serious?" image by unrevoked.
I restored my backup but still get the same image.
I'm guessing it's to do with the HBOOT version and my Radio version?
Please check attached images.
You do have to change the splash if you want to, thats why the image is how it is because it has changed from the HTC one, to AlphaRev's. Your radio is so old, really old. Try and install a newer one (been tested) or the newest one (get the second radio). See if that does anything for you. Just let things load up, they can take a while to do.
Thanks for the reply.
The thing is, i don't mind the splash, it's kinda cool.
The problem is the fact it just hangs, just stays on the splash screen.
I'll try what you suggested, unless others have another suggestion?
If you wanted S-Off badly, you could just download the correct RUU and then freshly install the stock ROM. It would wipe everything and you would need to run Unrevoked and AlphaRev again. But nontheless, you would have S-Off. Or you could download the stock rooted ROM and then S-Off from that.
Just an update.
The problem has been solved thanks to GoogleJelly's steps in pm.
Why did you sort that out by pm?
Maybe there are other people experiencing the same problem and are interested in the solution too...
just sayin...
lol yeah true, let me ask his permission if I can post the pm
Okay here are the steps I got:
If your able to get into the recovery then you're ok. You can try to install a stock Froyo ROM if you like, pre-rooted. See how that turns out.
If not, then I guess all you can do is install the RUU. You need the correct on that represents your installed radio so you can update. It will reset everything and I mean everything so you will need to root and S-Off again. Hopefully that will of fixed everything. But I don't recommend restoring. I have had some weird stuff happen to me through restoring before but your welcome to try it again.
To Get Into Recovery
1) Turn off your phone
2) Hold down volume down and press the power button
3) Wait for it to check your SD Card then press vol down to highlight recovery and press power button to select it
4) Should take up to 30 seconds to boot into recovery
Whilst in the recovery, you're able to mount USB to transfer the pre-rooted stock ROM across and then you can install it that way.
I hope this helps you out. If you need anymore help, just ask.
Click to expand...
Click to collapse
thanks
10charrrrrrrrrrr
Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.
Hello,
I have for quite some time used leedroids rom lately the the hd port.
That rom has been a little bit unstable but no real big issue. Now however my
phone has gone totally bonkers.
I have leedroids http://forum.xda-developers.com/showthread.php?t=1038195 due to that i tried to solve the issue. Using the a2sd+ version. Tried the alignment patch etc and spend more or less the entire day studying the forum.
The issue is that the phone is highly unstable.
Most often the alpha rev joker image just keeps rebooting after the joker show up, or it just sit's there. If i pull the battery for a while like a few minutes the phone often boots up but after a while it reboots again. Faster if i open an app. Especially the market app then i get almost an instant reboot.
Did a full wipe ofcourse when installing the rom, did a checkdisk on the sdcard and got new partitions for it both primary of course etc.
I just cant seem to figure out what the error might be. Only thing i havent tried is to install the stock rom. Mainly because i'm not quite sure which one i should use. So if someone could please provide a link the the proper one i would be gratefull. Rooted and s-off one would be good. I'm on the 3 network in sweden but i think they use the standard rom.
no errors while installing
hboot 0.93
Anyone got any ideas?
Well you should start by flashing any other rom using a full wipe.
If that doesn't cut it, you should try to install a htc one. This can be easily done if you are s-off. You should install the latest alpharev hboot with stock partition-layout. Then you can flash a ruu thile staying s-off. Please write back for further help, if the first option didn't help you.
mortenmhp said:
Well you should start by flashing any other rom using a full wipe.
If that doesn't cut it, you should try to install a htc one. This can be easily done if you are s-off. You should install the latest alpharev hboot with stock partition-layout. Then you can flash a ruu thile staying s-off. Please write back for further help, if the first option didn't help you.
Click to expand...
Click to collapse
Is there a way to flash the latest alpharev without having the phone booted? In recovery for example? It's a bit dangerous i noticed cause if my phone crash in the middle of flashing that i would probably be bricked i think. But i'm already s-off though should i do it again to get the latest?
To put it simple yes there is a way to do it without being booted.(actually that is the only way you can't do while booted to the system)
And no you should not run the tool itself again. When you are already s-off you can just download a new hboot image from their website and flash it directly. Download:
http://alpharev.nl/bravo_alphaspl.img
And flash it by following my directions given here:
http://forum.xda-developers.com/showthread.php?t=1248910
You will need to have the sdk installed beforehand.
mortenmhp said:
To put it simple yes there is a way to do it without being booted.(actually that is the only way you can't do while booted to the system)
And no you should not run the tool itself again. When you are already s-off you can just download a new hboot image from their website and flash it directly. Download:
http://alpharev.nl/bravo_alphaspl.img
And flash it by following my directions given here:
http://forum.xda-developers.com/showthread.php?t=1248910
You will need to have the sdk installed beforehand.
Click to expand...
Click to collapse
doesn't seem to be able to connect it via adb. tried the zipfile thing too but it wouldn't allow to install the file using the recovery tool.
Also it seems to be able to boot if i pull the battery for a long time. But as soon as it seems to heat up a bit poof it goes into a reboot. Could there be something wrong with the battery so it get's to hot and reboots?
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
mortenmhp said:
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
Click to expand...
Click to collapse
Ok great thanks, trying cyanomod now to see if i get the same issues. But i put the phone in the fridge for a few minutes, then it booted just fine and i put set cpu to powersave and phone didnt get hot and no reboot. So gonna try cyano and see if the same happends. Will try full stock when i wake up tommorow. Thanks for the help
ok got reboot on cyano too
It seems to be the famous boot loop problem in HTC desire .
To confirm flash the original RUU, if the problem persist then your mainboard has developed fault.
Sent from Hell
Got it to work for a few hours this morning. Had it turned off and charged it to full during the night. Worked for some 2-3 hours and then reboot.
mortenmhp said:
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
Click to expand...
Click to collapse
Ok tried this now, had the battery charged over night also, when i tried to install it it says battery below 30% but he battery has full charge :S
Hi,
I have an HTC One M8 (AT&T) . I had 5.02 on it earlier today and wanted to upgrade it. I don't have service so can't use the ATT Updated. I unlocked the boot loader and loaded a boot.img. Now my phone turns on the the HTC and goes to the HTC screen. It does says that the image should not be distribute outside of HTC.
Any help in getting past this?
You didn't brick. You didn't install a ROM. You just installed the kernel when you flashed boot.img, which is like 1% of what it takes to have a working OS. A kernel is about 25 MB, where a Sense ROM is around 1.5 GB.
You're not the only person to make this mistake. But I'm at a loss to understand why folks think that a boot.img is the same as a ROM. They are 2 completely different (although related) things.
Flash the entire ROM. No need to flash boot.img seperately (it flashes with the ROM/system partition).
Also, the red text on the boot screen is perfectly normal, once you've installed a custom recovery (TWRP).
Any particular ROM you recommend? What you say makes sense, as to how I got there, I was following a set of steps.
redpoint73 said:
You didn't brick. You didn't install a ROM. You just installed the kernel when you flashed boot.img, which is like 1% of what it takes to have a working OS. A kernel is about 25 MB, where a Sense ROM is around 1.5 GB.
You're not the only person to make this mistake. But I'm at a loss to understand why folks think that a boot.img is the same as a ROM. They are 2 completely different (although related) things.
Flash the entire ROM. No need to flash boot.img seperately (it flashes with the ROM/system partition).
Also, the red text on the boot screen is perfectly normal, once you've installed a custom recovery (TWRP).
Click to expand...
Click to collapse
salevine said:
Any particular ROM you recommend? What you say makes sense, as to how I got there, I was following a set of steps.
Click to expand...
Click to collapse
Where did you get the boot.img, was it from a ROM?
What steps were you following? I know you can't link, due to not enough posts. But you can describe if its an XDA thread, describe the guide, ROM thread, or process in question. Just saying you were "following a set of steps" doesn't really tell us anything.
I actually managed to finally get it fixed. Just in case anyone else has the issue, here is what I had to do. I left it on until the battery completely died. Then I was able to finally get it on and into HBOOT. Since I had made the mistake of installing TWRP but not making a backup, I could not restore from a backup. I took the SD card out of my phone and downloaded venomROM and put it on my SD card. I then was able to get into HBOOT, Recover and install using TWRP and the ROM from the SD card. All is well now.
redpoint73 said:
Where did you get the boot.img, was it from a ROM?
What steps were you following? I know you can't link, due to not enough posts. But you can describe if its an XDA thread, describe the guide, ROM thread, or process in question. Just saying you were "following a set of steps" doesn't really tell us anything.
Click to expand...
Click to collapse
salevine said:
I actually managed to finally get it fixed. Just in case anyone else has the issue, here is what I had to do. I left it on until the battery completely died. .
Click to expand...
Click to collapse
No need to have done that (let the battery die) but I guess if it worked, power to you. I would have pointed out how to reboot, but got sidetracked when you asked for ROM recommendations, and referenced some guide, but not telling us what guide, which confused the conversation.
For future reference, next time, hold power+vol up to force a reboot (may need to hold a minute or so, in the case of stuck on HTC logo screen or similar condition). The moment the screen goes dark, slide your finger from vol up, to vol down (no need to keep holding power button at this point) and keep holding vol down until bootloader screen appears. If it doesn't, just repeat, as you got the timing wrong (either started pressing vol down to late, or let go of it too early).
Whatever guide you were following was wrong (or possibly for an older device) as you don't need to flash boot.img seperately, unless the intent is to install a custom kernel (different thing from flashing a ROM).