I got myself in a bit of a pickle. I was running a custom ROM (TW based) for a while, and sometime 2 weeks ago i started having hardware camera issues. I called AT&T about it and their sending me another unit. That was yesterday. Today i Odin'ed my current phone back to stock non-rooted to make the warranty guys happy. but.. i chose not to factory reset my phone because i still need my phone until the new unit comes in. Because of that Samsung's Setup Wizard likes to crash on load. well it doesn't fully crash, it just hangs. I unlock my phone, goes right to black screen with notification bar and hangs. I pull down that bar to go to settings and that all works. In lock screen i changed a shortcut to go to nova launcher so I can use that. But my issue is, that setup wizard is the "default home launcher" and it is preventing me from changing that. Also meaning that my home button stops working because its trying to load a dead app. I currently just lock my phone and shortcut back to nova to get to my home screen but that's a pain. I have 1-2 weeks i have to wait till my new phone comes.
I have 2 possible idea's that would need your help. One would be to backup my phone (non rooted) and restore it keeping apps and data (and I don't know how to do that), or 2 is to manually go into es file explorer and find the config for default launchers and manually set it to nova (and im not sure if you need root for that, and if not, where the config file would be). Any love from the family?
Thanks, Tommy
What phone do you have and what firmware were you on?
Reply to that
jd1639 said:
What phone do you have and what firmware were you on?
Click to expand...
Click to collapse
ATT Galaxy S4 (i337) on UCUAMF3 (i was also at --MDL but then updated to see if it fixed it(it didnt))
tommydrum said:
ATT Galaxy S4 (i337) on UCUAMF3 (i was also at --MDL but then updated to see if it fixed it(it didnt))
Click to expand...
Click to collapse
Mf3 is your problem. You can not use Odin. You're basically screwed right now until an odin flashable firmware comes out, If it ever does.
jd1639 said:
Mf3 is your problem. You can not use Odin. You're basically screwed right now until an odin flashable firmware comes out, If it ever does.
Click to expand...
Click to collapse
I was JUST on MDL and updated to MF3 in hopes it would fix it... MF3 is not the problem. When i Odin'ed I Odin'ed to MDL from a custom ROM.
tommydrum said:
I was JUST on MDL and updated to MF3 in hopes it would fix it... MF3 is not the problem. When i Odin'ed I Odin'ed to MDL from a custom ROM.
Click to expand...
Click to collapse
So are you on mf3 now or mdl?
jd1639 said:
So are you on mf3 now or mdl?
Click to expand...
Click to collapse
From custom rom to MDL, then from MDL to MF3.. So I am on MF3 right now..
tommydrum said:
From custom rom to MDL, then from MDL to MF3.. So I am on MF3 right now..
Click to expand...
Click to collapse
Ok, you won't be able to use odin anymore. But the phone does boot? And you get the setup wizard at that point? And then it doesn't let you get any further than that? I'm a little confused on exactly what's happening.
jd1639 said:
Ok, you won't be able to use odin anymore. But the phone does boot? And you get the setup wizard at that point? And then it doesn't let you get any further than that? I'm a little confused on exactly what's happening.
Click to expand...
Click to collapse
It boots up, into lock screen. When i unlock it gets a black screen with a notification bar on top. It is trying to load the Setup Wizard even though its already activated and set up.
Related
Hey guys,
I flashed back to stock with ODIN. Everything passes. But when the phone reboots it comes up with Samsung custom logo and seems to get stuck there? Any ideas?
EDIT: this is the ATT I337, I have flashed with ODIN before and it worked out fine. I am doing everything I normally did.
evolution2012 said:
Hey guys,
I flashed back to stock with ODIN. Everything passes. But when the phone reboots it comes up with Samsung custom logo and seems to get stuck there? Any ideas?
EDIT: this is the ATT I337, I have flashed with ODIN before and it worked out fine. I am doing everything I normally did.
Click to expand...
Click to collapse
Have you made any changes since you last used ODIN? Did you flash a different version? How long are you waiting?
hamzer11 said:
Have you made any changes since you last used ODIN? Did you flash a different version? How long are you waiting?
Click to expand...
Click to collapse
I waited like 3 minutes or so. But it never passes the custom Samsung screen at boot. Maybe I need to give it more time? I flashed Loki and I installed slimbean. Slimbean was a little buggy as it is still in beta so I went to restore my recovery. My recovery was missing from TWRP so I tried flashing back to stock odin to start over from square one.
I am using ODIN 3.07 on a PC running Windows 8. If I find out that all i have to do is wait longer I am gonna feel like an idiot lol.
evolution2012 said:
I waited like 3 minutes or so. But it never passes the custom Samsung screen at boot. Maybe I need to give it more time? I flashed Loki and I installed slimbean. Slimbean was a little buggy as it is still in beta so I went to restore my recovery. My recovery was missing from TWRP so I tried flashing back to stock odin to start over from square one.
I am using ODIN 3.07 on a PC running Windows 8. If I find out that all i have to do is wait longer I am gonna feel like an idiot lol.
Click to expand...
Click to collapse
Initial boots can be long but I don't know about more than 3 minutes? Not really sure about what happens if you ODiN back after TWRP? I'll let more technical folks take a stab at it. It can't hurt to wait though.
Well I don't know what was ailing the odin flash, but I just used Kies emergency recovery and all is fine now. Weird... Appreciate your help.
evolution2012 said:
Well I don't know what was ailing the odin flash, but I just used Kies emergency recovery and all is fine now. Weird... Appreciate your help.
Click to expand...
Click to collapse
Question for you, does recovering this way wipe everything? Apps, root, settings, all mods? Just want to know for my own reference.
hamzer11 said:
Question for you, does recovering this way wipe everything? Apps, root, settings, all mods? Just want to know for my own reference.
Click to expand...
Click to collapse
This was my first time ever using KIES recovery. As far as I could tell everything is wiped. I did a factory reset afterwards just to be safe so I can't say with 100% certainty. I had the custom logo after reboot for 10 seconds, then after a manual reboot it boots regularly without the custom logo.
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
amishbobinc said:
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
Click to expand...
Click to collapse
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Cytality said:
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Click to expand...
Click to collapse
I think I did....is that bad?
amishbobinc said:
I think I did....is that bad?
Click to expand...
Click to collapse
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Cytality said:
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Click to expand...
Click to collapse
What about the stock MDL, if I flash that rom it should work - right?
amishbobinc said:
What about the stock MDL, if I flash that rom it should work - right?
Click to expand...
Click to collapse
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Cytality said:
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Click to expand...
Click to collapse
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
amishbobinc said:
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
Click to expand...
Click to collapse
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Cytality said:
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Click to expand...
Click to collapse
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
amishbobinc said:
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
Click to expand...
Click to collapse
Whats the rom you are using?
Cytality said:
Whats the rom you are using?
Click to expand...
Click to collapse
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
amishbobinc said:
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
Click to expand...
Click to collapse
While you have the phone turned on, go in settings and see what your baseband version is. If it ends in MDL then you're good.
After that, I don't know. I've never used that rom personally, it could be an issue with the rom itself, nothing really wrong with your phone. You can try to wipe and reinstall, or just try a different ROM.
Ok got it!!
TWRP and clockworkmod were both NOT formatting like they said they where. I had to manually go in and erase everything except the external SD. Then I did a clean install and everything works great.
Thank you for your help!
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
NidexX said:
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
Click to expand...
Click to collapse
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Aww really, i totally missed that this was for sprint:/. I have the NEE version(unbranded GT-I905). Are you sure i can flash stock, what if it would reboot while flashing? It is already stock, just that I have this damn problem with the reboots;(
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
jejb said:
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
Click to expand...
Click to collapse
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
NidexX said:
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm now very stable on MF9, rooted, stock rom.
jejb said:
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm not very stable on MF9, rooted, stock rom.
Click to expand...
Click to collapse
nvm dude, seems like it's hardware failure. I tried flashing it with stock MGA firmware and the problem remains, as well as the screen ****ing up just before it is about to reboot. Well, thanks anyway!
sph-l720 4.3 rooted by cf auto root
I put system files in the phones framework folder to hack free hotspot. I rebooted and the phone was stuck on the yellow sprint logo. I pulled the battery and used odin to i guess flash mf9, then cf auito root. last time i was stuck on this screen this worked.
But now i'm screwed.
I tried a wipe factory reset and it still didn't help.
I flashed a kernel zip file using odin by accident (KERNEL - SPR _ L720vpuamf9-1372121308)
now it boots and gets stuck at the same screen but the screen is blank. only the blue light lights up.
any clues???
now it says set warranty bit kernel, when it used to say set warranty bit recovery
You cannot go back with Odin to MF9 once you are on MjA.
Sent from my SPH-L720 using Tapatalk
.....
EDIT NEVER MIND I didn't see that first part about 4.3!
Hello Sprint I've got a TEP claim for you.
Okay well maybe not totally there yet. There are a couple threads on how to get 4.3 to boot do spend some time searching reading, and then read and look some more. Good place to start would be here
brewmanate said:
sph-l720 4.3 rooted by cf auto root
I put system files in the phones framework folder to hack free hotspot. I rebooted and the phone was stuck on the yellow sprint logo. I pulled the battery and used odin to i guess flash mf9, then cf auito root. last time i was stuck on this screen this worked.
But now i'm screwed.
I tried a wipe factory reset and it still didn't help.
I flashed a kernel zip file using odin by accident (KERNEL - SPR _ L720vpuamf9-1372121308)
now it boots and gets stuck at the same screen but the screen is blank. only the blue light lights up.
any clues???
now it says set warranty bit kernel, when it used to say set warranty bit recovery
Click to expand...
Click to collapse
Flash KT kernel 4.3 if you are on mja, that should fix it, if not, make sure you have a custom recovery(not TWRP) and flash the stock 4.3 rom in the dev section
thank you...
negamann303 said:
Flash KT kernel 4.3 if you are on mja, that should fix it, if not, make sure you have a custom recovery(not TWRP) and flash the stock 4.3 rom in the dev section
Click to expand...
Click to collapse
i just have to get it replaced.
I never fully rooted. I had stock recovery and binary ond kernel. I just has su.
I screwed the pooch on this one. Thanks anyway guys. I will get a new one. Or maybe a note 3 in its place. What do you think?
If you can get to download mode it's not bricked
Sent from my SPH-L720 using Tapatalk
Your not bricked
This is exactly the same issue I had. You tried to downgrade after upgrading and flashed some stuff to fix it right? Yeah bad idea. Anyway.
Go to this thread http://forum.xda-developers.com/showthread.php?t=2506562
Follow it step by step. It solved my issues.
I already sent it out to be replaced
I have insurance through a 3rd party, so it might be forgiven that I rooted it. If not, and they send it back to me, I will have to rely on all your helpful guidance. I am very grateful. You guys rock.
Just so its as clear as can be, here is a list of my mistakes. LOL
1. I did try to take the OTA update. It didnt take and only messed with storage for some reason. Not broke yet.
2. Flashed back to MF9 with Odin 3 v.1.87. Oops.
3. Flashed MF9 and CF auto root a few times back and forth trying to get it to take.
4. It is a bit hazy here, but I tried to use odin 3.07 to go back to mf9, but it wouldn't work. I instead used odin to root the f#cker and to my amazement it worked. Now I was rooted on 4.3! MJA I got the idea from this thread>>>>>>>>http://forum.xda-developers.com/showthread.php?t=2511209
5. Then it was all gravy for a few days minus the annoying security notifications every so often about an app trying to access the system..blah blah blah. I wanted my hotspot hack back (the entire reason for the root) so I placed the altered system files in the framework to allow for hotspot service
and rebooted. Thats when **** got real. it booted up to the full yellow screen that shows the sprint logo. The blue led was strobing slowly and it just stayed that way for a few minutes. I got scared and tried going through steps 1 through 4 again to no avail.
6. Then I really messed up and flashed the MF9 Kernel zip file by mistake or maybe more out of desperation, and all that did was make the screen black after the samsung logo, but the blue led still illuminated.
All well, I already sent it out. I should get a new one soon.
If they dont let me swap it I will upgrade to the note 3.
Any ideas about the note 3 vs the sgs4, except for the obvious size and Ghz difference?
I've recently flashed NAE modem via Odin 3.09, also flashed Philz latest recovery. I was doing this so i could flash Rawintellects Stock(ish) ROM.... which seemed so badass. Really wish i could have got it working. Anyway, on to the problem.
Firmware flash went fine, Philz reovery went fine, ROM flash went fine. Now... I BELIEVE (can't remember) that i was coming from a MDL firmware, not sure though. After ROM flash, things were glitchy. No wifi (fixed after following suggestions in his thread. No 3g... fixed after a clean wipe 3X's and fresh ROM flash. And NO SOUND... never fixed. I spent half a day trying to get it right, never could.
So I decided to try another ROM, next was Negalites WondROM. Seemed cool, but had all the same issues. Exact same. Locking up, swipe screen locking up. System crashes, random reboots. NO SOUND. Figured, WTF.... tried another ROM same issues. At this point I thought maybe all these ROMS had the same kernal and that was the issue, so i flashed dif kernals compitable and recommended for dif ROMS. ALL SAME ISSUES. From here I figured it was the NAE modem the phone didn't like for whatever reason.
So now I'm stuck. I want to start over, want to flash MDL modem again, want to put the ROM i had back on here (I believe it was BluKuban or something). I am fairly certain there is now ay to take this phone back to the store and have them repair it, they will surely find something that will void the warranty even though im also fairly certain there is no warranty left on the phone. This phone is a business phone on our business account (one of 6 phones) and we've had buisiness with this sprint location for over a decade so i amy be able to persuade a repair.
Need help guys =(
Fixed
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
ograyray said:
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
Click to expand...
Click to collapse
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
tensux said:
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
Click to expand...
Click to collapse
Thanks, at that point I was happy to get anything to work, nothing lost really, just maybe 4 or 5 roms, a few GAPS packages, dealing with realizing I flashed a 4.4.3 image though.... And reading through everything looks like there is no root method available for 4.4.3 yet.... BUT HEY, got the phone functional and usable.
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
tensux said:
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
Click to expand...
Click to collapse
I like two things. 1. Phone works 2. 4.4.3 is fast and battery life is awesome so far. I do hate the bloatware and bright ass yellow splash screen on boot. But i believe i can stick with this until root for 4.4.3 is out.
Gonna miss my ROMs till then. Unless you can find root method for 4.4. It's out for S5 but not S4. I'd be shocked if i was wrong.
You should read up a bit... No reason you can't be rooted on 4.4.3
Sent from my SPH-L720 using XDA