Hello.
I just rooted my Samsung Galaxy Nexus and installed the latest CyanogenMod 10 nightly build but then I rebooted and now I've waited about 15-20 minutes if not more and it's still loading or something.
There is a blue circle with white text in the middle saying "CyanogenMod" and the circle just keeps spinning.
I don't know how long I am supposed to wait but it seems like there might be something wrong...
dingdong10 said:
Hello.
I just rooted my Samsung Galaxy Nexus and installed the latest CyanogenMod 10 nightly build but then I rebooted and now I've waited about 15-20 minutes if not more and it's still loading or something.
There is a blue circle with white text in the middle saying "CyanogenMod" and the circle just keeps spinning.
I don't know how long I am supposed to wait but it seems like there might be something wrong...
Click to expand...
Click to collapse
Try wiping and reflashing your CM10 build
AshtonTS said:
Try wiping and reflashing your CM10 build
Click to expand...
Click to collapse
Thanks! I took the battery out and then I did as you said and it worked
dingdong10 said:
Thanks! I took the battery out and then I did as you said and it worked
Click to expand...
Click to collapse
Glad you got it working unending boot screens are one of the scariest problems in my opinion lol
i downloaded teamwin recovery, then downloaded cm10 from some rom app in the market, when i put it on my phone it got stuck on the spinning cyanogenmod 10 screen and it's been there for 2 hours now just spinning. i trued going into bootloader mode & factory resetting it but it just went back to that screen. im terrified that i have bricked or ruined my phone some please help
Go to recovery, wipe everything, flash again.
If that doesn't work: Download CM10 again (get.cm), adb push it to your device in recovery mode and flash. Don't forget the Gapps.
I wish I was a noob again I loved learning the basics of flashing.
FrostyF7 said:
I wish I was a noob again I loved learning the basics of flashing.
Click to expand...
Click to collapse
You are still a noob you just don't know it.
jcoffland said:
You are still a noob you just don't know it.
Click to expand...
Click to collapse
Three years and this is your first post...
Related
First off I have a Verizon gnex. My phone was all fine and dandy running CM9 on ICS, then I installed CM10 and it was working great until I would get weird bootloops at the Google screen. Eventually it would boot, I guess it's some sort of file check or something? But it was really making me mad.
I tried wiping everything and installing CM9 again but it was still stuck and when it eventually booted, nothing was changed! I still had CM10 and all my apps/data were there. Weird I thought, so I just kept using my phone trying to find a fix and trying to not let it die.
I did a factory reset and it seemed to make the process of getting passed the Google screen faster up until last night...it died and did not want to get past the Google screen. So I ran Odin with all the factory images and what not and thought it was going to work..but nope same problem.
Also my recovery will not work and I tried to flash it again but if I hold up and down volume and power and choose recovery it will just restart and be back at the google screen.
PLEASE HELP! I just shelled out 280 bucks for this used because I didn't want to lose my unlimited data and now I can't even use my phone!
I've waited up to 15 min sometimes on JB. Just be patient. Flash the Verizon JB boot loader if you haven't already. It's here on XDA somewhere
Sent from my Jelly Beaned toro. You mirin brah?
BFirebird101 said:
I've waited up to 15 min sometimes on JB. Just be patient. Flash the Verizon JB boot loader if you haven't already. It's here on XDA somewhere
Sent from my Jelly Beaned toro. You mirin brah?
Click to expand...
Click to collapse
I've waited way more than 15 minutes..it will just keep going and going until it freezes or dies.
edit: also I'm not even on JB, stock ICS.
Is anyone else having the same problem? Anyone have suggestions on what I should do?
Flash the stock images using fastboot instead of ODIN.
See if that will work.
El Daddy said:
Flash the stock images using fastboot instead of ODIN.
See if that will work.
Click to expand...
Click to collapse
Sorry I should have mentioned that I tried that before Odin, thanks though.
El Daddy said:
Flash the stock images using fastboot instead of ODIN.
See if that will work.
Click to expand...
Click to collapse
Well i just went back and tried that again and it finally let me boot but it soon went back into bootloop madness. I did it again and it booted up gain but of course went back into the loop. Now injust tried it again and that wont even work now..
I have the same problem, but when using JB ROMs...
See here (still cannot figure it out):
http://forum.xda-developers.com/showthread.php?t=1826749
-edit-
N/m, figured it out.
crobs808 said:
I have the same problem, but when using JB ROMs...
See here (still cannot figure it out):
http://forum.xda-developers.com/showthread.php?t=1826749
-edit-
N/m, figured it out.
Click to expand...
Click to collapse
Followed that thread, but didnt really see exactly how you went about fixing it. What method is in the exe you created?
Do you have a VZW Nexus (toro)? I can post my EXE if so.
-edit-
Reset guide in my sig now
So I managed to Brick my sprint version of the galaxy s3. Like an idiot I overlooked a rom and used the i9300 version instead of my model version(nood move). Anyway I can't turn my phone on AT ALL!! I tried putting in into download and recovery and I get nothing. How do i fix this?? Anyone???
If u can't get download mode or recovery than there is no help. Maybe a jig if u have one but I'm not sure if they even work for the s3.
Sent from Galaxy SIII
musclehead84 said:
If u can't get download mode or recovery than there is no help. Maybe a jig if u have one but I'm not sure if they even work for the s3.
Sent from Galaxy SIII
Click to expand...
Click to collapse
Ahhhh shyt! These new phones are harder to fix now, never had this problem before, but its like if mess up once with these new galaxy s3's thats it, whats the point of flashing roms when you chance it every time. Thanks though man looks like I'll have to call to get a new one.
jsmoof21 said:
Ahhhh shyt! These new phones are harder to fix now, never had this problem before, but its like if mess up once with these new galaxy s3's thats it, whats the point of flashing roms when you chance it every time. Thanks though man looks like I'll have to call to get a new one.
Click to expand...
Click to collapse
Its not a problem as long as you flash a rom FOR YOUR PHONE.....
Did you try this?
jsmoof21 said:
So I managed to Brick my sprint version of the galaxy s3. Like an idiot I overlooked a rom and used the i9300 version instead of my model version(nood move). Anyway I can't turn my phone on AT ALL!! I tried putting in into download and recovery and I get nothing. How do i fix this?? Anyone???
Click to expand...
Click to collapse
I thought I hard brick my sons phone and here is what I did: Worth a try at this point.
Take battery out and do NOT put it back in. Take SD card out. Plug phone into computer and attempt download mode. Mine booted right up with this method when it wouldn't with anything else. If it does flash the stock rom through Odin right away and you are good to go.
tyler1037 said:
I thought I hard brick my sons phone and here is what I did: Worth a try at this point.
Take battery out and do NOT put it back in. Take SD card out. Plug phone into computer and attempt download mode. Mine booted right up with this method when it wouldn't with anything else. If it does flash the stock rom through Odin right away and you are good to go.
Click to expand...
Click to collapse
I just tried that and no luck. sounds like u soft bricked it. I can't get it to turn on period. The only thing that turns on is the lcd light but only for 10 seconds then shuts off. Thanks for the help though!
If your getting a light, even temporary, I'd boot a tinycore Linux and see what mode its in for that 10 seconds
18th.abn said:
If your getting a light, even temporary, I'd boot a tinycore Linux and see what mode its in for that 10 seconds
Click to expand...
Click to collapse
I gave up an ordered a new one lol that's the only solution I could come up with
galaxy s3 softbrick
jsmoof21 said:
I gave up an ordered a new one lol that's the only solution I could come up with
Click to expand...
Click to collapse
hey jsmoof21 did you got you galaxy s3 back from sprint, im asking because my is softbrick and i need to know if i can bring mine to sprint and getting a replacement because my dont start up eather. thanks
bonao1851 said:
hey jsmoof21 did you got you galaxy s3 back from sprint, im asking because my is softbrick and i need to know if i can bring mine to sprint and getting a replacement because my dont start up eather. thanks
Click to expand...
Click to collapse
Do you get a screen at all? You say you're softbricked but you also say it doesnt start up. If you are really just softbricked then you have a screen too, in which case you'll just look like an ass going to sprint because they will see you fuucked with it and laugh you out the store. If you are hardbricked then you would have just a black screen. If you have a screen, do some reading like you shouldve done in the first place and fix it yourself.
bonao1851 said:
hey jsmoof21 did you got you galaxy s3 back from sprint, im asking because my is softbrick and i need to know if i can bring mine to sprint and getting a replacement because my dont start up eather. thanks
Click to expand...
Click to collapse
Mine was hard bricked and it couldn't be turned on period. If yours is soft brick then you should be able to get it back into download mode but you can't get it to turn on at all, then you have a hard brick. I went to sprint and got a brand new one because they couldn't fix it either. So unless they can fix it you will have to get a new one!
Also Hard Bricked.
18th.abn said:
If your getting a light, even temporary, I'd boot a tinycore Linux and see what mode its in for that 10 seconds
Click to expand...
Click to collapse
On the advice for taking the battery out and trying to get into download mode, I tried and now without my battery in I get my red light but still no luck on download mode. any advice like "tinylinux". Sorry not a noob but not a pro so whereever that middle area is is where I stand. Thanks in advance.
UNBRICK
Hi please follow these steps
1 download stock firmware below
http://forum.xda-developers.com/showthread.php?t=1737859
2 download clock work mod (CWM-Recovery-LTE-SGS3-Sprint-v5.zip) below
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
3 copy the CWM recovery zip to ext sd card using some card reader trough a pc and insert the sd card into your SGS3.
4 now i still presume your phone is still booting but gets stuck at samsung boot screen. reboot to ODIN mode and flash the
CWM file downloaded earlier with "AUTOREBOOT" unchecked.
5 once the cwm is flashed remove the usb cable and remove battery, hold for a sec and put the battery back again.
6 Reboot to recovery VOL UP + HOME Button + POWER, you should boot to CWM.
7 do DATA WIPE 3 times
8 do CACHE WIPE 3 times
9 under advanced do DALVIK CAHCE WIPE 3 times
10 click on reboot, as soon as you do it the vibrates, remove battery as soon as it vibrates.
11 put the battery back again and boot to odin mode again
12 flash stock firmware with F.RESET and AUTO REBOOT checked
13 your phone should reboot,
14 wait for it
please let me know if it helped.
Please do as it says without step number 3
pvinodnayak said:
Hi please follow these steps
1 download stock firmware below
http://forum.xda-developers.com/showthread.php?t=1737859
2 download clock work mod (CWM-Recovery-LTE-SGS3-Sprint-v5.zip) below
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
3 copy the CWM recovery zip to ext sd card using some card reader trough a pc and insert the sd card into your SGS3.
4 now i still presume your phone is still booting but gets stuck at samsung boot screen. reboot to ODIN mode and flash the
CWM file downloaded earlier with "AUTOREBOOT" unchecked.
5 once the cwm is flashed remove the usb cable and remove battery, hold for a sec and put the battery back again.
6 Reboot to recovery VOL UP + HOME Button + POWER, you should boot to CWM.
7 do DATA WIPE 3 times
8 do CACHE WIPE 3 times
9 under advanced do DALVIK CAHCE WIPE 3 times
10 click on reboot, as soon as you do it the vibrates, remove battery as soon as it vibrates.
11 put the battery back again and boot to odin mode again
12 flash stock firmware with F.RESET and AUTO REBOOT checked
13 your phone should reboot,
14 wait for it
please let me know if it helped.
Please do as it says without step number 3
Click to expand...
Click to collapse
DUDE THANK YOU SO MUCH OMG
I had same stuck at boot screen but could get odin download mode still this literally saved my phone thanks your awesome!
I Screwed Up
Hello All,
I wish my first post was not for the issue of a bricked phone but it seems like it might be.
I have the sprint samsung S3 and was installing the http://forum.xda-developers.com/showthread.php?t=1905676 Rom and something seems to not have gone right.
I got an error and when I went to restart my phone I get nothing...
Thanks for the help and if I have no options would anyone like to by a lovely almost new GS3?
Jonathan
jonathanod said:
Hello All,
I wish my first post was not for the issue of a bricked phone but it seems like it might be.
I have the sprint samsung S3 and was installing the http://forum.xda-developers.com/showthread.php?t=1905676 Rom and something seems to not have gone right.
I got an error and when I went to restart my phone I get nothing...
Thanks for the help and if I have no options would anyone like to by a lovely almost new GS3?
Jonathan
Click to expand...
Click to collapse
I think you may have flashed your Sprint GS3 with an international GSM GS3 ROM. I think you are not going to be able to recover from that.
m20120 said:
I think you may have flashed your Sprint GS3 with an international GSM GS3 ROM. I think you are not going to be able to recover from that.
Click to expand...
Click to collapse
why are people still doing this?
nicholaaaas said:
why are people still doing this?
Click to expand...
Click to collapse
Some people really should get an iPhone...
Sent from my SPH-L710 using xda app-developers app
WHYDavid said:
Some people really should get an iPhone...
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Totally agree.That or a motorola
Try YouTubeing QBKing77 on his video for bricked S3's
Good luck. There will be a way to unbrick. Just have to find the right method.
[JellyBombed S3 via XDA premium]
Hey guys, today I decided to root my Galaxy Nexus on Android 4.2.2, so far so good. The root is done and I wanted to install the Avatar ROM but there's a problem. After the installation my Nexus reboots and the Avatar Bootlogo appears but nothing happens (I think it was a bootloop). I waited about 15 minutes and then I decided to restore my backuped Stock ROM but it would be nice to try something new, the Avatar ROM. Can anyboby help me please? Don't know what went wrong and I really need help from you :s. Thanks a lot.
Sounds like someone didn't follow directions and do a factory reset from recovery
Sent from my Galaxy Nexus
Pirateghost said:
Sounds like someone didn't follow directions and do a factory reset from recovery
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ah... No, I did follow them and I got same result on KitKat Avatar.
are you sure
Hmm waiting 15 main cannot be called boot looping because if it was a boot loop then it can be easily spotted since galaxy nexus dims the brightness few seconds before completion of boot
Sometimes it takes more time then you think
I'll preface this by saying I have searched the forums here and after reading a few threads about similar problems to mine, I haven't been able to find a solution. So, I'm making a new thread in the hopes you fine individuals will be able to help me troubleshoot what's going on.
The problem:
I was running CM 12 on my T800 for a while, but after some bugs and random reboot issues, I decided to give the new IronRom a shot. I went ahead and flashed it through TWRP and everything went swimmingly. I was able to set up the tablet and use it for a while. However, two days ago when my wife was using the tablet, it randomly restarted while she was using it and then froze at the Samsung startup screen. It would show the screen, then blink to black like the tablet had restarted, show the screen and repeat this about 4 or 5 times before freezing at the Samsung start screen.
What I have tried doing:
First thing I tried was home+power+volume up to get into TWRP and do a wipe and start over. But I cannot get into recovery. Once the tablet is frozen the only way to get it to restart is with a hard reset power+volume down, nothing done after that seems to make any difference.
Second, I realized I could still get into download mode, so using ODIN I tried going back to stock. Flashed the stock rom for my region but when Odin is done with the initial flash, it reboots the tablet and everything is the same. Frozen at the Samsung screen.
I've tried flash TWRP again, but once the tablet reboots after download mode, it just freezes at the Samsung screen.
Any suggestions at this point would be welcome.
last time i had this same trouble but on my T705. I had to wipe everything including the internal storage. only then the device boot properly.
edan1979 said:
last time i had this same trouble but on my T705. I had to wipe everything including the internal storage. only then the device boot properly.
Click to expand...
Click to collapse
I would love to be able to, but as I said in the original post, I can't get the tablet to enter recovery, so I can't wipe it. The only thing I can get it to do is boot into download mode.
Hi, sorry to be that guy who bumps threads, but I'm still sitting here with a tablet I can't use and no more ideas on what I can do to fix it. I'd really appreciate any ideas at this point. Thanks again!
Drschplatt said:
Hi, sorry to be that guy who bumps threads, but I'm still sitting here with a tablet I can't use and no more ideas on what I can do to fix it. I'd really appreciate any ideas at this point. Thanks again!
Click to expand...
Click to collapse
I had similar experience, and even started downloading official samsung image, with odin etc. However it looks like I was able to enter recovery if rebooting using the following sequence:
- power-vol_down-home combination until the screen goes black
- moving finger from volume-down to volume-up
-> waiting a few seconds (less than 10) until recovery screen shows up.
Then I just reinstalled the good old cm 12.1 (instead of the failing lineageos 14.1), and then all happy again.
Drschplatt said:
Hi, sorry to be that guy who bumps threads, but I'm still sitting here with a tablet I can't use and no more ideas on what I can do to fix it. I'd really appreciate any ideas at this point. Thanks again!
Click to expand...
Click to collapse
Hallo.
Try this https://forum.xda-developers.com/ga...k-disaster-t2838473/post54618555#post54618555.
It work for me, when i have similar problem.
Carlosk1966 said:
Hallo.
Try this https://forum.xda-developers.com/ga...k-disaster-t2838473/post54618555#post54618555.
It work for me, when i have similar problem.
Click to expand...
Click to collapse
Thanks for the link. I tried it but never could get the tablet turned off to see the battery icon. When I used the method in the link it just returned to the Samsung Galaxy Tab S startup screen
Drschplatt said:
Thanks for the link. I tried it but never could get the tablet turned off to see the battery icon. When I used the method in the link it just returned to the Samsung Galaxy Tab S startup screen
Click to expand...
Click to collapse
Well that is not good. Like i said, it allways work for me, when i get bootloop.
Hello!
I purchased a Galaxy S6 two days ago and have yet to really use it...
I wanted to have a fully fresh phone so i flashed the latest firmware available to me (USA, Sprint, sm-g920p, zerofltespr, QB1)
Everything flashed as normal (not my first S6, I'm familiar with ODIN) but upon booting up the first time it goes to a blue screen that says initializing update.. then the progress bar goes to 32% and then says erasing.. then it reboots and i get to optimizing apps (starts at some random number 8 of 33, 13of 33, 12 of 33, etc.) and then reboots and goes back to optimizing apps again... it's maddening!!!
I've tried at least 5 different firmwares, all with the same result. Always to 32% then bootloop on optimizing apps
I've tried using the PIT file for my phone along with flashing the firmwares, same result
When i try to enter recovery to wipe cache or factory reset, i get the blue screen that says initializing update then i get some yellow exclamtion warning for a second and i get to recovery... i wipe cache, reboot... same boot loop result
Back to recovery, factory reset, reboot... same boot loop result trying to optimize apps.
I've tried adb sideloading a couple different ROMS but those just bootloop at the Galaxy S6 logo splash screen.
I've run out of ideas for what to do to fix this.. every great once in awhile ill get to the welcome screen and itll get to Setting up your device for first time use... then itll just reboot and go right back to that screen... i havent been passed that once...
Please any ideas would really be great. Thanks
Saafir said:
Let the phone battery run dead. Then charge 15% and boot it. Problem will likely have fixed itself. [Not joking]
Click to expand...
Click to collapse
Do what @Saafir says, it usually works.
Saafir said:
Let the phone battery run dead. Then charge 15% and boot it. Problem will likely have fixed itself. [Not joking]
Click to expand...
Click to collapse
thanks so much for your response... Just got to work for my 12 hour shift... ill let it boot loop til it dies... im so curious to see if thats what will work..
thanks again!
Edit: just noticed your profile.... GO BLUE!!!!!!!!! (huge Michigan fan here) Aint that right, Koop?
blacksantron said:
thanks so much for your response... Just got to work for my 12 hour shift... ill let it boot loop til it dies... im so curious to see if thats what will work..
thanks again!
Edit: just noticed your profile.... GO BLUE!!!!!!!!! (huge Michigan fan here) Aint that right, Koop?
Click to expand...
Click to collapse
If you get this going, please send me (or post here via file attach) the file: /proc/last_kmsg -- you need to be rooted to get that so hopefully you are. To get this right, you need to copy that file to /sdcard (or somewhere there) and only on the first successful boot.
I want to see what is complaining so I can (hopefully) write a fix for future sufferers that won't require the reboot til dead game.
Sent from my iPad using Tapatalk
tdhite said:
If you get this going, please send me (or post here via file attach) the file: /proc/last_kmsg -- you need to be rooted to get that so hopefully you are. To get this right, you need to copy that file to /sdcard (or somewhere there) and only on the first successful boot.
I want to see what is complaining so I can (hopefully) write a fix for future sufferers that won't require the reboot til dead game.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Right on, unfortunately i wont be rooted since Im bootlooping right after flashing stock firmware..
I cant believe that worked!!!!!!!!!!!!!!!!
If you were anywhere near me id buy ya a beer... i swear i tried everything for two days... so many firmwares i downloaded... oh my word...
thanks so much1
blacksantron said:
I cant believe that worked!!!!!!!!!!!!!!!!
If you were anywhere near me id buy ya a beer... i swear i tried everything for two days... so many firmwares i downloaded... oh my word...
thanks so much1
Click to expand...
Click to collapse
If you ever need, I try to keep the latest firmware posted here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Hey guys I'm in need of some help, I've flashed my s6 sm-g920p phone about 7 times and it still won't boot up it gets to the lte screen just before startup and keeps rebooting what might be the problem ? Might it be the battery is not good ?