i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip
Related
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
KingKobra813 said:
I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
Click to expand...
Click to collapse
Yes wipe your storage n youll. Be good to go
pbedard said:
Yes wipe your storage n youll. Be good to go
Click to expand...
Click to collapse
I wiped my internal storage and I'm still getting stuck in at the same part. Do I need to wipe my external storage as well?
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
Thank you. I will try that.
KingKobra813 said:
Thank you. I will try that.
Click to expand...
Click to collapse
Forgot to mention that Flashify has become a trusted source, to me and maybe others here. You can find it on Google Play and it will download TWRP, I recommend the non-zip latest one. Flashify will also automatically prompt you to install it from where it just downloaded it and checks its integrity. Since TWRP updates frequently, could be a manual step saver.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
So I used a totally different computer and new cable and I'm still getting stuck at the exact same place. Everything on ODIN said it worked but my phone just bootloops.
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
samep said:
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
Click to expand...
Click to collapse
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
KingKobra813 said:
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
Click to expand...
Click to collapse
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
samep said:
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
Click to expand...
Click to collapse
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
KingKobra813 said:
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
Click to expand...
Click to collapse
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
samep said:
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
Click to expand...
Click to collapse
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
KingKobra813 said:
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
Click to expand...
Click to collapse
Correct.
Refer to post 8 for the links to alternate rooting method files if you don't already have them.
Best wishes for success. No luck to it.
I was on CM 12.1 and I want to go back to completely stock Note 4, as if I purchased my device from the Sprint Store!
I went to download Odin and the stock firmware of Android 5.0.1 for my device, I followed instructions online, and when I press start in Odin, after about 3 seconds it Fails.
Can I not go back to stock Touchwiz 5.0.1 firmware after being on CM 12.1? I do not have a nandroid backup, and even when I try and access Recovery, it is no longer custom recovery, it is a very simple looking recovery screen, with no option to restore a backup.
What can I do! ): I'm extremely stressed and worried I'm not quite sure what to do.
My phone does go into Download mode just fine and show up in Odin.
Also, my phone actually boots up fine, and works fine, but there is no custom recovery, and Odin is failing when trying to flash the stock firmwares
Down load the latest tar from samsung its in the dev section that will fix your phone with odin
pbedard said:
Down load the latest tar from samsung its in the dev section that will fix your phone with odin
Click to expand...
Click to collapse
Since you're familiar with CM and recent OE1 writes both on TW and CM, can you tell the OP if reactivation lock exists on CM, please? How to disable, if enabled?
He's trying to flash OF5 in Odin but it quickly fails or he's downloading the correct OF5 tar now. Add any suggestions you think he might need when coming from CM12 to stock tar these days.
I suspect the recovery is now stock due to partial flash (if possible), reactivation lock or attempt to root in Odin again.
Thanks in advance.
Sent from my SM-N910P using Tapatalk
Ok I dont know the fancy terms so please bear with me as I explain what I did.
I wanted to root my note 4 I downloaded odin v 3.07 and followed the "easy" online steps.
so it did its thing odin said pass then the phone started resetting this just looped and looped. so I tried and tried again and no success . I factory wiped the phone and still nothing, I fear I bricked this thing can someone help me I feel like a complete idiot. Thanks
From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the exploited kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk
samep said:
From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the rooted kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I believe i had the latest update 5.1.1 I got the phone working again. I found the latest Md5 and used odin 10.7. I am so new to this its stupid its taken me 2 hours to fix my first mistake I basically lost everything but im ok with that. Thanks let me give this another try i was scared id be at sprint in the morning buying a new phone.
A month ago I needed to get an extra Note 4 I had back to 5.0.1, it was on 5.1.1. I flashed it in Odin everything worked perfectly, rooted it, phone works great. A bout 2 weeks ago, I helped someone out that needed a phone temporarily, so I let them borrow it being the phone is unlocked. The person reset the phone and updated it before giving it back to me, they thought they were being nice because I let them borrow the phone. I wasn't mad but the unlock went away, no big deal, but now I can't get it off 5.1.1, and back to 5.0.1. I tried 4.4.4 and 5.0.1 a few times now Odin keeps giving me a fail. Here is what I have done:
-Tried both Odin 10.6 & 10.7 (use as admin)
-Tried 4.4.4 and 5.0.1
-There is no Google account on the phone
-Reactivation lock is off
I had flashed this phone and 2 other same model without any issues. Like I stated I have done this a few times on the SM-N910P, not to mention I'm not an expert but have been rooting and using Odin for a few years. Any help would be greatly appreciated, and I will answer any questions as far as what I did. I'm not looking for the fix to be spoon fed to me, but maybe some other options I should look at.
"long time listener, first time caller"
If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7 shouldn't be attempted.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk
Thanks for the quick reply
samep said:
If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened
Alex215 said:
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened
Click to expand...
Click to collapse
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I left the phone at the shop and will be picking it up tomorrow to try to figure it out. I have a feeling it was updated beyond the OB7, I will use PhoneInfo to verify the current bootloader.
Bootloader version...
samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.
Alex215 said:
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.
Click to expand...
Click to collapse
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk
Thanks
samep said:
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...
Alex215 said:
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...
Click to expand...
Click to collapse
I just can't understand why it won't at least allow me to return to the stock firmware.
Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you trying to get your MSL? Or UICC unlock?
Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk
samep said:
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.
ianmb said:
Are you trying to get your MSL? Or UICC unlock?
Click to expand...
Click to collapse
MSL
Alex215 said:
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.
Click to expand...
Click to collapse
Presently, the only tars that will restore are OJ6 OK1. OK1 is on Sammobile now.
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
Alex215 said:
MSL
Click to expand...
Click to collapse
MSL doesn't change. If you had it before, it still works. If not, there is a galaxy tools version that still works. If your phone is paid in full, Sprint will release it in chat session.
Sent from my SM-N910P using Tapatalk