Hi,
I had a rooted s-off Sensation that was previously running CM7 alpha build and a couple of days ago was upgraded to Virtuous Quattro alpha 3.
I had all the correct firmware installed from RUU 3.24.401.1, and Quattro was running without any major problems.
I was playing with settings for SMS go pro, and the phone froze. I gave it a couple minutes to defrost, but nothing took. So I removed the battery and restarted the phone.
It vibrated and I awaited the HTC white splash screen but nothing, it kept the lights off but it would vibrate every 20 -30 seconds like it was booting up.
I let it run for 30 min thinking it would fix something. I took the battery out, took the sim card and sd card out. I charged it from the wall, from a computer, booted with a computer that has Android SDK on it.... nothing.
T-mobile is sending me a new one. But I just want to figure out what happened.
Any insight?
turn it on and let it just sit for 20 minutes. ive seen an inspire 4g do this
EDIT: didnt read OP's full thread. My bad
Don't know when you updated your firmware since the new way doesn't require SuperCID that should not be the problem.. But was wondering have you tried to return to recovery and flash CM7 again?
I don't have access to recovery. The phone loops in the boot cycle before hboot is initialized
Related
Hey everyone I am having some trouble with my friends HD2.
He installed HSPL3 with 2.08.hspl
Then Magldr 1.10
Then installed android 2.2 ROM
Everything worked fine, made phone calls, texts, all that except 3g didn't work but I am assuming that was because he didn't install a radio?
Now, heres where I am stuck.
He told me he used the phone for awhile without 3g.
Yesterday he turned off the phone before school and turned it on after school.
-The phone started to fail to boot up in multiple ways
-It sat at the stick together screen
-Got to MAGLDR 123456 go go go (would get stuck there sometimes)
-Got fully booted up and would search for a signal and freeze
-Or it would fully boot up and work normally until he had to restart it again
Now he told me this is what he did when he got home from school
-He opened magldr and did a usb flash
-opened bootloader and tried to reinstall android
-got two errors
-could no longer boot passed Magldr
I recommended he switched back to a shipped ROM from t-mobile it was the (3.14 update)
He told me he tried it, got to 8% and failed, and now he gets an error along the lines of:
-software update failed please try again
He gets that whenever the phone started up.
Now I said oh lord that sucks, now I have the phone.
-The phone is still on 2.08 hspl
-magldr 1.10 still installed
-Just did a USB flash
What do I do? I have tried looking at guides to install android but seeing as how there is no ROM on the phone anymore I can't do an SD install.
How do I tell if my phone is 512mb or 1024mb?
Is the phone bricked?
I currently have the Android 2.2 that my friend installed on the phone installed on this computer should I continue to use that?
Hey guys, I could really use some help right now. I think my Sensation just went into a boot loop. I've never had it happen to me before, but I was using the XDA app on my phone when all of a sudden the phone went to the CoreDroid boot animation. The animation plays for about 10 seconds, freezes, and then plays again, over and over. I've tried holding down the power button, which doesn't do anything, and I also tried to boot into recovery to no avail as well. I looked up how to to fix a boot loop on an Android phone but it seems like most sites say the first step is to boot the phone into recovery (and like I said, I can't do that). Do I have to pull the battery? I don't want to do that until someone says it's the right step to take because I'm worried that could seriously screw it up.
I'm on CoreDroid 2.4 and on faux's 0.1.2 1.56 GHz NoHz kernel btw. I could really use the help because I'm leaving tonight on a vacation.
OK, update, I ended up pulling the battery, putting it back in, booting into recovery, and rebooting the phone, and it actually worked! You can sure bet that I'm doing TB to back up all my apps/data right now and I might even do a nandroid even though I have a nandroid of CoreDroid 2.3 and a couple others. And boy is boot looping a battery hog! I had 98% right before it began, and after only like 10-15 minutes of boot looping it was at 66% lol (phone got extremely hot too).
Now I'm just curious if this happened because of the kernel or if it might be due to the beta battery monitor widget that I had just installed (I'm not sure if beta apps can cause problems).
Each phone and set up is different. Sounds like a kernel issue. I have read that if your phone reacts in the way described, you should just revert to stock kernel that can be found on coredroid's fixes post.
I have gotten bootloops with one of faux's kernels, I think it was the nohtz 1.7. Now on the JRCU 1.5 with coredroid 2.4.
If you are concerned with bootloops, besides the battery pull, which I personally like to avoid, I just plug it in the usb port and do a adb reboot recovery command from your cmd window. I recommend just reverting to the stock kernel for now until you are comfortable in troubleshooting away from a comp. And remember to always have a nandroid to revert to in case of any emergencies.
yesterday I downgraded and rooted my Inspire 4G using this guide
http://wiki.cyanogenmod.com/wiki/AT&T_Inspire_4G:_Firmware_Downgrade_(Gingerbread)
I followed the guide most thoroughly and it gave me no errors what so ever. But I guess somewhere after installing the PD98IMG.zip my phone started acting funny
I would restart it to flash a custom ROM (Revolution HD) but it would take forever to boot up.
First (after I click the Power Button) it waits for about 10-15 mins to actually turn on to the HTC Logo. After that another 10 mins stuck on HTC Logo and VIBRATING constantly the whole time. After the 10 mins of vibration it waits for about 4-5 mins before it shows the "quietly brilliant" and then it starts normal!! with everything ok (rooted with the latest ARHD ROM!!)
It's not that I'm gonna be restarting it on a daily basis or anything but you know how annoying it is to have such a problem... whenever I wanna flash a ROM tweek it takes me more than an hour.
Any suggestions on what I should do? (I flashed also the recommended radio.img for my ARHD as well - took me another 40 mins as well)
UPDATE: Another problem I just found out as well, the speakers (when I picked up a phone call) seem to be somewhat crackling! the voice isn't as clear as it used to be...
Reda88 said:
yesterday I downgraded and rooted my Inspire 4G using this guide
http://wiki.cyanogenmod.com/wiki/AT&T_Inspire_4G:_Firmware_Downgrade_(Gingerbread)
I followed the guide most thoroughly and it gave me no errors what so ever. But I guess somewhere after installing the PD98IMG.zip my phone started acting funny
I would restart it to flash a custom ROM (Revolution HD) but it would take forever to boot up.
First (after I click the Power Button) it waits for about 10-15 mins to actually turn on to the HTC Logo. After that another 10 mins stuck on HTC Logo and VIBRATING constantly the whole time. After the 10 mins of vibration it waits for about 4-5 mins before it shows the "quietly brilliant" and then it starts normal!! with everything ok (rooted with the latest ARHD ROM!!)
It's not that I'm gonna be restarting it on a daily basis or anything but you know how annoying it is to have such a problem... whenever I wanna flash a ROM tweek it takes me more than an hour.
Any suggestions on what I should do? (I flashed also the recommended radio.img for my ARHD as well - took me another 40 mins as well)
UPDATE: Another problem I just found out as well, the speakers (when I picked up a phone call) seem to be somewhat crackling! the voice isn't as clear as it used to be...
Click to expand...
Click to collapse
You have just messed your bootloader up. You did what you are not suppossed to. You have to fix the hboot in order to have a working phone again....
glevitan said:
You have just messed your bootloader up. You did what you are not suppossed to. You have to fix the hboot in order to have a working phone again....
Click to expand...
Click to collapse
I see that the OP's next question might be how to fix this..
http://forum.xda-developers.com/showthread.php?t=1342791
this thread, I believe is basically the same problem and that OP gave a pretty detailed step by step on how he fixed it.
that was helpfuly guys thx a lot. But it's not clear in the second post if only using the Advanced Ace Hack Kit is enough to return it back to normal... is the goldcard the only possible way (I'm asking this cause I had bad luck with finding a working memory card)
I have the nexus s 4g flashed to boost mobile. it has ran great for over a year now. i have flashed many roms and kernals to it and it has worked like a charm with only the occational hickup. but a few weeks ago when i would power it down and change may battery it would start to get stuck on the google screen. i could pull the battery a few times and it would eventually take off and work fine for a few day and then do it again. this last time it done it i cant get it to go past the google screen for nothing. i can get into the fast boot mode and also into clockworkmod touch recovery but when i go into flash zip from sd it say error loading sd, when i plug it into my computer it conects when in fastboot but i cannot access my sd memory at all. i tried the pdanet but it wont work due to no access to the sd. i downloaded the program wugs nexus tool kit and tried to flash stock and unroot with option bootloop / soft-brick in my boot loader. the program seems like it is working, it takes control of my phone restarts bootloader a few times then says restarting your now stock phone, but my phone just sits in bootloader. i have tried to manually reboot system and it just goes to the google screen and stops. when i power on my phone the google logo comes up, flashes away for a split second then pops back up with the leds at the bottom of my phone on this time but thats all i can get. please help i dont know what to try next. let me know if any of you have had this problem before and what you did to get it fixed. Please help i miss my Nexus...
** UPDATE *** Well i havnt really given up on my Nexus but i gave in and bought a new Galaxy S II so i could have a working smart phone again. Ill still be working on the Nexus in my spare time so ill update if i have any luck.
Sent from my SPH-D710 Galaxy S II running Crossbones JB ROM with matrix using xda app-developers app
this is my first htc and so far i am missing my samsung and motos
the phone is now completely non responsive and is stalled at the HTC boot screen with the text "this build is for development purposes only " i have the verizon htc one m8 ive tried removing the sd and sim holding power holding volume and power nothing makes a difference.
rooted with s off twrp is my custom recovery
started by putting slimrom on for a change of pace i had horrible signal strength and decided to try another rom somewhere in the process of flashing venom one my sd lost its backups the phone had stayed on the same screen for a while but eventually booted to a stable seeming venom rom and had 3g but no 4g service i ended up rebooting the phone today around 11 am and its been in this loop / screen since. i let the battery die down and was able to get to recovery and searched for my back ups but they were gone i ended up rebooting and now am stuck on the same screen as before. even after trying to enter recovery twrp it goes back to htc and not twrp
i tried every combination of buttons the few times and have drained the battery twice and now it just boots to this screen and is non responsive. hope that i can manage to find a way to push something to it or enter recovery and go back to stock using ruu's
anyone with input or advice would be a blessing at this point id be happy to make a donation for any useful help / anything to get me out of this screen even so i can push another rom or ruu to get me to stock
im afraid ive ruined a perfectly awesome phone
update got back to twrp and tried to re flash the venom one rom after full wipe but used their option for "stock" install said 100% and sucessful but upon the reboot is now seems to be stuck in the same screen.
got into the recover after battery died re flashed venom
after about 15 minutes on the htc screen it went to set up ....still very buggy more so than last time the phone was actually working but it is at least from what i can tell working ... going to try to get back to square one somehow
screen wont turn on and acts very buggy only time it stays on is holding power and gives reboot options... i done f ' ed this phone up.
How long are you waiting after I restarts when the install is finished? It will take a long time on that first boot. I have seen them take more than 5 minutes and if you interrupt it it can cause problems.