Related
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
Hi,
I have a rooted Sprint GS3, running the stock ROM with just one or two root based apps. Do I need to unroot to accept the OTA update? If so, how do I go about doing that?
TheSapient said:
Hi,
I have a rooted Sprint GS3, running the stock ROM with just one or two root based apps. Do I need to unroot to accept the OTA update? If so, how do I go about doing that?
Click to expand...
Click to collapse
if you would like to run a 4.3 stock ROM, there are a couple in the development section that you can choose from without having to run the 4.3 boot loader that contains KNOX. That way you don't have to go through the unroot process to accept the OTA.
jdelano said:
if you would like to run a 4.3 stock ROM, there are a couple in the development section that you can choose from without having to run the 4.3 boot loader that contains KNOX. That way you don't have to go through the unroot process to accept the OTA.
Click to expand...
Click to collapse
Thanks. I think the preference is to accept the OTA. If we need to unroot, we'll do that if we can figure out how. Sorry for being a little vague. I'm trying to help someone else out.
ok, you can go here Restore to unrooted MD4 follow that and you're good to go
I was stock rooted with clockwork recovery.
Took the OTA without unrooting with no problems at all, just had to re-root when it was done.
dotNETProgrammer said:
I was stock rooted with clockwork recovery.
Took the OTA without unrooting with no problems at all, just had to re-root when it was done.
Click to expand...
Click to collapse
Really? I thought it was always a bad idea with a custom recovery. Maybe we will try it rooted as well. Thanks.
Every other time I've tried it would download, but just wouldn't flash the OTA.
This time, it did. Surprised me.
Re
I got the update notification today when i woke up and when i clicked the restart and install it went to recovery mode, i panicked and clicked reboot (honestly still dont know what to do),
and restarted the phone without updating
I'm running stock 4.1.2 with just 2 root apps (superuser) and tatanium backup, how can i update ?
thanks
mjkubba said:
I got the update notification today when i woke up and when i clicked the restart and install it went to recovery mode, i panicked and clicked reboot (honestly still dont know what to do),
and restarted the phone without updating
I'm running stock 4.1.2 with just 2 root apps (superuser) and tatanium backup, how can i update ?
thanks
Click to expand...
Click to collapse
Relax . You do not have to update. You do not have to lose Root. Check out THIS thread. It will explain a few things to you in detail about Updates, and how to stop the update nag. If you want to update to the latest TW 4.3 Stock Rooted, check out the thread HERE. Just make sure you read, and read again before doing anything. Also make sure to download the correct Rom. There are several versions on the thread.
prboy1969 said:
Relax . You do not have to update. You do not have to lose Root. Check out THIS thread. It will explain a few things to you in detail about Updates, and how to stop the update nag. If you want to update to the latest TW 4.3 Stock Rooted, check out the thread HERE. Just make sure you read, and read again before doing anything. Also make sure to download the correct Rom. There are several versions on the thread.
Click to expand...
Click to collapse
Thanks for the answer.
I actually want to update to stock 4.3, and I was trying to achieve that by getting the OTA update.
And i was wondering if i can still do that?
If I simply can't then I'll just go to CM instead of getting other rooms since I used to have them with my old HTC.
Thanks again
If you want completely Stock Rooted 4.3, it's the second link I posted for you. It's the Stock, Rooted, Factory Rom, with Knox removed. All done by CNexus . Just be sure to read before doing anything. As there are several versions posted. I would highly suggest going this route instead of taking the OTA update. Once you take the OTA you will have Knox, and a different bootloader.
TEAM MiK MikROMs Since 3/13/11
Thanks a lot man, I'm having a problem installing the ROM, I'm getting assert error (status 7) error when trying to install the odexed rom,
I have just updated my CWM to 6.0.4.5
Sorry I cant reply to the thread directly, need 10 posts to be able to do so.
MJ
edit: now it's stuck on boot loop
edit: I downloaded the original recovery rom and installed it from ordin, then updated phone through kies. it's all good now.
Title sums it up. Currently on AllianceROM 5.0.1 OB7. Want to go to stock (rooted probably) so I can get MM when it (if it ever) drops. Do I need to do anything special or can I just wipe everything in TWRP, then Odin the stock zip? I get a little weary reading about bootloaders locking above OB7. What does that mean for flashing ROMs if I upgrade the bootloader? Also, does the hotspot fix work on the most recent stock ROM?
Thanks for any help. I have three little kids and no time to research this fully, otherwise I would.
If you're looking to stay OTA capable without going through Odin again to update to MM (weeks to go possibly, IDK?), you most likely wouldn't be able to add hotspot mod without losing OTA capability.
- Use the updated Chainfire Auto Root for Note 4 mostly stock with OTA capability.
*You'd use the full un-root option in SuperSU to update. It's supposed to work if no system mods or system mounting occurs but no guarantee or confirmation I'm aware of on that. You could test that with OJ6, full un-root and take OK1 OTA update if so inclined to test it.
==================================
If upgrading to the reactivation locked bootloaders, alternate ROMs really have little limitation if done without Odin downgrading (only where the ROM you seek or return to is on an older update- that applies to alliance whether you're restoring a backup or flashing a ROM zip). But that also requires Odin again at some point unless you wait and do it only when necessary. You must flash ROM zip or restore a backup and flash a 5.1 kernel like Beastmode rather using Odin to downgrade. The kernel had to be flashed in order to get it to boot. Only limitation that I'm aware of is that your screen may not auto-dim on handset call when you put phone to ear. I had that issue with OB7 ROM with 5.1 kernel; I used the power button to dim the screen but you can't have power button set as an option to dismiss call or that happens when you don't want it to.
=================================
Moar 2.1 ROM is coming soon. That may help with the anticipation of waiting long for MM. But again, that means Odin for OK1 update, then Odin for MM. There's a chance that OTA to MM could be achieved even if dm-verity gets detected in stock recovery while trying to OTA. I think you'd have to clear and download the MM OTA again but first root with Chainfire Auto Root, full un-root in SuperSU app then try the OTA again. Odin OK1 by itself may not clear the modified status but systemless root and un-root may clear it. Just thinking ahead though; no guarantees. May have to wait for MM stock tar.
If not interested in current or future Lollipop rooms, you could just wait, Odin OK1 and OTA to MM when the update is available. Easy?
To answer the Odin question, you're correct on the update though. I tried to answer any questions you might have but may confuse you. I'd need more information on direction you're considering to answer more thoroughly if that leaves more questions.
Sent from my SM-N920P using Tapatalk
I'll have to find a time when I have time and can be without a working phone for a few hours and try to play around with some of this stuff. I'm sure I'll be back on here with questions at some point. Thanks for the initial guidance.
Sent from my SM-N910P using Tapatalk
Okay. I think today is the day. I've downloaded MOAR 2.1 and am going to try this for now. I also have the OJ6 stock (I know it's not the absolute most current) downloaded and ready for standby if I so choose. Here is my plan.
1) Wipe Factory Reset in TWRP 3x's (actually include internal storage as well, correct?)
2) Install TWRP 3.0 via Odin (currently 2.8.5)
2a) Per MOAR install instructions, install stock OJ6 via Odin and activate, etc, etc. Ensure everything works, maybe take the OTA to OK1.
3) install MOAR via TWRP from micro SD card
4) Profit!
If I want to install stock, all I need to do is install the stock ROM via Odin and I will be able to update OTA since I will by default be unrooted, correct?
Thanks for the help. I plan to attempt this later today.
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
samep said:
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
pilotmills said:
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
Click to expand...
Click to collapse
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
samep said:
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I think I need to slow down my postings . I looked around and found out basically what you just told me. Flashing the stock OK1 now, then I'll redo TWRP. Thanks for the timely replies. I'll try to keep it to only issues I run into that I can't resolve after some Google research. I really do appreciate the help.
Progress, but now I can't get the GPS to lock. Tried GPS status app, GPS Status and toolbox. Occasionally I get one or two satellites that show a signal being received, but never locking onto them. Eventually they will drop completely to zero signal. On the other hand, somewhere between OB7 and OK1, Samsung actually addressed the barometer issue that had plagued the N4 since launch where above about 3,000', it would not register anything but a sea-level pressure. Baby steps. . .
Is GPS failing to lock on stock OK1 tar update or the port? The port has GPS a release with fixes pending. But most were only reporting GPS navigation in Google Maps lagging or losing sync during navigation.
Sent from my SM-N910P using Tapatalk
Sorry, should have specified. I'm on stock OK1 now.
pilotmills said:
Sorry, should have specified. I'm on stock OK1 now.
Click to expand...
Click to collapse
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
samep said:
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
The GPS chip in this phone is horrible. I had the phone up against the window as a last resort and still nothing from the GPS. Went outside and it grabbed a lock within 30 seconds. I didn't opt for the anti-NSA snooping coating on the windows when we had them installed either. . . Backing up OK1 in TWRP now, then attempting to flash MOAR.
Thanks again. Stay tuned. . .
Got MOAR up and running. I had an activation issue the first time which was strange since I was able to send and receive texts and calls, but I kept getting an activation not complete message popping up and persisting. I did exactly as posted in the OP as well. Anyway, went back to OK1 stock and waited even longer after the data established before reflashing MOAR. Works like a charm now. Thanks for the patience and assistance!
So the story is about 9 months ago my Galaxy note 4's USB port got messed up. I cannot charge my phone without using an external battery cradle, nor can I connect my phone to computer and sync/odin. I am stuck on a rooted BOB7 rom specifically the noterized rom stable 3. I know I cannot jump from BOB7 to COK1 etc... via flashing. I was wondering if the jump to marshmallow from lollipop would work.
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Thank you
Thank you very much tx_dbs_tx, you are a life saver! I have been stuck for the past 9 months.
tx_dbs_tx said:
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Click to expand...
Click to collapse
Is there a chance of doing the same on OG5? Using OBAR
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Can someone confirm with me, that sending picture messages won't go through. Or is it just me?
cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
Sorry for the late reply Cheryl. There is no reason not to update your software to Marshmallow 6.0. Typically updates bring improved performance and battery life as well as other software optimizations which are always better than previous software builds. You should backup your photo's etc before installing any update just in case. If you're one of those who doesn't like change and is content with your phone with it's current software then you don't have to update the software as long as there isn't a critical update that would prevent something from working on your phone unless you take the update. If everything works and your happy then you can leave it as is. But if you are interested in improved battery life and overall performance as well as new security features and policies of android, then by all means update your software the first chance you get. there are no drawbacks that i have noticed or read from any other users. Marshmallow is a go! :good:
cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Sterist said:
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Click to expand...
Click to collapse
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
cherylbaker said:
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
Click to expand...
Click to collapse
if you don't have your MSL, and don't know where to find/how to get Galaxy Tools, and you still have a while left on contract, it wouldn't hurt to downgrade and grab your MSL first then jump straight to MM
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
kjtrini1 said:
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
Click to expand...
Click to collapse
I don't know how to extract it from a .tar but I know it can be acquired it like this:
1. full backup in TWRP
2. copy the backup to pc for safekeeping
3. odin full OB7 stock tar
4. without flashing TWRP, root using CF auto root*
5. install Flashify from Google Play
6. backup recovery
7. copy the backup to pc for uploading
*I don't know which version (if applicable) as I never use that method to root. sorry
obviously you wouldn't be able to do this yourself, you would need someone on the forum with OB7 bootloader to do this, and honestly, without knowing how to extract / find it in the.tar I still think that would take a lot less time and effort than this method lol
I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.
toenail_flicker said:
I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.
Click to expand...
Click to collapse
You lose root updating.
Fyi: recent updates do not have developer support but maybe latest security update is your goal?
If you're not interested in rooting again and flashing custom ROM and prefer latest stock ROM, I'd recommend:
decrypt any data encrypted
backup any keepsakes to ext SD Card
remove fingerprints
make a TWRP backup (backups should be on external SD Card)
factory reset
wipe internal memory
Power down and remove battery prior to download mode
Flash latest stock tar with Odin from this thread (it may download faster- QB3 would be OK unless you want to download latest, if available. Updates usually aren't available for some time). Use Odin defaults and go through setup wizard.
https://forum.xda-developers.com/showthread.php?p=63868221
Quickest way to latest update is to install Smart Switch (unless you found latest to download for Odin).
https://www.sammobile.com/samsung-smart-switch/
Note: If you do decide to run a custom ROM, security updates are not up to date but it's recommended to install the update recommended in OP for those custom ROMs. You may lose some compatibility by not flashing the recommended update.
Stock tar updates for Odin are full updates so they're not required to be flashed in sequential order. Same for Smart Switch updates. Smart Switch likely only works for non rooted phones which is why I recommended to start with Odin stock tar.
OTA updates patch the previous update sequentially. So OTA update would only be ideal to update after getting to latest with Smart Switch. Odin updates are slower to become available as I recall.
Make your battery is charged to 80% or more. I wouldn't recommend a battery that's over a year old. Start with a fresher battery and replace batteries that have over 500 recharge cycles on them. This could save you trouble in the long run.
Also, keep your phone cool during these initial boots after flash. Forced air from a small fan or air purifier should do fine.
Sent from my SM-N920P using Tapatalk
"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.
wow. so much valuable information in your reply. this is amazing. thank you.
toenail_flicker said:
"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.
Click to expand...
Click to collapse
You do recall that once you upgrade past OB7 that you lose the ability to return to KitKat via Odin stock tar?
The TWRP backup I recommended is still useful but likely you'd need to downgrade bootloader firmware to 5.1 (OG5 to OK1 is recommended once you've upgraded beyond OB7), factory reset, wipe internal, restore backup and flash Beastmode 1.0 kernel prior to booting.
I think you also need to flash SuperSU zip after kernel to get a boot but I'm not sure on that.
Have you already been through this with lollipop 5.1 and went back to KitKat? If so, you know the drill, just make sure you have the right bootloader.
If you're looking for developer support on stock like ROM, check out dtux or UN7 ROMs with aroma flash modset mods. There's also a few modified stock ROMs that are newer.
I discovered this morning that older updates for Note 4 are vulnerable to BlueBorne exploit through Bluetooth. I keep mine off mostly and disable the options in improve location and nearby devices so it shouldn't be a issue for me. There's a BlueBorne vulnerability scanner in Google Play to check later updates if you like. Search for it in Play.
Sent from my SM-N920P using Tapatalk