[Q] HTC Amaze stuck on Cyanogenmod CM10 boot screen - HTC Amaze 4G

Used this thread http://forum.xda-developers.com/showthread.php?t=1426377 which was for beginners. Loaded the CM10 and just stuck on the splash screen. Can anyone point me in the right direction? Thanks

ksharifr said:
Used this thread http://forum.xda-developers.com/showthread.php?t=1426377 which was for beginners. Loaded the CM10 and just stuck on the splash screen. Can anyone point me in the right direction? Thanks
Click to expand...
Click to collapse
That happened to me and I wasn't properly rooted. I booted back into recovery and restored to stock. I re-followed all of the directions for rooting and it worked the second time.

iraethan said:
That happened to me and I wasn't properly rooted. I booted back into recovery and restored to stock. I re-followed all of the directions for rooting and it worked the second time.
Click to expand...
Click to collapse
These are some of the screens I am getting.

ksharifr said:
These are some of the screens I am getting.
Click to expand...
Click to collapse
What happens when you try to factory reset?

ksharifr said:
These are some of the screens I am getting.
Click to expand...
Click to collapse
flash 4ext from bootloader and try flashing the rom again!

That happened to me. Had to format the SD card (was going from encrypted to nonencrypted) and then re flash and it worked fine.
Sent from my Amaze 4G using xda app-developers app

Finally got the CM10 installed. I flashed it with a different ROM and then it finally booted into the OS. It is fast and responsive. I am definitely hooked on it.
Sent from my Nexus 7 using xda app-developers app

Related

Nook Tablet Jellybean 0.05.1 Issue

So, I downloaded the necessary files too go from CM9 to CM10 via recovery in my nook tablet and I did a factory reset. From there, I flashed the cm10-acclaim-0.05.1-full-of-bugs.zip. After flash I fixed permissions, wiped Dalvik, took out my sd card and hit reboot. It boots into the universal bootloader, but that's about it...please help! I can't find a solution! Please and thank you so much!
kameronamurray said:
So, I downloaded the necessary files too go from CM9 to CM10 via recovery in my nook tablet and I did a factory reset. From there, I flashed the cm10-acclaim-0.05.1-full-of-bugs.zip. After flash I fixed permissions, wiped Dalvik, took out my sd card and hit reboot. It boots into the universal bootloader, but that's about it...please help! I can't find a solution! Please and thank you so much!
Click to expand...
Click to collapse
What recovery did you use to flash the rom? What version?
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
What recovery did you use to flash the rom? What version?
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
I honestly couldn't tell you. I just know that when I boot into recovery, the n screen flashes, than a BIG n flashes then goes to the recovery screen. It's so confusing! Lol
kameronamurray said:
I honestly couldn't tell you. I just know that when I boot into recovery, the n screen flashes, than a BIG n flashes then goes to the recovery screen. It's so confusing! Lol
Click to expand...
Click to collapse
ok lets put it this way... in your recovery how do you navigate the menu? if you do it by the volume up, down and n button then you are using cwm.
if its all touch screen based then its twrp...
ShinnAsuka said:
ok lets put it this way... in your recovery how do you navigate the menu? if you do it by the volume up, down and n button then you are using cwm.
if its all touch screen based then its twrp...
Click to expand...
Click to collapse
Oh it's cwm for sure!
kameronamurray said:
Oh it's cwm for sure!
Click to expand...
Click to collapse
ok can you tell me what version of cwm you have? usually it shows it in the top left corner when you go into cwm.
ShinnAsuka said:
ok can you tell me what version of cwm you have? usually it shows it in the top left corner when you go into cwm.
Click to expand...
Click to collapse
I'm pretty sure it is 5.0.2.8 if I'm not mistaken. I tried to remember it but I'm away from it right now.
I was having reboot issues with that ROM. I ended up putting the original acclaim_update.zip file on a blank SD card, factory resetting it, then rerooting.
kameronamurray said:
I'm pretty sure it is 5.0.2.8 if I'm not mistaken. I tried to remember it but I'm away from it right now.
Click to expand...
Click to collapse
That's your.problem then. Flashing any rom with a 3.0+ kernel using that cwm will result in a bootloop. so eight now you need to flash a newer cwm and then try flashing cm10 again.
look in the dev section for a newer recovery.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
That's your.problem then. Flashing any rom with a 3.0+ kernel using that cwm will result in a bootloop. so eight now you need to flash a newer cwm and then try flashing cm10 again.
look in the dev section for a newer recovery.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
You're a genius! Thank you so much!

Tried to upgrade to CM10 Now im stuck in a bootloop

I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Ventus_zx said:
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
Im not an expert, but did you create a backup? or try wiping twice over and re-installing.
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
xndabox said:
Need a littlemore information. Are you s-off? What recovery are you using?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Ventus_zx said:
Im using 4EXT And I am not S-OFF
Wow it bootlooped all night ;(
Click to expand...
Click to collapse
same thing happened to my phone with CM 10, so i ended up instaling the android revolution rom for the time being.
What recovery are you using? Use 4ext if you aren't, try again, if it loops more than once, you either forgot to wipe before install or you need to flash the kernel manually.
Sent from my SGH-T999 using xda app-developers app
I was on speed rom 7.5, but i liked the way cm10 looked so I wiped my data and all that and flashed it. My phone hasn't done anything but stay on the cyanogen rotating thing for like 15 minutes. Please help. (Ps. I was dumb and didnt make a nandroid backup -_-)
Click to expand...
Click to collapse
I also had a problem when I flashed Speedrom but with versions 6.5 which I had previously working perfectly but then decided to switch to SS3 and then switch back. Now I also had the bootloop issue thing where the thing would just keep spinning. So I re-flashed SS3 with the faux kernel and then just did the two things:
4EXT Recovery btw
Wipe data/factory reset
Clear dalvik cache
Then install the rom and once done, go back to menu and reboot from recovery. It should tell you that the previously used boot.img will be used (that is what I get when I flash my roms and they work perfectly).
+1 is this helped!
Thanks it worked! Though I switxhed back to speed rom lol
Sent from my HTC Ruby using xda premium
Nice! And no problem, just happy your phone's back to normal! =)

[Q] Evo 4g LTE Stuck in boot loop, tried everything I can think of...

Ok, I thought I knew what I was doing. Unfortunately, wine had a factor in my issue... I have a rooted Evo 4g LTE. S-on Hboot 1.15. I was using Clockwork Recovery. I probably should have been using TWRP, from what I've read. When I first got the phone, I was over zealous, and flashed a Mod before saving a recovery. I hated it. So I flashed back to Stock ROM (jewel 1.22.651.3). I wanted to try out a Jelly Bean ROM so I flashed codefireX CM10. It worked but when the phone loaded it kept saying "phone error" and wouldn't let me click okay. So I rebooted into recovery and flashed my previous rom. I was a little tipsy, so I tried it again... It still didnt work... Rebooted into revovery, and this time I cleared cache, cleared davaik cache, and did a factory reset... Then, It wouldn't recover my saved rom. I must have cleared everything again, that I remember, now it won't load into Clockwork. I've tried everything I can think. I tried RUU, No luck. I tried flashing through Fastboot, No luck. Tried Well, I really have researched everything I could think about Boot loops... I'm stuck .... Everything I try seems to have a step missing or issue with my phone because its S-on and I relocked it through abd because RUU needs to be lock on.. I read I may have to flash a new kernel. I'm in over my head. I had to revert to using my Palm Pre. (which I loved for many years, But I really miss my EVO!) PLEASE HELP. :crying:
Check out om4's guide in general, it will tell u all you need to know...good luck.
Sent from my EVO using xda premium
Your issue is that you need a different kernel for CM10, and it needs to pushed in before you flash the ROM(because you're S-on and hboot 1.15).
This will help: http://forum.xda-developers.com/showthread.php?t=1847860
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah... I realize now after research... I installed it through ROM manager. Not again. Ugh
shook187 said:
I stopped reading once I read you was using clockwork.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Im now using TWRP. Everythings working again. Thank you.

[Q] Rooted phone using Odin3, upon restarting phone getting error.

Hey folks,
So just got my replacement Galaxy from AT&T (had last phone rooted/ROMed fine). Anyways, followed the directions to root using Odin3 from the Sticky. Everything seemed to have worked fine, it said PASS but after restarting the phone I have the following issue:
Shows me the new phone setup screen but keeps displaying the following message....
1. The application Google Services Framework (proccess.com.google.process.gapps) has stopped unexpectedly. Please try again.
This keeps popping up and when I click the Android it just takes me to the next screen but it won't load properly.
Any help would be MUCH appreciated. Thanks!
Boot into recovery and reflash.
Sent from my SGH-I777 using xda app-developers app
dsebbs said:
Hey folks,
So just got my replacement Galaxy from AT&T (had last phone rooted/ROMed fine). Anyways, followed the directions to root using Odin3 from the Sticky. Everything seemed to have worked fine, it said PASS but after restarting the phone I have the following issue:
Shows me the new phone setup screen but keeps displaying the following message....
1. The application Google Services Framework (proccess.com.google.process.gapps) has stopped unexpectedly. Please try again.
This keeps popping up and when I click the Android it just takes me to the next screen but it won't load properly.
Any help would be MUCH appreciated. Thanks!
Click to expand...
Click to collapse
Factory reset time
Sent from Team Pirate's Transmitter Thingy
122ninjas said:
Factory reset time
Sent from Team Pirate's Transmitter Thingy
Click to expand...
Click to collapse
THANK YOU!
dsebbs said:
As in phone's fried?
Click to expand...
Click to collapse
No my friend... boot into recovery... do a factory reset from recovery and try reflashing... or if you kept a nandroid backup why not try restoring what you once had...
Sent from my SGH-I777 using xda premium
No the phone is not fried,just do a factory reset and start over with the flash.
swole2 said:
No the phone is not fried,just do a factory reset and start over with the flash.
Click to expand...
Click to collapse
TiCaLuVeR said:
No my friend... boot into recovery... do a factory reset from recovery and try reflashing... or if you kept a nandroid backup why not try restoring what you once had...
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
On it (reflashing currently)... I'm extracting ODIN to the Desktop as opposed to just running it straight from WinRAR... wonder if that'll fix it.
dsebbs said:
On it (reflashing currently)... I'm extracting ODIN to the Desktop as opposed to just running it straight from WinRAR... wonder if that'll fix it.
Click to expand...
Click to collapse
Let us know if you succeed
Sent from my SGH-I777 using xda premium
TiCaLuVeR said:
Let us know if you succeed
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Beautiful - worked perfectly! Thanks everyone!
(reflashing currently)... I'm extracting ODIN to the Desktop as opposed to just running it straight from WinRAR... wonder if that'll fix it.
I had the same problem but I was going to flash a rom right after root so it didnt matter much to me
dsebbs said:
THANK YOU!
Click to expand...
Click to collapse
Just hot the thanks button
Sent from Team Pirate's Transmitter Thingy

[Q] Stuck on boot screen

So, i updated my rom (to Elegancia 4.8, as I heard 4.9 has problems), and now I am stuck at boot. If I try to boot to recovery, the TeamWin logo comes up and then the phone reboots. How do I go about fixing this?
EDIT: Just got weirder. It fully booted, then sort of shut off the screen when i touched it. I turned the screen back on, and then it rebooted again.
InternetCliche said:
So, i updated my rom (to Elegancia 4.8, as I heard 4.9 has problems), and now I am stuck at boot. If I try to boot to recovery, the TeamWin logo comes up and then the phone reboots. How do I go about fixing this?
EDIT: Just got weirder. It fully booted, then sort of shut off the screen when i touched it. I turned the screen back on, and then it rebooted again.
Click to expand...
Click to collapse
Do a full wipe, flash stock kernel and try again. If that doesnt work lock bootloader again and flash stock ruu.
Sent from my HTC One X+ using xda premium
phikal said:
Do a full wipe, flash stock kernel and try again. If that doesnt work lock bootloader again and flash stock ruu.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Full wipe from where? I can't get to recovery. It has now fully booted, but if i try to get back to recovery it kind of lags out a bit and eventually reboots into rom. I am backing up everything now. I already tried reflashing the recovery, it still just crashes when i boot into it.
if i were you i would lock the bootloader again and flash the stock ruu, after that start from scratch.
phikal said:
if i were you i would lock the bootloader again and flash the stock ruu, after that start from scratch.
Click to expand...
Click to collapse
How does one lock the bootloader? I might try after everything finishes backing up.
InternetCliche said:
How does one lock the bootloader? I might try after everything finishes backing up.
Click to expand...
Click to collapse
Am not near a pc right now there should be a sticky for it.
Sent from my HTC One X+ using xda premium
phikal said:
Am not near a pc right now there should be a sticky for it.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Except somehow now it is doing recovery and everything just fine. I did a full wipe and titanium restore, just to be safe. Seems to be all good. Thanks for your help!

Categories

Resources