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
Related
Hey there I know this might sound like a complete newbie question but I have honestly run out of ideas so posting here for some idea.
I have at this point decided my phone must be a lemon.
1. Day 1 received phone installed CM ran it for multiple days no problems.
2. After a few days of this wanted to try Wanams i9505 rom so wiped everything including data in recovery rebooted recovery and installed. First boot was fine setup was fine got it working but then after my first try to reboot it ot stuck at SAMSUNG GALAXY S4 second time it made it to the boot animation but crashed half way through it and reset.
3. Thinking my phone wasn't playing nice with the kernel in Wanam's rom (Adam I believe) I flashed his ROM then immediately flashed the stock m919 kernel after. Same results after first boot.
4. Then tried restoring my nandroid of complete stock. Same problem.
5. Wiped all (except SD) and restored nandroid of stock. Problem gone.
6. After my next backup of stock problem is back.
7. If I do a full odin to stock it works and reboots for days no problem.
I am using TWRP for TMO, have a m919v (Canadian Variant)
Any advice at all would be great, I could easily have overlooked something obvious. Thanks!
Should I not be wiping preload and EFS when doing a "full wipe" ?
No, if you are just flashing a rom from another carrier, which you are, wipe as usual, flash the rom, and before you boot use the tmo canadian kernel, it will boot.
TheAxman said:
No, if you are just flashing a rom from another carrier, which you are, wipe as usual, flash the rom, and before you boot use the tmo canadian kernel, it will boot.
Click to expand...
Click to collapse
Hey thanks for the response yes it does boot once, but after that it seems to not. I have even tried re-flashing the stock m919 kernel after flashing the target rom fails booting and that doesnt seem to fix it.
Idyar said:
Hey thanks for the response yes it does boot once, but after that it seems to not. I have even tried re-flashing the stock m919 kernel after flashing the target rom fails booting and that doesnt seem to fix it.
Click to expand...
Click to collapse
Where did you happen to find the kernel for your device?
TheAxman said:
Where did you happen to find the kernel for your device?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2262729
Idyar said:
http://forum.xda-developers.com/showthread.php?t=2262729
Click to expand...
Click to collapse
whoa, and that is for the 919v? Now I am really confused.
hmm, if thats the correct one, we have a problem. Let me ponder the moment. give me a few...maybe someone else could enlighten us...
is it just happening with this rom, does any of your backups restore ok?
TheAxman said:
whoa, and that is for the 919v? Now I am really confused.
hmm, if thats the correct one, we have a problem. Let me ponder the moment. give me a few...maybe someone else could enlighten us...
Click to expand...
Click to collapse
Good point they are not specifically for V variant but it is my understanding that they should be identical. I have the odin flash for it so what I will do is use that to be 100% sure thanks for the tip.
Idyar said:
Good point they are not specifically for V variant but it is my understanding that they should be identical. I have the odin flash for it so what I will do is use that to be 100% sure thanks for the tip.
Click to expand...
Click to collapse
You flashed Odin then made backup of stock right? And it still had an issue?
Seems like a recovery issue. Try CWM recovery instead
Sent from my SGH-M919 using Tapatalk 2
Yup cmw seems to have fixed all my problems thanks.
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
nayte1993 said:
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
Click to expand...
Click to collapse
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
C.Sweat said:
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
Click to expand...
Click to collapse
Could I return to stock using Odin? If so I'll try that when I'm able too.
nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
Yeah you sure can. :good: Go here for instructions and stock firmware
nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
try a factory reset/wipe first, before you go to stock again
Bob Hodges said:
try a factory reset/wipe first, before you go to stock again
Click to expand...
Click to collapse
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
nayte1993 said:
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
Click to expand...
Click to collapse
AFTER you flash stock rom, perform factory reset wipe, and you wont get stuck. flash recovery. and then flash custom rom and you should be fine
wrong kernels...period
TheAxman said:
wrong kernels...period
Click to expand...
Click to collapse
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
nayte1993 said:
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
Click to expand...
Click to collapse
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Toleraen said:
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Click to expand...
Click to collapse
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
nayte1993 said:
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
Click to expand...
Click to collapse
That's a matter of preference...just make sure to pull a TW kernel. Of course, the kernel built into Wicked should work just fine as well.
I've been a fan of ktoonsez's kernel (link in my sig). 7/7 got a little crashy on me, but 7/2 has been running smooth
Problem fixed, thanks everyone.
I have received a replacement GS3 2 days ago. I rooted the phone no problems and it came with MK3 already on it. But no matter what rom I flash, they all cause a lot of random reboots and lockups. TW and CM based roms ive tried with the same results. I do multiple wipes before installing any rom so I know that cant be the problem. It got so annoying that i just flashed the stock tar in odin even though i hate not being rooted. Can anyone shed some light on this?
cbond007 said:
I have received a replacement GS3 2 days ago. I rooted the phone no problems and it came with MK3 already on it. But no matter what rom I flash, they all cause a lot of random reboots and lockups. TW and CM based roms ive tried with the same results. I do multiple wipes before installing any rom so I know that cant be the problem. It got so annoying that i just flashed the stock tar in odin even though i hate not being rooted. Can anyone shed some light on this?
Click to expand...
Click to collapse
Are you flashing 4.3 TW ROMs? Do you format system before flashing the ROMs (if they do not say that they do it for you)?
Yes, I'm flashing 4.3 roms. I do wipe the system, I don't know if that is the same as formatting the system though(?)
kennyglass123 said:
Are you flashing 4.3 TW ROMs? Do you format system before flashing the ROMs (if they do not say that they do it for you)?
Click to expand...
Click to collapse
cbond007 said:
Yes, I'm flashing 4.3 roms. I do wipe the system, I don't know if that is the same as formatting the system though(?)
Click to expand...
Click to collapse
In CWM the option is format /system. Is wipe system an option in TWRP? And when you flashed the ROMs and the FCs show up, have you tried a factory data reset to clear all data?
Yes, in TWRP in the wipe options, (wipe system) is an option. I haven't gotten any FC's on the 4.3 roms i were flashing. Moar's rom is the main one i used after i got the replacement. Wicked's rom in recovery when I tried to flash would always say unable to mount \system. I can flash CM 11 nightlies fine, but they just have too many random reboots for my liking. I havent tried to factory reset after flashing a rom yet though.
kennyglass123 said:
In CWM the option is format /system. Is wipe system an option in TWRP? And when you flashed the ROMs and the FCs show up, have you tried a factory data reset to clear all data?
Click to expand...
Click to collapse
cbond007 said:
Yes, in TWRP in the wipe options, (wipe system) is an option. I haven't gotten any FC's on the 4.3 roms i were flashing. Moar's rom is the main one i used after i got the replacement. Wicked's rom in recovery when I tried to flash would always say unable to mount \system. I can flash CM 11 nightlies fine, but they just have too many random reboots for my liking. I havent tried to factory reset after flashing a rom yet though.
Click to expand...
Click to collapse
The thing is with Knox in the bootloader you are stuck with and the warranty bit in the secondary bootloader you need to stick with 4.3 and above ROMs as they include compatible kernels. Your options are more limited now than they were. If the Wicked ROM is 4.3 you might try flashing with CWM.
Cool. I will try it with CWM. This sucks because my replacement phone came with Knox already on it. I just wish CM 11 roms werent so buggy on my phone so I could stick with that. Thanks for all your help.
kennyglass123 said:
The thing is with Knox in the bootloader you are stuck with and the warranty bit in the secondary bootloader you need to stick with 4.3 and above ROMs as they include compatible kernels. Your options are more limited now than they were. If the Wicked ROM is 4.3 you might try flashing with CWM.
Click to expand...
Click to collapse
cbond007 said:
Cool. I will try it with CWM. This sucks because my replacement phone came with Knox already on it. I just wish CM 11 roms werent so buggy on my phone so I could stick with that. Thanks for all your help.
Click to expand...
Click to collapse
I would also suggest trying Philz Touch recovery instead of CWM or TWRP.
http://forum.xda-developers.com/showthread.php?t=2446393
---------- Post added at 10:36 AM ---------- Previous post was at 10:25 AM ----------
If you do decide to try Philz (highly recommended!), the option for wiping prior to a ROM install is under Wipe Data/Factory Reset and then choose "Clean to Install New ROM" this will take care of everything you need to start properly. CM11 has run flawlessly for me since its release in early December, but I also am Knox-free. I don't believe that should make a difference though, sounds more like you are not getting a good install, as @kennyglass123 is suggesting. Additionally, some users find that you need to let the ROM "settle in" before doing anything. This means flash just the ROM, and once it boots up don't do anything-no WiFi setup, no fiddling around with apps, nothing for a few minutes. Then, boot back into recovery, flash GApps, boot back into system, and let it sit for a few minutes more. Then, go ahead and setup WiFi connection, Google account, etc.
I am currently running SkyNote Air and want to do a clean wipe and start fresh. I've done this before without a problem but am having trouble this time around. After a clean wipe and ROM install, the phone will boot but after seeing the "Android is upgrading, Starting Apps" screen and momentarily displaying the Welcome screen the phone will go into a loop. Seems to happen after the phone connects to the network. I can interact with it to reboot into recovery if I'm quick enough.
From the searches I've done, I've already tried clearing cache and Dalvik and factory reset without any luck. I used Philz to wipe for a new ROM and TWRP to wipe internal storage as well without any luck. I've tried installing the ROM twice before rebooting recovery. Fix Permissions from TWRP also hasn't helped. I already had the 43paramtz.tar flashed and reflashing it does not help either. I have not tried the One-click method yet. That seems the only thing left to try. Just want to see if anyone else has any suggestions. Thanks in advance!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
ojai00 said:
I am currently running SkyNote Air and want to do a clean wipe and start fresh. I've done this before without a problem but am having trouble this time around. After a clean wipe and ROM install, the phone will boot but after seeing the "Android is upgrading, Starting Apps" screen and momentarily displaying the Welcome screen the phone will go into a loop. Seems to happen after the phone connects to the network. I can interact with it to reboot into recovery if I'm quick enough.
From the searches I've done, I've already tried clearing cache and Dalvik and factory reset without any luck. I used Philz to wipe for a new ROM and TWRP to wipe internal storage as well without any luck. I've tried installing the ROM twice before rebooting recovery. Fix Permissions from TWRP also hasn't helped. I already had the 43paramtz.tar flashed and reflashing it does not help either. I have not tried the One-click method yet. That seems the only thing left to try. Just want to see if anyone else has any suggestions. Thanks in advance!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Are you on T-mobile ?
dicksteele said:
What bootloader are you on ??? Did you do the 4.3 OTA ?
Click to expand...
Click to collapse
I believe I am on a 4.1.2 bootloader (I317UCAMA4). I have not restored to stock or done a 4.3 OTA.
ojai00 said:
I believe I am on a 4.1.2 bootloader (I317UCAMA4). I have not restored to stock or done a 4.3 OTA.
Click to expand...
Click to collapse
And you're on T-Mobile ?
dicksteele said:
And you're on T-Mobile ?
Click to expand...
Click to collapse
Yep. Using an unlocked i317 on T-Mobile with the AWS Mod. My first instinct was to remove the SIM since the phone seemed to be restarting once I was connected to the network but that didn't work either.
ojai00 said:
Yep. Using an unlocked i317 on T-Mobile with the AWS Mod. My first instinct was to remove the SIM since the phone seemed to be restarting once I was connected to the network but that didn't work either.
Click to expand...
Click to collapse
Ahhhh.. Like it says in your signature.... :cyclops:
Yea I'm awake.
Have your ever flashed anything else besides Sky Air ? That's the one you have reflashed after Philz/TWRP wipes right ?
dicksteele said:
Ahhhh.. Like it says in your signature.... :cyclops:
Yea I'm awake.
Have your ever flashed anything else besides Sky Air ? That's the one you have reflashed after Philz/TWRP wipes right ?
Click to expand...
Click to collapse
SkyNote is the only 4.3 ROM I've tried. Yes, that was the ROM I reflashed after the full wipes. I've been flashing SkyNote from version 8 onwards and am now running the N3 version. I've seen some people have issues with the N3 version but not the Vanilla version. I haven't tried that one. I've been following MeanBean but I'm worried if I can't even get a reinstall of SkyNote Air working my chances of another ROM will probably be the same!
ojai00 said:
SkyNote is the only 4.3 ROM I've tried. Yes, that was the ROM I reflashed after the full wipes. I've been flashing SkyNote from version 8 onwards and am now running the N3 version. I've seen some people have issues with the N3 version but not the Vanilla version. I haven't tried that one. I've been following MeanBean but I'm worried if I can't even get a reinstall of SkyNote Air working my chances of another ROM will probably be the same!
Click to expand...
Click to collapse
MeanBean is pretty sweet. You have to remember to run the fixdata.sh.
I'm thinking you should give this a try, a stock ROM.
http://forum.xda-developers.com/showthread.php?t=2589891
It's still flashing from a custom recovery.
You've done everything short of sacrificing a chicken.
Gotta run to a mind numbing meeting.....
dicksteele said:
MeanBean is pretty sweet. You have to remember to run the fixdata.sh.
I'm thinking you should give this a try, a stock ROM.
http://forum.xda-developers.com/showthread.php?t=2589891
It's still flashing from a custom recovery.
You've done everything short of sacrificing a chicken.
Gotta run to a mind numbing meeting.....
Click to expand...
Click to collapse
I'll give it a shot. Good luck with the meeting. Thanks for your help! :highfive:
ojai00 said:
I'll give it a shot. Good luck with the meeting. Thanks for your help! :highfive:
Click to expand...
Click to collapse
Good luck.... Hopefully it works.
Tried flashing the stock deodexed ROM in Philz and still the same result. I can at least make it far enough to the home screen but am still getting the same reboots. I also upgraded to the 4.3 bootloader from seanz thread here (http://forum.xda-developers.com/showthread.php?t=2502464) without luck. I wonder if flashing the ROM in Odin will be any different? I have my doubts but want to hear it from someone else.
ojai00 said:
Tried flashing the stock deodexed ROM in Philz and still the same result. I can at least make it far enough to the home screen but am still getting the same reboots. I also upgraded to the 4.3 bootloader from seanz thread here (http://forum.xda-developers.com/showthread.php?t=2502464) without luck. I wonder if flashing the ROM in Odin will be any different? I have my doubts but want to hear it from someone else.
Click to expand...
Click to collapse
If you're game you could try this
http://forum.xda-developers.com/showthread.php?t=2618447
If you do sections 1 and 2, and don't get boot loops, you can flash that stock/root/odex ROM.
dicksteele said:
If you're game you could try this
http://forum.xda-developers.com/showthread.php?t=2618447
If you do sections 1 and 2, and don't get boot loops, you can flash that stock/root/odex ROM.
Click to expand...
Click to collapse
Thanks again. I'll try that next. Attempting the Odexed version of Zen's package first.
ojai00 said:
Thanks again. I'll try that next. Attempting the Odexed version of Zen's package first.
Click to expand...
Click to collapse
Sounds good. Good luck.
Not sure what is residual and causing the boot loops.
So I dirty flashed the odex version and that seems to be stable. I then factory reset to wipe it clean and that came up fine. Going to try wiping completely and installing Stock Odex again.
Update: Rooted Stock Odex seems to be the only one that is booting up fine. I then flashed SkyNote Air without any wipes and it was fine again. Once I tried to factory reset to defaults after Air is installed (wiping cache and Dalvik in the process), the boot loops begin. Guess this is what I'm going to have to do if I want to start fresh on any ROM.
ojai00 said:
So I dirty flashed the odex version and that seems to be stable. I then factory reset to wipe it clean and that came up fine. Going to try wiping completely and installing Stock Odex again.
Update: Rooted Stock Odex seems to be the only one that is booting up fine. I then flashed SkyNote Air without any wipes and it was fine again. Once I tried to factory reset to defaults after Air is installed (wiping cache and Dalvik in the process), the boot loops begin. Guess this is what I'm going to have to do if I want to start fresh on any ROM.
Click to expand...
Click to collapse
Too wierd. At least you found a path.... Not optimal, but functional.
I'm fighting why I can't flash a custom recovery now.
dicksteele said:
Too wierd. At least you found a path.... Not optimal, but functional.
I'm fighting why I can't flash a custom recovery now.
Click to expand...
Click to collapse
Just a thought even though I'm sure you verified. You're sure you're trying to flash the proper recovery for the device? I know TWRP and Philz make a specific version for the i317 with t0lteatt in the file name.
ojai00 said:
Just a thought even though I'm sure you verified. You're sure you're trying to flash the proper recovery for the device? I know TWRP and Philz make a specific version for the i317 with t0lteatt in the file name.
Click to expand...
Click to collapse
Yepper. They live on my machine and phone. Thought it was an ODIN thing, just rooted my phone.
I do so much crap to it maybe that's was I was missing .... We'll see.
EDIT : And that was it. Interesting .....
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.