Database Info

[Q] Help me get out of this bootloop!?!?!

HELP!!!
Hey guys need some help here...was running the CM7 alpha7 and everything has been great. Phone was fully charged on the charger this morning and I rebooted just for kicks. I come back in the room a few mins later and the phone is bootlooping. Tried restoring a backup of cm7 and same thing even after a fresh wipe and install.
Restored a miui backup i have and everything is fine with that.
I cannot install a new rom or my cm7 nandroid only this miui one. tried flashing old cwr and same results. have even tried sense based roms and they will not boot. all i get is the htc splash screen and then it bootloops.
Any idea what I need to do or what went wrong? thanks!!!

Maybe kernel or radio not compatible or something? You could try the RUU
Sent from my HTC Sensation Z710e

I would advise to run the RUU and start fresh.
Might be radio issue most likely since CM7 uses their own one according to xda users.
Sent from my HTC Sensation 4G using XDA App

Thanks guys finally have the ruu downloaded and its running. Hope this works. Thanks for looking out! Running off the sidekick 4g so I really hope it works out haha
Sent from my SGH-T839 using xda premium

Tried it and it didn't work...wouldn't boot kept bootlooping the slash screen. So the only two nandroids I can restore and only two Roms I can flash are trips miui and rcmix sense 3.5 isn't that weird? I'm so confused...
Sent from my TripNMiUI Pyramid using xda premium

Did you get your problem solved? I have almost the exact same issue, but with a slightly different experience. I was using a sense 3.5 rom (Insert Coin) and, when I tried to update the ROM to the newest version, I couldn't get past the HTC splash screen (the HTC splash screen would come on for about 3 seconds, and then reboot). I was able to get into recovery and restore a CM7 rom and a previous Insert Coin rom, but I can't flash anything else without bootlooping.
I've tried flashing an older recovery (didn't work), using an alternative recovery (didn't work), flashing the RUU (didn't work), and formatting my SD card (didn't work). Nothing seems to work. :-(

[Q] trouble installing other ROMs

hey guys,
i'm having a issue with flashing new ROMs. i am currently running android revolution HD 3.6.2. i was curious on trying a different roms and i tried to install insert coin 3.3.0 and clockwork said rom installed successfully after following the steps. but i get to a htc boot screen then the screen goes black then htc screen pops up again. i left the phone alone thinking it was just part of the first boot process. left the phone alone for 20 minutes still doing the same thing. so then i tried cm7, and got the same issue after following the sticky guide for cm7. i flashed back to hd and it booted fine. then i tried to use RUU to go back to stick, and the two tmobile versions up didnt work.
any suggestions? i am curious to try other roms.

Zarch1991 said:
hey guys,
i'm having a issue with flashing new ROMs. i am currently running android revolution HD 3.6.2. i was curious on trying a different roms and i tried to install insert coin 3.3.0 and clockwork said rom installed successfully after following the steps. but i get to a htc boot screen then the screen goes black then htc screen pops up again. i left the phone alone thinking it was just part of the first boot process. left the phone alone for 20 minutes still doing the same thing. so then i tried cm7, and got the same issue after following the sticky guide for cm7. i flashed back to hd and it booted fine. then i tried to use RUU to go back to stick, and the two tmobile versions up didnt work.
any suggestions? i am curious to try other roms.
Click to expand...
Click to collapse
Just kind of a basic step. If you go from one rpm to a completely different one your going to want to superwipe. Especially if they are different builds. You can flash an update like 3.6.1 to 3.6.2 but not ARHD to insertcoin. Try superwipe and flash a new Rom. Just make sure you make nand backup so you can always go back If something goes wrong.

Getting BootLoop when installing Theme On Sensation XE

Hello Gentlemen and Gentlewomen,
I know this is my first post, but i have been on XDA quite a while, i'm a not a noob anymore, but i am not far from it .
This week i revieved my sensation, after half a day of playing with it, i quickly wanted more and when i got home i did some googling i came up with the InsertCoin rom, I had some expierence flashing before with my Galaxy S and everything went according to plan. I have InsertCoin 3.4.3 smoothly running now.
The problem is when i tried to get the FULL THEME GingerThyparancy V3.0 - Sept 16th, 2011 for XE based ROMS (1.72.401.1) running on my mobile it gave me a boot loop, i tried different versions of it, still boot loops. And when i downloaded the skin only version from the market i cant select it in the skin ''chooser''.
This is what i did:
Rooted it and made it ready for flashing with help of the noob proof guide here on XDA. Then i flashed InsertCoin 3.4.2, let it boot. Flashed 3.4.3 over it, let it boot. And then flashed the theme, this time when i reboot it i get the boot loop. Doesnt matter wich version i use, always get the bootloop.
I am rocking a brand new HTC Sensation XE. As you by now know i have InsertCoin 3.4.3 on it. Its not branded.
I really hope you guys can help me out because i freaking love the theme, esspacially the theme with a touch of blue.
If you need further info or anything ask me.
Greet, Mark

mariikvt said:
Hello Gentlemen and Gentlewomen,
I know this is my first post, but i have been on XDA quite a while, i'm a not a noob anymore, but i am not far from it .
This week i revieved my sensation, after half a day of playing with it, i quickly wanted more and when i got home i did some googling i came up with the InsertCoin rom, I had some expierence flashing before with my Galaxy S and everything went according to plan. I have InsertCoin 3.4.3 smoothly running now.
The problem is when i tried to get the FULL THEME GingerThyparancy V3.0 - Sept 16th, 2011 for XE based ROMS (1.72.401.1) running on my mobile it gave me a boot loop, i tried different versions of it, still boot loops. And when i downloaded the skin only version from the market i cant select it in the skin ''chooser''.
This is what i did:
Rooted it and made it ready for flashing with help of the noob proof guide here on XDA. Then i flashed InsertCoin 3.4.2, let it boot. Flashed 3.4.3 over it, let it boot. And then flashed the theme, this time when i reboot it i get the boot loop. Doesnt matter wich version i use, always get the bootloop.
I am rocking a brand new HTC Sensation XE. As you by now know i have InsertCoin 3.4.3 on it. Its not branded.
I really hope you guys can help me out because i freaking love the theme, esspacially the theme with a touch of blue.
If you need further info or anything ask me.
Greet, Mark
Click to expand...
Click to collapse
Hi,
Just a minor observation.
Is IC 3.4.3 a Sense 3.5 ROM?
And you have installed:
FULL THEME GingerThyparancy V3.0 - Sept 16th, 2011 for XE based ROMS (1.72.401.1)
Which I believe is for Sense 3.0 ROMS
I think that may be your problem.
Re-install the IC 3.4.3 ONLY.
Then look for a Sense 3.5 theme HERE

Going to try that when im home, got the phone working, only the theme not. Just checked and i got sense 3.5... Thank you
Sent from my HTC Sensation Z710e using XDA App

You are trying to install a theme that is made for a sense 3.0 on an sense 3.5 rom.
that definitly is your problem.

Mr. Me Too
Hi guys,
I seem to be havinghe same thing happening with my htc sensation .
im new to this also but i figured some things out.
I flashed a sensey rom 3. and it worked great but after flashing some themes on it * and I made sure the theme was a 3. theme) im having boot loops at my recovery screen and my rom startup screen. i can still get into hboot tho.
is there a way to stop the madness?
ccan i flash a rom from my pc like the hd2 just to get it working again?
if you guys know a solution i'd be very thankful...
wont be messing with that again!

fred7012 said:
Hi guys,
I seem to be havinghe same thing happening with my htc sensation .
im new to this also but i figured some things out.
I flashed a sensey rom 3. and it worked great but after flashing some themes on it * and I made sure the theme was a 3. theme) im having boot loops at my recovery screen and my rom startup screen. i can still get into hboot tho.
is there a way to stop the madness?
ccan i flash a rom from my pc like the hd2 just to get it working again?
if you guys know a solution i'd be very thankful...
wont be messing with that again!
Click to expand...
Click to collapse
Hi,
Go into recovery, wipe your cache partition and dalvik, and then reflash your ROM.
This will restore you back to sanity.
For future reference, always make a nandroid backup BEFORE you make any changes to your phone.

thanks
thanks for the help,
but the problem is when going into recovery or just powering on the phone its going into boot loop.
so the boot screen comes on like the phone is starting but it just keeps repeating and when i boot into recovery the recovery starts, the menu pops up but within about 4 seconds it starts over again in recovery, so both recovery and the actual rom is going intoo boot loop...
thats why I was wondering if it was possible to reflash the rom like the hd2 from hboot bcuz thats the only thing thats seems to be working...
thanks again for any ideas.

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.

[Q] Crazy insane inverted touchscreen issue

crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help

Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app

mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.

HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion