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

[Q] Trying to downgrade from 4.4.2 (Cyanagenmod 11) to 4.1.2 stock (T999UVDMD5)

As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?

huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.

Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.

Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?

Yes you can go back to 4.3 Stock.

Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.

huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk

serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.

Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747

You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk

nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.

Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.

nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.

[Q] Can't boot after 4.3 ota from 4.1.1

Okay so i got a note 2 and had to odin it to 4.1.1 and it worked fine. then got the sim reader working and att ota popped up so i downloaded it and it download a 302 mb file rebooted installed and completed and now it wont boot. now i have tried many different rom, kernals, recoverys, and everything through odin but it wont go past the note 2 logo and wont boot into recovery. really need help

Look up a thread by mrrobinson. Root no tripping counter. It has most stock Roms with root injected.In one of the posts in that thread. It will explain how to recover from this. You have to pull the battery and reflash while phone is still connected. I'm sorry I can not remember exact instructions on how to do this. But, it is in that thread. Wish I could help further. It was a while back when this happened to me. Would post the link if I could..one last thing. Did you do a factory reset after the update? Can you get in to stock recovery?
Sent from my A200 using xda app-developers app

No after the ota and after odin 4.1 it hangs and when I do a battery pull then try to go to recovery(stock) I just shows the note 2 logo. I've tried using the same files that worked last time but I guess it has 4.3 leftover not letting it boot and I can't get into the recovery.

Same instructions as what Zen and I told you to do in your post in the How to OTA to 4.3 MK6 from LJ2 4.1.1 thread.
No need to post 469 times. Someone will answer if the question can be answered.
Yours was a few hours after you posted.

[Q] I bricked my note 2 sph-l900 please help

I think i Have bricked my phone I was on the new 4.4 I flashed back to [ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset .. And then was taking the OTA back to 4.3. When it rebooted it gets stuck on the Samsung note2 screen and sits there. I can't get intoo any kind of recovery it brings up the connect to kies screen that says Firmware Upgrade encountered an issue connect to kies. I have tried flashing recovery again with odin to no avail I have also tried flashing the unbrick.tar file that is floating aroung here. I cant get anything to flash everything fails. I can get into download mode.. PLEASE HELP!!!!

jyerly said:
I think i Have bricked my phone I was on the new 4.4 I flashed back to [ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset .. And then was taking the OTA back to 4.3. When it rebooted it gets stuck on the Samsung note2 screen and sits there. I can't get intoo any kind of recovery it brings up the connect to kies screen that says Firmware Upgrade encountered an issue connect to kies. I have tried flashing recovery again with odin to no avail I have also tried flashing the unbrick.tar file that is floating aroung here. I cant get anything to flash everything fails. I can get into download mode.. PLEASE HELP!!!!
Click to expand...
Click to collapse
Looks like your having the same issue I was having. Check the 4.4 update thread about rwilco's modified restore. The one with the sboot or boot.ini in it works. Trust me It works I just got my phone back to 4.3 then back up to 4.4. If u have any questions pm me.

puffyjello said:
Looks like your having the same issue I was having. Check the 4.4 update thread about rwilco's modified restore. The one with the sboot or boot.ini in it works. Trust me It works I just got my phone back to 4.3 then back up to 4.4. If u have any questions pm me.
Click to expand...
Click to collapse
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!

arichter35 said:
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
Click to expand...
Click to collapse
If it's the Samsung screen u need to go into factory recovery and do a factory reset. If u stuck at the note 2 screen u need to use odin and use the modified restore that was posted on the 4.4 update discussion thread. i think i used odin 3.4 or something. Ill turn my computer on to see.
---------- Post added at 04:25 AM ---------- Previous post was at 04:11 AM ----------
arichter35 said:
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
Click to expand...
Click to collapse
ok to make things short as possible. i dont want this discussion to get out of hand and i will be as helpful as possible. I was stuck on the samsung note 2 screen. i couldnt get past it. tried everything for like 2 days and then rwilco12 posted his modified 4.3 restore on page 50 of the Note II - the 4.4.2 update - discussion thread. all i did was flash that through Odin3 v3.04. just reboot checked on PDA. nothing else. when it rebooted it took a while but it booted to the samsung screen that changes colors. it stuck there so what i did was reboot into recovery mode and did a factory reset. after that it booted into 4.3 no problems.
---------- Post added at 05:06 AM ---------- Previous post was at 04:25 AM ----------
arichter35 said:
puffyjello,
what version of Odin did you use? reboot checked/unchecked?
ive used three different versions and have been unsuccessful in getting out of the samsung logo screen.
im having the same problems as the OP.
thanks for the help!!!
Click to expand...
Click to collapse
Any progress?

puffyjello said:
Looks like your having the same issue I was having. Check the 4.4 update thread about rwilco's modified restore. The one with the sboot or boot.ini in it works. Trust me It works I just got my phone back to 4.3 then back up to 4.4. If u have any questions pm me.
Click to expand...
Click to collapse
Up and running thank you!

jyerly said:
Up and running thank you!
Click to expand...
Click to collapse
Your welcome. Glad i could help. what about you arichter35??

It worked!
Thank you!!
If I go back to mc2 through billards file to get all the ota's in order will go through the same bs? If so, I will use the other method that was posted using the ota 4.4.2 file on XDA...
I appreciate all the help!
Sent from my SPH-L900 using XDA Free mobile app

arichter35 said:
It worked!
Thank you!!
If I go back to mc2 through billards file to get all the ota's in order will go through the same bs? If so, I will use the other method that was posted using the ota 4.4.2 file on XDA...
I appreciate all the help!
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
Honestly I'm not quite sure. What u could do is use billards mc2 then ota to 4.3 and when u reboot if u soft brick again just use the modified restore again. If u want to try it go ahead no harm in trying. i might try it later but chances are its going to fail anyways. Since downgrading from 4.4 is what caused the problem in the first place.

puffyjello said:
Honestly I'm not quite sure. What u could do is use billards mc2 then ota to 4.3 and when u reboot if u soft brick again just use the modified restore again. If u want to try it go ahead no harm in trying. i might try it later but chances are its going to fail anyways. Since downgrading from 4.4 is what caused the problem in the first place.
Click to expand...
Click to collapse
Puffyjello,
I simply flashed the OTA 4.4.2 in stock recovery and rebooted to the update no problem. No new Odin's of MK4 or anything, just flashed the OTA after i used your method to unbrick.
I then Odin'd Philz, flashed SuperSu and now im rooted and on 4.4.2, no problems.
Again, thanks for the help with the 'unbricking'!

arichter35 said:
Puffyjello,
I simply flashed the OTA 4.4.2 in stock recovery and rebooted to the update no problem. No new Odin's of MK4 or anything, just flashed the OTA after i used your method to unbrick.
I then Odin'd Philz, flashed SuperSu and now im rooted and on 4deeded problems.
Again, thanks for the help with the 'unbricking'!
Click to expand...
Click to collapse
Np. And what I thought u meant was going back to mc2 from 4.4 then ota to 4.3 and see if it bricks again. I wasnt sure if it would. Ne ways I'm glad everything's fixed. And I hope anybody that has this problem follows what fixed our phones. you guys take care. Running stock deodexed ne2 and loving it. Can't wait to try out their s5feat rom when they release it.

Does the LJC_Stock_With_Count_Reset[FINAL].zip still work after ota 4.4.2 ?
This to me is the best back to unrooted stock. It resores the LJC PIT, kernel, and modem. Compared to all the other stock roms; I find this one read and writes easier with QPST & CDMA-ws.
Im currently running stock rooted MC2 with stock LJ1 baseband.
In my opinion so far this is the recipe for this phone. Oldest basebands seem to have better battery life. I'm not really sure if the newer modems are actually faster causing the battery to drain faster, or generate more compression and share more detailed information with big brother which would also cause it to slow down.
I have this theory the manufacturers purposely slow peoples equipment down with the OTA after the first couple years to motivate them to buy the newer model flagships that supports the same software more efficiently. maybe I'm just crazy but can someone please try the back to LJC stock unrooted. and let me know if it works better than the back to stock MC2.
plus it could possibly be better doing all the OTA to 4.4.2 from an older stock rom.

[Q&A] [ROM] [N910PVPU1BOB7] [100% Stock, Rooted, Odexed/ART, No KNOX/Itson] [3/20/20

[Q&A] [ROM] [N910PVPU1BOB7] [100% Stock, Rooted, Odexed/ART, No KNOX/Itson] [3/20/20
Q&A for [ROM] [N910PVPU1BOB7] [100% Stock, Rooted, Odexed/ART, No KNOX/Itson] [3/20/2015]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [N910PVPU1BOB7] [100% Stock, Rooted, Odexed/ART, No KNOX/Itson] [3/20/2015]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Well, my fellow Central Daylight Time dweller... the 48 hour mark from your initial Beta release is rapidly approaching. .. and since i hear nothing but great things, I sincerely hope that those of us who missed out on the privledge of testing, will get a public release soon.

Where do i find the theme chooser once i enable it

Tanx for you hard work for sprint community

Google Voice
On Dark Theme, could set google voice to always respond to "OK Google". On your Lollipop the always on is greyed out and will not turn on.

any chance to release hybrid series
any chance to release hybrid series like we had for kitkat

please help
I have been trying to my galaxy note 4 back to stock because i brick it can someone send me the orginal firmware rom so i can fix it or can it be even fixed model # n910p

manning713 said:
I have been trying to my galaxy note 4 back to stock because i brick it can someone send me the orginal firmware rom so i can fix it or can it be even fixed model # n910p
Click to expand...
Click to collapse
Odin the stock ob7 file in the general section. That should fix you up.

worked like a charm
jhill110 said:
Odin the stock ob7 file in the general section. That should fix you up.
Click to expand...
Click to collapse
Thanks for the info is there any way I can Sim unlock it so I can use it with at&t gsm network new cricket

manning713 said:
Thanks for the info is there any way I can Sim unlock it so I can use it with at&t gsm network new cricket
Click to expand...
Click to collapse
Unfortunately not in the U. S. Internationally yes but not here.

Issues with boot loop after flashing ROM
After following all of the directions correctly, the ROM is flashed successfully. When I go to reboot, I get the Galaxy Note 4 page and after 7 seconds, it reboots over and over. Is there anything that I can try?

BleedingEdge38 said:
After following all of the directions correctly, the ROM is flashed successfully. When I go to reboot, I get the Galaxy Note 4 page and after 7 seconds, it reboots over and over. Is there anything that I can try?
Click to expand...
Click to collapse
Did you start with OB7 on your phone before flashing this? Or were you on a different one...OE1 , OF5? If you were on OB7 I would try to download and install the stock .tar of OB7 through Odin then re-root. Make backup of stock ROM then try and re-flash this.
If on OE1 or OF5 beforehand then you have to flash the stock .tar of OF5. You won't be able to flash an OB7 ROM.
Could also have been a bad download.

ianmb said:
Did you start with OB7 on your phone before flashing this? Or were you on a different one...OE1 , OF5? If you were on OB7 I would try to download and install the stock .tar of OB7 through Odin then re-root. Make backup of stock ROM then try and re-flash this.
If on OE1 or OF5 beforehand then you have to flash the stock .tar of OF5. You won't be able to flash an OB7 ROM.
Could also have been a bad download.
Click to expand...
Click to collapse
I do remember upgrading my firmware OTA, so there's a good chance I upgraded to OF5. I didn't check before....I will look for an OF5 ROM. Thanks

So now I'm stuck in a pickle here. I tried flashing all types of stock ROMs, but they all give me fails. I tried using different USB ports and everything. Every time I flash anything through TWRP, it installs fine, but then when I go to reboot, it resorts to show me the Galaxy Note 4 logo then restarts. *So Frustrating* I don't know for sure what build number I was on before all of this happened, but I know that I updated to the latest firmware as per the latest OTA update. Any help is appreciated.

BleedingEdge38 said:
So now I'm stuck in a pickle here. I tried flashing all types of stock ROMs, but they all give me fails. I tried using different USB ports and everything. Every time I flash anything through TWRP, it installs fine, but then when I go to reboot, it resorts to show me the Galaxy Note 4 logo then restarts. *So Frustrating* I don't know for sure what build number I was on before all of this happened, but I know that I updated to the latest firmware as per the latest OTA update. Any help is appreciated.
Click to expand...
Click to collapse
You need to flash CWM and download Sacs Rom and install that via CWM. That should get you out of the bootloop.

xxSTARBUCKSxx said:
You need to flash CWM and download Sacs Rom and install that via CWM. That should get you out of the bootloop.
Click to expand...
Click to collapse
Thanks for the advice, but I keep on getting a "Status 7 error". I think I'll go with CM for now until updated ROMs come out. I probably shouldn't have updated to the latest firmware before all of this happened, as it seems that I cannot revert back to older build types.