HELP! i'm running liquid smooth on my S3 right now. the phone has been having issues, shutting down on its own, and i was going to load the stock rom to send it in for warranty.
the last time i was able to use the phone, a message popped up saying "System UI has stopped working". later on, the phone shut down on its own and when i turn it on, it gets stuck on the liquid smooth boot screen forever. i plug it into the comp, still nothing.
is my phone dead at this pont?! any way i can load the stock rom onto it or get it back to functioning?!! argh!
You can always go to recovery and do a factory reset that should get you booting again with liquid smooth if you want to go back to stock boot into download mood and from your computer Odin back to stock. The links can be found in Android dev section.
To boot into recovery from phone off hold volume up+home+power and to boot to download volume down+home+power
Making the iPhone jealous one user at a time.
Sounds like a framework issues to me. I would backup your ROM and then clean install after factory reset and cache wipe from recovery.
Sent from my Nexus 7
If you can get in to a custom recovery. You can use this.
http://forum.xda-developers.com/showthread.php?p=43598518
I use it from time to time. No pc, complete stock totally on the phone itself. You will still need to wipe your internal storage. I do that first.
I use Phil's recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Related
hi all, my wife has been running cm6.1 and lately it has had a few issues, so i go to download through rom manager, it fails downloading several times, download on a computer and transfer it over, boot into recovery through rom manager(i feel retarded for this one... no back up, didnt wipe) and install, well, it goes to the cm boot animation, sits for a long time, then i remember i didnt wipe so i attempt to get back into recovery and wipe, well, some how, the phone managed to go back to the stock recovery... needless to say i became very very confused...
does anyone have any insight?
thanks in advance
If you havent s-off, then you probably will see stock recovery and need to flash the update.zip to get to clockworkmod. I think i remember that right.
Sent from my T-Mobile myTouch 3G Slide using XDA App
i finally did get cm 7 up and running, and in rom manager it says that i have the latest availible clockwork recovery, but i can only get to it if i rebot to recovery through rom manager, if i go through the boot loader, it takes me to the black screen with the ! in the triangle, then after several button pushes takes me to stock recovery
This happens because ROM Manager reads the altered 'update.zip' from your SD card and it is recommended you use that program (app) to do all your loading and ROM stuff. Though if your phone is powered off you can hold Volume Down and power then after getting to the Triangle "!" screen pressing volume up and power gets you to altered 'update' screen.
So this has happen twice. My gnex has just restarted and get stuck at the bootloader in an endless loop.
I have a stock, rooted, 4.0.4 gnex.
Last time this happen I had to completely wipe my phone and start over. Dont want to do that again.
Has this happen to anyone else?
Thanks
-J
When I load in to recovery I cant even see the CWM menu.
Can you run fastboot commands
Sent from my Galaxy Nexus using xda premium
I could but now the phone wont turn on at all. Im actually one the phone with google right now to try to figure this out.
charge the phone (plug it in).
unplug it, press and hold both volume buttons, and press and hold power
bootloader comes up, plug it into computer
in this screen, flash the latest cwm file using the command:
fastboot flash recovery clockworkfilenamehere.img
press vol buttons to restart the bootloader, then select recovery, should pull up cwm.
Go wipe cache and dalvik cache (in advance), then pick restart, see if phone boots up.
If not, you'll need to reflash stock google image.
Charged phone over night and still wouldnt turn on.
Have you tried reseating the battery?
jp555soul said:
Charged phone over night and still wouldnt turn on.
Click to expand...
Click to collapse
Funny, my CDMA gnex just started doing exactly the same thing. Verizon is overnighting me another one, with Saturday delivery even.
you must factory restore your phone
you need to restore your phone to the factory image, use wugs toolkit,
galaxynexusforum.com/forum/galaxy-nexus-hacking-mods-lte-cdma/1445-wugs-galaxy-nexus-root-toolkit.html
it will download the 4.0.2 factory img for you. then use the same tool to root your phone. then install your rom. Install Liquid rom 1.4. i have tried them all it is by far the most stable and the fastet. coupled with franco or imoseyon kernel i am getting 20+ hrs of battery life and a smokin fast phone.
stuck in bootloader
My GSM nexus running aokp milestone 4 randomly got stuck in the bootloader the other day. It was working fine and after hitting my snooze button on my alarm and waiting a few minutes I realized it was off. when i turned it on it was stuck. I tried clearing cache and dalvik cache which wouldnt work so I was forced to do a factory reset. Came right back to life (with none of my data obviously).
This happened to me last night after trying to restore a nandroid. Wouldn't go past the Google screen when trying to boot the rom and wouldn't go past the team win recovery plash screen.
Luckily I have basic fastboot and adb command skills. Flashed fully back to stock, boot loader, radios, from, kernel. Booted up fine after that and no issues since.
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
probablecauz69 said:
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
Click to expand...
Click to collapse
Just press and hold volume down + power and once the blue letters " booting in recovery mode" show up let go you will be in recovery mode
rudyp9 said:
Just press and hold volume down + power and once the blue letters " booting in recovery mode" show up let go you will be in recovery mode
Click to expand...
Click to collapse
lol wow. don't know how that worked. every time before when i wanted to get into recovery i held it until it actually went into recovery. thanks:good:
My phone is verizon s4 sch-i545 when I try to boot up in recovery mode it shows booting in recovery but it just boots up normally .I wanted to do a factory reset but the factory reset just restarts my phone and when I try to get into recovery mode for a hard reset I cant boot into recovery mode. I don't know what to do
For recovery, try holding down the volume up, home and power button. Once the phone starts to boot, release the power button only. Keep pressing the volume up and home button. When you see the dead android, release all buttons.
Rahimwahid said:
My phone is verizon s4 sch-i545 when I try to boot up in recovery mode it shows booting in recovery but it just boots up normally .I wanted to do a factory reset but the factory reset just restarts my phone and when I try to get into recovery mode for a hard reset I cant boot into recovery mode. I don't know what to do
Click to expand...
Click to collapse
Odin stock firmware.
probablecauz69 said:
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
Click to expand...
Click to collapse
Try rooting your phone and then you may install flashify app and reflashed your recovery. For more info visit - youtu.be/dUb7oISR6wA
my video where I hv solves this problem
My brother has an S3 on AT&T running a nightly build of CyanogenMod 11.
It's been running this build for a while. However, he was on it today, and it crashed. Now it won't even try to boot unless you take out the battery and put it back in, in which it will show the samsung logo and shut off. It won't boot into recovery, it won't boot into download mode.
I'm thinking it's hard bricked, but why would it randomly hard brick itself like this? And is there any way to fix it?
Maybe it bricked because some files got corrupted? Not sure. If you can get into recovery, try wiping the cache, data, and Dalvik. If that doesn't work, you could try an updated CM11 ROM.
Did you try to get into download mode with a USB jig?
Its not hard bricked. Boot it into download mode and Odin back to stock
Sent from my Nexus 7 using xda app-developers app
Don't use desktop Odin if the phone has been updated via an OTA update to stock AT&T 4.3 ROM.
I'm the brother with this problem, I just couldn't post at the time.
Anyway, I can't boot it into anything. not recovery, not download mode, nothing. The only way I can force it to even try to boot is to take the battery out, and back in.
After this, "Samsung" appears for all of about a second, and it shuts off again.
Edit: it seems I can boot into download mode, but like the samsung logo, it disappears. It's almost as if it's crashing after a second each time. Any ideas?
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
flash back to stock rom
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
Good thing is you are not "hard bricked" just "soft bricked." Press the power button and volume up and hold till your phone reboots then immediately press the volume button and power down button to enter recovery.Then do a complete wipe, factory reset, then and only then reflash your stock CWM backup of your stock Rom . Just guessing mind you ,because I do not know every single thing you did before trying to return to stock but you should always do a full Wipe or factory reset before flashing between different roms. If your trying to flash a stock image, not a CWM backup, of your firmware you'll need to first reflash your stock recovery and relock your boot loader.
Is your phone a single SIM or dual SIM? Dual SIM phones have allot more issues on Cyanogenmod . If yours is dual SIM I'd stick to stock Rom or sense based custom roms made for our device. By the way what didn't you like about CM if your on a single SIM phone? It had a few issues but with a few tweaks you can get it working great and it's alot less bloated than stock lollipop. I'm on unofficial 12.1 CM with the a5_chl single SIM and it's fine. Having said that I had to tweak several things and I exempt dual SIM versions from my reasons for me liking this Rom. I get that it's sadly alot buggier for those phones . Let me know how things go in fixing your issue and best of luck.
---------- Post added at 10:43 PM ---------- Previous post was at 10:02 PM ----------
Ddreth said:
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
Click to expand...
Click to collapse
First thing, some friendly advice and I truly do mean friendly, not accusing, but you should never let anyone else touch your device when it's in custom recovery. They can seriously mess it up not just"soft brick" it like yours is now.
2nd thing is the factory reset in your custom recovery doesn't have anything to do with your personal files. It's to clean your system and its data so that you can do a fresh install of a different Rom. It's called a "clean flash." A dirty flash is when your upgrading the same custom Rom and you just flash it over the previous version without wiping then clear your Dalvik cache and reboot. These wipes leave your personal files on your internal and external SD card intact unless you specifically wipe then in your custom recovery . They just call it factory reset to make it familiar to the stock Roms use of the term in my opinion. When you have this"soft brick" you can press your power button and volume up to reboot then quickly press power button and volume down to enter recovery. Then factory reset or wipe Dalvik cache if not wanting to reset and reboot one or the other should get you back into your rom.
Hope this helps and good luck plus let me know if this works to resolve your issue. Be happy to help in any way because I have been there myself in the past. Bootloops, soft bricks,etc etc................... If you can name it, I've messed it up.