(Note - I'm unrooted and on stock MC2)
I'm going crazy at this point... I figured I'd just wait for my phone to get the OTA but it's already been 11 days, no OTA.
So then, fine, I figured I might as well use Kies to do the trick - no dice, I get the following message: "Your device's current firmware version is not supported to update firmware via kies."
Whatever, I just hit up trusty old XDA to find the update.zip file that I can apply easily from stock recovery. I found the file here. After realizing I needed an SD card for some reason (since stock recovery doesn't have the option to apply update.zip from internal storage) I finally did it... Until it encountered an error and terminated. Rebooted, still on 4.1.2. Tried again, same problem.
THEN I started looking for the files I could use to push the update to my phone through Odin.This thread sent me to sammobile, which, after making me register, sent me to hotfile. I keep trying to press the "Regular Download" button but nothing happens... it's not downloading!
Now I'm super frustrated, can someone tell me how I can get my hands on this elusive beast? Again, I'm unrooted and stock and have no desire to flash a ROM.
Okay, I'd got here and follow the OP instructions http://forum.xda-developers.com/showthread.php?t=2541395
Then i'd stop posting they same thing in to different sections. Just root your phone, place a custom recovery on it, and flash 4.3. I do want to sound rude or disrespectful but we have to keep the forums clean and clutter free.:laugh:
daswahnsinn said:
Okay, I'd got here and follow the OP instructions http://forum.xda-developers.com/showthread.php?t=2541395
Then i'd stop posting they same thing in to different sections. Just root your phone, place a custom recovery on it, and flash 4.3. I do want to sound rude or disrespectful but we have to keep the forums clean and clutter free.:laugh:
Click to expand...
Click to collapse
Sorry, are you saying that the only way to update is by rooting and installing this ROM?
You should get the OTA, just got a notification today on mine and I'm not even on stock Might be a good to root though as there are nasty bootloader mods in 4.3. If you are rooted on 4.1.2 check out the Note 2 development threads for the mk4 zip and several mk4 based rom updates (synergy etc). Just flash the modem then the Rom. (use goo manager to make sure you're on the latest boot manager). No custom kernels that I've been able to find yet unfortunately. Figure since you're rooted this all makes sense to you
I'm on stock and waited for the update for many days. No dice. But then I installed Kies on my PC, connected the phone, and was prompted to run the update. Now running 4.3.
I posted it at the end of the thread here (it's hosted from my Dropbox account).
http://forum.xda-developers.com/showthread.php?t=2536242
This is the MK4 Stock Un rooted Odin file I found in a tmp folder on my computer while Kies was grabbing the update. I've had it up for a few days with no complaints and I've flashed it 3-4 times with no issues. Just to be safe, wipe data and cache AFTER update has completed.
Sent from my SPH-L900 using xda app-developers app
Related
So I rooted mine S III and flashed the clockworkmod recovery in preparation to install Cyanogen mod 10 ROM for it, bute after reading more I decided to not do it, afraid of bricking, unstable ROM etc. After a while I used super user option to ''Un-root'' it, after reboot it was gone and I though it was back to normal state. Now just last week I received Update from T-mobile which is bugging me every few days, but when I try to install it the phone boots with Android icon and it's belly open like shelf with tesseract moving around and progress bar for few seconds, then recovery shows up and says something failed. Can I throw it out somehow and install the update? I'm worried because I won't be able to install the 4.1 which is coming sometime soon.
I have yet to come across a stock recovery file on its own. You probably need to ODIN back to stock. Make sure you back up.
Also, (assuming you have a T Mobile phone)I believe the OTA you are receiving is the UVALH2 update, in which case you can already find that ODIN package in this thread if not, there are other stock images in this thread also.
Infamous_Cheez said:
I have yet to come across a stock recovery file on its own. You probably need to ODIN back to stock. Make sure you back up.
Also, (assuming you have a T Mobile phone)I believe the OTA you are receiving is the UVALH2 update, in which case you can already find that ODIN package in this thread if not, there are other stock images in this thread also.
Click to expand...
Click to collapse
Screw the update I want Jelly Bean, what if it shows up and phone just boots up into recovery and just stands there like an idiot?
Only two ways to get jb right now is to update to UVALH2 then apply the ota patch from samsung. Alternatively wildchld has the jb rom ready to go in the dev thread.
Note that with these updates if you flash a rom with cwm or twrp you will not get the full update. Only odin or kies can update all partitions available in the ota.
Sent from my SGH-T999 using xda app-developers app
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Monoclypsus said:
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Click to expand...
Click to collapse
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
ok
topherk said:
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
Click to expand...
Click to collapse
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Monoclypsus said:
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Click to expand...
Click to collapse
Yeah, that same method should work. I personally like the custom recoveries, but understand your desires to leave it at stock recovery (not triggering the flash counter).
Like I mentioned before, Samsung hasn't (and most likely won't) locked their bootloaders, so any rooting method that has worked in the past should work in the future. Just make sure to read the last 3-4 pages of the thread for whatever method you're trying to use to see if there are any issues. I know an earlier version of mskip's toolkit was having issues with JB for a little bit (it's updated now).
Well I'm gonna give it a shot. Ill let you know how it turns out.
Sent from my SPH-L710 using xda app-developers app
Just went with cf autoroot. Worked fine.
Sent from my SPH-L710 using xda app-developers app
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
jkj said:
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
Click to expand...
Click to collapse
I replied to your thread. I hope it works for what you need.
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...
Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.
As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
I had the same problem
I just had this same problem and was lucky enough to fix it!!!!
vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it
Have you tried the auto root course??
Sent from behind you
Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.
Co-author root didn't work, and nor did Root66
I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?
You can try first wiping just dalvik and cache, then try factory reset.
Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.
I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.
I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. VoilĂ !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?
DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk
Rooted/Flashed my phone a long time. Constant bugs and errors. I really don't remember what all I did but I think I almost have it completely unrooted and back to stock. However, I can't update OTA. I've reflashed using this file, http://forum.xda-developers.com/showthread.php?t=2658486. Fixed just about all my issues and I actually have a lot of space on my phone. When I try to do the OTA Update, it doesn't install the update. Once it boots into recovery mode to install the update it gives an error. Can someone help my to 100% fully get my phone back to stock and be able to install OTA updates? I'm clueless.
First, did the 4.4.2 ota fail after a certain percentage? If so you may actually be partially updated already. If so, flashing MJB firmware/bootloader will hard brick.
Install and open Terminal Emulator and enter this:
getprop ro.bootloader
If it says MJB, you are still on 4.3 and can refresh that. If it says NE4, do not flash MJB!
If you can still flash MJB, there is a thread in General (I think that's where) that has the Odin flashable firmware package. Flash that with Odin and factory reset. Then try the OTA.
Factory resetting with stock recovery installed will wipe internal sd card, so back up first!
There are also a few threads in General that can help you update if the OTA continues to fail.
I'm unrooted. At least im pretty sure of that. I cant run superu anumore and root checker says im not rooted. Can I still access the terminal without being rooted. I know I had clockeork mod recovery. I also had used cyanogen mod at one point. Now I have the stock recovery but when I boot into recovery I get an error. I will post the error and install percentage as soon as the ota update downloads.
Yes, you can still run getprop w/o root. Just install terminal emulator by jackpal from the play store.
Yeah it said I747UCUEMJB. Like I said my recovery gives me an error. When I try flashing at all with odin it fails. Trying to install the ota update now. After it fails ill give the error recovery gives me. OTA update fails at 24%
Ok, booting into Android system recovery gives me a no command error than it shows the list of options. When I go to reboot system now, it gives me a no command error as well. Download mode used to give me an error, might only show up when attempting to flash something. However, these are the details of my ODIN Mode right now.
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
When you try to flash the firmware with Odin, what does it say in the message box?
Have you tried flashing TWRP via Odin?
A lot of people seem to be having issues with the OTA failing at 20-something percent. No idea why though. I know some found that their firmware was partially updated afterwards though, which is why they couldn't flash with Odin. Need to know what odin says about the failure to know for sure though.
You might need to factory reset btw.
I've already did a factory reset when I flashed this latest rom from that thread I posted.
Point me in the right direction of the firmware I need. I've got AT&T btw.
Try MJB firmware again. Im assuming that's what you tried to flash with odin earlier right? When/if it fails again, copy the text from the message box and paste it here.
So you want me to try flashing using Odin with that firmware I provided in that link? Like I said, ODIN on the pc gives me an error. I'll provide the error later when I get off work. Before I just put the firmware on my sd card, went into refovery mode and installed it from there.
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
I'll try ut as soon as I get home from work and posy my results. Thanks for the help so far!
Wow I think one of the reasons I couldn't use ODIN after trying to unroot, is because I never had turned on USB Debugging mode. You wanted me to just go through Step 4 for right now right? Just to get back to stock 4.3 AT&T S3 like right out the box?
Thanks so much Doc. After following step 4 on that thread I was able to Ota update!
DocHoliday77 said:
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
Click to expand...
Click to collapse
Been using my newly updated S3 and now the Touchwiz Home stops on startup and resets my default app settings repeatedly. Not sure what's the deal, tried suggestions on diff sites and am trying a factory restore, wipe date, and wipe cache partition. Any clue how to fix this?
PS: Seen in Android System Recovery it says KOT49H.I747UFNE4. Should that be I747UCEMJB since that's what mine is and recovery still gives me no command when I start it up?
You said you had updated with the OTA so NE4 would be correct.
As for recovery, if you want to keep stock recovery, enewman17 has it available in one of his threads (in development section I think). Redland that by itself and it ought to be good to go.
Otherwise, use Odin to flash TWRP recovery.
Factory reset should take care of the launcher/home issue you mentioned. You may not be able to though since it sounds like recovery is corrupted. Fix recovery as I said above and then try the reset.
If you factory reset with stock recovery installed, it will wipe your internal sd card. With custom recovery it will not.
You could also try clearing data for Touchwiz Home in application management.
I am having issues updating OTA too. It gets to 100% and then says my phone will reboot in 5 seconds, then it reboots and some at&t logo with a % counter comes up, that gets to 100% then it reboots into Android and it still says 4.3...what am I doing wrong? Anyone have any advice? Many thanks if so.
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
DocHoliday77 said:
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
Click to expand...
Click to collapse
I am trying to update by going to settings --> more --> about device --> software update. Not using a thread, no. I was rooted and uninstalled google books and newsstand then unrooted and did a factory reset in stock recovery because I found out that if you are rooted the OTA update won't take. I am 100% bone stock now except for the 2 bloatware apps I uninstalled. I have since reinstalled them via the play store , but I hear they need to be system apps?
They do, but they also need to be the same versions that were originally included. If you get them from the store they'll be updated and will cause the ota to fail.
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
samep said:
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
So, now I am on PJ1 and I don't know how to put TWRP on my phone, I want to put tx_dbs_tx's UN7 hybrid on my phone and I am having issues both finding and putting TWRP on my phone... and I can't find a download or anything for it...
I've downloaded 2 different versions of twrp and used odin to put them on but I think I am doing something wrong because it isn't booting into twrp
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Curtai said:
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Click to expand...
Click to collapse
Oh your talking about installing twrp? Yeah you have to not let it reboot. And when is done pull battery and boot into recovery to get it to stick. Obviously you figured it out. But just saying. I think earlier versions you didn't need to do that but now you do.
Glad you got it going. How you like the Rom? Running smooth for me.
ROM is good
Well I obviously got it going and didn't read the first couple posts after the install and didn't notice the SMS issue so I had that problem and I can't find a lot of the menu options that I had with the OB7 original I've been running for about 18 months... It's pretty smooth now and I'm wondering how fast it will fill up my internal memory I like that it's almost 20 gigs free.. for a while I was running on less than 6 I need to find an efficient way to use my external SD card... Other than that the options are neat but it seems really bloated all the extra Google apps make me sick even though I never use them... I've got titanium backup and am freezing them and will probably uninstall them soon... I want a small ROM that I can customize myself or apps that are easily removed or whatever half the apps I don't want are in ROM which is a pain to remove or I just don't know how to unless I use TB
Wow that's a novel sorry but yeah that's my ramblings for the next week I guess... Now I'm gonna hit the rack...