Related
I am currently running dl01 and I want to upgrade to dl09 tonight. Here's what I am going to do please tell me if this is correct.
using these pieces
http://forum.xda-developers.com/showthread.php?t=894126
boot phone into download mode, flash the dl09 modem file via odin (pda section). then restart and somehow get back into recovery and wipe everything and flash a dl09 rom and kernel.
I guess my concerns surround what happens after the modem is flashed. Will the phone boot like normal after just flashing the modem so I can use cwm to get into recovery or will I have to boot into recovery via volume button?
Wagz513 said:
I am currently running dl01 and I want to upgrade to dl09 tonight. Here's what I am going to do please tell me if this is correct.
using these pieces
http://forum.xda-developers.com/showthread.php?t=894126
boot phone into download mode, flash the dl09 modem file via odin (pda section). then restart and somehow get back into recovery and wipe everything and flash a dl09 rom and kernel.
I guess my concerns surround what happens after the modem is flashed. Will the phone boot like normal after just flashing the modem so I can use cwm to get into recovery or will I have to boot into recovery via volume button?
Click to expand...
Click to collapse
Are you running stock DI01 or rooted/ROMed/etc? If you're stock, just OTA update. It began rolling out last night.
If you're rooted/ROMed/etc, then yes, your steps are correct.
Apply modem, boot into CWM, apply ROM and kernel.
The OTA is out and you can pull it - I'd reset the phone to do it, though.
Yeah, if you are still stock, just hit the update function in the phone and get the OTA update. It takes less than 10mins and doesn't mess with anything on your phone.
Then if you feel the need to root for roms or something do it after.
Thanks everyone for the quick reply, I am not on stock anything at the moment so I will go ahead and get this thing updated with odin
Hi Everyone,
I formatted my i9505 using TWRP - Format Data. Now for those of you who aren't aware, it formats everything on the phone.
Most people panic about bricking their phone. The truth is you can get your phone working with about 30 mins spare time.
I wanted to share the exact method I used as it's not clearly described online. If this helps one person with the same problem I had then I'm satisfied.
METHOD
1. Download Time - Download the latest version of Odin (3.xx), a stock version of your ROM (from Samsung), the new modified ROM you want to use (or old one you already have on file) and a Recovery program for the phone like TWRP.
2. Open Odin and click PDA and then select the original ROM. Don't change any of the other settings. Get your phone and load it in Download Mode then plug it into the PC (Make sure it connects, there will be a "COM" connection in Odin).
3. Click Install. This will take a while to load the software... Be patient. As Odin is set to reboot the phone when it's done, the phone will hang.
4. Turn the phone off - Either hold the power button down long enough or pull the battery.
5. Don't install anything else just yet. What you need to do is load up into stock recovery and reset everything.
6. Once you have done this the phone will work. You can load up in stock ROM or go straight to installing the custom Recovery and custom ROM.
If you want to go custom again...
7. Open Odin and install CF-Root
8. Install custom Recovery via Odin
9. Install custom ROM either via Odin or via custom Recovery.
10. WINNER WINNER CHICKEN DINNER
Any questions I'll do my best to help.
I followed the instructions in the thread that describes how to update to NAE from MF9 while keeping the MF9 bootloader: http://forum.xda-developers.com/showthread.php?t=2277480
I was on MF9 stock rooted (with TWRP recovery installed when I flashed the NAE modem via odin 3.0.7, not sure if that makes a difference).
All the steps seemed to go okay. As far as I can tell the versions look good. However, the device is super sluggish at times, especially the dialer. Sometimes I have trouble waking it. I can't toggle the WiFi on. I have not set the hotspot mod or sd card mod yet.
The device is essentially unusable. Every so often I will get a request to force close some app (like the dialer) because it is hanging.
I tried repeating the steps described in the thread above over and still get the same behavior. The second time I also did some more checking in the intermediary MK2 step after everything was set up and I did notice that sometimes it was doing the weird hanging problems there too (i.e. even before the NAE rom was installed).
I had no problems whatsoever with the device when it was on MF9.
Help! Any ideas??
Have you tried to install the nae modem. Its been observed that you need to install it in order to get full use of a NAE rom
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Have you tried to install the nae modem. Its been observed that you need to install it in order to get full use of a NAE rom
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yes, that is the very first step in the instructions. For good measure I even went back and reinstalled the NAE modem (even though it appeared to be successful).
I am thinking maybe I should go back and try to install/downgrade back to the MF9 modem to see if that would help.
Update: Everything seems okay now. I went back and flashed the MK2 modem, then reinstalled the MK2 ROM, then the NAE modem, booted into MK2 to see that it was okay, then installed the NAE rom. So far so good :fingers-crossed:
Reverting back to MF9 from NAE
myphone12345 said:
Yes, that is the very first step in the instructions. For good measure I even went back and reinstalled the NAE modem (even though it appeared to be successful).
I am thinking maybe I should go back and try to install/downgrade back to the MF9 modem to see if that would help.
Update: Everything seems okay now. I went back and flashed the MK2 modem, then reinstalled the MK2 ROM, then the NAE modem, booted into MK2 to see that it was okay, then installed the NAE rom. So far so good :fingers-crossed:
Click to expand...
Click to collapse
Anyone got the instructions to revert back to MF9 from NAE, I installed 4.4.2 and NAE but it is very buggy, slow , sometimes unresponsive. Like to get back to MF9.
This is the link to what steps I took. http://forum.xda-developers.com/showthread.php?t=2277480
Thank you
zeplman said:
Anyone got the instructions to revert back to MF9 from NAE, I installed 4.4.2 and NAE but it is very buggy, slow , sometimes unresponsive. Like to get back to MF9.
This is the link to what steps I took. http://forum.xda-developers.com/showthread.php?t=2277480
Thank you
Click to expand...
Click to collapse
You could flash a MF9 stock rooted zip. Or Odin MF9 tar.
Sent from my SPH-L720 using Tapatalk
myphone12345 said:
I followed the instructions in the thread that describes how to update to NAE from MF9 while keeping the MF9 bootloader: http://forum.xda-developers.com/showthread.php?t=2277480
I was on MF9 stock rooted (with TWRP recovery installed when I flashed the NAE modem via odin 3.0.7, not sure if that makes a difference).
All the steps seemed to go okay. As far as I can tell the versions look good. However, the device is super sluggish at times, especially the dialer. Sometimes I have trouble waking it. I can't toggle the WiFi on. I have not set the hotspot mod or sd card mod yet.
The device is essentially unusable. Every so often I will get a request to force close some app (like the dialer) because it is hanging.
I tried repeating the steps described in the thread above over and still get the same behavior. The second time I also did some more checking in the intermediary MK2 step after everything was set up and I did notice that sometimes it was doing the weird hanging problems there too (i.e. even before the NAE rom was installed).
I had no problems whatsoever with the device when it was on MF9.
Help! Any ideas??
Click to expand...
Click to collapse
I had the same exact problem and I found a way to fix that so I can run NAE.. I read someone post and I just did these step to have a perfect running NAE stock rom.
Steps How To Install NAE (Odex) properly with MF9 Bootloader
1. Back-up apps with Titanium Backup or MyBackup
2. Download the following tools and files to have on-hand
A. Odin 3.07
B. CF-Root
C. Philz Recovery [I used the latest one 6.41.6.tar.md5]
D. MF9.tar Official
E. MK2 Modem.tar (No Firmware)
F. Stock MK2 Odex ROM (No Bootloader)
G. NAE Modem.tar (No Firmeware)
H. Stock NAE.Odex Rom (No Bootloader)
I. SDCard Fix for NAE
J. Hotspot Mod NAE (Odex) [If you want Hotspot]
3. Put the following files on your External SDcard from Step 2 (E,G,H,I)
4. Start by opening up Odin 3.07, and flashing MF9.tar (Make sure everything is unchecked but Auto Reboot)
5. Once flashed let the phone boot up and skip all the steps of setting up your phone. Then check to see if your baseband and firmeware is on MF9. If thats all okay completely shut down your phone.
6. Go back to Download Mode and to Odin. Then flash CF-Root (Make sure everything is unchecked but Auto Reboot)
7. Once its booted shut down and back to Download Mode and to Odin then flash MK2 Modem.tar (Make Sure Everything Is Unchecked) Once that is done Hold the power button for 10 seconds.
8. Boot up and check your baseband and firmeware in About Phone. Once everything is okay shut down the phone.
9. Boot your phone into Philz Recovery Mode then find and Install Stock MK2 Rom
10. Boot up the phone and skip all the steps setting up your phone, Do the lockscreen fix shut down your phone.
11. Go back to Odin and Flash NAE.Modem tar file (Make sure everything is unchecked) Hold the power button for 10 seconds
12. Reboot into Philz Recovery Do the wipe to do a Clean Install of Rom
13. Install Stock NAE Rom then Boot Up
14. Shut down and go back to recovery and install the SDCard Fix and Hotspot then Reboot
Then you can get Triangle Away and wipe your counter clean.
This is what I did and it worked perfect several times without problems.
(Optional part if you want to reset custom ROM counter)
1. Odin flashed a full stock firmware (ROM and all) MF9 or below (I had MDL tar already so just used that)
2. CF-Root the installed rom.
3. Run Triangle Away to reset boot counter.
(Main part)
1. Odin flash TWRP recovery .tar and did a full wipe.
2. Odin flash Mf9 AIO .tar
3. Odin flash MK2 modem only .tar (NAE won't stick unless you do this first)
4. Odin flash NAE modem only .tar
5. Odin flash TWRP (You can use other recoveries for some other ROMS, but most NAE roms including Sacs Custom ROM and NAE stock rooted need TWRP to install properly or you get no cell. I haven't tried it on CWM, but know when I tried it wouldn't work on PhilZ Touch)
7. full data wipe using the recover for good measure (not necessary, it should be clear already)
6. Flash your ROM in recovery (I used stock rooted NAE)
8. Flash your add-ons, mobile hotspot, boot screen, kernel , etc. (I just flashed the odex mobile hotspot for NAE and a boot screen, left the kernel at stock because of a camera issue ktoonsez seemed to be presenting)
9. Reboot and enjoy.
(Note, only if using NAE stock rooted)
If your using the NAE stock rooted you will need and want to run and let the pre-installed supersu app disable Knox, then using an SE linux status changing app from the app store you will need to temporarily change your SE linux status. From there you can install the Xposed Framework and Wanam Xposed. In Wanam Xposed you can set the SE linux status so it wont reactivate after a reboot. Now you can uninstall the SE linux switcher you downloaded before. Next you can download an app that will do it, or manually fix the SD card write permissions. Finally using a root exploring file manager you can fix the permissions to make the lock screen work.
CatFood said:
This is what I did and it worked perfect several times without problems.
(Optional part if you want to reset custom ROM counter)
1. Odin flashed a full stock firmware (ROM and all) MF9 or below (I had MDL tar already so just used that)
2. CF-Root the installed rom.
3. Run Triangle Away to reset boot counter.
(Main part)
1. Odin flash TWRP recovery .tar and did a full wipe.
2. Odin flash Mf9 AIO .tar
3. Odin flash MK2 modem only .tar (NAE won't stick unless you do this first)
4. Odin flash NAE modem only .tar
5. Odin flash TWRP (You can use other recoveries for some other ROMS, but most NAE roms including Sacs Custom ROM and NAE stock rooted need TWRP to install properly or you get no cell. I haven't tried it on CWM, but know when I tried it wouldn't work on PhilZ Touch)
7. full data wipe using the recover for good measure (not necessary, it should be clear already)
6. Flash your ROM in recovery (I used stock rooted NAE)
8. Flash your add-ons, mobile hotspot, boot screen, kernel , etc. (I just flashed the odex mobile hotspot for NAE and a boot screen, left the kernel at stock because of a camera issue ktoonsez seemed to be presenting)
9. Reboot and enjoy.
(Note, only if using NAE stock rooted)
If your using the NAE stock rooted you will need and want to run and let the pre-installed supersu app disable Knox, then using an SE linux status changing app from the app store you will need to temporarily change your SE linux status. From there you can install the Xposed Framework and Wanam Xposed. In Wanam Xposed you can set the SE linux status so it wont reactivate after a reboot. Now you can uninstall the SE linux switcher you downloaded before. Next you can download an app that will do it, or manually fix the SD card write permissions. Finally using a root exploring file manager you can fix the permissions to make the lock screen work.
Click to expand...
Click to collapse
Thanks fir this. I flashed one modem than the next one right after and wifi fixed. Been working on this all day glad I found this thread
Cheryl
I have a retail-dev converted Note 4 Verizon - rooted and Unlocked. I decided to be a guinea pig and try to update the stock OTA MM 6.0.1 Verizon - for Note 4 N-901V.
** If you are rooted and unlocked you CANNOT flash update.zip directly and it will give errors. You have to downgrade, as below, and then flash.
YOU WILL LOSE ROOT AND THE BOOT LOADER WILL BE LOCKED BACK.
ALL DATA WILL BE WIPED. ALL DATA WILL BE WIPED. EVERYTHING.
YOU WILL LOSE ROOT AND THE BOOT LOADER WILL BE LOCKED BACK.
===BUT=== YOU CAN STILL GO BACK TO LOLLIPOP 5.1.1 AND RE-ROOT AND UNLOCK BOOTLOADER. I FULLY TRIED TO DOWNGRADE AND REDO THE UNLOCK OF BOOTLOADER AND ROOT. I WAS ABLE TO UNLOCK AND ROOT BY GOING BACK TO 5.1.1.
** You MUST downgrade to 5.1.1 STOCK. One big advantage - the "lock" symbol and "custom" will be reset and the phone will look for all intent and purposes as not being flashed. BUT I AM NOT SURE IF KNOX MAKES A LOG SOMEWHERE, which may reside somewhere.
------------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: Because of Google's verity check I am recommending the following full stock kernel, recovery flash steps before a full stock flash. If there is any root/unlock anywhere in bootloader or kernel you may get a dm-verity failed error.
For now I would suggest a complete wipe and complete stock flash:
BEFORE FLASHING ANYTHING, REBOOT TO RECOVER AND DO A FULL ADVANCED WIPE LIKE THIS:
1. Do a full wipe. Wipe also "internal storage". Dalvik cache, data, system, INTERNAL STORAGE, cache, ......EXCEPT externalsd or MicroSD.
** USE ODIN. Make sure Auto-Reboot is UNTICKED. So the phone does not reboot after every flash.
2. Flash stock recovery first from the post I linked (see below where hsbadr's thread link is for stock firmwares). (AGAIN: Do the wipe first and then flash stock recovery.) Use the AP slot in Odin.
** Phone will not reboot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 3.
3. Flash the stock Bootloader again available in that post. Us the BL slot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 4.
3. From the same hsbadr's post flash the stock kernel via odin (use AP slot). Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to next step.
4. Now flash full stock. See step 2 in section BELOW.
IF YOU GET "DM-VERITY FAILED" 1. PULL THE BATTER AND DISCONNECT PHONE FROM COMPUTER, Then use buttons to get download mode.
** UNTICK auto-reboot in Odin, and flash STOCK kernel. dm-verity error should go away on reboot.
** Now you have remove battery again and get download mode, and reflash full stock from section below, step 2 below.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
USE THESE STEPS ONLY TO GET MORE DETAILS: BUT PLEASE FLASH STOCK , kernel, and recovery first via odin as above.
STOCK FILES ARE IN .ZIP FORMAT. UNZIP THEM TILL YOU GET A .TAR.MD5 FILE. I strongly recommend using 7-zip.
1. Download Odin from attachment here. You must have odin working and drivers installed etc.
2. Go to this thread : http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
** Choose N910VVRU2BPA1
** Download FULL FIRMWARE version. You MUST use full firmware version.
** UNZIP the file, till you get a .tar.md5 file (N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5) using the AP slot of Odin.. Dont flash this yet, you need the recovery first (step 3).
** Download FROM SAME section the stock RECOVERY.
3. The stock recovery must be flashed first because the stock firmware detects the root/unlocked boot. When this happens you get a "fuse 2" error.
NOTE: If you flash the full firmware before stock recovery you will get an error TO USE THE VERIZON REPAIR ASSISTANT.. Do not worry, you can reflash stock recovery and then go into download mode.
4. Go into download mode: Volume down +Home+Power button at the same time. Just hold till you get download mode.
5. Open Odin and connect phone to computer. Wait for COM signal. Load recovery into AP.
6. Flash, and then pull battery. Put back battery and get back into download mode.
7. Load the firmware N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar into AP in ODIN.
8. Flash and reboot!! NOW YOU ARE ON COMPLETE STOCK 5.1.1.
9. Download the update.zip for the MM 6.0.1 stock OTA here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
** Go to section N910VVRU2CPD1.
** Download "OTA Update from N910VVRU2BPA1 to N910VVRU2CPD1". MAKE SURE IT IS NAMED "update.zip", otherwise rename to update.zip.
10. PLACE update.zip IN EXTERNAL SD CARD..
11. Reboot into STOCK recovery. Remember !! Youa re now on stock,
12. Choose the option to apply update.zip from externla sd.
13. Apply the update.
14. Yoohoo! You have full stock MM 6.0.1 Verizon.
TO GO BACK TO ROOTED/UNLOCKED BOOTLOADER:
15. Redo steps 1-8. You will get back to stock 5.1.1.
16. Now you can re-root and unlock bootloader like you did before.
PLEASE THANK @hsbadr for his collection of softwares/firmware.
I'm place Update.zip into SD card, and i'm in Recovery Mode it "say"
dm-verity verification failed
Apply update external storage => Update from external storage is disabled.
How to fix it ? Thankyou !
Sorry for my bad English !
One minor correction: the file you download should be a .zip file. Don't append a .zip to the file that you download or you will have a file called update.zip.zip. I'm pretty sure that won't work.
Knox absolutely DOES make a "record" of sorts, in the form of a hardware fuse that was tripped when you unlocked the bootloader. Your warranty is invalid to anyone who decides to check the state of that permanent, irreversible hardware flag.
Bicknasty said:
Knox absolutely DOES make a "record" of sorts, in the form of a hardware fuse that was tripped when you unlocked the bootloader. Your warranty is invalid to anyone who decides to check the state of that permanent, irreversible hardware flag.
Click to expand...
Click to collapse
Yes, that figures about Knox. But it is not like the eFuse on say th Amazon Fire TV which is bricks the device. I put the line in there so that there is some "hope" of at least going back to the store with a phone that is not "obviously" unlocked. Just a minor bit of light in the tunnel!!!!!!
duyvinhnguyen said:
I'm place Update.zip into SD card, and i'm in Recovery Mode it "say"
dm-verity verification failed
Apply update external storage => Update from external storage is disabled.
How to fix it ? Thankyou !
Sorry for my bad English !
Click to expand...
Click to collapse
%%%% Please explain when exactly the dm-verity showed. After flashing stock recovery? If yes, then you need to follow steps below.
dm-verity is explained here with respect to Marshmallow http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
For now I would suggest a complete wipe and complete stock flash:
BEFORE FLASHING ANYTHING, REBOOT TO RECOVER AND DO A FULL ADVANCED WIPE AS IN STEP 1.
1. Do a full wipe. Wipe also "internal storage". Dalvik cache, data, system, internal storage, cache, ......EXCEPT external.
** USE ODIN. Make sure Auto-Reboot is UNTICKED. So the phone does not reboot after every flash.
2. Flash stock recovery first from the post I linked.....the one with the stock firmware. (Do the wipe first and then flash stock recovery.) Use the AP slot in Odin.
** Phone will not reboot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 3.
3. Flash the stock Bootloader again available in that post. Us the BL slot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 4. There is no stock bootloader, sorry my bad !
3. From the same hsbadr's post flash the stock kernel via odin (use AP slot). Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to next step.
4. Now flash full stock.
Please let me know if it helps. I will update the instructions, since I think this is the safest route.
chappatti said:
I have a retail-dev converted Note 4 Verizon - rooted and Unlocked. I decided to be a guinea pig and try to update the stock OTA MM 6.0.1 Verizon - for Note 4 N-901V.
** If you are rooted and unlocked you CANNOT flash update.zip directly and it will give errors. You have to downgrade, as below, and then flash.
YOU WILL LOSE ROOT AND THE BOOT LOADER WILL BE LOCKED BACK.
ALL DATA WILL BE WIPED. ALL DATA WILL BE WIPED. EVERYTHING.
YOU WILL LOSE ROOT AND THE BOOT LOADER WILL BE LOCKED BACK.
===BUT=== YOU CAN STILL GO BACK TO LOLLIPOP 5.1.1 AND RE-ROOT AND UNLOCK BOOTLOADER. I FULLY TRIED TO DOWNGRADE AND REDO THE UNLOCK OF BOOTLOADER AND ROOT. I WAS ABLE TO UNLOCK AND ROOT BY GOING BACK TO 5.1.1.
** You MUST downgrade to 5.1.1 STOCK. One big advantage - the "lock" symbol and "custom" will be reset and the phone will look for all intent and purposes as not being flashed. BUT I AM NOT SURE IF KNOX MAKES A LOG SOMEWHERE, which may reside somewhere.
------------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: Because of Google's verity check I am recommending the following full stock BL, kernel, recovery flash steps before a full stock flash. If there is any root/unlock anywhere in bootloader or kernel you may get a dm-verity failed error.
For now I would suggest a complete wipe and complete stock flash:
BEFORE FLASHING ANYTHING, REBOOT TO RECOVER AND DO A FULL ADVANCED WIPE LIKE THIS:
1. Do a full wipe. Wipe also "internal storage". Dalvik cache, data, system, INTERNAL STORAGE, cache, ......EXCEPT externalsd or MicroSD.
** USE ODIN. Make sure Auto-Reboot is UNTICKED. So the phone does not reboot after every flash.
2. Flash stock recovery first from the post I linked (see below where hsbadr's thread link is for stock firmwares). (AGAIN: Do the wipe first and then flash stock recovery.) Use the AP slot in Odin.
** Phone will not reboot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 3.
3. Flash the stock Bootloader again available in that post. Us the BL slot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 4.
3. From the same hsbadr's post flash the stock kernel via odin (use AP slot). Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to next step.
4. Now flash full stock.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
USE THESE STEPS ONLY TO GET MORE DETAILS: BUT PLEASE FLASH STOCK Bootloader, kernel, and recovery first via odin as above.
1. Download Odin from attachment here. You must have odin working and drivers installed etc.
2. Go to this thread : http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
** Choose N910VVRU2BPA1
** Download FULL FIRMWARE version. You MUST use full firmware version. N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
** Download FROM SAME section the stock RECOVERY.
3. The stock recovery must be flashed first because the stock firmware detects the root/unlocked boot. When this happens you get a "fuse 2" error.
NOTE: If you flash the full firmware before stock recovery you will get an error TO USE THE VERIZON REPAIR ASSISTANT.. Do not worry, you can reflash stock recovery and then go into download mode.
4. Go into download mode: Volume down +Home+Power button at the same time. Just hold till you get download mode.
5. Open Odin and connect phone to computer. Wait for COM signal. Load recovery into AP.
6. Flash, and then pull battery. Put back battery and get back into download mode.
7. Load the firmware N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar into AP in ODIN.
8. Flash and reboot!! NOW YOU ARE ON COMPLETE STOCK 5.1.1.
9. Download the update.zip for the MM 6.0.1 stock OTA here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
** Go to section N910VVRU2CPD1.
** Download "OTA Update from N910VVRU2BPA1 to N910VVRU2CPD1". MAKE SURE IT IS NAMED "update.zip", otherwise rename to update.zip.
10. PLACE update.zip IN EXTERNAL SD CARD..
11. Reboot into STOCK recovery. Remember !! Youa re now on stock,
12. Choose the option to apply update.zip from externla sd.
13. Apply the update.
14. Yoohoo! You have full stock MM 6.0.1 Verizon.
TO GO BACK TO ROOTED/UNLOCKED BOOTLOADER:
15. Redo steps 1-8. You will get back to stock 5.1.1.
16. Now you can re-root and unlock bootloader like you did before.
PLEASE THANK @hsbadr for his collection of softwares/firmware.
Click to expand...
Click to collapse
The newest Bootloaders offered is for N910VVRU1BOAF. Is that the one to use. ?
..
chappatti said:
%%%% Please explain when exactly the dm-verity showed. After flashing stock recovery? If yes, then you need to follow steps below.
dm-verity is explained here with respect to Marshmallow http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
For now I would suggest a complete wipe and complete stock flash:
BEFORE FLASHING ANYTHING, REBOOT TO RECOVER AND DO A FULL ADVANCED WIPE AS IN STEP 1.
1. Do a full wipe. Wipe also "internal storage". Dalvik cache, data, system, internal storage, cache, ......EXCEPT external.
** USE ODIN. Make sure Auto-Reboot is UNTICKED. So the phone does not reboot after every flash.
2. Flash stock recovery first from the post I linked.....the one with the stock firmware. (Do the wipe first and then flash stock recovery.) Use the AP slot in Odin.
** Phone will not reboot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 3.
3. Flash the stock Bootloader again available in that post. Us the BL slot. Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to step 4.
3. From the same hsbadr's post flash the stock kernel via odin (use AP slot). Pull the battery, disconnect USB, put battery back, re-enter download mode. and attach cable. The go to next step.
4. Now flash full stock.
Please let me know if it helps. I will update the instructions, since I think this is the safest route.
Click to expand...
Click to collapse
Thankyou so much, I'll try !
i did step 13 and nothing happens. it is restart as normal 5.1.1
lymada said:
i did step 13 and nothing happens. it is restart as normal 5.1.1
Click to expand...
Click to collapse
Did you go under "About device" and look. This is an "update" so preserves all your apps/settings and looks like your old phone! Just check at about device.....it should say 6.0.1.
duyvinhnguyen said:
I'm place Update.zip into SD card, and i'm in Recovery Mode it "say"
dm-verity verification failed
Apply update external storage => Update from external storage is disabled.
How to fix it ? Thankyou !
Sorry for my bad English !
Click to expand...
Click to collapse
I had the same errors. I flashed the full firmware again via Odin and that fixed it. I didn't install the update.zip I let the phone do the OTA. now I'm on MM
datstudandre said:
I had the same errors. I flashed the full firmware again via Odin and that fixed it. I didn't install the update.zip I let the phone do the OTA. now I'm on MM
Click to expand...
Click to collapse
On two of my Note 4's All I had to do was Odin downgrade to Sammobile sm-n910v stock 5.1.1. do a factory reset and take the MM OTA. I have a third Note 4 and it wont take the MM upgrade because of the dm verification failure issue. This is the phone I used KingOroot to root. I'll just wait until we get a custom ROM. I'm not too worried about it.
chappatti said:
Did you go under "About device" and look. This is an "update" so preserves all your apps/settings and looks like your old phone! Just check at about device.....it should say 6.0.1.
Click to expand...
Click to collapse
yeah i think it good. i have 6.0.1. i think this update not good at something. charging too slow. i dont know why.....i have 3hours full battery.
hey guys. im on MM and how to root it ?
How is the stock mm ? My phone keeps telling me to update and it is getting annoying. Can I down grade latter to get root and such ?
tydiamond11 said:
How is the stock mm ? My phone keeps telling me to update and it is getting annoying. Can I down grade latter to get root and such ?
Click to expand...
Click to collapse
If you stay on this version of MM, you can downgrade to 5.1.1 and unlock bootloader and root. I have done it 2 times already. That is 2 full cycles of downgrade and re-root. Just use the procedure in the OP to downgrade, and the you can use the retail-dev bootloader conversion.
My opinion of MM 6.0.1?? It is exactly as all the custom MM 6.0.1 ROMs out there. The only ROMs that have something better are the S7 Edge ports, but if you want Wifi calling, VolTE (though, which some people say can cause voice issues) you have to get stock since the S7 Edge ports do not have this. Also, the MM ports are T-Mobile port to Verizon, and there are minor issues - for example, the phone uses the VZW roaming APN. If you want something solid/stable, then you should try stock.
One big thing is that the theme store is not available on the Note 4 even with MM. This is a bummer.
lymada said:
hey guys. im on MM and how to root it ?
Click to expand...
Click to collapse
Verizon STOCK MM cannot be rooted. The bootloader unlock and root is only for the original 5.1.1 bootloader (I think, the BOAF one). Flashing Verizon STOCK MM re-locks the boot loader and removes root.
However, if you want to try MM custom ROMs, then you MUST downgrade to 5.1.1 FULL stock - everything stock - and then unlock bootloader and then root, and then flash upgrade to custom MM ROM. No big deal, steps are easy. But some work required.
heeheeheee....... @hasbdr just fixed this . Now you can have rooted MM on Verizon . see here.....: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
lymada said:
yeah i think it good. i have 6.0.1. i think this update not good at something. charging too slow. i dont know why.....i have 3hours full battery.
Click to expand...
Click to collapse
This is the OFFICIAL Verizon update. You may need to go into settings and enable fast charging. I am using this update and it does fine. Go to "settings>>battery>>"...and tick fast charging.
Thanks for the post OP.
I used this as a general guide with some differences of my own to go from non-rooted stock MM back to LP as my battery was not doing good at all on MM.
Again, thanks for the post... it helped me to get things right so I didn't brick / boot-loop my device.
Slim!
It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
beerindex said:
It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
Click to expand...
Click to collapse
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
mattzeller said:
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
Click to expand...
Click to collapse
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
beerindex said:
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
Click to expand...
Click to collapse
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
mattzeller said:
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
beerindex said:
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
Click to expand...
Click to collapse
Feel free to post back here or PM me if you have any more questions or problems, it wouldn't be the first time walking someone through the process via pm here or other methods
Sent from my SCH-R220