I am unsure if I bricked my Sprint Note 3, but I tried to roo it with Chain Fire and odin, using Qbking77's YouTube video as a guide. But after the root was complete, 60% of my apps were gone, I can't using any google powered apps, and I can't go into the phones settings. Everything force closes. Honestly, I'm just trying to do a proper root so I can use Cyanogen Mod. Can someone help me revert to before I rooted,and explain the process to get cyanogen?
I followed the instructions provided, and downloaded
SM-N900P (Sprint): CF-Auto-Root-hltespr-hltespr-smn900p.zip
Followed the further stated instructions, open odin, and I cannot insert the MD5 file into odin. I was able to before, and now I cannot. Earlier I was able to do so, and as stated above, after I did it several apps disappeared, google play services no longer works,supersu is on the phone, and I cannot access the phones settings. The only thing I can do is use the stock browser. I am asking what to do/what I did wrong/how to fix it/or how to continue. If these questions cant be answered, how do I revert back to stock?
Thealbatross said:
I am unsure if I bricked my Sprint Note 3, but I tried to roo it with Chain Fire and odin, using Qbking77's YouTube video as a guide. But after the root was complete, 60% of my apps were gone, I can't using any google powered apps, and I can't go into the phones settings. Everything force closes. Honestly, I'm just trying to do a proper root so I can use Cyanogen Mod. Can someone help me revert to before I rooted,and explain the process to get cyanogen?
I followed the instructions provided, and downloaded
SM-N900P (Sprint): CF-Auto-Root-hltespr-hltespr-smn900p.zip
Followed the further stated instructions, open odin, and I cannot insert the MD5 file into odin. I was able to before, and now I cannot. Earlier I was able to do so, and as stated above, after I did it several apps disappeared, google play services no longer works,supersu is on the phone, and I cannot access the phones settings. The only thing I can do is use the stock browser. I am asking what to do/what I did wrong/how to fix it/or how to continue. If these questions cant be answered, how do I revert back to stock?
Click to expand...
Click to collapse
I would Odin back to nk4, then do the ota, and then instead of all the cf stuff I would just odin twrp and flash supersu. It's literally that simple.
Sent from my SM-N900P using XDA Free mobile app
How do I do these things?
Thealbatross said:
How do I do these things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=60272319
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
http://forum.xda-developers.com/showthread.php?p=60272319
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
The TWRP file in that post downloads as .img, and when I change it to .tar it becomes unusable and odin marks it as a fail. This has been the issue for me throughout this entire root process. People to me "Download this" and it either
1. Doesn't work
2. Gets to 100% extraction then fails
3. Odin wont let me insert the file.
I know its not me doing anything wrong. Right now, my phone boots to the sprint logo, and nothing past it. I can go into download mode and that's about it. I just need help and the proper instructions to either put it back to stock, or do a proper root. I rooted a Galaxy S2 years ago, and several other phones between now and then, and got it on the first try. This process with the Note 3 has been very frustrating, and I've been without my phone for 4 days. So if you, or anyone else knows the DETAILED steps I need to take, please help.
I did what you said with the NK4 thing, and like I said above, it would get to 100% extraction then fail. I got it from the sammobile site, and they wouldnt even let me redownload it. And I dont know what OTA is.
Thealbatross said:
The TWRP file in that post downloads as .img, and when I change it to .tar it becomes unusable and odin marks it as a fail. This has been the issue for me throughout this entire root process. People to me "Download this" and it either
1. Doesn't work
2. Gets to 100% extraction then fails
3. Odin wont let me insert the file.
I know its not me doing anything wrong. Right now, my phone boots to the sprint logo, and nothing past it. I can go into download mode and that's about it. I just need help and the proper instructions to either put it back to stock, or do a proper root. I rooted a Galaxy S2 years ago, and several other phones between now and then, and got it on the first try. This process with the Note 3 has been very frustrating, and I've been without my phone for 4 days. So if you, or anyone else knows the DETAILED steps I need to take, please help.
I did what you said with the NK4 thing, and like I said above, it would get to 100% extraction then fail. I got it from the sammobile site, and they wouldnt even let me redownload it. And I dont know what OTA is.
Click to expand...
Click to collapse
If you're not getting a boot then you need to restart.
1)Get the tar for nk4.
2)Odin the nk4 (but get to download mode by pulling the battery then boot to download mode).
3) After a successful odin of nk4, you should be official. If not, boot to recovery, wipe data, then odin again (battery pull)
4) If going to oc5, take the ota. Or go to next step.
5) after ota (or not) now we root. Provided you don't care about knox, the best way is to get the twrp img from their site. Flash that with odin (battery pull).
6) download a supersu.zip to flash from twrp, and flash it.
I can't link these files right now, but it's easy to find them. If you need links later, I can help in an hour or so.
And ota is over the air, when you get a notification for an update
Sent from my SM-N900P using XDA
Ok, thanks, Ill wait for the file links.
Thealbatross said:
Ok, thanks, Ill wait for the file links.
Click to expand...
Click to collapse
Nk4 tar: http://forum.xda-developers.com/showthread.php?p=47355107
Twrp link to sprint note 3, pay attention to the odin instructions: http://twrp.me/devices/samsunggalaxynote3sprint.html
SuperSU: https://docs.google.com/file/d/0B8umY4TqG8CVamo0amUtQ3hKNXc/edit?usp=docslist_api
There ya go.
Sent from my SM-N900P using XDA Free mobile app
I can very thankfully say that md5 file downloaded and is installing without a problem.
now, the TWRP site you gave me, I can use the most recent version, correct?
EDIT: Both NK4 and TWRP are installed but still cant get by sprint logo. Is this normal?
Thealbatross said:
I can very thankfully say that md5 file downloaded and is installing without a problem.
now, the TWRP site you gave me, I can use the most recent version, correct?
Click to expand...
Click to collapse
Yes.
Link post updated for supersu
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
If you're not getting a boot then you need to restart.
1)Get the tar for nk4.
2)Odin the nk4 (but get to download mode by pulling the battery then boot to download mode).
3) After a successful odin of nk4, you should be official. If not, boot to recovery, wipe data, then odin again (battery pull)
4) If going to oc5, take the ota. Or go to next step.
5) after ota (or not) now we root. Provided you don't care about knox, the best way is to get the twrp img from their site. Flash that with odin (battery pull).
6) download a supersu.zip to flash from twrp, and flash it.
I can't link these files right now, but it's easy to find them. If you need links later, I can help in an hour or so.
And ota is over the air, when you get a notification for an update
Sent from my SM-N900P using XDA
Click to expand...
Click to collapse
So steps 2 and 3 worked, but I still get stuck at the sprint logo.
Actually, ignore everything stated above, Im back to stock with custom recovery. What's Next?
Thealbatross said:
So steps 2 and 3 worked, but I still get stuck at the sprint logo.
Click to expand...
Click to collapse
Boot to recovery, wipe data, and try booting. If that didn't do out, wipe data again then pull battery, boot to download mode, and odin nk4 again. Those files are the ones I have used so...yeah...lol.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
Boot to recovery, wipe data, and try booting. If that didn't do out, wipe data again then pull battery, boot to download mode, and odin nk4 again. Those files are the ones I have used so...yeah...lol.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Its good to go now, look above lol
Thealbatross said:
Actually, ignore everything stated above, Im back to stock with custom recovery. What's Next?
Click to expand...
Click to collapse
Well, if you have custom recovery and don't want ota, flash supersu.
If you want ota you gotta redo the nk4 steps and then take ota, but do not install twrp once you odin
Sent from my SM-N900P using XDA Free mobile app
Do I need it? Im not even sure what it and oc5 are.
Thealbatross said:
Do I need it? Im not even sure what it and oc5 are.
Click to expand...
Click to collapse
Oc5 is lollipop. Major upgrade to Android. However, many things, like xposed, aren't working yet. Your call man.
Sent from my SM-N900P using XDA Free mobile app
Well, ota sounds like it will be helpful. And the version of Cyanogen I want required lollipop. So walk through me through I guess. Everything has gone well so far haha
jlechner said:
Oc5 is lollipop. Major upgrade to Android. However, many things, like xposed, aren't working yet. Your call man.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Actually, ill just move on without them. I dont want to mess up my current progress.
Thealbatross said:
Actually, ill just move on without them. I dont want to mess up my current progress.
Click to expand...
Click to collapse
Ha! It's all in learning man. That and finding downloads. If you decide you want ota, just re-odin nk4 (after a factory reset, and use battery pull for download mode), take the ota, re-odin twrp, reboot to twrp and flash supersu.zip. Pretty easy.
Sent from my SM-N900P using XDA Free mobile app
Related
Hers my dilema, i had 4.1.1 rooted and unlocked and decided to return to stock so I could update to 4.1.2. all went well downgrading to stock but when I got the OTA the phone bootlooped. I could not access the recovery menu to wipe cache (as suggested in a few other post) so I ended up having the download the newest image and flash it to my phone. That worked after using the 16Gb pit file that is here in the forum (it kept failing before trying the pit file). THE QUESTION I have is, how do I root with casual without bootlooping? I tried after getting 4.1.2 installed and it went back into the bootloop. Any help would be greatly appreciated.
big.daddy said:
Hers my dilema, i had 4.1.1 rooted and unlocked and decided to return to stock so I could update to 4.1.2. all went well downgrading to stock but when I got the OTA the phone bootlooped. I could not access the recovery menu to wipe cache (as suggested in a few other post) so I ended up having the download the newest image and flash it to my phone. That worked after using the 16Gb pit file that is here in the forum (it kept failing before trying the pit file). THE QUESTION I have is, how do I root with casual without bootlooping? I tried after getting 4.1.2 installed and it went back into the bootloop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
OK, how exactly did you get 4.1.2 on your phone? You say that using the very latest version of CASUAL still causes bootloops when trying to unlock?
The obvious thing here is YOU NEVER SHOULD HAVE WENT TO ACCEPT THE OTA.
As it is this is a question better answered by AdamOutler or Droidstyle.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
OK, how exactly did you get 4.1.2 on your phone? You say that using the very latest version of CASUAL still causes bootloops when trying to unlock?
The obvious thing here is YOU NEVER SHOULD HAVE WENT TO ACCEPT THE OTA.
As it is this is a question better answered by AdamOutler or Droidstyle.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
big.daddy said:
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
Click to expand...
Click to collapse
The more updates Verizon pushes the tighter they luck the phone down trying to deal up all the holes our exploits could use, in turn that makes the exploits more risky and more prone to cause potential trouble.
It is best to just leave everything alone once you get rooted and unlocked and just flash the updates via TWRP/CWM, there is no real reason or advantage to updating the normal way. It does nothing different than flashing the ROM in recovery and has no advantages and a huge amount of risk.
It may be that the Odin flashable ROM you got was missing something or was wonky in some way since it didn't come from XDA. It shouldn't have reacted that way if you were using the most up to date version of CASUAL.
Sent from my SCH-I605 using XDA Premium HD app
big.daddy said:
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
Click to expand...
Click to collapse
Big.daddy can I ask what you used to get back from the bootloop to where your at now? Sorry to bother you but I screwed up somewhere, once again
chiefsfan69 said:
Big.daddy can I ask what you used to get back from the bootloop to where your at now? Sorry to bother you but I screwed up somewhere, once again
Click to expand...
Click to collapse
I used Odin to get the phone back to stock (vramc3). I tried it on two computers and eventually got it to rum when using the 16 GB .pit file that can be found on this forum. That got me back to stock. I then used casual to re-root and unlock. The thing I have learned is that once twrp is intalled, I only need to download a ROM based on the Verizon stock (unless you want custom) and flash it through twrp. NOT WHAT I INITIALLY DID. I flashed back to stock and accepted an ota which didn't work out well. Took me 5 hours of downloading and trying to get the phone flashed. Good luck. The first thing I would try is downloading the beanstown vzw stock ROM and flash it with the .pit file.
big.daddy said:
I used Odin to get the phone back to stock (vramc3). I tried it on two computers and eventually got it to rum when using the 16 GB .pit file that can be found on this forum. That got me back to stock. I then used casual to re-root and unlock. The thing I have learned is that once twrp is intalled, I only need to download a ROM based on the Verizon stock (unless you want custom) and flash it through twrp. NOT WHAT I INITIALLY DID. I flashed back to stock and accepted an ota which didn't work out well. Took me 5 hours of downloading and trying to get the phone flashed. Good luck. The first thing I would try is downloading the beanstown vzw stock ROM and flash it with the .pit file.
Click to expand...
Click to collapse
Thanks man, **** I just went through all this bs and finally got mine last night but then I tried to do casual and something went wrong and now I am back in the loop and I don't know if i should just flash the same I did just last night to get it back or what? Thank you though I really appreciate your help
I would try casual agai if you can get into download mode (power + vol dn+ home). If that doesn't work I'd try reflashing. Good luck.
big.daddy said:
I would try casual agai if you can get into download mode (power + vol dn+ home). If that doesn't work I'd try reflashing. Good luck.
Click to expand...
Click to collapse
I can get in download mode but the problem seems to be the adb, and since i can't get in the phone to turn it on casual never picks up the device, for all I know?
chiefsfan69 said:
I can get in download mode but the problem seems to be the adb, and since i can't get in the phone to turn it on casual never picks up the device, for all I know?
Click to expand...
Click to collapse
Reflash with Odin
big.daddy said:
Reflash with Odin
Click to expand...
Click to collapse
Hold on, reflash casual in odin?
chiefsfan69 said:
Hold on, reflash casual in odin?
Click to expand...
Click to collapse
No, do what you did last time in Odin again.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
No, do what you did last time in Odin again.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I have been trying, this time around it hasnt passed a single flash, on anything?
chiefsfan69 said:
I have been trying, this time around it hasnt passed a single flash, on anything?
Click to expand...
Click to collapse
Check the drivers to make sure the CASUAL driver isn't the one in use.
Sent from my SCH-I605 using XDA Premium HD app
You may also want to try a different computer...... Different USB ports too. I will work it takes a little patience.
I just rooted a Verizon GS4 (VRUAME7) using this method. Everything went fine. I verified root with Root Checker, rebooted the phone, checked again.
Then I followed this method to install TWRP. When I rebooted the device as instructed, it got stuck on a splashscreen that has and Android logo and says "Downloading...Do not turn off target!!" :'(
The upper left in red says "Could not do normal boot. ODIN MODE"
I tried a battery pull, vol dwn + power, vol up + power and vol down + up + power.
How do I get back to normal boot or into TWRP recovery? I have a ROM I'd like to install, and as of now...it won't get past that splash screen.
What do I do?
Thanks!
First off youre in the wrong section. Questions go in the Q and A section. Second your on the me7 ota and you cant install a custom recovery/roms on the me7 ota. To get your phone booting again you will have to flash the stock recovery (not sure if someone has posted a stock recovery flashable via odin as I havent looked)or flash me7 again.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
First off youre in the wrong section. Questions go in the Q and A section. Second your on the me7 ota and you cant install a custom recovery/roms on the me7 ota. Not yet at least. I havent ran into this problem myself so I dont know an exact fix. To get your phone booting again you will have to flash the stock recovery (not sure if someone has posted a stock recovery flashable via odin as I havent looked)or flash me7 again (which will work without a doubt).
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Where was there a note about ROMS not working on ME7. I didn't see that anywhere.
Regardless, how do I fix it?
dreamliner330 said:
Where was there a note about ROMS not working on ME7. I didn't see that anywhere.
Regardless, how do I fix it?
Click to expand...
Click to collapse
In the thread about the me7 update.
Also in the 500 or so threads where people freaked out when they couldn't ROM anymore after they took the update.
Or in the bounty thread.
Sent from my SCH-I545 using xda premium
^I didn't update.
dreamliner330 said:
^I didn't update.
Click to expand...
Click to collapse
if your on me7 then you updated..
Sent from my SCH-I545 using xda app-developers app
Check this thread
http://forum.xda-developers.com/showthread.php?t=2301259
Sent from my SCH-I545 using xda app-developers app
elliwigy said:
if your on me7 then you updated..
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I didn't. Perhaps it automatically did it or it was updated when I got it, as I don't recall manually doing it.
Regardless. What do I do now?
I already posted how to fix it ............ if you dont know how to restore your phone via odin then you have a small amount of reading to do and then your phone will be back up and running in no time :thumbup:
Sent from my SCH-I545 using Tapatalk 2
dreamliner330 said:
I didn't. Perhaps it automatically did it or it was updated when I got it, as I don't recall manually doing it.
Regardless. What do I do now?
Click to expand...
Click to collapse
There are reports of it doing it over night.
To fix the phone find the full me7 Odin package and Odin it back to stock. Id link you but I have had no reason to have links for me7 packages yet.
Sent from my SCH-I545 using xda premium
dreamliner330 said:
Regardless. What do I do now?
Click to expand...
Click to collapse
I had this same problem trying to install TWRP. What I did to fix it was to boot into download mode (volume down + home +power) and then I got prompted for did I really want to do that, I responded no and the phone booted up.
Sent from my SCH-I545 using Tapatalk 2
thornev said:
I had this same problem trying to install TWRP. What I did to fix it was to boot into download mode (volume down + home +power) and then I got prompted for did I really want to do that, I responded no and the phone booted up.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. :victory:
This worked perfectly.
Hopefully it'll won't fall back into that. Can't wait until I can ROM this sucker. Laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaag.
Since you have the update, boot the phone up in Odin mode and plug in your USB cable.
If you installed the desktop software you will have a Verizon folder in your start menu.
In that folder there should be an app "Verizon Software Upgrade Utility"
Run that and it should tell you you are up to date.
There is a repair utility within that app, run that and it should fix your problem.
It takes a while because it downloads the rom and then flashes it.
No guarantees, but I believe that will get you back to stock unrooted.
Sent from a Galaxy S4... Far far away
Sounds like he just got into download mode and didn't recognize it, and his rom, recovery, and everything was untouched.
To the OP, you're probably good if your phone has booted normally, works fine, and you're still rooted. You can't flash any roms or mods, but you can still apply some mods by simply pushing them to your /system partition, setting permissions, and rebooting. Either follow the instructions for which directory to put the file/files in, or you can open up a flashable zip and use the same path as the directories in the zip.
You should even be able to push a modded framework-res.apk and SystemUI.apk and rename the old ones, once people start building ME7 roms, though I can't guarantee it'll work. All you can do is try, and now you know how to get into Download mode to use Odin if it doesn't work.
As far as plain lag goes, just freeze alot of the bloat, there's around 50 apks (in MDK, anyway) that aren't doing anyone any good. Then grab a cpu app like Trickster Mod and see what, if any, parameters the stock kernel enables you to change. If you can set the Interactive cpu governor, Deadline scheduler, Performance gpu governor, and increase the read-ahead size, you should see a significant improvement.
:thumbup:
Sent from my SCH-I545 using Tapatalk 2
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Development is only for developers to post work
Thread moved
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
bunklung said:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
Click to expand...
Click to collapse
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
Surge1223 said:
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
Click to expand...
Click to collapse
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
He isnt rooted though, so would have to root right away. If he rebooted before the update started deleting/patching files and changining permissions then it might be ok. I just would rather have no chance of the update patching the recovery or the kernel. The odin image would format the partitions and would delete the update it shouldny brick the phone because the bootloader and firmware arent patched until literally the screen shows 95.39% of the update is complete.
set_progress(0.953849);
ui_print("Patching hidden files...");
ui_print("Patching NON-HLOS modem image...");
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name
Etc..etc
And rooting is a long process? Hes going to have to root regardless if he wants to cancel it out. No reason to take an extra step to do the same thing.
Sent from my SCH-I545 using Tapatalk 2
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
Sent from my SCH-I545 using XDA Premium 4 mobile app
bunklung said:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).
The phone rebooted into recovery to apply the update, but I pulled the battery.
I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.
How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?
I can get into odin mode, but when I try to load recovery it tries to apply the update.
Click to expand...
Click to collapse
Boot and pull the battery at the same place you did before, after about 9 or 10 times the phone will tell you update failed. Then root immediately. Do not pass go do not collect $200
Sent from my BNTV250A using xda app-developers app
Surge1223 said:
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hear ya there.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
bunklung said:
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
Click to expand...
Click to collapse
Wasnt for sure if the odin decline would work but if it would have it would of saved you a lil bit of time. Glad you got her up and running.
Sent from my SCH-I545 using Tapatalk 2
bunklung said:
All,
Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.
I used the nowipe Odin image and all is well:
http://forum.xda-developers.com/showthread.php?t=2301259
Still on MDK!
I took the extra steps and rooted the phone and renamed/deleted:
/data/fota contents
FWUpgrade.apk
FWUpgrade.odex
SDM.apk
SDM.odex
LocalFOTA.apk
I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
Click to expand...
Click to collapse
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
Party_Grunt said:
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
Click to expand...
Click to collapse
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
Surge1223 said:
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
Click to expand...
Click to collapse
Thanks, it did work. Unfortunately the last time this happened I was on vacation with no computer available so I was forced to take the OTA update or have no phone for two weeks. I had only rooted the week before and had not gotten around to putting in a custom recovery and bootloader, so I was SOL. Didn't even know root had been found for ME7 until last week. My timing seems to suck on this.
Now time to root and delete the upgrade files.
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
james581 said:
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
Click to expand...
Click to collapse
Safestrap doesn't root, so there's things that you've done that you're not telling us. How did you root your phone? What else did you do after you rooted?
The "firmware detected issues" usually means that you tried to flash recovery, custom kernel, etc. Did you try to flash custom recovery?
james581 said:
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
Click to expand...
Click to collapse
How did u root your phone?
safestrap enabled, Hyperdrive driven
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
james581 said:
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Why were you in odin? What were you flashing?
james581 said:
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I don't really know what's going on here as you're a little confusing but figured I'd chime in here..
If you were on mk2 then you should just rooted the phone using SafeRoot, very easy and reliable and Safe!
Then you should have installed SafeStrap by simply downloading the. Apk file from that thread. Boooom you'd be all set and ready to flash.
None of that requires Odin. Unless I missed the post where you said you were trying to Odin back for a fresh start??!!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
I don't really know what's going on here as you're a little confusing but figured I'd chime in here..
If you were on mk2 then you should just rooted the phone using SafeRoot, very easy and reliable and Safe!
Then you should have installed SafeStrap by simply downloading the. Apk file from that thread. Boooom you'd be all set and ready to flash.
None of that requires Odin. Unless I missed the post where you said you were trying to Odin back for a fresh start??!!
Click to expand...
Click to collapse
I used Odin because the get root string wasn't working it rooted phone then after a reboot it rebooted itself twice and went to screen saying firmware issue detected. but I b no longer have that phone I have a replacement one that followed safe root and everything working good to the best of my knowledge. . I am a noob and have a lot to learn. thanks for all the feedback.
Sent from my SCH-I545 using XDA Premium 4 mobile app[/QUOTE]
james581 said:
I used Odin because the get root string wasn't working it rooted phone then after a reboot it rebooted itself twice and went to screen saying firmware issue detected. but I b no longer have that phone I have a replacement one that followed safe root and everything working good to the best of my knowledge. . I am a noob and have a lot to learn. thanks for all the feedback.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
[/QUOTE]
a sticky thread is set up and is a WIP for S4 people in the general section to assist those who wish to mod their phones
http://forum.xda-developers.com/showthread.php?p=49335074
I've been so busy and just completely forgot how to mess with my phone since I have not needed with it for awhile, I'm pretty much lost now. Here's what I am currently running :
Jellybomb ver 2.0, freeza's 3.4.0 beastmode kernel, still on mj4 4.3.
Can someone provide me with step by step instructions on how to update to the current version. If possible, I want to keep my current setup, like my homescreen icon setup, apps, etc. Basically I want to keep my phone the way it is now, but just update it. If it's not possible, guess I'll just start over after the update. I feel like a noob all over, please bare with me.
Sent from my SM-N900P using XDA Premium 4 mobile app
You'll want to accept the ota updates, then find how to root note 3; thread in general, it's quick and easy. Just watch the video by qbking77.
Good luck
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
I've been so busy and just completely forgot how to mess with my phone since I have not needed with it for awhile, I'm pretty much lost now. Here's what I am currently running :
Jellybomb ver 2.0, freeza's 3.4.0 beastmode kernel, still on mj4 4.3.
Can someone provide me with step by step instructions on how to update to the current version. If possible, I want to keep my current setup, like my homescreen icon setup, apps, etc. Basically I want to keep my phone the way it is now, but just update it. If it's not possible, guess I'll just start over after the update. I feel like a noob all over, please bare with me.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, there are very specific instructions on upgrading from MJ4 to NAB (or NC5). You can't just do a wipe in recovery and update. I have written up fool-proof instructions over in this thread, which I have copied below:
I just took the plunge and found it to be a relatively easy process. I followed the procedure I listed earlier, but still got the symlinks error, so I did a "TWRP Format" as suggested by derail412 and that fixed it. Overall, it took less than 1 hour to do everything. I'll outline my process below:
Detailed instructions on upgrading from a MJ4 (Jellybean) to NAB (KitKat) Rom.
Downloaded all files required. I will provide a link to the files. For all ODIN file flashing, I had "Auto Reboot" and "F. Reset Time" checked.
Backed up all "important" files off of the internal memory to the MicroSD card. Copied the fre3 Rom file to the MicroSD Card.
Use ODIN 3.07 "PDA" to flash the MJ4 Stock TAR file (filename: N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md5). Took 5-10 minutes.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Download Mode.
Use ODIN 3.07 "PDA" to flash the NAB Stock TAR file (filename: N900PVPUCNAB_N900PSPTCNAB_N900PVPUCNAB_HOME.tar.md5). Took 5-10 minutes.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Download Mode.
*Optional Step* Use ODIN 3.07 "Bootloader" to flash the NAB Engineered Bootloader TAR file (filename: nabfirmware.tar). Took 1 minute.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Download Mode.
Use ODIN 3.07 "PDA" to flash the TWRP 2.7.0.0 TAR file (filename: openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar). Took 1-2 minutes.
Once phone reboots, allow a few minutes for things to get settled. Reboot into Recovery Mode.
Made a TWRP Backup of the Stock NAB Rom, set backup location to the MicroSD Card. Took 5-10 minutes.
Did an "Advanced" Wipe on TWRP. Checked all options except MicroSD Card.
Once done, go back to "wipe" menu in TWRP. Choose "Format Data" and had to type in "yes" to wipe.
Rebooted to Recovery. Do not try to install SuperSu, since you have no ROM loaded yet.
Install the ROM in TWRP.
Rebooted to ROM and allowed a few minutes for everything to settle down.
Rebooted ROM to make sure everything is running fine.
All-in-all, took only about 45 minutes, but with writing this down, I'd say it took a total of 1 hour. Not too shabby.
Click to expand...
Click to collapse
The latest version is NC5, but if you just replace all of the above NAB files with NC5 ones, it'll work and you'll be on the most-recent version of the phone software.
If you want a bloatware-free ROM, I'd recommend using either of Freeza's Roms. If you want a more modded or themed one, there are tons on the Development Section.
As far as keeping everything the same as you have it now... I'd point you to Titanium Backup. With it you can backup and restore many of your settings and data when you upgrade. I'd just recommend not restoring too many system files (red ones), as they can mess things up.
Let me know if you have any more specific questions, I can hopefully answer anything you might need help on.
topherk said:
Well, there are very specific instructions on upgrading from MJ4 to NAB (or NC5). You can't just do a wipe in recovery and update. I have written up fool-proof instructions over in this thread, which I have copied below:
The latest version is NC5, but if you just replace all of the above NAB files with NC5 ones, it'll work and you'll be on the most-recent version of the phone software.
If you want a bloatware-free ROM, I'd recommend using either of Freeza's Roms. If you want a more modded or themed one, there are tons on the Development Section.
As far as keeping everything the same as you have it now... I'd point you to Titanium Backup. With it you can backup and restore many of your settings and data when you upgrade. I'd just recommend not restoring too many system files (red ones), as they can mess things up.
Let me know if you have any more specific questions, I can hopefully answer anything you might need help on.
Click to expand...
Click to collapse
Very detailed, thanked you already but I want to say thanks again. I will give it a go tomorrow night.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
Very detailed, thanked you already but I want to say thanks again. I will give it a go tomorrow night.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How did it go? Any issues?
topherk said:
How did it go? Any issues?
Click to expand...
Click to collapse
Have not tried yet, been so busy haven't had time... Hopefully in 2 weeks or so lol
Sent from my SM-N900P using XDA Premium 4 mobile app