I think I managed to brick it :D - HTC Inspire 4G

I think I managed to brick my Inspire some how I tried using a nandroid backup to restore to an older ROM. Everything restored correctly apparently, but when I go to restart it, I just get stuck on the HTC white screen.
Tried reflashing a few different ROMs, but its still stuck on the HTC screen. How long is this screen supposed to take after a fresh flash?
Any other ideas?
EDIT: SOLUTION FOUND. DO NOT USE CWM 3.X!! More info here: http://forum.xda-developers.com/showthread.php?t=956367

What is the longest you waited?

JCreazy said:
What is the longest you waited?
Click to expand...
Click to collapse
30 min
I just flashed CM7 and it booted right up. I think it's a problem with CWM 3.x and Froyo ROMs. From what I've gathered, CWM 3.x is unstable with Froyo based ROMs.
Just flashed CWM 2.5.1.3, gonna see if I can get this damn thing to work

The new clockwork requires changes to the update scripts be implemented by the devs/modders.
http://forum.xda-developers.com/showthread.php?t=954654
Sent from my ADR6300 using XDA App

Related

New Rom=Long Reboot?

(Noob) Haven't ever tried installing new roms before and giving it a new shot using clockwork recovery mod.
My question is this, I've tried putting two new roms in and both cases, the phone reboots and seems to be stuck on the "htc incredible" with white background boot theme. It just hangs there, both time I waited about 10 minutes. Is this normal, should I wait longer, or just do a recovery and retry?
Thanks
What roms?
Sent from my Incredible using XDA App
jdkoreclipse said:
What roms?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
The sense red and sense froyo with apps aligned from Jonnybueno. I just did a recovery and it booted up back to normal, trying the cyanogen 6 build now
bjw1979 said:
The sense red and sense froyo with apps aligned from Jonnybueno. I just did a recovery and it booted up back to normal, trying the cyanogen 6 build now
Click to expand...
Click to collapse
Maybe try unrevoked3 again. If that doesnt work, unroot using the ruu and reroot and reflash with unrevoked3. Remember if you are um rooting, backup all data contacts and apps.
Sent from my Incredible using XDA App
Yes, a new ROM can take several minutes to boot the first time. As far as how long... I don't know that I have ever sucessfully waited more than 15 or 20 minutes for first boot.
Take preceding advice with a grain of salt, I have not flashed a new ROM on my Incredible yet, I only have ROM experience with my Magic.

CWM partially flashed/some glitches?

My brother got tired of all the bloatware on his G2x with 2.3.3 OTA, so I proceeded to try to flash a custom ROM. Did the process of NVFlash, but with some unexpected results:
1) As I'm lead to believe, I should see an orange "ANDROID" show up when holding volume down and power. But instead I get a green "ANDROID" with a bunch of Android icons like messaging.
2) When it gets past the screen I mentioned, it does go into CWM Recovery but as soon as I let go of a button to navigate, the phone shuts off. Sometimes it stays on if, while still holding down volume and power, I press volume up, release down, then release power. Even then, it sometimes still shuts off.
3) When trying to flash a rooted ROM (CyanogenMod 7.1, after doing a data wipe/factory reset), I get an error message and the installation aborts.
Was able to restore the 2.3.3. OTA because I had backed up, but any ideas?
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
mojorisin7178 said:
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Click to expand...
Click to collapse
Would you recommend I reflash CWM straight up, or the stock recovery through NVFlash before trying again? I'd assume I should follow all the same steps as if I was trying to flash CWM, but instead of clicking on CWM, click stock recovery instead.
jboxer said:
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
Click to expand...
Click to collapse
Positive. I downloaded the necessary files and followed all the steps from here:
http://forum.xda-developers.com/showthread.php?t=1056847
Again I am no expert but that sounds like a good idea i would say you it cant hurt. I think you will have to reflash cwm but you have to do that anyway so I would say it is the best way to start clean.
Got CWM Recovery to work. It still shows the green ANDROID with the icons, but I no longer have to struggle to keep it from shutting off. I was able to flash xboarder's tweaked Gingerbread ROM, but still unable to flash CyanogenMod 7.1. I did a factory/wipe data, wiped cache, and dalvik cache. Still get an error message upon trying to install.
when i first did the nvflash my phone was getting shut off when it got to the recovery and then i let go of the power button. Until i realized that you are supposed to let go of the power/volume button when the word android appears and all those icons u mentioned, yeah i get the same screen. i had no problems flashing 3 builds of cm7 and xboarder's rom 2 times.
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
The green android with the icons is just a different splash screen in the newer version of cwm.
lcambriz said:
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Could've been a bad download. Sometimes you just gotta download the file again and it'll flash no issues.
But I'd go for the latest CM7 nightly. They are leaps and bounds ahead of where they were with RC1.
I figured that might be the problem. Eaglesbood seems to be working really well for him, so I think he'll just stick with that. My bro is more of the "If it isn't broken, don't fix it" type, whereas I'm more inclined to try the latest. I'm tempted to try the nightlies myself on my Glacier, if they really are better than RC1.
Sent from my HTC Glacier using XDA Premium

[Q] stuck in recovery/clockwork mod what to do now?

I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
jonslaught said:
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
Click to expand...
Click to collapse
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Mr. Apocalypse said:
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Click to expand...
Click to collapse
I've wiped everything multiple times and flashed just the eg rom on its own and it still sends me back to recovery. x.x
i'm using g2x nullifier to see if after doing that, then flashing any rom will make it work.
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
I would a give a shot of this tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize all your partitions.
Sent from my LG-P999 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
ratza66 said:
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
Click to expand...
Click to collapse
was looking around for some tool like this and couldn't find it x.x
I used it and presto! my g2x is alive and kicking again, thanks alot man
And thanks to everyone else that bothered posting, really helps alot

GRRR! Tbolt won't boot with any roms I try to install

My wife's phone is rooted and has been running BAMF for a long time. Well, it's slow as nuts right now and she asked me to redo it. I've been using Jellyblur on my phone, she liked it, and asked that i install that. Well, i can't for the life of me get the phone to boot with a new rom. Multiple downloads, and even downloaded about 3 different roms and it won't get past the white HTC screen.
I can reload my backup I made and it will start up just fine, but it just DOES NOT want to boot with a new rom.
I'm doing full wipes and I even copied the file I installed on my phone to her phone and tried installing that. No go.
Any ideas?
Thanks!
damon
SubliminalME said:
My wife's phone is rooted and has been running BAMF for a long time. Well, it's slow as nuts right now and she asked me to redo it. I've been using Jellyblur on my phone, she liked it, and asked that i install that. Well, i can't for the life of me get the phone to boot with a new rom. Multiple downloads, and even downloaded about 3 different roms and it won't get past the white HTC screen.
I can reload my backup I made and it will start up just fine, but it just DOES NOT want to boot with a new rom.
I'm doing full wipes and I even copied the file I installed on my phone to her phone and tried installing that. No go.
Any ideas?
Thanks!
damon
Click to expand...
Click to collapse
You likely need to update the Recovery.
I'm guessing it has some older form of Clockwork Mod Recovery on it.
You should update to 4ext.
That link is the app that you use as an interface for while in Android OS and it also installs the Recovery.
Install it while in Bamf, load the app and install recovery for HTC Thunderbolt.
Then try updating the rom, good luck!
If you end up liking it, support the dev and buy the full version of the controller app.
The recovery is free and so is the app I linked you however...
Recovery was indeed out of date. Thanks a million ..wouldn't have thought of that!
Sent from my Nexus 7 using Tapatalk 2
SubliminalME said:
Recovery was indeed out of date. Thanks a million ..wouldn't have thought of that!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No problem.
Glad you got it resolved.

odd black screen after every boot/reboot ?

i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !

Categories

Resources