Develop Bugs

[Fix] 4.3 ROMs stuck on splash screen after first reboot

For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).

Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app

bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.

spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!

bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.

Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.

Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.

This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:

spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!

I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.

Solved
Thanks, also works for i727 skyrocket

wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?

Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.

spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?

Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.

spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?

shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse

Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Help with reverting back to stock

so i have a rooted at&T galaxy s3 on the latest stock firmware which i guess is 4.3. i tried flashing resurrection rom which was kit kat and it failed. so i restored my back up and the phone would get stuck on the splash screen. so i formated the whole phone and forgot to save my backup to my sdcard. twrp now says that i have no OS installed and also says i am not rooted anymore. im scared and need a little assistance. i just want to get it going.

Just flash the latest TWRP, copy a custom ROM to your phone, boot into TWRP, and flash it.

audit13 said:
Just flash the latest TWRP, copy a custom ROM to your phone, boot into TWRP, and flash it.
Click to expand...
Click to collapse
i bought a micro sc card reader and transfered a superuser zip and an old 4.3 beanstalk rom. it flashed fine last night. i used my phone all day and downloaded the latest 4.3 beanstalk rom and just tried to flash it and it FAILED. This is the second time i had a flash fail. I tried flashing that old beanstalk rom again and it failed too! what the heck???? my battery is a little low.....does twrp have some kind of safety built in where it wont flash if bettery is low?

ok...so i flashed cwm because im more familiar it than twrp. then i flashed an old slimbean 4.3 rom i had. everything worked fine and the phone booted up perfectly. i dont want slim bean so i rebooted into cwm and tried to flash the newest 4.3 beanstalk rom and it failed.....why?

scorey03 said:
ok...so i flashed cwm because im more familiar it than twrp. then i flashed an old slimbean 4.3 rom i had. everything worked fine and the phone booted up perfectly. i dont want slim bean so i rebooted into cwm and tried to flash the newest 4.3 beanstalk rom and it failed.....why?
Click to expand...
Click to collapse
Did you install the latest CWM? Is the 4.3 Beanstalk based on Kit Kat?

audit13 said:
Did you install the latest CWM? Is the 4.3 Beanstalk based on Kit Kat?
Click to expand...
Click to collapse
no its not based on kitkat. i flashed an older version of cwm via odin. i figured i could just update it with rom manager. i tried to update cwm to the latest verion and it fails everytime. so...i downloaded root checker from the play store and it says im not rooted. i need to fix this lol

im running a custom rom but yet root checker says its not rooted...hmm

Flash the latest Philz and. Validus as I know that is a rooted ROM. Personally, I don't use ROM manager.

scorey03 said:
im running a custom rom but yet root checker says its not rooted...hmm
Click to expand...
Click to collapse
What custom Rom is this?
Sent from my HTC One using Tapatalk

I'm on slimbean 4.3 and I've lost root. I want root back so I can get rid of this ROM. Ive flashed supersu multiple times with cwm..but I still do not have root access.

So I guess my question now is.....how do I get back to stock rooted? Im on slimbean 4.3 without root access.

scorey03 said:
I'm on slimbean 4.3 and I've lost root. I want root back so I can get rid of this ROM. Ive flashed supersu multiple times with cwm..but I still do not have root access.
Click to expand...
Click to collapse
Rooting is not needed to flash another ROM. Just boot into recovery, wipe, and flash another ROM.

audit13 said:
Rooting is not needed to flash another ROM. Just boot into recovery, wipe, and flash another ROM.
Click to expand...
Click to collapse
I tried and it failed......

scorey03 said:
I tried and it failed......
Click to expand...
Click to collapse
What rom and which recovery did you try?

I suggest you Odin to stock and try all this again
Sent from my ATT Samsung Galaxy SIII using TapaTalk

crazymonkey05 said:
I suggest you Odin to stock and try all this again
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I agree 100%. Can you tell me where I can get stock 4.3 firmware?

Here is a repository with a lot of stock firmwares http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my ATT Samsung Galaxy SIII using TapaTalk

scorey03 said:
I agree 100%. Can you tell me where I can get stock 4.3 firmware?
Click to expand...
Click to collapse
There is no stock ATT 4.3 ROM because ATT only released 4.3 as an OTA update. Do not flash any 4.3 firmware (even from sammmobile.com) unless it has been compiled for installation via Odin. Check the development threads for firmware that can be flashed via Odin.

crazymonkey05 said:
Here is a repository with a lot of stock firmwares http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ok. im going to flash I747UCUEMJ2.7z which came from that link/thread you posted via odin.

If you got the phone on 4.3 you need to flash mjb or else you will brick the device
Sent from my ATT Samsung Galaxy SIII using TapaTalk

[Q]Need clarification for rooted rogers note 2, android 4.4

Hello, I recently just updated my Rogers SGH-i317M to 4.3, which then downloaded a system update which put it at 4.4. I was running Jedi X20, which is based on 4.1.2, when I first tried updating, I flashed the "4.3param_tz" file in odin, and was left with an error screen saying I need to recover using Kies, so I downloaded the official release, flashed via odin, and thats how I got to where I am now. I want to try the "Ditto Note 3" rom, "Sky Note Air 4.3", "Mean Bean" and "Beanstalk". My main question is, can I just start flashing these roms like I was before on 4.1.2, or do I need to use the specific kernel listed on their page? Before you needed a specific kernel to run a touchwiz rom or an aosp rom, so is it still the same? Or can I use my stock 4.4 kernel and try both aosp and tw roms now? If so could you point out the kernels I would need? And educate me on anything else I should know about before flashing 4.3 and 4.4 roms, (I'm not worried about warranty), this would be greatly appreciated. Thanks for your time in reading this and helping me out, much appreciated!!

Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.

just_visiting said:
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
Click to expand...
Click to collapse
I did all that except flash SU 1.99, so I tried flashing SKynote Air and it didnt work, upon restarting my phone it said no os is available. So I tried restoring from the backup I made of the official 4.4.2 Samsung rom in twrp, didn't work. Tried Odin, didn't work. Then I tried flashing the Skynote rom again and it worked. So I'm afraid of flashing any other roms now.

Sgh-i747 4.4.2

Hello all. I just received a galaxy s3 from my sister in law running 4.4.2. I am aware I can't downgrade the complete firmware using Odin. The phone it's rooted. My question is what can I do with this thing as far as playing with roms and what not? Can I only install 4.4.2 based roms? Can I even unroot? I have been rooting and installing roms for years now but never have a phone felt more unfriendly before this. Thanks in advance.

Is the phone running stock 4.4.2?
You can install a custom recovery to the phone, copy some custom ROMs to an external SD card, and try out a bunch of ROMs.

Yeah its stock 4.4.2 rooted with clockwork mod recovery. Do the roms have to be 4.4 or 4.4.2 based? Tried cyanogenmod 4.3 and failed. I pretty much would like to flash via odin to go back to stock unrooted but 4.4.2 was over the air. Got 4.3 via sammobile but that fails. Kies won't show my device for firmware recovery. Shows it as normal to sync.

What error did you get when trying to flash CM10.2? Is your CWM up to date?
I would have assumed that CM10.2 would be comaptible with your KK bootloader and modem.
Do not make anymore attempts to flash 4.3 via Odin. This could result in a bricked phone because a KK modem on a 4.3 bootloader cannot be fixed using any method available on XDA.

Yeah I'm aware of the boot loader and modem downgrade issue. Tried odin once and just left it as is.

Is your CWM up to date? What error did you get when trying to flash CM10.2?

I don't remember the error. According to Rom manager, my recovery is up to date

What version is the cwm? I prefer to manually flash a custom recovery instead of relying on ROM manager.

Cwm 6.0.4.7. I've always used rom manager except for my galaxy nexus. Flashed with windows terminal and fastboot.

Since CWM is up to date, try flashing the most recent CM11.

Older cm roms, and any older roms should run fine on NE4. Some may not flash though, such as cm10. This is because the updater script doesn't include NE4 as it wasn't out when the rom was built. If you edit the script to make it flash, any of the available roms should run just fine.
As it stands though, the easiest thing would be to do as audit13 suggested and flash cm11. That and most other recent roms should flash just fine w/o any extra work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

well, after downloading the most recent cm11 nightly and gapps, rebooted into recovery and wiped. when trying to flash cm11, sd card not mounting. couldn't mount, restored a backup only to be greeted to a display that would not go to sleep and a fury of app and processes stopping pop ups. settings-accounts-backup and reset-factory data reset-etc did nothing but ask for a password. did it through recovery to a perfectly working phone with baseband version: unknown, IMEI: unknown, IMEISV: unknown. flashed the NE4 modem Doc posted in another forum, no dice. same message from cm as before. this time i remember. it was a bunch of basebands not including NE4.

And getprop ro.bootloader says NE4. first said unknown but maybe i typed it wrong.

Got it all back running. tried the S3Rx NE4 aroma zip that would end with installation aborted. found enewman17's post on updating using a stock-rooted 4.4.2 zip after flashing Doc's modem zip. all is well! So thank you DocHoliday77, and thank you enewman17!

Glad you got it working!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Hangs on setup

hey can anyone help me? i've recently reverted my note 2 back to stock via odin and everything seemed fine. When the phone booted and i went through the setup process it always hangs. No matter what i do it always hangs. I've tried reflashing it and rebooting it over and over again but it always hangs. anyone know why this keeps happening?

Are you flashing the latest stock ROM? You're performing a factory reset before booting the ROM for the first time?

audit13 said:
Are you flashing the latest stock ROM? You're performing a factory reset before booting the ROM for the first time?
Click to expand...
Click to collapse
Yup latest stock rom, and before i flashed via odin i deleted my previous rom via twrp and formatted internal storage so its 100% clean

I've downgraded a Note 2 sgh-i317m to 4.1.1 from 4.4.2 by flashing a stock 4.1.1 ROM from sammobile.com in order to network unlock the phone. Flashing the stock 4.1.1 ROM tripped knox and could be installed via Odin because the 4.1.1 ROM from sammobile.com did not contain a 4.1.1 bootloader so I wound up with a stock 4.1.1 ROM on a 4.4.2 bootloader. After unlocking, I flashed the stock 4.4.2 ROM again and the the phone worked as it should.
I'm not sure which phone you have and I'm not sure downgrading and upgrading will work in your case but it's something you may want to look into.

audit13 said:
I've downgraded a Note 2 sgh-i317m to 4.1.1 from 4.4.2 by flashing a stock 4.1.1 ROM from sammobile.com in order to network unlock the phone. Flashing the stock 4.1.1 ROM tripped knox and could be installed via Odin because the 4.1.1 ROM from sammobile.com did not contain a 4.1.1 bootloader so I wound up with a stock 4.1.1 ROM on a 4.4.2 bootloader. After unlocking, I flashed the stock 4.4.2 ROM again and the the phone worked as it should.
I'm not sure which phone you have and I'm not sure downgrading and upgrading will work in your case but it's something you may want to look into.
Click to expand...
Click to collapse
I've managed to get the phone working (N7100) and it seems to run fine on Nougat. I did some testing and indeed it would always crash on setup with kitkat roms. I wonder why this is the case....

It is strange that kit kat causes a problem.
Have you tried using a different version of twrp to wipe the system before flashing with Odin? Can't think of anything else that may solve the problem.