I am trying to update from MDC to MDL. Android System Update says "downloaded and verified - 23.8 MB." I hit restart and install and it counts down to "Rebooting now - 23.8 MB." It never reboots, just sits there.
I rooted using CF and installed TWRP. I backed up MDC and then flashed stock recovery. Went to system update and that is where I am. Is the fact I am rooted causing my problems?
todivefor said:
I am trying to update from MDC to MDL. Android System Update says "downloaded and verified - 23.8 MB." I hit restart and install and it counts down to "Rebooting now - 23.8 MB." It never reboots, just sits there.
I rooted using CF and installed TWRP. I backed up MDC and then flashed stock recovery. Went to system update and that is where I am. Is the fact I am rooted causing my problems?
Click to expand...
Click to collapse
Try this. Worked flawlessly for me and others
http://m.youtube.com/#/watch?v=ONzx...top_uri=/watch?v=ONzxfyTnWIY&feature=youtu.be
Sent from my SPH-L720 using xda premium
Reflash stock Recovery in Odin and Unroot then root by using the cf auto root http://forum.xda-developers.com/showthread.php?t=2291827 and get twrp back with the goo manager app in the play store.
Sent from my SPH-L720 using xda premium
E The Magnificent said:
Try this. Worked flawlessly for me and others
http://m.youtube.com/#/watch?v=ONzx...top_uri=/watch?v=ONzxfyTnWIY&feature=youtu.be
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Thanks, but rooting is not the problem. I am trying to apply MDC -> MDL after rooting.
You have to Unroot first then flash stock Recovery them root using cf auto root http://forum.xda-developers.com/showthread.php?t=2291827
Sent from my SPH-L720 using xda premium
todivefor said:
Thanks, but rooting is not the problem. I am trying to apply MDC -> MDL after rooting.
Click to expand...
Click to collapse
**Edit** dammit didn't read post above mine. doh, facepalm
I was stock rooted w/ twrp recovery when I wanted to go from MDC to MDL. I did a nand, then unrooted and flashed a completely stock MSC ROM with stock recovery. Allowed MDL update to download then installed, then flashed CFs Auto Root after MDL was applied.
Everything went without a hitch. Probably took longer than should have cause of the nand then flashing complete unrooted stock.
Sent from my SPH-L720 using xda app-developers app
FanOfSkynyrd said:
**Edit** dammit didn't read post above mine. doh, facepalm
I was stock rooted w/ twrp recovery when I wanted to go from MDC to MDL. I did a nand, then unrooted and flashed a completely stock MSC ROM with stock recovery. Allowed MDL update to download then installed, then flashed CFs Auto Root after MDL was applied.
Everything went without a hitch. Probably took longer than should have cause of the nand then flashing complete unrooted stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Hello Folks... I'm currently unrooting to try this method from above link > after can i flash a ROM (example ForceROM)?
Thanks
I was unable to get the MDC -> MDL upgrade to work (stock MDC, rooted, stock recovery), so I flashed stock MDC per http://forum.xda-developers.com/showthread.php?t=2277480. Took upgrade to MDL and rerooted. I read where people were able to upgrade while rooted (some losing root), but did not work for me.
FanOfSkynyrd said:
**Edit** dammit didn't read post above mine. doh, facepalm
I was stock rooted w/ twrp recovery when I wanted to go from MDC to MDL. I did a nand, then unrooted and flashed a completely stock MSC ROM with stock recovery. Allowed MDL update to download then installed, then flashed CFs Auto Root after MDL was applied.
Everything went without a hitch. Probably took longer than should have cause of the nand then flashing complete unrooted stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
How did you unroot?
todivefor said:
How did you unroot?
Click to expand...
Click to collapse
I just installed the stock ROM/firmware/recovery in this thread:
http://forum.xda-developers.com/showthread.php?p=40889088#post40889088
I used the SPR one.
Once I flashed this gave everything a few minutes and MDL update was downloaded and ready to install.
Installed, then rooted via CF-Auto Root.
Just make sure you make a nand before doing any of this.
Sent from my SPH-L720 using xda app-developers app
Related
I recently flashed the 4.3 update and immediately rooted and flashed twrp. I then decided to go full stock. I thought I could just Odin back to mf9 and flash the update again. This is not the case. I got back to 4.2.2. But it was not mf9. The software version stayed at mja. The update zip would not install anymore. Odin was failing with errors. My nandroid of 4.3 would not take. Just bootlooped. I thought I was screwed until someone pointed me to a nandroid of boot and system that could be flashed with philz recovery. So I'm back to 4.3. What I'm looking to do is get this to pure stock 4.3. Stock recovery and all. I'll wory about the Knox flags later. Is there anyway this can be done yet?
Sent from my SPH-L720 using xda app-developers app
Should have put this in the qua section...sorry
Sent from my SPH-L720 using xda app-developers app
Thread moved
FNM
prc292 said:
I recently flashed the 4.3 update and immediately rooted and flashed twrp. I then decided to go full stock. I thought I could just Odin back to mf9 and flash the update again. This is not the case. I got back to 4.2.2. But it was not mf9. The software version stayed at mja. The update zip would not install anymore. Odin was failing with errors. My nandroid of 4.3 would not take. Just bootlooped. I thought I was screwed until someone pointed me to a nandroid of boot and system that could be flashed with philz recovery. So I'm back to 4.3. What I'm looking to do is get this to pure stock 4.3. Stock recovery and all. I'll wory about the Knox flags later. Is there anyway this can be done yet?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Read through this thread and follow the directions. http://forum.xda-developers.com/showthread.php?t=2506562 It will do what you need.
I did use this thread and got back to 4.3 with philz recovery. What I'd really like to do is get completely stock, recovery and all. Gonna have to wait for a 4.3 .tar for an Odin flash. Or maybe someone can figure a way to flash stock recovery back and I can factory restore. This Knox security stuff is for the birds!
Sent from my SPH-L720 using xda app-developers app
I used the MF9 stock recovery after going to MJA in order to do a factory restore. Then I used it again to manually force the update with the cce8d8a155a0602c83356e00311a1695e9a9383f.USER_L720_SPT_MF9_CSB_user_RP_to_MJA_CSB_user_RP_Update_FWD.zip file.
Have you tried just doing an RTN via the phone dialer? Enter ##786# on phone keyboard, Select "reset", Enter MSL.
Both of those methods will wipe everything, of course, so backup using Helium, etc.
Hello.First post here.
I currently have been using CM11 for a few months now but miss some features on stock. (multiwindow, air view) so I installed Sacs ROM.
Everything was working great today except a known problem is wifi will not work due to radio opbstructions (i believe). So i attempted to change the baseband to MF9.
At first, Odin started then immidately it failed. The error read 'Fused 4 Binary 1'
So i assumed it was a connection error. I loaded back into download mode and tried again. Failed.
At this point i thought screw it, and took the battery out. tried to reboot and stuck at the soft brick "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I installed Kies. Plugged in my phone. Drivers installed but Kies will not connect. Try to do 'Firmware Upgrade and Initialization'
However Kies will NOT accpet my S/N number. i tried everything. writing it all out or with a space every 3 numbers or with 'DEC' at the front. nothing worked.
I even called sprint to double check S/N (ESN/DEC)
so basically I'm soft bricked and Kies is screwing me over. Any ideas?
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
whatthe_fuzz said:
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
Click to expand...
Click to collapse
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
whatthe_fuzz said:
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
Click to expand...
Click to collapse
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i searched around and eventually found a working .md5 file. its apparently is stock. got my phone to start booting but it got stuck at the yellow sprint screen. im going to try to boot into safe mode. any ideas how to access my recovery file? i have one form CWM and one from Ti Backup
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
leaderbuilder said:
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
Click to expand...
Click to collapse
I think i fixed it.
Problems resolved.
The issue was i had Sacs v4 which didnt support wifi and i read that it needed MF9 firmware.
i had a lapse in judgement and without thinking tried to go back from MJA. didnt catch it until now.
I eventually found the correct stock file. eventually got into the phone. rerooted and in the process of install the proper sacs ROM (v5.6)
this was a simple error that i shouldve caught thanks guys!
hopefully this ROM will work with wifi...
BTW, all my backups were wiped
Your backups weren't on your external sd? Ooo, that sucks. Glad you got it.
Sent from my SPH-L720 using XDA Premium 4 mobile app
I installed the KOT49H GE ROM on my AT&T SGH-I337 and it runs great. I then decided to see if there was an update to TWRP and I found an updated one and flashed it via goo.im. I later read that this is not the way to do it. Anyway, when I boot into recovery a big yella triangle appears and at&t scolds me for running in authorized firmware. I can boot into download, cancel it and the ROM boots and runs fine.
Under the "about device" page on settings it says the baseband is MK2 (because I flashed that modem). If I look at the boot loader version via android terminal emulator it shows I'm still on MDL.
Any ideas how to get recovery working again?
I am trying to understand the reason why you flashed a recovery.
From your post, it looks like you are using safestrap and deadly venom tool to run GE.
You can flash the MLD files from the tool to get the recovery back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
insaneretard said:
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
Click to expand...
Click to collapse
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
jmjoyas said:
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
Click to expand...
Click to collapse
Thanks for helping me out. I tried this yesterday and today with the link you provided. When I try to flash it via odin, it comes up as failed. On my phone, it says "SECURE CHECK FAIL: recovery" in red letters on the download page. Any other ideas?
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Do i need root to do this? I don't think I even have root any more. I'm running a custom ROM without root access. I tried to use CASUAL to root and install the recovery but it couldn't root it.
You will only need to root again if you go all the way back to stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hello All,
I am trying to update my wife's S4 to KitKat from MF3.
I unrooted using SuperSU. Prior to the unroot, I went to the system/xbin folder and deleted all references to BusyBox which left me with just 3 files.
Then I removed xposed and all other root apps except for Titanium Back up.
After that, I unrooted through SuperSu, and can confirm the phone does not have root any longer. Device Status: Official, if that means anything.
When I click on "Software update", the phone does not respond or even attempt to check for an update. Kies says I'm running the latest firmware... what am I doing wrong.
Thank you!
tarikakleh said:
Hello All,
I am trying to update my wife's S4 to KitKat from MF3.
I unrooted using SuperSU. Prior to the unroot, I went to the system/xbin folder and deleted all references to BusyBox which left me with just 3 files.
Then I removed xposed and all other root apps except for Titanium Back up.
After that, I unrooted through SuperSu, and can confirm the phone does not have root any longer. Device Status: Official, if that means anything.
When I click on "Software update", the phone does not respond or even attempt to check for an update. Kies says I'm running the latest firmware... what am I doing wrong.
Thank you!
Click to expand...
Click to collapse
You can update manually. You will go from MF3 to MK2 to NB1 to NC1.
MF3 to MK2:
Download the update from this post - link has title "DOWNLOAD >>>MF3>MK2<<< HERE"
MK2 to NB1:
Download the update from this post - link has title "DOWNLOAD>>>>>update.zip<<<<<HERE"
NB1 to NC1:
Download the update from this post
How to use the update is given in post 2 of the first link.
jmjoyas said:
You can update manually. You will go from MF3 to MK2 to NB1 to NC1.
MF3 to MK2:
Download the update from this post - link has title "DOWNLOAD >>>MF3>MK2<<< HERE"
MK2 to NB1:
Download the update from this post - link has title "DOWNLOAD>>>>>update.zip<<<<<HERE"
NB1 to NC1:
Download the update from this post
How to use the update is given in post 2 of the first link.
Click to expand...
Click to collapse
Thank you.
Now I am unable to boot to recovery. I believe I screwed it up sometime back when I tried to flash TWRP using Goo. Ran across a couple threads that had similar issues, but no workaround.
So now I am with an unrooted MF3 S4 that can't get into stock recovery and can't update over the air.
If you don't mind losing the data, you can directly Odin flash the stock full NB1 firmware.
If not you can search for stock mf3 recovery. I will provide a link if I find one.
jmjoyas said:
If you don't mind losing the data, you can directly Odin flash the stock full NB1 firmware.
If not you can search for stock mf3 recovery. I will provide a link if I find one.
Click to expand...
Click to collapse
Awesome. I'll search for it when I get on a computer.
How would I install the stock MF3 recovery?
Sent from my SM-N900T using XDA Free mobile app
jmjoyas said:
If you don't mind losing the data, you can directly Odin flash the stock full NB1 firmware.
If not you can search for stock mf3 recovery. I will provide a link if I find one.
Click to expand...
Click to collapse
Is this the method you are referring to?
stevey500 said:
I am on locked-bootloader MF3.
I have had a broken/non-bootable recovery menu since I started tinkering with modifying MF3 bootloader.
I followed this guide and did it all within my stock rooted touchwiz rom using terminal emulator and it worked perfectly. I didn't even have to run the last .sh, just simply dd'd the stock recovery.img image to its appropriate location.
So, bootable people with MF3 bootloader and broken recovery menus... do this:
http://d-h.st/AuY put this image file on your internal storage.
Run this command in ADB (type adb shell to get to shell) or go to terminal emulator and enter this:
su -c "dd if=/storage/sdcard0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
You should have a fully working stock recovery menu now.
Click to expand...
Click to collapse
Sent from my SM-N900T using XDA Free mobile app
I bet you'll be able to do the same procedure now using Flashify app to flash the stock recovery image file. Couldn't be so certain with an locked bootloader but it might. If flashify won't work to flash the stock recovery image, you'll have to do what is quoted above that worked for me in the past.
I'm baffled with this problem too. The OTA doesn't get sent to my phone either. I rooted my phone and deleted some bloatware but I have since unrooted and tried to flash the MK2 update zip in the stock recovery but all it does is just perform a factory reset. I'm stuck on 4.2.2
Exbruce said:
I'm baffled with this problem too. The OTA doesn't get sent to my phone either. I rooted my phone and deleted some bloatware but I have since unrooted and tried to flash the MK2 update zip in the stock recovery but all it does is just perform a factory reset. I'm stuck on 4.2.2
Click to expand...
Click to collapse
Odin the stock firmware
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Odin the stock firmware
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Is there anyway to do it without Odin?
Exbruce said:
Is there anyway to do it without Odin?
Click to expand...
Click to collapse
What's wrong with Odin? You've already done a factory reset so you won't lose sunny more data.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What's wrong with Odin? You've already done a factory reset so you won't lose sunny more data.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
At the moment, I don't have any access to a computer
Exbruce said:
At the moment, I don't have any access to a computer
Click to expand...
Click to collapse
That's a good reason, lol. If you've modified system files, removed bloat ware, the ota won't work.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
That's a good reason, lol. If you've modified system files, removed bloat ware, the ota won't work.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Damn I should've looked at the forums before I did all of that
I apologize in advance for my lack of knowledge and understanding. I recently flashed a custom rom on my Galaxy S4, and it worked but I noticed the Wifi wasn't working, so I attempted to get it to work by trying again. It ended up badly, and it's now been stuck on the boot screen for a while. I tried doing a factory reset and wiping the cache partition, but it was still stuck on the screen. I can also still get onto download mode, so I'm hoping that means I can still save my phone.. I'm also not worried if I lose my internal storage, considering I'm just desperate to get my phone working again. I have an SGH-I337 AT&T phone.
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What rom did you try to flash and what firmware version are you on. You're phone is not bricked and is recoverable.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Daze_ said:
Thank you for the fast response. I tried flashing Goldeneye rom and used Safestrap recovery. I'm on firmware version NC1. It's relieving to hear my phone is still fixable. Thank you again!
Click to expand...
Click to collapse
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would flash the nb1 tar file in Odin. Then do the nb1 to nc1 update and start over again. You'll need to root again and install safestrap. Have you successfully flashed roms in safestrap before?
Start here for the nb1 tar http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I'll try that. Also, this was the first time I've ever flashed a rom, and I'm unsure if you would consider it successful, since the wifi wasn't working, but besides that, I saw no issues.
I had to go this same route when I was messing around and soft bricked like you. It's not hard to recover following the instructions . Odin the NB1 stock tar, let phone boot to ensure it is alive again. Then use the built in recovery to install the NC1 update. Reboot and you are ready to towelroot/supersu/safestrap.
Don't worry. It will be ok!
Sent from my SAMSUNG-SGH-I337 using Tapatalk