Database Info

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

Phone keeps rebooting, even in recovery?

Hi. I was toolin' along doing real well on CleanRom 4.5 for several days. Starting yesterday, the phone would randomly reboot itself to the HTC screen. I figured I had a bad app or something. Today, I went to open an app (Draw Something) and the phone froze for a bit. Then it rebooted, and now I cant get it booted back up. I usually never make it past the HTC screen. Got into recovery once but it rebooted in the middle of clearing the cache.
Any advice?

Welp, just made it through cache and dalvik and rebooted in the middle of factory reset. I wonder if I'm doing more harm than good.

Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.

hcricket said:
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
Click to expand...
Click to collapse
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:

omario8484 said:
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
Click to expand...
Click to collapse
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?

hcricket said:
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
Click to expand...
Click to collapse
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?

omario8484 said:
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
Click to expand...
Click to collapse
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?

hcricket said:
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
Click to expand...
Click to collapse
What's your battery at?

Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*

hcricket said:
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
Click to expand...
Click to collapse
Keep that simmy in there..now what's your battery ....when does it reboot ...when trying to get into aroma installer?
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Worst case scenario you can relock the bootloader and run an RUU. But I think u can get out of this without having to do that

I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.

hcricket said:
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
Click to expand...
Click to collapse
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird

omario8484 said:
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
Click to expand...
Click to collapse
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.

hcricket said:
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
Click to expand...
Click to collapse
Hold down your power button until your screen turns black and than see if it's still rebooting

Still no go. Thank you for your help - I've got it to 98% battery, powered it down, and I'm going to the bar, hah hah.

try flashing CM10 instead of a Sense rom. Aroma can cause freezes and reboots on its own. I would also be scared to run the RUU also since your phone freezes randomly. whats was your stock version?

It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.

denversc said:
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
Click to expand...
Click to collapse
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium

kleeman7 said:
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I told him to flash a rom that doesn't use aroma. He is getting freezes all the time. TWRP used to freeze up on me all the time after the 2.20 ruu until twrp 2.2.2.0 was released. Phone still has trouble getting into recovery from the bootloader though. He should install CM10 or codefirex without using a custom kernel. Maybe run "fastboot erase cache" in bootloader then wipe cache,dalvik,factory reset,system,external in recovery then flash CM10 or codefirex and gapps. keep it plain until you find issues you can attribute to the rom or to the phone. i have had very few issues with latest builds of jb aosp roms besides some battery stuff.

Well, although I had fully charged it and then powered down, now that I am ready to work on it this AM, it wont start at all. I'm thinking she's gone, captain.
Thank you everyone for the replies.

Flash Kernel

So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.

what are you doing before flash the new rom?

juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...

Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app

Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash

andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.

Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.

Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.

So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(

I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium

Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.

[Q] Getting bsod after reboot on Liquid Smooth

Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.

CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.

CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.

jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.

CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link

theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.

Cyanogenmod 12.1 Upgrade from Slimkat 4.4.4 - Bootloop after optimization

So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....

hypercoyote said:
So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....
Click to expand...
Click to collapse
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?

hypercoyote said:
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?
Click to expand...
Click to collapse
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.

hypercoyote said:
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.
Click to expand...
Click to collapse
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.

hypercoyote said:
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.
Click to expand...
Click to collapse
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Me too! lol

Hehehe