Related
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.
cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing
1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?
And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966
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
Was running alliancerom on 4.4.2 and found the unlocking bootloader option. Unlock worked and tried the jasminerom after installing ttwrp-3.0.2-0-hltevzw-4.4.img. Then discovered cm13 which worked great but discovered a kernel opps so installed new modem and bootloader based on of1. The bootloader bricked. Odin won't let me install the retail stock roms. It gives an error in korean. I was able to install of1 recovery but cannot get the system.img.ext4 thru odin without the korean error popping up.
At this point I don't see how I can return to stock. Is there a way out or do I have a dead device? Any help appreciated.
Thanks.
[This link makes me think I am screwed: http://forum.xda-developers.com/showpost.php?p=68406517&postcount=515]
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.
Dear Community,
I have managed to reach this wonderful error message on my S8. A few of you knew this maybe with "FRP" from other Samsung devices. However, I know I get this because I am using a custom rom and a modified kernel. I also do know a possible solution might be flashin a new stock firmware through Odin - so my question is, how can I save my data? I only need my Whatsapp folder and my pictures.
For the nosy readers, I did download a GPS Faker App from the Google Playstore, and I had to re-enable my developer settings. Sadly I forgot to push the button for "OEM Unlock" to yes.
Have a nice day!
Sadly there is no other way to fix this, the only way I got it to work again was to go into Odin mode and flash a stock firmware ( I also lost root access and TWRP, which I installed afterwards again )
You can YouTube how to flash a stock firmware
Hopefully this helped
ItsYeBoi2016 said:
Sadly there is no other way to fix this, the only way I got it to work again was to go into Odin mode and flash a stock firmware ( I also lost root access and TWRP, which I installed afterwards again )
You can YouTube how to flash a stock firmware
Hopefully this helped
Click to expand...
Click to collapse
Is there no other option like installing an unmodified kernel through odin? Tried with Jesse, but I was not able to transform the flashable .zip to a .tar.md5 for Odin.
I'm pretty sure to install a custom kernel you need OEM unlocked, but I might be wrong... I just installed the firmware i needed from sammobile and flashed it using Odin.
ItsYeBoi2016 said:
I'm pretty sure to install a custom kernel you need OEM unlocked, but I might be wrong... I just installed the firmware i needed from sammobile and flashed it using Odin.
Click to expand...
Click to collapse
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
dave7802 said:
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
Click to expand...
Click to collapse
but what if the file i downloaded is just a *.zip file?
is there a way that i wont lose my data?
Same problem
Hello. I got stuck in the "custom binary blocked FAP lock" too. my question is: will there be any problem if i try to flash a firmware from another country? Also, what are the risks that i completely brick my phone?
I was on stock rom 8.0, with twrp and magisk installed.
dave7802 said:
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
Click to expand...
Click to collapse
one of the lucky ones here.
I think my biggest obstacle is my Mac. Got all my pre-requistes sorted out , run jOdin, connected to phone, open up the firmware folder and designate the correct files, get the PIT file, and click start.... and get "A corrupted file was detected. In order to continue, you must select a valid Odin File" error . Downloaded several firmwares and cant get past this issue.. Not sure what to do (new versions of jOdin comptability? But even back in 2017, i tried flashing with jOdin but never succeeded despite following every step.