I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
Just to be clear:
1. You successfully booted into CM7 after installing it? Then you went to install gapps and couldn't get past the boot logo?
2. Or were you trying to install gapps right after flashing CM7 (i.e. stayed in recovery and did not boot into OS)?
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
Hmm, well that definitely rules out an outdated recovery, which is what usually causes people to get stuck at the bootlogo. If you can't even re-install after wiping, then I would just restore a backup and start over.
Maybe try getting a fresh download of the gapps package. You may have possibly had a corrupted download?
Are you running CWM recovery or Rom Racer's? I had a problem where I was stuck at the boot logo while using CWM (latest one) but when I switched to Rom Racer's recovery and flashed everything worked.
I ended up having to use an older CWM recovery and wiping the phone and SD card with a lot of help from a friend of mine whos knows more about this than i do
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
How did you prep for the CM7 and GAPPS flash? If you did not wipe correctly, there was a first indication you might have problems.
How long did you wait after the phone first booted into CM7? If you rebooted as soon as the OS was up, that's more than likely your issue. You need to wait 10 minutes to let the phone build system files after flashing.
Also, an older CWM would have, if anything, caused more problems. If you had the latest ROM Manager or Romracer CWM then that was definitely not your problem, so your friend using an "older" CWM wasn't helping any.
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
I have run into this issue before when flashing any apps that update an app that is already there. I have found that a Dalvik wipe is needed before the flash. It is good practice to wipe Dalvik at least when flashing anything that changes the System Files. I also wipe the cache Partition before any flashes just to help mitigate issues like this.
Okay I know this is a noob question so PLEASE excuse my noob-ism. Not sure if this should be in Q&A or Dev so please move to the correct section if I posted in the wrong one.
Okay, so my phone was originally 4.0.4 with a 1.19 HBOOT and 4.1 Sense. I rooted my phone, read up on a couple of threads and youtube videos regarding how to flash CM10 and from what I got if you have 1.19 HBOOT you can't just flash it using TWRP because you can't go S-OFF. Here is where I was a bit confused and think I went wrong. I read in the description of this video http://www.youtube.com/watch?v=HsQKOhqdPpM that if you aren't S-OFF that there is a workaround, which linked me to this page http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397 . So the 1st option said that it's possible to flash using Flash Image GUI to flash CM10 THEN to flash it in recovery, which I did. However now that I look closely at the pics it says only for EVO4G and the 3D. Here's where I'm at, Flashed using Flash Image GUI, then rebooted to HBOOT, then recovery, then flashed using TWRP. It looked like a success after rebooting because I seen the CyanogenMod boot screen but it's been about 25 minutes and it's just stuck there. Read up on it some more and it said that it should only take about 5-7 minutes for the first boot. I don't know what to do from here. Is there any way to still boot CM10 on my device since it seems essentially stuck at the "CM" boot screen? If not, what ROM would take me back to where I initially started off previous to trying to flash CM10 (like sense essentially)?
Once again, sorry for the noob-ism but kinda stuck here. Thanks!
I would try going into recovery and wipe Dalvik, Cache and then factory reset, do not wipe system just the 2 I mentioned and reboot, if it stays on boot anim, go to bootloader and fastboot kernel and reboot
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
drlzanej said:
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
Click to expand...
Click to collapse
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
om4 said:
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
Click to expand...
Click to collapse
THANK YOU! IT WORKED!
mista_k said:
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
THANK YOU! IT WORKED!
Click to expand...
Click to collapse
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
om4 said:
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
Click to expand...
Click to collapse
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
EdRF said:
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
Click to expand...
Click to collapse
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
om4 said:
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
Click to expand...
Click to collapse
Following this step of the process fixed this same issue for me.
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
corcgaigh said:
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
Click to expand...
Click to collapse
CaptinStabN said:
Following this step of the process fixed this same issue for me.
Click to expand...
Click to collapse
EdRF said:
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hmm...well this time I just went to recovery. Made a backup and erased, cache, dalvik, system. Did a factory reset as well (didn't do that before) and in the end did as you guys suggested. Flashed rom and then boot.img via fastboot. Thank you very much!!! :victory:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Nothing works!
om4 said:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Click to expand...
Click to collapse
Okay so I did all of this and still..... doesn't work. I'm not really a phone wiz. I paid someone to root my phone before and I used the CM10 ROM, everything was fine until I tried to change my font, the phone rebooted and got stuck on the CM 10 boot screen. I went to recovery and restored my phone from September. I then went to Flash Image GUI and flashed the boot.img for CM!0. Then went into recovery and flashed CM!0 and gaaps and wiped the cache, delv cache, system and factory reset. When I rebooted I was still stuck on the boot screen. :/ I am able to restore back to September but my camera or wifi doesn't work. Anyone know how to help me?
Try flashing meanrom, it has the kernel installer and doesn't require flash image or fastboot. If you still have any issues with the camera then relock the bootloader and flash ruu. If that doesn't fix the camera then its most likely hardware failure.
flash gui image htc evo lte
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
SunnyDNuts said:
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
Click to expand...
Click to collapse
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
I tried. It either says the file is to big or don't have the right file
I tried all the files on the backup
---------- Post added at 09:40 PM ---------- Previous post was at 09:15 PM ----------
FinZ28 said:
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I tried compressing the backup file so GUI would search for the
Kernel but it can't find the image
Bootloop Battery Issue
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
ross7alex said:
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
Click to expand...
Click to collapse
Do you have android sdk setup on your PC?
No but I can download it. Where should I find it?
---------- Post added at 05:27 AM ---------- Previous post was at 05:21 AM ----------
bigdaddy619 said:
Do you have android sdk setup on your PC?
Click to expand...
Click to collapse
Ok I found it and Im downloading it now. How will this help me?
I've been having a problem getting any 4.3 ROM to boot after the initial boot. I've seen a few other people with the same problem and I can't figure out a fix. Thought I'd ask the general Q&A.
I've used Beanstalk and Carbon (great ROMs) a few carbon 4.3 nightlies and Beanstalk 4.3.00. I installed their 4.3 builds (after checking sums to verify download) flash gapps, wipe cahce/dalvik and boot up. Set up goes great and rom runs great. but even without installing any other apps, using no backups or anything if I reboot it sticks on samsung screen and can't get past it. Every time, I even rebooted without finishing setup and wouldnt advance past samsung.
I even flashed 4.3 rom and gapps, let it reinstall apps from market then booted to recovery and made a backup. Then could'nt reboot. But if I wipe and restore the backup it will boot fine the 1 time, but again any attempts to reboot stick on samsung screen. Wiping cache/dalvik from recovery does not help, fix permissions from recovery does not help.
Anybody have this problem and find a fix?
Ok, I tried slim bean beta 2, no luck, tried ktoons kernel, no luck. Guess I'm staying with 4.2.2 until there is some movement on this issue.
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
I've been trying to install the most recent PAC Rom nightlies on a stock, rooted phone. I'm using the newest TWRP to flash it. The flash goes through fine, so I wipe cache/dalvik. When I reboot my phone it gets stuck in the PAC rom loading screen.
What should I try?
Thank you.
Did you do a full wipe/factory reset before flashing the rom?
I did. Somehow it decided to work when I tried again. Newest TWRP was messing with the install. Had to try several times for it to work.
I believe there was issues with the latest TWRP recovery. The previous build worked better. Switched over to Phil Cwm and haven't really gone back since.
Sent from my SCH-I605 using Tapatalk