Hey guys, I'm REALLY hoping someone can help me. My phone was rooted on 4.3 and I stupidly accepted the KitKat OTA update without unrooting, and now my phone wont boot pass the AT&T logo. I have tried factory data wipe, doing an emergency firmware recovery on kies, tried flashing a stock rom on odin, and tried putting stock update on sd card and doing it that way, but it either wont flash or STILL wont boot past the at&t logo. Besides the root access, everything on my phone was stock. I just want to be able to use my phone again! Can someone please help me? I NEED my phone lol
I just installed a custom recovery. Now what?
Have you waited a bit for the boot process to go through it took me like 5 minutes after a ota to KK.....IF the little att chime at the att logo by all means it should boot
yeah I let it sit like half an hour...
Did you get the att chime?
KillaMike99 said:
I just installed a custom recovery. Now what?
Click to expand...
Click to collapse
Can you boot into your custom recovery? If you can, try flashing a custom KK ROM.
yes I get the AT&T chime. sometimes the chime is real choppy tho. what KK rom should I flash?
Any of your choice
do you recommend any? Im new to custom firmwares on android
Try Carbon or Valudus.
Thanks Guys! I installed a custom ROM and its working like new! I dont think I can ever get stock back, but I dont see much of a difference. Now that my warranty is gone, whats the benefits of having a custom ROM and what one has the best features? I am on hyperdrive ATM, but I would like a good kitkat rom
same issue, only....
I can not get ANY rom to get past the boot screen,.... I have no idea why it is getting stuck...
I have tried CM - various nightlies and screenshots. validus, c-rom, all to no avail.
i am going nuts over here...any one know what I might be doing wrong?
i have tried all the formating, cache, dalvik wipe, format system, reset all user data etc....
could it be a kernel I need?
Related
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Flash the stock ROM on the phone. You have access to recovery so use it then after you verify you can boot with the stock ROM then try flashing another ROM on again.
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
No idea what caused you from being able to boot to this issue but this is my advice.
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
Click to expand...
Click to collapse
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
polish_pat said:
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
Click to expand...
Click to collapse
Go into cwm, do a wipe and also go into advanced and wipe dalvik. You should then be able to reflash your custom rom to fix your boot loop. If thats successful then go back to cwm and make a NANDROID backup so they have a restore point if anything goes wrong in the future.
If you want to flash back to stock its quite simple and can all be done from my ToolKit. Its basically going to http://code.google.com/android/nexus/images.html and downloading the latest factory rom for your model, moving it to the correct folder in the ToolKit and then selecting option 8 from the ToolKit to extract the images and flash it.
Mark.
polish_pat said:
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Click to expand...
Click to collapse
I've run into the same issue tonight going back to Apex 1.0.2 from the 4.0.4 leak. I'm trying the suggestion below to wipe and re-flash the ROM. I'll report back when I'm finished.
Edit: Yep, it worked!
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
JaedenRuiner said:
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
Click to expand...
Click to collapse
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
lvpre said:
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
Click to expand...
Click to collapse
I eventually found a 4.4.2 full stock ROM and was able to get that over. Of course this wasn't until after some sight suggested a wipe user data could help, so I'm re-building the phone from the base...*sigh* It happens. I'm about due for an upgrade anyway, so I can make due.
Thanks for the response,
J"SD"a'RR
Recently tried several times to flash cm or other aosp roms. Always get stuck on boot screen. Only roms that boot are tw based. So are aosp roms not possible on my locked bootloader? Is my bootloader locked lol?
Did you do a full wipe before you flashed?
Full wipe / factory reset.
Only way to go from TW to cm.
Pp.
Yes. Using twrp. Used the standard wipe method. Also tried wiping caches and the system. Ive even formatted my system. Still always stuck on boot screen. It is the CM boot screen however.
PanchoPlanet said:
Full wipe / factory reset.
Only way to go from TW to cm.
Pp.
Click to expand...
Click to collapse
So it is possible to go to a CM rom even with the MK2 bootloader. Can anyone confirm this?
Take a look at this,
Galaxy S4 How To Install CyanogenMod 11 CM 11 Kit…: http://youtu.be/gUhlLgMA-cA
Pp.
Looks like only TW roms for me.......Thanks everybody.
Cm isn't as bad on a device that doesn't need to be super reliable, like my phone, I need it to be on point at all times having a disabled child in school and never knowing when the school may call for whatever reason. I do run it on my Gal Tab 2 and it runs great, no issues and great battery life.
Pp.
Alex1212 said:
So it is possible to go to a CM rom even with the MK2 bootloader. Can anyone confirm this?
Click to expand...
Click to collapse
I have a T-Mobile S4 with MK2 and I've been running CM since I bought it.
Sent from my SGH-M919 using XDA Free mobile app
Seriously? Weird. Are u sure its not your modem thats mk2?
Alex1212 said:
Seriously? Weird. Are u sure its not your modem thats mk2?
Click to expand...
Click to collapse
Bootloader or modem doesn't make a difference, even with NH7 bootloader you should be able to flash any rom
Now I'm confused...So then what's the big deal about locked/unlocked bootloaders? Any idea why aosp roms won't boot on my phone? I'm fairly positive I've done every wipe and my twrp is the most recent one....thanks in advance
Alex1212 said:
Now I'm confused...So then what's the big deal about locked/unlocked bootloaders? Any idea why aosp roms won't boot on my phone? I'm fairly positive I've done every wipe and my twrp is the most recent one....thanks in advance
Click to expand...
Click to collapse
We don't have locked bootloaders.. Don't know, try different kernel after you flash or another recovery like cwm or philz
I thought they locked them with the mk2 bootloader when they added knox. Ill try again ive tried flashing kt kernel after flashing rom and gapps(made sure it wasnt the tw version). Ill try with cwm recovery. Thanks for trying to help. Ill make a backup of my current rom and try again.
Alex1212 said:
I thought they locked them with the mk2 bootloader when they added knox. Ill try again ive tried flashing kt kernel after flashing rom and gapps(made sure it wasnt the tw version). Ill try with cwm recovery. Thanks for trying to help. Ill make a backup of my current rom and try again.
Click to expand...
Click to collapse
If they were locked you wouldn't have been able to flash a custom recovery
Locked bootloaders are seen on the Verizon and att varients of the S4 , that's where safestrap comes into play. Locked means you can't flash a recovery/custom Roms etc. T-Mobile comes with unlocked BL allowing us to customize our phones. NH7 doesn't allow to you to downgrade BL's, not the same as locked BL. Its a Knox thing, and that only messes with warranty.
Pp. ?
Tried flashing liquidsmooth last night and again stuck at boot screen. Wiped phone flashed rom then gapps. Also tried wipe rom, gapps, kt kernel. Waited 30 minutes then just went back to backup. Thanks for clearing this up guys. Any suggestions?
Alex1212 said:
Tried flashing liquidsmooth last night and again stuck at boot screen. Wiped phone flashed rom then gapps. Also tried wipe rom, gapps, kt kernel. Waited 30 minutes then just went back to backup. Thanks for clearing this up guys. Any suggestions?
Click to expand...
Click to collapse
Can you state exactly what you wipe?
In twrp I use the standard wipe. I forget what it's called but it's the top right button. Brings you to a screen that says that this is all u need to wipe for flashing a new rom. I think it's basically a factory reset. In addition to that I go in advanced wipe and do both caches. I've also even tried wiping system and a few times I've even formatted my data which I think deletes absolutely everything. I tried using Odin to go back to complete stock and re root then Odin twrp. Still sits at boot screen unless I flash a tw style rom...... I'm starting to think it might not even be worth it anymore, not even sure what I'm missing out on honestly. It's just really bugging me that aosp roms won't boot.
That is rather odd, they boot.. Only other thing to try is to flash a different kernel or switch recovery to cwm or philz
So I posted a thread here months ago asking for help but got no help so I'm trying again. Basically the official kitkat update from samsung severely messed up my tablet to the point where it's almost unusable. My question is, is there any way i can do like an ultimate, complete wipe of the tablet? Like wipe partitions, recovery, everything?
I've tried installing nolekat and tranchidakat with still the same problems. I've flashed both the jellybean stock rom and the kitkat stock rom through odin with still the same problems. I even clicked re-partition under odin hoping that would help but still no luck.
Also the problems I'm having are constant reboots, processes and apps just stopping such as systemui, settings, and basically all of my system apps and apps installed from the playstore.
This is a very irritating problem I'm having to the point where I just wanna destroy my tablet. I don't have the money to send it to samsung so I've been trying to find another solution.
Any help at all would be greatly appreciated!
I maybe not have the answer but the reason. How did you update you device kies or OTA. If a custom recovery was install your device it's maybe brick. Me i probably test something like flash a custom recovery only and them flash a rom through to there. Or search to unbrick flash somethings like that.
nannaniel said:
I maybe not have the answer but the reason. How did you update you device kies or OTA. If a custom recovery was install your device it's maybe brick. Me i probably test something like flash a custom recovery only and them flash a rom through to there. Or search to unbrick flash somethings like that.
Click to expand...
Click to collapse
It was an OTA. I had no custom recovery installed prior to the update
I have a SPH-L710 with a stock ROM and CWM root, I just tried to flash a boot animation and am now stuck in a boot loop. I did not make a backup before I tried this. I have wiped cache,div and did fact reset and can not get out of boot loop...................PLEASE HELP
Runing KK 4.4.2 on VIRGIN MOBILE/SPRINT NETWORK
aanddink said:
I have a SPH-L710 with a stock ROM and CWM root, I just tried to flash a boot animation and am now stuck in a boot loop. I did not make a backup before I tried this. I have wiped cache,div and did fact reset and can not get out of boot loop...................PLEASE HELP
Runing KK 4.4.2 on VIRGIN MOBILE/SPRINT NETWORK
Click to expand...
Click to collapse
You most likely will have to flash a stock rom using Odin on the computer.
The only problem with that is if you had to get your phone flashed to Virgin Mobile like I did with PagePlus, it may or may not erase those critical settings. I could never get a clear answer on that, but it is best to play it safe and assume it will. However, your phone should be functioning once again.You will however have to re-root the phone, and might as well install TWRP. All of this can be done through Odin.
Alternatively, if you have a custom recovery installed and a rom or two on your sdcard, you could try to flash the rom instead of going all the way back to stock. That would help ensure your carrier settings arent wiped related to Virgin, as it could if you were to flash back to stock.
Then for the love of god, devil, or whoever you believe in... make a backup once you are fixed and back up and running!! They are perfect and extremely helpful for situations like this.
Rawb0Ss said:
You most likely will have to flash a stock rom using Odin on the computer.
The only problem with that is if you had to get your phone flashed to Virgin Mobile like I did with PagePlus, it may or may not erase those critical settings. I could never get a clear answer on that, but it is best to play it safe and assume it will. However, your phone should be functioning once
again.You will however have to re-root the phone, and might as well install TWRP. All of this can be done through Odin.
Alternatively, if you have a custom recovery installed and a rom or two on your sdcard, you could try to flash the rom instead of going all the way back to stock. That would help ensure your carrier settings arent wiped related to Virgin, as it could if you were to flash back to stock.
Then for the love of god, devil, or whoever you believe in... make a backup once you are fixed and back up and running!! They are perfect and extremely helpful for situations like this.
Click to expand...
Click to collapse
Thank you for the reply and thank you for the help. i did get it to un-bootloop, i unfortunately did not have a rom backup, now i have a full backup zip using CMW on my sd card which i hope would fix this in the future. nothin worked until i found a good boot animation, i should have look for more firat but.once i re-flashed the 3rd one it booted.
aanddink said:
Thank you for the reply and thank you for the help. i did get it to un-bootloop, i unfortunately did not have a rom backup, now i have a full backup zip using CMW on my sd card which i hope would fix this in the future. nothin worked until i found a good boot animation, i should have look for more firat but.once i re-flashed the 3rd one it booted.
Click to expand...
Click to collapse
You have to have the proper boot animation binaries before you go flashing boot animation. Those zips are for flashing in custom roms that already have the proper binaries.