Recently decided to try the Bootloader unlock.
Thought everything had gone well, it seemed OK.
Flashed TWRP, and now it won't boot.
I'm stuck at the phone telling me to take it to a Verizon store to fix it.
That being said, I can get into download mode and I get the following :
ODEN MODE
PRODUCT NAME : SM-N900V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOW WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SMREV: S1, T1, R1, A2, P1
WRITE PROTECTION: Enable
UDC START
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
From all that, it seems that my recovery is not any good (probably from flashing twrp, duh).
I haven't been able to find a NC2 or NC4 flashable recovery anywhere.
Help?
Or am I barking up the wrong tree and do I need something else?
darkhawkff said:
Recently decided to try the Bootloader unlock.
Thought everything had gone well, it seemed OK.
Flashed TWRP, and now it won't boot.
I'm stuck at the phone telling me to take it to a Verizon store to fix it.
Click to expand...
Click to collapse
That "Verizon" message means that you did NOT unlock the bootloader succesfully.
You would normally see [size=+1]MODE: Developer[/size] in the Odin/Download mode screen if you had successfully unlocked.
As a matter of fact, that condition should always be checked for before trying to flash any recovery.
darkhawkff said:
AP SMREV: S1, T1, R1, A2, P1
Click to expand...
Click to collapse
[size=+1]Whoa! HOLD THE PHONE![/size] (Somebody with an older bootloader - MJE or NC2 at the latest)
If you reflash with Odin, USE EITHER MJE or NC4 at most - nothing later than that!
darkhawkff said:
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
Click to expand...
Click to collapse
I've never seen those messages before, but it's probably because you flashed something either into the boot partition or the recovery partition and your bootloader is not yet unlocked.
darkhawkff said:
From all that, it seems that my recovery is not any good (probably from flashing twrp, duh).
I haven't been able to find a NC2 or NC4 flashable recovery anywhere.
Help?
Click to expand...
Click to collapse
I will help you out. Please stand by. DO NOT FLASH NJ6 NK1 OB6 or OF1.
darkhawkff said:
Or am I barking up the wrong tree and do I need something else?
Click to expand...
Click to collapse
Stand by for more. posting now (quickly) so you don't do something rash.
bftb0 said:
That "Verizon" message means that you did NOT unlock the bootloader succesfully.
You would normally see [size=+1]MODE: Developer[/size] in the Odin/Download mode screen if you had successfully unlocked.
As a matter of fact, that condition should always be checked for before trying to flash any recovery.
[size=+1]Whoa! HOLD THE PHONE![/size] (Somebody with an older bootloader - MJE or NC2 at the latest)
If you reflash with Odin, USE EITHER MJE or NC4 at most - nothing later than that!
I've never seen those messages before, but it's probably because you flashed something either into the boot partition or the recovery partition and your bootloader is not yet unlocked.
I will help you out. Please stand by. DO NOT FLASH NJ6 NK1 OB6 or OF1.
Stand by for more. posting now (quickly) so you don't do something rash.
Click to expand...
Click to collapse
Thanks for the insight. No worries, I was downloading NC4 ATM, but I would prefer NC2 I think, for now. I got no problems waiting...it isn't my 'main' phone anymore. I got a note 5, but I prefer my note 3 for most usage. It's just....nicer....
I appreciate the help greatly though! Finding older files (like NC2) is damn near impossible. If I was at home, it's probably sitting on my file server somewhere, but I don't have access at the moment. Still at work.
I will also note, I did verify prior to trying to bootloader, to ensure the CID started with 0x15, and it does. Checked like 5 times, just to be sure.
And I figured it would.....since I bought this the day it was released. Anyway.....
Thanks!
OK. First things first. Let's examine the state your phone is currently in before you flash anything.
My educated guesses are that (a) your bootloader is NOT unlocked, and possibly (b) the phone is "stuck" always trying to boot into the recovery - which gives you the Verizon screen, or (c) something worse - for example if you flashed the custom recovery into the wrong partition.
The not-unlocked condition means that whatever is trying to be booted (either the recovery partition or the boot partition) has something non-Samsung in it. Either one would give you the Verizon message about unauthorized software.
When the phone boots from a cold startup, it looks at something in NVRAM called the "BCB" - the Boot Communication Block. If it is "empty" it will do the normal thing - try to boot the phone normally, starting with the "boot" partition. But, the BCB can contain other instructions, such as "boot to recovery", or "boot to Odin mode". And experience seems to indicate that the conditions under which the BCB is cleared (i.e., goes back to the default) is a little bit buggy or quirky - so that the phone can get "stuck" always trying to boot either the recovery or Odin/Download mode.
The "three-finger salute" of Vol-Down + Home + Power - which you normally use to start up Odin - seems to clear the BCB when you choose the "Cancel" option (Vol-Down) from that initial splash screen, and it usually will attempt to boot the normal ("boot") partition if you select "Cancel" ( = Vol-Down ).
So FIRST: Pull your battery. Re-insert. Vol-Down+Home+Power until you get that "do you want to install custom software?" screen. Press Vol-Down to cancel.
===> Does your ROM boot correctly?
If so, then you can attempt to unlock again without any flashing. I suppose you are still rooted if your phone still boots.
===> If your ROM still boots, please report it's exact firmware version. It makes a big difference whether it is a M-series or an N-series. (Note: I am asking about the bootloader firmware, not the ROM version).
If your ROM does not boot, then you are going to have to use Odin in one way or another.
I can help you out with that and point you at the correct custom recovery, depending on which bootloader firmware you want to end up with. (Especially if you have a copy of the NC2 firmware at home (it's the only one I don't have).) DON'T FLASH NJ6 OR ABOVE IN ODIN - yet. (Towelroot V3 is trivially easy on anything from MI9 through NC4, and rooting appears to be a pain in the rear beyond that)
let me know what you find.
darkhawkff said:
I will also note, I did verify prior to trying to bootloader, to ensure the CID started with 0x15, and it does. Checked like 5 times, just to be sure.
And I figured it would.....since I bought this the day it was released.
Click to expand...
Click to collapse
That certainly is a mandatory prerequisite to success. But it doesn't mean that something won't go wrong during the unlock process. To be sure, just boot into Odin mode after you think everything has succeeded and look for that "MODE: Developer" message on the Odin screen to verify that the unlock process succeeded.
There are a couple different versions of the unlocker binary in that Unlock thread, and most of the variations have to do with how the program went about reading the CID value out of the volatile filesystem /sys during initial sanity checks. As that location seemed to change from firmware release to release, there was some dependency between the unlock binary version and the OS release level of the rooted ROM it was used on. So a "safety check" in the code was what was making it non-portable; the actual CID change and binary patching of the "aboot" partition was the same in every version.
I might have used @donc113's original variant (post #218) when I was on MJE. If you are rooting with M* or N* ROM firmware, that version should work.
The other thing that happened was that (I think?) someone released an app that was really just a wrapper around the binary file. That had the unfortunate side effect of hiding the status and error messages the unlock binary produces if someone happened to use it on the wrong OS version. It's possible that someone that is rooted could slip a different version of the "unlock" binary underneath that app (in it's appropriate /data/data/* location), but that's asking a lot from people who gravitate towards using "one click" apps.
You didn't mention whether you were using the app or just the command line. If it was the latter I think that careful inspection of the unlock binary's output would have indicated success or failure.
Anyway, some TWRP custom recovery links:
TWRP for hltevzw
If you have a M* series bootloader use the -4.3.img recoveries, otherwise use -4.4 for N*, O*, or P* firmware
(The AryaMod ROM uses the Aroma installer, which apparently needs the twrp-2.8.7.0-hltevzw version, not the twrp-3.0.2-0-hltevzw. So... grab both of them)
PS I recently "upgraded" my bootloader from MJE to NC4. I did this because the M* series bootloader is incompatible with later kernels (due to technical issues about how the "DTB" (Device Tree Blob) attached to the kernel is parsed and initialized by the bootloader). I probably would have gone with NC2 instead of NC4, but all the links for the NC2 leak firmware were dead. At least NC4 is easy to root with Towelroot v3, and so far I've been able to boot and run not only lolipop roms (e.g. CM13) but a marshmallow rom (AryaMod) without major troubles. So I have an Odin-back-to-stock method for device recovery that is easily rootable (in contrast to NJ6, NK1, or PL1 which have no root method, or OB6/OF1 which have crufty/difficult rooting methods (& perhaps dodgy too)).
.
Any chance of just using Odin and flashing a stock recovery image? Rather than killing the entire os too?
I can't find just a recovery image though.
darkhawkff said:
Any chance of just using Odin and flashing a stock recovery image? Rather than killing the entire os too?
Click to expand...
Click to collapse
That works when the bootloader is unlocked (even with unsigned recoveries such as TWRP). Not sure about the locked case.
Code:
tar -H ustar -c -f my_recovery_only_Odin_bundle.tar recovery.img
md5sum my_recovery_only_Odin_bundle.tar >> my_recovery_only_Odin_bundle.tar
mv my_recovery_only_Odin_bundle.tar my_recovery_only_Odin_bundle.tar.md5
Note that the above technique for preparation of Odin flashables isn't restricted to adding just a single file. For instance, someone that had a bootlooping stock ROM in need of repair could probably create a tar.md5 bundle that only contained "boot.img" and "system.ext4.img"* Note that when Odin does the MD5 checking, it wants the filename to be unchanged (other than the .md5 extension). So don't change the name of the .tar.md5 file to something else or the MD5 check in Odin will fail.
darkhawkff said:
I can't find just a recovery image though.
Click to expand...
Click to collapse
It's inside the stock Odin tar.md5 bundle. Just extract it.
Is it even important at the moment? So long as your phone boots normally, what's in the recovery partition simply doesn't matter
Did you try the Vol-Down+Home+Power startup (followed by Cancel == Vol-down) that I suggested above? What happens?
.
* There is one place where partial firmware flashes would be extremely ill-advised: if you were flashing a bootloader (dear lord why?) ALL five pieces (aboot.mbn, sbl1.mbn, rpm.mbn, tz.mbn, sdi.mbn) need to be flashed as a group all in one go
Yup. Just tried that finally (was busy at work).
Fixed. I'm unlocked bootloader.
Yup, I'm still on NC2 (not that it's a surprise).
Still haven't been able to find the files at home. I thought I might have them saved somewhere, but apparently not. Still have 1 or 2 places to look, but I'm going to guess that I don't have it anywhere.
darkhawkff said:
Yup. Just tried that finally (was busy at work).
Fixed. I'm unlocked bootloader.
Yup, I'm still on NC2 (not that it's a surprise).
Still haven't been able to find the files at home. I thought I might have them saved somewhere, but apparently not. Still have 1 or 2 places to look, but I'm going to guess that I don't have it anywhere.
Click to expand...
Click to collapse
hope I helped.
Make a backup of your current ROM in TWRP and get it off the phone into a safe place. Then you will feel free to experiment with different ROMs as time allows. I would also suggest it is really a good idea to save that "debrick" image on the SD card in case a utter disaster happens (probably you will never use it though).
(before reformatting the SD card to get it back to usefulness)
Code:
dd if=/dev/block/mmcblk1 bs=4096 count=65536 of=/data/local/debrick.img
(or, too-late... get a debrick image with the modded "aboot" partition unlocked bootloader)
Code:
dd if=/dev/block/mmcblk0 bs=4096 count=65536 of=/sdcard/debrick.img
I'll archive the NC2 if you can find it (send me a PM) even though I can't use it any longer as I recently flashed NC4 bootloader. I have all the other firmware releases, just not that one.
The NC2 (leak) engineering bootloader appeared at a time when the kernel DTB blobs were changing structure; hopefully it is able to boot all later kernels. Please drop a note somewhere in these forums if you discover problems booting newer kernels - whether custom or stock. As I mentioned, if NC2 won't work, NC4 seems decent enough so far and it preserves a full-stock Odin recovery/rescue to a ROM version which is easily rooted with Towelroot v3
As to modems, I've done a few pairings of my flashable-stock ROMs with different modem releases (see the flashable stock thread for downloads) and - strangely - the NC4 modem won't work at all with NJ6 or NK1 (no service) kernels/ROMs, but it will work with later kernels/ROMs e.g. OB6-PL1. Just mentioning it because the NC2 modem might behave in a similar strange fashion since it is of the same vintage. I haven't had any troubles flashing modems up-version or down-version.
.
Well, all great!
I got Aryamod installed and going well.
NC2 bootloader yet too! TWRP obviously installed and OK, with 2.8.7 I believe. Installing apps now.
It really makes a difference with this phone too. I'm quite surprised by it to be honest.
All I know, is I might actually switch back to using my note 3 instead of my note 5 as my daily driver again.
Thank you again for the help. I really appreciate it.
darkhawkff said:
Well, all great!
I got Aryamod installed and going well.
NC2 bootloader yet too! TWRP obviously installed and OK, with 2.8.7 I believe. Installing apps now.
It really makes a difference with this phone too. I'm quite surprised by it to be honest.
All I know, is I might actually switch back to using my note 3 instead of my note 5 as my daily driver again.
Thank you again for the help. I really appreciate it.
Click to expand...
Click to collapse
Good deal.
AryaMod is a pretty nice ROM. Marshmallow FTW!
(I'm glad I bought a device with 3GB of RAM.)
Could you please message me at [email protected] I tried to root my sm-n900v note 3 on 5.0 and it's soft bricked. I can't get Odin to flash..keeps failing. I need to talk to someone just bought it week ago man.
Related
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Slimfast35 said:
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Click to expand...
Click to collapse
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
bftb0 said:
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
Click to expand...
Click to collapse
I just flashed back to stock via odin. Worked fine.
Slimfast35 said:
I just flashed back to stock via odin. Worked fine.
Click to expand...
Click to collapse
Full MJE over the top of soft-bricked MJE?
bftb0 said:
Full MJE over the top of soft-bricked MJE?
Click to expand...
Click to collapse
Yeah.
Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
kociubin said:
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
Click to expand...
Click to collapse
In Odin flash an older firmware then reroot and wait for a root update from Chainfire and the TWRP team
I know a couple people that have done that.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F
When I first upgraded to the new firmware, I found the same thing that you did - I wanted to be able to flash custom roms and didn't know when or if TWRP and ROOT was going to be possible with this new firmware - so I used odin and reflashed July's Firmware and I was able to do so without any Issues - so then I decided to try to upgrade the AP/CSC/CP files from the latest update and replaced the bootloader with the bootloader from july's update and it worked.
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not an indication of future issues for rooting samsung phones....
mocsab said:
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not indication of future issues for rooting samsung phones....
Click to expand...
Click to collapse
No it isn't. Korean models had already been incompatible with official TWRP since firmware APG7 and I confirmed it working again when I replaced the kernel inside TWRP with one built from the latest source released by Samsung. So, someone needs to build a new TWRP recovery with BPH6 kernel source and everything will become fine again.
I didnt know that but it is very good news as far as I am concerned.
I have alwasy been fearful that Samsung was going to eventually lock down their international phones like they did to the US Variants - and when this originally happened to me, I started thinking that maybe my worst fears had come true. Thanks for the information....
I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Xlim said:
I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Click to expand...
Click to collapse
pls send related boot loader download link
same iussue .. some news??
by the way to use root now i put the old firmwere
FARSHOOD said:
pls send related boot loader download link
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24671318762848807
When flashing bootloader in Odin there is an options tab, there are checkboxes - Auto Reboot which is checked - Re-Partiion which is unchecked - and - F.Reset Time which is checked, I flashed new bootlaoder and modem and now my phone will not restart no matter the key combination I press. So Are those checkboxes suppose to be checked off or unchecked
help me please: with my Samsung Galaxy Note 3 900V. I have a problem: got root and can not unlock the bootloader of the fact that I have a CID begins with the digits "11", and because of which it is impossible to boot into recovery. Safestrap The program also fails to take advantage of (by clicking on "reboot to recovery" device is loaded into the system, have tried almost all the versions of this app and the new and old), I have the firmware is now 5.0 N900VVRUEOF1, what to do and how I can install custom? Maybe we can somehow lower firmware version from 5.0 to 4.4.2 or 4.3, there use to Safestrap? Or somewhere you can find Firmware N900V_VZW_N900VVRUCNC4 service with 4 files? Because a single file, this firmware is not installed - an error aboot? Please help me for 4 days already suffer...
Here is the sequence of SM-N900V stock firmware releases:
MI9->MJ7->MJE->(NC2)->NC4->NJ6->NK1->OB6->OF1
Shown above (in red) are the "RP SWREV" anti-rollback protection trigger points: MJ7, NC4, and NK1.
Once you have flashed a stock firmware in this sequence, you can roll backwards (or forwards) only to the closest prior trip point.
So for instance - in your case - you had/have OF1 firmware on your phone, so you can only flash NK1, OB6, or OF1. You can not flash NC4 (or NJ6, or anything else before NK1).
If you were to flash NK1, you might have trouble rooting - I'm not sure if Towelroot works on NK1.
And even then, if I recall correctly there is no Safestrap version for NK1. But don't quote me on that.
Perhaps you could query @donc113
If I recall correctly he is on NK1, so he might have some ideas for you. He is unlocked now & so probably has more freedom (bcuz of custom recovery), but if he spent time "rooted but locked" on NK1, he'll know what your options are.
.
apxati said:
help me please: with my Samsung Galaxy Note 3 900V. I have a problem: got root and can not unlock the bootloader of the fact that I have a CID begins with the digits "11", and because of which it is impossible to boot into recovery. Safestrap The program also fails to take advantage of (by clicking on "reboot to recovery" device is loaded into the system, have tried almost all the versions of this app and the new and old), I have the firmware is now 5.0 N900VVRUEOF1, what to do and how I can install custom? Maybe we can somehow lower firmware version from 5.0 to 4.4.2 or 4.3, there use to Safestrap? Or somewhere you can find Firmware N900V_VZW_N900VVRUCNC4 service with 4 files? Because a single file, this firmware is not installed - an error aboot? Please help me for 4 days already suffer...
Click to expand...
Click to collapse
You can NOT unlock a Note 3 where the CID starts with 11.
Sorry..but as of now... It simply can not be done.
The exploit that was used to unlock those whose cid begins with 15. Only eMMC chips that start with 15 have the 'backdoor' that was used to unlock the bootloader.
Sent from my SM-N900V using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 08:15 PM ----------
bftb0 said:
Here is the sequence of SM-N900V stock firmware releases:
MI9->MJ7->MJE->(NC2)->NC4->NJ6->NK1->OB6->OF1
Shown above (in red) are the "RP SWREV" anti-rollback protection trigger points: MJ7, NC4, and NK1.
Once you have flashed a stock firmware in this sequence, you can roll backwards (or forwards) only to the closest prior trip point.
So for instance - in your case - you had/have OF1 firmware on your phone, so you can only flash NK1, OB6, or OF1. You can not flash NC4 (or NJ6, or anything else before NK1).
If you were to flash NK1, you might have trouble rooting - I'm not sure if Towelroot works on NK1.
And even then, if I recall correctly there is no Safestrap version for NK1. But don't quote me on that.
Perhaps you could query @donc113
If I recall correctly he is on NK1, so he might have some ideas for you. He is unlocked now & so probably has more freedom (bcuz of custom recovery), but if he spent time "rooted but locked" on NK1, he'll know what your options are.
.
Click to expand...
Click to collapse
There are none. He can root OF1 via the Arabian program but no version of Safestrap works with it.
As to NC4... I was on 4.4.2 which is NC2/NC4 and it was root able... and OF1 (nor NK1) Can not be rolled back to NC4 or NC2.
I know of no way to root NK1 (4.4.4)
(I had NC4 modem [still do] but NC2 firmware)
Sent from my SM-N900V using Tapatalk
@donc113 Oops, my bad - I thought you were on NK1
if I install NK1 then will I be able to take advantage Safestrap got root? Or wait until be able to unlock the bootloader on the " 11 " chip?
apxati said:
if I install NK1 then will I be able to take advantage Safestrap got root? Or wait until be able to unlock the bootloader on the " 11 " chip?
Click to expand...
Click to collapse
NK1 didn't have a publicly-available rooting method, and even if it did, Safestrap never supported NK1.
Unfortunately you are stuck with "rooted stock" only on Ox11 CID phones that have been flashed to NK1 or later firmware.
The hazard with only having a single root (no custom recovery as an alternative boot) is that if you make a mistake that boot loops or otherwise wedges your OS boot, you'll have to start completely over from Odin - and will have no backups.
My next phone is going to be a Nexus. All this dicking around with arcane rooting methods on Samsung devices is BS. It results in a tiny dev community on what is otherwise nice hardware... so, very scarce ROM development.
Can I install custom firmware android 6.0 in some way in my situation ?
apxati said:
Can I install custom firmware android 6.0 in some way in my situation ?
Click to expand...
Click to collapse
In your situation - rooted but without a known way to unlock the bootloader - you have to live within the restriction of using Samsung-signed boot images.
The closest thing to that is Jasmine (for locked/retail devices), but it is a Lolipop ROM.
The chance of you being able to make a custom MM ROM behave nicely with a stock Lolipop boot/kernel image seems a bit remote.
You could experiment but you need to be fully aware that any mistake or booting problem means that you would have to start all over with Odin (full stock flash) and re-rooting.
bftb0,
Here a similar instruction to unlock the bootloader, but the Note 4 with a change in the CID on the "15 .." http://forum.xda-developers.com/not...erting-retail-note-4-to-t3358957#post66367497 How can I do something like this to change my CID and make it starting with "15 .." and continue the unlock here on this instruction http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
apxati said:
bftb0,
Here a similar instruction to unlock the bootloader, but the Note 4 with a change in the CID on the "15 .." http://forum.xda-developers.com/not...erting-retail-note-4-to-t3358957#post66367497 How can I do something like this to change my CID and make it starting with "15 .." and continue the unlock here on this instruction http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Click to expand...
Click to collapse
The issue is not the number 15, it is what that number means.. It means that a specific eMMC chip was used and that specific chip had a known 'backdoor' that was used to unlock Note 3's. The code that worked for that specific chip does not work other chips.
So changing your cid to start with 15, would not replace the eMMC hardware and the code still would not work.
Until someone finds the backdoor into those other chips.. Your phone can not be unlocked.
Sent from my SM-N900V using Tapatalk
@apxati
donc113 said:
The issue is not the number 15, it is what that number means.. It means that a specific eMMC chip was used and that specific chip had a known 'backdoor' that was used to unlock Note 3's. The code that worked for that specific chip does not work other chips.
Click to expand...
Click to collapse
^this.
If you are curious, the details of the exploit are described in a file in beaups' github - see SAMDUNK_1.0-03262016.pdf
It happens to turn out that 0x15 is the vendor code for Samsung. But that's more or less just a coincidence; Samsung makes all sorts of stuff... including eMMC flash memory.
bftb0 said:
Here is the sequence of SM-N900V stock firmware releases:
MI9->MJ7->MJE->(NC2)->NC4->NJ6->NK1->OB6->OF1
Shown above (in red) are the "RP SWREV" anti-rollback protection trigger points: MJ7, NC4, and NK1.
Once you have flashed a stock firmware in this sequence, you can roll backwards (or forwards) only to the closest prior trip point.
So for instance - in your case - you had/have OF1 firmware on your phone, so you can only flash NK1, OB6, or OF1. You can not flash NC4 (or NJ6, or anything else before NK1).
If you were to flash NK1, you might have trouble rooting - I'm not sure if Towelroot works on NK1.
And even then, if I recall correctly there is no Safestrap version for NK1. But don't quote me on that.
Perhaps you could query @donc113
If I recall correctly he is on NK1, so he might have some ideas for you. He is unlocked now & so probably has more freedom (bcuz of custom recovery), but if he spent time "rooted but locked" on NK1, he'll know what your options are.
.
Click to expand...
Click to collapse
Is this true with dev edition running OF1?
seadooman said:
Is this true with dev edition running OF1?
Click to expand...
Click to collapse
Yes but you will lose root and bootloader unlock.
Sent from my SM-N900V using Tapatalk