[Q] Stuck at CM10 boot screen. Can't recover. - Verizon Samsung Galaxy S III

Hi there, this evening I was on the forums, looking for an easy way to root my S3. I followed the steps exactly, and got it rooted. I then went to flash Cyanogen mod 10. I booted into recovery, wiped the cache, and installed the .zip and the gapps.zip. Well I rebooted it from CWM, and it just sits at the boot screen. I've turned it off and tried booting into recovery by holding both volume buttons and the power button, but it just boots up normally back to the CM10 screen. So, I cant seem to get it into recovery, or anything. Please lend me your knowledge.

Did you unlock the bootloader?
JMoneyCountIt said:
Hi there, this evening I was on the forums, looking for an easy way to root my S3. I followed the steps exactly, and got it rooted. I then went to flash Cyanogen mod 10. I booted into recovery, wiped the cache, and installed the .zip and the gapps.zip. Well I rebooted it from CWM, and it just sits at the boot screen. I've turned it off and tried booting into recovery by holding both volume buttons and the power button, but it just boots up normally back to the CM10 screen. So, I cant seem to get it into recovery, or anything. Please lend me your knowledge.
Click to expand...
Click to collapse

Recovery is volume up, power, and home. Just boot your phone up by holding all 3.
p.s. - if all you did was wipe cache before going from Stock (ICS) to CM10 (JB) - bad idea. You should always wipe cache, data and dalvik as well if you're going from ICS to JB or vice versa.

You should also format the system when changing base versions (4.0 to 4.1). Especially on aosp roms, and definitely when returning to tw. Most roms incorporate this, but it is evident that it does not always clean it out fully all the time. True clean install is factory data reset/cache/dalvik/format system.
Sent from my Galaxy Player 5.0 running CM9

I did unlock the boot loader. I used the EZ Unlock. But it said that status was unknown. I clicked unlock though and it said it unlocked the boot loader. And there was only one option when I was in CWM, to wipe the cache (it might have been the data I can't quite remember) but either way there were no choices to wipe the data, cache, and dalvik. I tried holding the power, volume down, and home. It said it was downloading, but I let it sit overnight and it never did anything.
Sent from my Nexus 7 using xda app-developers app

JMoneyCountIt said:
I did unlock the boot loader. I used the EZ Unlock. But it said that status was unknown. I clicked unlock though and it said it unlocked the boot loader. And there was only one option when I was in CWM, to wipe the cache (it might have been the data I can't quite remember) but either way there were no choices to wipe the data, cache, and dalvik. I tried holding the power, volume down, and home. It said it was downloading, but I let it sit overnight and it never did anything.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Recovery is volume UP, power, and home. Downloading is down. Download mode is when you connect it to your computer to flash firmware via ODIN. CWM definitely has options to wipe data and cache on the main area, with wiping dalvik as an option in advanced options.

I'm very sorry everyone. I took it to my brother and he fixed it for me. Thank you for being so helpful though I just booted to recovery and wiped the cache, dalvik and data. Then it booted up good. I wish I was good with technology
Sent from my Nexus 7 using xda app-developers app

I ran into the same problem. Do you know how your brother fixed it?
I'll appreciate any help.
Thanks!
JMoneyCountIt said:
I'm very sorry everyone. I took it to my brother and he fixed it for me. Thank you for being so helpful though I just booted to recovery and wiped the cache, dalvik and data. Then it booted up good. I wish I was good with technology
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse

abum said:
I ran into the same problem. Do you know how your brother fixed it?
I'll appreciate any help.
Thanks!
Click to expand...
Click to collapse
Well, I had been pressing the wrong buttons when trying to boot into recovery *facepalm*. Also, I was too dumb to look in the advanced options for the other options, like wiping the cache, data, Dalvik, etc. Pretty much me just being a noob at all that is technology haha

Related

[Q] lock up wheel while updating to ics

trying to update to ics did a factory reset in recovery then installed
Eos-wingray-1.0.0 Tiamat-Xoom-3.0.5-gpuoc plus google aps my xoom is currently stock on the wheel loading screen it just keeps going. I have no idea what to do.
Did you also wipe cache and Dalvik cache?
To do a hard reboot hold down the volume up and power buttons for a few seconds...your XOOM should reboot, when you see the red Motorola logo wait 3 seconds and hit volume down...you should see "android recovery" in the upper left corner, when you do, hit volume up to enter recovery.
Also just wanted to make sure, are you currently rooted with your bootloader unlocked and a custom recovery installed?
Sent from my Xoom using xda premium
Did you also wipe cache and Dalvik cache?
To do a hard reboot hold down the volume up and power buttons for a few seconds...your XOOM should reboot, when you see the red Motorola logo wait 3 seconds and hit volume down...you should see "android recovery" in the upper left corner, when you do, hit volume up to enter recovery.
Also just wanted to make sure, are you currently rooted with your bootloader unlocked and a custom recovery installed?
Yea I also wiped both caches I did a nandriod backup to my last working install a tiamat kernal. I have tried multiple times with no luck the install goes kernal rom then apps right? I'm rooted and the bootloader is unlocked just flashed the lastest recovery still no luck.
I think I have figured it out I have encrypted my xoom which is keeping me from clearing the cache and other things I have tryed a factory wipe but the encryption is still there.
I had the same problem. I could use adb to open a shell on the xoom once the encrypt access password had been entered, but the xoom itself would not get past the boot animation. I eventually had to 'fastboot erase userdata' to clear the encryption out. This erases entire /data directory, so all my files had to be restored from my pc backup. You might be able to back them up through the adb shell if you don't already have them backed up on another device (I don't know for sure).
Sent from my Xoom using xda premium

HELP!!! I Think?

I just flashed redemption ROM coming from Tundra ROM and I did a factory wipe, then flashed redemption, and then I was gna wipe cache/dalvick before rebooting. Everything seemed to go OK and on the last step I pressed next and the button glowed like it allowed me to select it but nothing happened? It says at the bottom of screen to reboot device but idk if I shld do this manually or if I'm froze up or what? I'm afraid to touch anything. I assumed after hitting next it would have taken me back to the twrp recovery home screen to wipe cache and reboot, but it did nothing. Can anyone help me? Is my tablet froze or can I somehow get back to recovery home and reboot???
Sent from my SCH-I605 using xda app-developers app
Ibkevin said:
I just flashed redemption ROM coming from Tundra ROM and I did a factory wipe, then flashed redemption, and then I was gna wipe cache/dalvick before rebooting. Everything seemed to go OK and on the last step I pressed next and the button glowed like it allowed me to select it but nothing happened? It says at the bottom of screen to reboot device but idk if I shld do this manually or if I'm froze up or what? I'm afraid to touch anything. I assumed after hitting next it would have taken me back to the twrp recovery home screen to wipe cache and reboot, but it did nothing. Can anyone help me? Is my tablet froze or can I somehow get back to recovery home and reboot???
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
you haven't tried anything till now?... it says there to reboot.... maybe it didn't get you back to twrp menu but i think it's safe to reboot your device now... the installation of the rom was finished safely.... the problem was with the aroma installer... try rebooting now...
nadmaj said:
you haven't tried anything till now?... it says there to reboot.... maybe it didn't get you back to twrp menu but i think it's safe to reboot your device now...
Click to expand...
Click to collapse
Yeah I got brave and rebooted and all worked out but I just realized there's a newer version of the ROM so I'm downloading it now and going to install that one but thank you for responding. Everything is OK now so if anyone needs to delete or close this thread feel free. My apologies. Thank you again.

Nexus soft-Bricked :(

Hey, xda people.
I have a consult here:
I have a hammerhead bright red (if that is useful to know) and I install the AOKP in the latest version, with root and super su. I install the ROM toolbox app from the play store and in there there is a feature in which you can install ROMs and ROM utilities. One of them is the Franco kernel so I went ahead and installed, thought TWRP, but because I didn't knew there were going to be any problems I didn't do any kind of wipe. My phone then boot into the Google loading screen but stuck there indefinitely. I tried getting into the bootloader/recovery and repowering my phone but it made no difference.
Hope you can help me up, cheers!
(All ideas are thanked)
Flash the stock rom using fastboot.
Lokke9191 said:
Flash the stock rom using fastboot.
Click to expand...
Click to collapse
Dude, it's impossible for me to get into the fastboot, it just won't load to me
Hold power about 10 sec(hard reboot)until device powers off to reboot and then hold volume down. This will get you into the bootloader using volume keys toggle to and select recovery using power. In twrp reflash rom. Wipe cache and dalvik and reboot. If that doesn't work you can do the same except wipe for clean flash flag ROM gapps reboot. If all else fails go to boot loader and flash factory images via fastboot.
Edit... You say it won't load meaning you can't get there?
If you will be flashing images it will wipe your device so that's a last option.
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5 using Tapatalk

Tried to Port Xperia remote play killed phone

Could someone please help, my nexus 5 is rooted and has twrp recovery.
I tried this http://forum.xda-developers.com/crossdevice-dev/sony/4-4-4-stock-xperia-devices-ps4-remote-t2868092
Flashed the zip file, then as I was wiping the dalvik cache my phones screen turned off and I was really scared, so pressed the buttons to get back into recovery volume down and power on, boot logo flashed up a twice and then a sigh of relief, then I realised I haven't got any signal on my phone, then looked into my files and they are all gone, I can't install any new apps. the phones internal memory is not showing up.
Just realized that it's not for twrp recovery it was for cwm.:crying:
How do I get out of this and back to normal
Edit -as the phone was wiping dalvik cache when the screen went off, I didnt know it was just turning the screen off, so I interupted it by reseting the device
thanks
Go into boot loader and flash stock
Sent from my Nexus 5 using XDA Free mobile app
EngineerNev said:
Could someone please help, my nexus 5 is rooted and has twrp recovery.
I tried this http://forum.xda-developers.com/crossdevice-dev/sony/4-4-4-stock-xperia-devices-ps4-remote-t2868092
Flashed the zip file, then as I was wiping the dalvik cache my phones screen turned off and I was really scared, so pressed the buttons to get back into recovery volume down and power on, boot logo flashed up a twice and then a sigh of relief, then I realised I haven't got any signal on my phone, then looked into my files and they are all gone, I can't install any new apps. the phones internal memory is not showing up.
Just realized that it's not for twrp recovery it was for cwm.:crying:
How do I get out of this and back to normal
Edit -as the phone was wiping dalvik cache when the screen went off, I didnt know it was just turning the screen off, so I interupted it by reseting the device
thanks
Click to expand...
Click to collapse
Why did you flash something for the Xperia on your device. Try flashing the factory image in fastboot but you might have bricked your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Why did you flash something for the Xperia on your device. Try flashing the factory image in fastboot but you might have bricked your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Luckily the zip just contains /system files on this occasion.
/system/etc/permissions and /system/frameworks
...so flashing a Nexus 5 ROM should remedy the problem.

Can't boot past Google logo white screen after flash-all.bat full restore

Hi all, been running a fairly stable non-Verizon (but on Verizon network) Pixel for several years now. Yesterday when using Google Maps my phone's screen blacked out and it immediately put itself into a boot loop. My bootloader is unlocked so it starts with the warning screen then the white background Google logo screen, then after ~25 seconds the screen blacks out again and it repeats.
I can hold down the power button to force the power off faster so I don't think it's a stuck power button. I have updated my SDK/platform-tools and have a fresh August factory image downloaded and re-downloaded, and all the images extracted to the correct folder and the flash-all.bat factory reset seems to run normally in cmd and on the phone (reboots happen at regular times, etc.) but as soon as it gets to the white background Google screen, cut to black after ~25secs.
I cannot reliably boot into twrp-3.2.3-1-sailfish.img, but it does work sometimes. ADB sideloading any ZIP does not seem to work (freezes TWRP and back into boot cycle). I can sometimes boot into stock recovery and have tried "Wipe data/factory reset" which appears to complete successfully but still does not get me past the white screen logo.
Anything else I can try? Does it seem broken to anyone else? I use custom roms, recently been on Bootleggers with no complaints, but I don't think it's related to that. Something seems irreparably corrupted or something, it was so weird that it just did it to itself mid-navigation and there's nothing I can do to restore it to any state--I even tried flashing last month's factory image, tried changing active slots, anything I could think of. Thanks for your time!
Jesse402 said:
Hi all, been running a fairly stable non-Verizon (but on Verizon network) Pixel for several years now. Yesterday when using Google Maps my phone's screen blacked out and it immediately put itself into a boot loop. My bootloader is unlocked so it starts with the warning screen then the white background Google logo screen, then after ~25 seconds the screen blacks out again and it repeats.
I can hold down the power button to force the power off faster so I don't think it's a stuck power button. I have updated my SDK/platform-tools and have a fresh August factory image downloaded and re-downloaded, and all the images extracted to the correct folder and the flash-all.bat factory reset seems to run normally in cmd and on the phone (reboots happen at regular times, etc.) but as soon as it gets to the white background Google screen, cut to black after ~25secs.
I cannot reliably boot into twrp-3.2.3-1-sailfish.img, but it does work sometimes. ADB sideloading any ZIP does not seem to work (freezes TWRP and back into boot cycle). I can sometimes boot into stock recovery and have tried "Wipe data/factory reset" which appears to complete successfully but still does not get me past the white screen logo.
Anything else I can try? Does it seem broken to anyone else? I use custom roms, recently been on Bootleggers with no complaints, but I don't think it's related to that. Something seems irreparably corrupted or something, it was so weird that it just did it to itself mid-navigation and there's nothing I can do to restore it to any state--I even tried flashing last month's factory image, tried changing active slots, anything I could think of. Thanks for your time!
Click to expand...
Click to collapse
I had this once. This worked for me; clean adb flash latest factory image and nothing else, let it boot to bootlogo, use button combo to get in stock recovery, in there wipe cache/ dalvik cache and reboot. Leave it alone for a few minutes.
Hope this will help, good luck.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
I had this once. This worked for me; clean adb flash latest factory image and nothing else, let it boot to bootlogo, use button combo to get in stock recovery, in there wipe cache/ dalvik cache and reboot. Leave it alone for a few minutes.
Click to expand...
Click to collapse
Hey, thanks for your time. By adb flash you mean the regular flash-all.bat or using fastboot flash commands to flash the imgs manually, right? Or is there some difference between fastboot and adb flashes? Then, my stock recovery does not have a wipe cache / dalvik option, only a wipe data / factory reset option. Is this hiding somewhere? Should I try that in TWRP instead of stock if I can get booted to an img of that? And then you're saying after the fastboot image install, immediately boot into recovery before letting it boot at all?
Jesse402 said:
Hey, thanks for your time. By adb flash you mean the regular flash-all.bat or using fastboot flash commands to flash the imgs manually, right? Or is there some difference between fastboot and adb flashes? Then, my stock recovery does not have a wipe cache / dalvik option, only a wipe data / factory reset option. Is this hiding somewhere? Should I try that in TWRP instead of stock if I can get booted to an img of that? And then you're saying after the fastboot image install, immediately boot into recovery before letting it boot at all?
Click to expand...
Click to collapse
Hi,
Sorry had to be more clear; yes, flash with the flash all.bat.
After the flash it will reboot, let it boot to google logo and try to get in stock recovery.
In stock recovery, if there is no clear cache/dalvik then yes, do wipe data/factory reset.
After the wipe let it boot for a while.
Don't flash anything else then the factory image until it booted up correctly and you set it up.
Good luck. If anything, just ask.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Sorry had to be more clear; yes, flash with the flash all.bat.
After the flash it will reboot, let it boot to google logo and try to get in stock recovery.
In stock recovery, if there is no clear cache/dalvik then yes, do wipe data/factory reset.
After the wipe let it boot for a while.
Don't flash anything else then the factory image until it booted up correctly and you set it up.
Good luck. If anything, just ask.
Click to expand...
Click to collapse
Appreciate it. Here's the order of operations:
- flash-all.bat
- After final reboot of flash-all.bat, hold volume down to get into bootloader immediately, then to recovery from there (no other way to boot into recovery mode faster AFAIK)
Unfortunately this is as far as I get. Choosing recovery after going to bootloader right after flash only takes me to the white screen for 25 seconds, then loop. At this point I can't get into recovery at all from bootloader, though it's been sometimes possible in the past. I think it's died, I've actually already ordered a new phone but will keep trying things with this one till that one arrives. I'll update if I'm able to get to recovery anymore, but like I noted in my OP I have tried the recovery factory reset already to no avail. It's too bad that I can't get it to work reliably enough to try your exact order of steps, but probably just a sign of larger problems.
Edit: Finally got to recovery and did the wipe again, and then it started booting to ONLY recovery after that! So the bootloop kinda changed but not so much for the better.
Jesse402 said:
Appreciate it. Here's the order of operations:
- flash-all.bat
- After final reboot of flash-all.bat, hold volume down to get into bootloader immediately, then to recovery from there (no other way to boot into recovery mode faster AFAIK)
Unfortunately this is as far as I get. Choosing recovery after going to bootloader right after flash only takes me to the white screen for 25 seconds, then loop. At this point I can't get into recovery at all from bootloader, though it's been sometimes possible in the past. I think it's died, I've actually already ordered a new phone but will keep trying things with this one till that one arrives. I'll update if I'm able to get to recovery anymore, but like I noted in my OP I have tried the recovery factory reset already to no avail. It's too bad that I can't get it to work reliably enough to try your exact order of steps, but probably just a sign of larger problems.
Edit: Finally got to recovery and did the wipe again, and then it started booting to ONLY recovery after that! So the bootloop kinda changed but not so much for the better.
Click to expand...
Click to collapse
That's a real bummer m8!. Starting to think there's a hardware problem of some kind.
Wish I could help you out a little more, but I can't from a distance.
Hope you're new phone does you well. What did you order? Another Pixel?
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
That's a real bummer m8!. Starting to think there's a hardware problem of some kind.
Wish I could help you out a little more, but I can't from a distance.
Hope you're new phone does you well. What did you order? Another Pixel?
Cheers
Click to expand...
Click to collapse
Thanks again for the attempts to help, I got a couple tips from posting on reddit too that didn't get me anywhere either--I've all but called it on the Pixel! But appreciate your time.
I went with the OnePlus 7 Pro and am looking forward to it. I'm disappointed the Pixel didn't make it to a full 3 years of use for me, hoping I can get more out of the next one! Cheers
Jesse402 said:
Thanks again for the attempts to help, I got a couple tips from posting on reddit too that didn't get me anywhere either--I've all but called it on the Pixel! But appreciate your time.
I went with the OnePlus 7 Pro and am looking forward to it. I'm disappointed the Pixel didn't make it to a full 3 years of use for me, hoping I can get more out of the next one! Cheers
Click to expand...
Click to collapse
You're welcome. If I can, I will always try to help.
Hope you will enjoy your OP 7 pro, think it's a nice phone.
It's a shame it did'nt bring you 3 years of pleasure, hope mine will, but will see.
Cheers
Sent from my Google Pixel using XDA Labs

Categories

Resources