Re-Partitioning Developer Edition - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

Can someone please explain to me how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!

doubleplay648 said:
Can someone please explain to me
how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!
Click to expand...
Click to collapse
I replied to you on PM, but this may be helpful for others.
Repartitioning has nothing to do with downgrade-ability. The Safe Upgrade won't work for you either, since it includes older TrustZone. N910VVRU2BPA1_StockRestore_Incremented.tar.md5 didn't change any of the critical partitions. You'll need a similar tar for OG5 to be able to downgrade, which isn't available unfortunately.
Click to expand...
Click to collapse
However, you could flash OG5 ROM via TWRP, if you wish.

Cannot install TWRP
hsbadr said:
I replied to you on PM, but this may be helpful for others.
However, you could flash OG5 ROM via TWRP, if you wish.
Click to expand...
Click to collapse
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?

doubleplay648 said:
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?
Click to expand...
Click to collapse
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.

hsbadr said:
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.
Click to expand...
Click to collapse
So i have the developer edition. I sent it into samsung for repair and i mentioned several times about the bootloader being unlocked. I tried flashing the twrp tar you gave me and it gave me a odin fail and my phone says SECURE CHECK FAIL: recovery
The only thing i did when i got my phone back was upgrade the 5.0.1 to your 5.1.1 incremented stockrestore.
Did i do this right?
1. put phone into download mode (power + volume down+ home)
2. plug into pc and open odin.
3. flash the tar via ap, without checking re-partition
So any idea why this isn't working? Samsung had to replaced the motherboard in my phone. Is it possible that when they sent back my phone they updated the SW to a locked bootloader?

Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!

doubleplay648 said:
Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!
Click to expand...
Click to collapse
Your phone is retail. If you want DevEd you will need to talk to one of the few folks at Samsung that know what a Deved is. Convince them that they retailed your phone when they replaced the main board. They should fix this. The only number you should call is the 800 number on your DevEd receipt. If the CSR doesn't know what your talking about, ask for a supervisor, escalate until they know what you have. They need to be clear what you have, or it will return retail again. The good news is they will flash your fuse 2 retail to DevEd.
The number is 800-757-0280
Click on image,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From Odin Download screen it should say "Mode: Developer"

From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
---------- Post added at 02:22 PM ---------- Previous post was at 02:02 PM ----------
anticloud said:
From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
Click to expand...
Click to collapse
and I can't help but mention - if you happened to use one of the safe upgrades to move forward, there is rollback.

Related

[BOOTLOADER] How to Install a Bootloader Update

NOTE: If anyone has any further questions about bootloaders on the S3, please note that I have moved on to another device. Sorry!
Hi everybody,
As you may or may not know, the latest builds of CyanogenMod 10.1 (and many other ROMs which use CM as a base) refuse to install without an updated bootloader on your device. Even if you bypass this requirement, the ROM won't boot. I haven't seen any clear-cut instructions on updating the bootloader except for a single post buried in the CM10.1 nightly thread, posted by Jiangyi, but that update also changes your modem, so I thought I'd throw together a thread dedicated to bootloaders only.
Step 1 - Identify your model
This subforum supports 2 different models; The I747 and the I747M. You can find your device's model in a few different ways:
While Android is running
In Settings, under About Phone, the Baseband version shows the currently installed modem firmware version. If your phone currently works on mobile networks, then you've probably got the right modem firmware for your model, and the Baseband version will start with either "I747" or "I747M". This is your model.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While the phone is off
Underneath your battery is a sticker showing your IMEI and other information, including the model number.
Step 2 - Download the correct update
You can install this updated bootloader in a couple different ways; Most people should be comfortable flashing ZIPs in their recovery (CWM or TWRP both work fine) while others may want to install the update via Odin. Choose your model and preferred method, and download the matching file from below.
I747U (AT&T)
I747UCALG1 - Jul 1, 2012 - boot_CWM_I747UCALG1.zip - 1.13 MB
I747UCDLK3 - Nov 3, 2012 - boot_CWM_I747UCDLK3.zip - 1.13 MB
I747UCDMG2 - Jul 2, 2013 - boot_CWM_I747UCDMG2.zip - 1.13 MB
I747UCUEMJB - Oct 11, 2013 - boot_CWM_I747UCUEMJB.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
I747M (Canada and overseas) (Updating this list shortly...)
I747MVLUEMK5 - Nov 5, 2013 - boot_CWM_I747MVLUEMK5.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
Check my Dropbox if d-h.st is giving you issues.
Step 3 - Flash the update
Depending on which type of update package you downloaded, follow one of the following steps:
Flashing with Odin
Download Odin: [link]
Put your phone into download mode. Some ROMs have this option in the Power>Reboot menu, otherwise just hold "Volume Down" and "Home" while powering on your device.
Launch Odin, then connect the USB cable to your device.
Click the "PDA" button and select the package you downloaded in step 2.
Click "Start" in Odin and wait for the process to complete. Your device should reboot automatically when the flash is complete, and you're done.
Flashing in recovery
If you've downloaded a flashable .ZIP from above, copy it to your SD card or internal storage. Reboot your phone into recovery mode (you can do this by holding "Volume Up" and "Home" while powering on your device; let go of the buttons when you see "Recovery booting..." in blue text in the top left of the screen) and install the .ZIP as an update. Reboot, and you're done.
Note: After flashing in recovery, you need to reboot before you (and ROM installers) actually see the new version number.
Did you brick your phone attempting to downgrade your bootloader?
There really is no reason to downgrade your bootloader; If you did it to be able to flash a ROM that doesn't recognize the newest bootloader version and therefore wouldn't let you flash, you should contact the ROM developer and tell them to add the newest bootloader version to their asserts. The latest bootloaders trigger eFUSEs within the device, no longer allowing it to boot from older bootloaders. These eFUSEs cannot be reset, but @-Mr. X- has come up with an unbricking method that may help you out. Check it out here.
If you're looking to update your modem as well, check my signature for a link to the modem thread.
Look forward to seeing a recovery flashable zip that updates the bootloader. Never have I seen that before. I have always used Odin for that. Thanks and looking forward to trying it out.
Sent from My Spiderman Themed I747
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
upndwn4par said:
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
Click to expand...
Click to collapse
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help. As a temporary option, you could just use the Odin update and then flash another modem on top of that.
dstruct2k said:
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help.
Click to expand...
Click to collapse
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
upndwn4par said:
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
Click to expand...
Click to collapse
The link in my first paragraph does just that, but since this is affecting a lot more ROMs than just CM, people are going to need this information and a single post on a random page of a massive thread usually gets overlooked by 99% of people. The point of this thread is to make information easy to find and ensure that people are able to update their bootloaders and run new ROMs.
Like I said, the links to his work are temporary while I get my own files uploaded. Not exactly on the fastest of connections right now.
Added recovery-flashable bootloaders to OP.
i found this post very helpful and informative i think i would have been MORE confused having just been linked to a single post. the pictures and instructions are so awesome!
thanks man the community appreciates your work, you can ignore the rent a mods
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
mcala said:
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
Click to expand...
Click to collapse
Depends on whether they updated just the modem to DLK3 or the entire system. If you have issues flashing ROMs, try flashing this first.
thanks! :good:
saves me the hassle of going thru 2k+ pages
If your unsure about which bootloader you have, check >>HERE<<
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Correct, the 4.1.1 bootloader does have the newer flash counter. It will increase your flash counter when you reboot if your not running stock (I think it checks the type of recovery installed and something with the kernel. I think.)
robbieas said:
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Click to expand...
Click to collapse
Using a recovery-flashable ZIP will not increase your flash counter.
And I take it you got his permission To post his work right?
Wayne Tech Nexus
I think it's ok to post links to other people's work, and to improve on it by creating another method of flashing, is it not?
Not without their permission it's not.
Wayne Tech Nexus
dstruct2k said:
Using a recovery-flashable ZIP will not increase your flash counter.
Click to expand...
Click to collapse
This is incorrect. Simply having a custom recovery period with the 4.1.1 bootloader will always increment your counter to 1 after a reboot. Triangle Away will reset your counter to 0, but upon reboot it will be back to 1.
This was my experience when I rooted from 4.1.1. Then I Odin`d back to 4.0.4, rooted, CWM, flased ROMs and my counter stayed at 0 through multiple flashes. As soon as I flashed this bootloader patch my counter went to 1 ater reboot. Triangle Away will reset to 0, but on reboot it goes back to 1.
Not sure it really matters, not sure why I even care about the flash counter... guess just want to hedge my bets in case I need warranty and can't Odin to stock before returning.
dstruct2k said:
Added recovery-flashable bootloaders to OP.
Click to expand...
Click to collapse
What does "OP"means?

Samsung tech support trashed wife's phone after Settings App failure fix

It seems that after the November AT&T OS upgrade that my wife was unable to get into the Settings App (Settings Failed Error). :crying:
1. Got on with Samsung support, they took me through several reboot sequences, etc.
2. Finally they said we need to Factory Reset. We backed up data with Kies and proceeded.
3. While rebooting from the factory reset, OP Sys fails on the language selection screen (Settings Failed Error)
4. Samsung took us too Kies and tried to flash the Op Sys.
5. Now getting "Firmware upgrade encountered an issue".
6. Tried Kies again but does not find my device.
7. Downloaded the I747 AT&T Rom and using Odin
8. Am able to get the "Downloading" screen to work
8. Odin sees the Com but when trying to flash, it Fails every single time.
HERE IS THE SEQUENCE:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I am stuck as to what to do next. PLEASE HELP :crying:
Ur wife seem to enabled the protection against odin flash. Too sad, else it would work.
This is why u should never enable that crap.
Good luck
Skickat från min SM-G900F via Tapatalk
Sachitoge said:
Ur wife seem to enabled the protection against odin flash. Too sad, else it would work.
This is why u should never enable that crap.
Good luck
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
Sachitoge, thanks for your reply!
So what your saying is that my Wife's phone is as good as being Hard Bricked?
Kinda
Samsung has implemented knox to prevent theft to reset phone, this will fail wth odin no matter what you do, its impossible because its locked and encrypted.
For now it seems its hard bricked, but if u never got root on it or if your knox trigger is 0x0, and u got this far with brick, then your operator or samsung is responsible to fix it no matter what, stay on what you say and push them saying you didnt do anything and that you enabled knox protection thus Odin flash fails. Say to them with a more serious speech and deeper speech like you its kinda feeling that you seem like you are angry. Tell them you need asap phone and replace it asap. You can even say to diagnose the phone and see that you didnt do anything illegal (root proccess) or dropped phone.
Just never take a break with whatever they say about refusing it, stay behind your words and phrase, they should and MUST help you fix the phone or replace it.
EDIT: This knox protection is additional optional protection, and is not must, so u know. Its impossible to turn it off without getting into your Settings app and disable it manually.
Skickat från min SM-G900F via Tapatalk
Sachitoge said:
Kinda
Samsung has implemented knox to prevent theft to reset phone, this will fail wth odin no matter what you do, its impossible because its locked and encrypted.
. . .
Just never take a break with whatever they say about refusing it, stay behind your words and phrase, they should and MUST help you fix the phone or replace it.
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
I talked to the voice tech support and they said that i should first try to image the operating system at the BestBuy store. If I can't get it to work then to send it into them and they will do a "free" evaluation. However since i started with a good phone, they are liable. Although they may try and get me to pay for fixing it
As it is, should i really send it to them? Or is there any other software solution, or a JTAG??? (not sure all that would involve)
Thanks!
Look, that knox protection is as good as Apple's remote iCloud lock function. It is encrypted, and it requires decryption of the system partition (i may be wrong, i just say what i believe is/can be). The Knox is a type of a Encryption, it's really secure and safe and is used widely worldwide, the decryption is hard because it must be protected with your samsung account and password, because it required that during enabling it. This indicates it is encrypted according to your specified Samsung account. I may be wrong, but try to find on internet whether it's possible to disable it remotely. Try to boot phone normally, then go on PC/Laptop and search to login to Samsung account and by any chance, look to remotely unlock this Knox security.
Other than that, without access to "Settings" app, you wont be able to disable it. Simply impossible. It is encrypted.
Same for iOS Devices that got locked with remotely iCloud lock app, it is locked and encrypted remotely and requires remotely decryption to system partition and this is why almost nobody can bypass it. There are ways but sadly are private from public to prevent Apple team patch the exploit. I do believe they use this exploit for iDevice that is stolen to afterward sell to another end-user the stolen phone, or possibly they could be unlocking devices in exchange of money. Easy money from my view, however, it is encrypted and is no way possible. MAYBE samsung can do it from their end without saying "we decrypted it and did clean install rom" instead of that, they will speak in a manner speech like "We did put the phone into a developer-only software from our end on our PC and did a full disk-clean which also killed all files, and had to re-attempt to install rom and reconfigure IMEI". Maybe not exactly like this but something close this. From what i know, whenever you do full clean, your IMEI mostly stays, this is because you mostly cant really navigate it manually or delete it, usually it is protected lol.
I hope you're not tired with this long message, you shouldn't be charged for such a mess they caused to you, so like i said, dont let your guard down and hesitate, stay behind your phrase/word! I promise, it will work!
You mentioned Voice Tech Support, talk serious, talk that you are not tech heavy, (for ur wife). Play a bit stupid-role about technology and that it happened while OS Upgrade.
Remember, they will be after your money, don't let them do it and get cash into their pocket for free, it's not worth and not your fault to cause you being charged!
Please, try my method and you will see it really saved you a couple 10 dollars. As of sending the phone, im not sure, they wont however pay the shipping fee, other than that any other cost is unacceptable so beware, dont get phished from IT experts.
Remember, reason this is long is to save you from being charged. Hope it helped, good luck buddy.
I recommend not using Odin to flash any ROMs at this point.
The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file.
There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates.
I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
audit13 said:
The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file.
There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates.
I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
Click to expand...
Click to collapse
You are right, it could be, i dont know how things really work in USA as i always bought unlocked phones and living in europe, so it was good to point that out. The error do happen while knox protection is on too, same type of message so its a bit tricky...
Skickat från min SM-G900F via Tapatalk
I have never seen Knox protection cause that error. I don't think it is not Knox that is stopping the flash, it is the bootloader security.
The only protection that I have seen that would have an effect in download mode would be re-activation lock.
Sachitoge said:
. . . other than that any other cost is unacceptable so beware, dont get phished from IT experts. . . Remember, reason this is long is to save you from being charged. Hope it helped, good luck buddy.
Click to expand...
Click to collapse
Thanks for your long reply! and in helping me with this issue. I will be firm with them. My wife is not tech savvy and I don't know how my wife's phone got encrypted, or if there was someone remotely hacking her phone from our PC or over the wireless. She always complained to me that someone was listening in on her conversations and interfering with her text messages. And we had some evidence this was taking place. She does not know how to encrypt her phone, so she didn't enable knox encryption. So perhaps her phone was hacked somehow.
On the download screen of the phone this is what I am getting:
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECURE BOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 3
SW REV CHECK FAIL : Fused 3 > Binary 0
Downloading.......
Does this mean anything to you that could possible help knowing what the problem is?
I see nothing to indicate that the phone is encrypted.
The existence of the warranty bit line tells me the phone has at least a 4.3 bootloader which caused the Odin flash to fail: the ROM being flashed has an older (probably 4.1.1) bootloader.
Knox and encryption are not the same thing. Encryption can take place in the absence of Knox and Knox can be present on a non-encrypted phone.
Whether the phone is or is not sim-locked isn't relevant to this situation as it can happen regardless of a phone's sim-lock status.
audit13 said:
I recommend not using Odin to flash any ROMs at this point. . . The flash is failing because you are trying to flash a ROM with a bootloader that is older than the bootloader on the phone which is indicated by the failure after trying to flash aboot.mbn file. . . There is not full ROM available for the i747 after 4.1.1. All OS upgrades were provided by AT&T as OTA updates. . . I recommend flashing a custom recovery, booting to recovery, mounting the data partition, a copy everything you can to a PC. Then, flash a custom ROM, Gapps, and install the Samsung Phone Info app from the Play Store to find the phone's bootloader version.
Click to expand...
Click to collapse
Thank you for your suggested solution! I have an Identical phone to my wife's phone. Is there anything else useful i can grab from my phone? The info App states:
Model: SAMSUNG-SGH-I747
Device Type: d2att
Product Name: d2uc
Country origin: MADE IN CHINA
Manuf. Date: 2012.08.31
Knox Warranty Void: 0x0
Storage: 16 GB
Product Code: SGH-I747RWBATT
Orig CSC Code: ATT
Firmware CSC Code: ATT
Active CSC Code: ATT
CSC Country: USA/US
Mobile Operator: AT&T / 310410
Bootloader Version: I747UCUFNJ2
PDA Version: I747ATTFNJ2
Baseband Version: I747UCUFNJ2
Latest Firmware: Not Found
Kernel Version:
3.4.0-1514807
[email protected] #1
32-bit
Java Virtual Machine: Dalvik 1.6.0
Root Existence: No
Android Version: 4.4.2
Build Number: KOT49H.I747UCUFNJ2
Build Fingerprint: samsung/d2uc/d2att:4.4.2/KOT49H/i747UCUFNJ2:user/release-keys
Build Description: d2uc-user 4.4.2 KOT49H I747UCUFNJ2 release-keys
Build Date: Mon Aug 10 14:43:43 KST 2015
Changelist: 1514807
Hardware / Board: qcom / MSM8960 [32-bit]
Platform / Chip: MSM8960
GPU: Qualcomm Adreno 225
Modem Board: MSM8960
Hardware Revision: REV0.4
Firmware: KIES SYMBOL --- I747UCDLK3 --- date: 2012-11-01 ---- USA (ATandT) ---- Version: 4.1.1 --- CSC: I747ATTDLK3
Your phone is running the latest ROM as indicated by the nj2.
The line about kies, where did that come from?
audit13 said:
Your phone is running the latest ROM as indicated by the nj2.. . . The line about kies, where did that come from?
Click to expand...
Click to collapse
That line came from the Firmware Browser page of the Phone INFO *Samsung* App.
Is it possible to extract all the files I need from my phone and burn them over to my Wife's semi-bricked phone?
Nope, that won't work.
If you backed up everything on her phone, I recommend flashing a custom recovery and then a custom ROM to see what baseband is on the phone. I would not flash anything until that has been confirmed.
Flashing the wrong bootloader and modem file could hard brick the phone.
audit13 said:
Nope, that won't work. . . .If you backed up everything on her phone, I recommend flashing a custom recovery and then a custom ROM to see what baseband is on the phone. I would not flash anything until that has been confirmed. . . .Flashing the wrong bootloader and modem file could hard brick the phone.
Click to expand...
Click to collapse
I am still new here, and although I am a computer programmer, a lot of the terms are foreign to me.... i understood the custom recover and the custom ROM but what is the "baseband" that needs to be determined? Can i get the baseband information from my identical phone?
The baseband or modem is software installed on the phone to control its functionality. The last 4 characters of the baseband/modem should match the last 4 characters of the bootloader.
From your post above, notice the fnj2:
Bootloader Version: I747UCUFNJ2
Baseband Version: I747UCUFNJ2
The bootloader and baseband/modem will change as you upgrade the phone's ROM.
If the soft-bricked phone has the mjb bootloader and you try to flash an lk3 bootloader, this will probably hard-brick the phone because the lk3 bootloader is an older bootloader. The i747 can only be flashed with an identical or newer bootloader which makes the bootloader version a very important piece of information.
audit13 said:
.......The i747 can only be flashed with an identical or newer bootloader which makes the bootloader version a very important piece of information.
Click to expand...
Click to collapse
So why not just flash her phone with the newest bootloader available?
If you want to flash the latest bootloader and modem, you'll have to install a custom recovery first. Also, I am not sure if the modem and bootloader need to be upgraded in release order. I wouldn't think so since I have flashed the Canadian version of the s3 (i.e. i747m) from 4.1.2 to 4.4.2 with no problem.
Always flash the bootloader and modem in the same session before rebooting. Don't flash a modem, reboot, and flash a bootloader as this could also cause a brick.
NOTE: flashing a custom recovery will change the warranty bit from 0 to 1 which will tell a Samsung tech that non-official software was installed on the phone and you may wind up with no recourse against Samsung.
I recommend this if you will not be pursuing the matter further with Samsung: install a custom recovery, boot into recovery, wipe cache, and reboot the phone. Hopefully, clearing the cache will allow the phone to boot as I think it is still stuck in a boot loop.
If the phone still will not boot and you have not back up all of the data, boot to recovery, mount the data partition, connect the phone to a computer, copy off what you need, wipe/format the data and cache, then reboot.
audit13 said:
If you want to flash the latest bootloader and modem, you'll have to install a custom recovery first. ... ... ...
Click to expand...
Click to collapse
I am willing to try it. Do you know a thread i can follow or how i can get some instruction on creating and flashing a custom recovery? Also..... i still have the option to bring the phone over to BestBuy store who is a Samsung tech center. I am not sure if they can do anything other that what I have already tried

Wifi and Bluetooth not working Verizon Galaxy Note 4

I have a used Verizon Galaxy Note 4.
I can't turn on the WIFI or the Bluetooth.
Nothing happens when you tap the buttons for either of these.
So far, I opened it up and detached and reattached the 2 cables for wifi and Bluetooth . This did not resolve the problem.
It also appeared to have a custom firmware on it so I used odin and installed the latest original firmware but it did not solve the problem.
I was wondering if it could be the charging port board or the Bluetooth and wifi cables but I have read that some people had to swap the main board instead.
A couple of other unusual things,
If I go to settings and tap "System Updates" it says Software update is temporarily unavailable "
Also, if I boot to recovery mode it says "Installing system update" and then says "No command" and finally goes to the menu.
What bootloader are you on? Also what is your baseband and currently installed android version? What firmware did you flash? Is your carrier Verizon?
I couldn't log back in here for some reason so I had to use a different account.
Yes it is Verizon
Baseband: N910VVRS2CQC1
Android Version: 6.0.1
Firmware: MMB29M.N910VVRU2CQC1
In bootloader it says:
Odin Mode: (High Speed)
Product Name: SM-N910V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Qualcomm Secure Boot: Enable (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
JediYeti said:
I couldn't log back in here for some reason so I had to use a different account.
Yes it is Verizon
Baseband: N910VVRS2CQC1
Android Version: 6.0.1
Firmware: MMB29M.N910VVRU2CQC1
In bootloader it says:
Odin Mode: (High Speed)
Product Name: SM-N910V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Qualcomm Secure Boot: Enable (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
Click to expand...
Click to collapse
If you have data working, can you download this from the playstore https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and after you install and open it, scroll over to firmware and tell me what it says there. That will tell you what bootloader you are on. You should be on the CPD1 bootloader.
dhplap said:
If you have data working, can you download this from the playstore https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and after you install and open it, scroll over to firmware and tell me what it says there. That will tell you what bootloader you are on. You should be on the CPD1 bootloader.
Click to expand...
Click to collapse
I thought we got an update after pd1 that could he could potentially be on . I realize the bootloader didn't change but it may have gotten renamed to the appropriate firmware . That looks right (his device info) if it were stock updated
mojoswagger1980 said:
I thought we got an update after pd1 that could he could potentially be on . I realize the bootloader didn't change but it may have gotten renamed to the appropriate firmware . That looks right (his device info) if it were stock updated
Click to expand...
Click to collapse
The information he provided doesn't show what bootloader he is on though.
Yetisimo said:
I have a used Verizon Galaxy Note 4.
I can't turn on the WIFI or the Bluetooth.
Nothing happens when you tap the buttons for either of these.
So far, I opened it up and detached and reattached the 2 cables for wifi and Bluetooth . This did not resolve the problem.
It also appeared to have a custom firmware on it so I used odin and installed the latest original firmware but it did not solve the problem.
I was wondering if it could be the charging port board or the Bluetooth and wifi cables but I have read that some people had to swap the main board instead.
A couple of other unusual things,
If I go to settings and tap "System Updates" it says Software update is temporarily unavailable "
Also, if I boot to recovery mode it says "Installing system update" and then says "No command" and finally goes to the menu.
Click to expand...
Click to collapse
Hey man I m not sure how far you've gone but I'd have to suggest a complete factory reset then wipe from recovery then reinstall via Odin (latest firmware down to bpa1 should all be usable if you plan on rooting you need to go back anyway . Either way your info is correct something is wrong with your radio flash either pd1 or bpa1 just to be certain the bug isn't inherint to your current firmware
Thanks. It says Bootloader version N910VVRU2CQC1
Some other things while I'm looking.
PDA VERSION N910VVRU2CQC1 / N910VVRU2CQC1_QC4
CSC VERSION N910VVZW2CQC1
BASEBAND N910VVRS2CQ1
Kernel Version 3.10.40-8025465
[email protected] #1
32 BIT
ROOT EXISTENCE No
JediYeti said:
Thanks. It says Bootloader version N910VVRU2CQC1
Some other things while I'm looking.
PDA VERSION N910VVRU2CQC1 / N910VVRU2CQC1_QC4
CSC VERSION N910VVZW2CQC1
BASEBAND N910VVRS2CQ1
Kernel Version 3.10.40-8025465
[email protected] #1
32 BIT
ROOT EXISTENCE No
Click to expand...
Click to collapse
Well that looks right. I would take mojoswagger1980's advice.
I think that's what I already did unless I'm missing something. I did factory reset and wipe and installed the aforementioned firmware with odin.
I'm new to this.
Are you saying I missed something?
should i try again with a different firmware?
JediYeti said:
I think that's what I already did unless I'm missing something. I did factory reset and wipe and installed the aforementioned firmware with odin.
I'm new to this.
Are you saying I missed something?
should i try again with a different firmware?
Click to expand...
Click to collapse
Could you provide the link of the firmware that you flashed with Odin?
Ok.
Please note that this problem existed before I updated firmware.
I was hoping that updating firmware would fix it.
---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------
The link was
https://www.androidfilehost.com/?fid=745425885120726202
JediYeti said:
Ok.
Please note that this problem existed before I updated firmware.
I was hoping that updating firmware would fix it.
---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------
The link was
https://www.androidfilehost.com/?fid=745425885120726202
Click to expand...
Click to collapse
Can I get the link to the thread that file came from? I checked Paul Pizz's threads and didn't find that exact download file. It seems like that should have worked. Might have been a bad download. I would try again and if that doesn't work I would Odin back to bpa1. That's lollipop but that would give you a fresh start so you could unlock your bootloader if you decided to. That's just my opinion though.
Could you send me links to good files please?
JediYeti said:
Could you send me links to good files please?
Click to expand...
Click to collapse
Try this with Odin https://www.androidfilehost.com/?fid=529152257862721079
I tried it but it didn't fix it. Maybe a hardware problem.
JediYeti said:
I tried it but it didn't fix it. Maybe a hardware problem.
Click to expand...
Click to collapse
are you sure its a verizon note 4? its easy to flash other carriers ROM . please post a pic of your devices about phone screen(s) so we have an idea what firmware we r talking about . you do lose WiFi f you take safe upgrade maybe you got a phone only partially updated . need more info

cant bring back to factory/ get out of factory binary

Samsung Galaxy S8+
Version Info
Model SM-G955U [SS]
PDA FA70_G955UQU4ARE1
PHONE G955USQU4CRE1
P_S/N UNKNOWN
H/W REV1.0
CAL.ID 2017.04.18
UN (NOT SURE IF TO GIVE THIS NUMBER)
MEMORY 64GB
Ran ODIN v3.12.7 and rom that came with it. now stuck in Factory Binary, trying to flash back to factory, any help? Ive tried several roms and either get fails. or sometimes gets abl.elf
in upload mode
[ UPLOAD MODE ]
User press powerkey 7 sec (it does nothing)
--------------------
DDR Vendor :Samsung
SOC_HW_REVISION : 2.1
last_ns :0xff
Generaring Summary
>>General Info
>>DDR Info
>>DCVS Info
>>RPM
>>Trust2one
>>Hypervisor
>>APSS
>>MOdem
Done!
in Downloading custom rom
CARRIER: vzw
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY: Samsung Official
SYSTEM STATUS : oFFICIAL
FRP LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2,1,1,1,1) K3 S4
SECURE DOWNLOAD: ENABLE
DID : 205E53BE31CB
AFTER RUNNING ODIN AND FAILING THERES ANEW RED LINE
SW REV CHECK FAIL : [ABL]FUSED 4 > BINARY 1
I am not an expert, but it sounds like you are trying to flash a bootloader that is an older version than the version 4 on your phone. I don't think you can downgrade the BL version. The fifth character from the end is the BL version. (e.g. G955USQU4CRE1) Also, you may need a newer version of ODIN.
Smithfolk4 said:
I am not an expert, but it sounds like you are trying to flash a bootloader that is an older version than the version 4 on your phone. I don't think you can downgrade the BL version. The fifth character from the end is the BL version. (e.g. G955USQU4CRE1) Also, you may need a newer version of ODIN.
Click to expand...
Click to collapse
so could i just google a "verison 4 BL for s8+" or something along those lines?
Kyles89 said:
so could i just google a "verison 4 BL for s8+" or something along those lines?
Click to expand...
Click to collapse
Yes. There are a lot of software versions available. If you use Updato you can search by model number and service provider (listed as region on Updato. I was able to find one with a version 4 bootloader. Similar to your version, but CRE9 at the end. It is an oreo version. Your phone is a model SM-G-955U when you search there. It might take a long time to download. I have sometimes had luck speeding things up by trying to restart the download. Sometimes it just takes a long time. Be careful when you are flashing if you have any desire to go back to a previous version. I am not sure of the limitations.
Another thing you could try that might be easier for you is to go to the JRKruse ROM thread here - https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206 and use the instructions he has there to install the ROM. There is another rooted ROM that he has that may also work for you. He has instructions on what to do.
Hello, my galaxy s8 is stuck in rpmb provisioned and its boot looping, I can get to download mode, it doesn't say things such as fuse blown etc. How can I get out of the boot loop? Help is appreciated.
Did you find a fix? Im having a very similar problem. I don't see any stock roms with a v4 bootloader. The most recent seems to be a v3.
Fixed it the way Smithfolk said. I was using the combination rom FA70_G955USQU4ARE1 with a V4 bootloader. I used odin v3.13.1 and flashed verizion G955USQU4CRE9 from Sammobile including the bootloader and it fixed my phone.

Error when installing stock OS: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6

Recently I rooted my S9 and installed Lineage OS but I didnt like it and decided to swap back to the stock OS. I used Frija to get the .tar.md5 files for Odin but once I select all the files and hit start the log in Odin loads up to system.img then stops and I get the SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6 error on my phone. Any idea on how to fix this? I'd really appreciate some help as I'm going to be travelling soon and I need my phone for it and I'd prefer not to use Lineage OS. Thanks in advance.
Do you have an At&t branded phone? SM-G960U?
I am having a very similar problem. A customer came in and was having issues with device. I told them to back up, wipe, and update device. That didn't work so I tried a full flash with ODIN. Now I can't get the phone to boot at all and it says, "Secure Check Fail : Modem" and "Unauthorized software visit nearest AT&T blah, blah,..)
I think it is because AT&T has pushed out the latest update(OCT. 18th), but the Odin files are not out yet. According to:
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U
G960USQS7CSI5 is the latest FW. If you google it, there are only four results.
Yep, the problem was the phone was on the latest FW. Newer firmware was just uploaded a few days ago.
I flashed:
G960USQU7CSJ2_G960UOYN7CSJ2_CHA
and now I'm booting again.
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
ma777 said:
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
Click to expand...
Click to collapse
^^^^ this ^^^^
the Odin error is telling you that youre trying to flash a revision of the bootloader than was last installed on the phone. to to sammobile.com/fimrwares and get the one with the correct bootloader for your specific phone and flash that.
also download the firmware with the frija tool or samfirm. trust me, its literallt 5x faster than a direct download from the site. The 5 min it takes to get samfirm up and running is worth it, believe me on that.
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Youdoofus said:
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Click to expand...
Click to collapse
Getting no help was meant I hadn't Posted asking Questions, I read everything ya'll put up and I was able to do it on my own without continuing to ask, so Yeah I did get help here but not by asking only reading what is available
downgrade samsung sm-g570m
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
pol1345 said:
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
Click to expand...
Click to collapse
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
TheMadScientist said:
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
Click to expand...
Click to collapse
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
Like 99.9%. That's what that error is. The bootloader is blocking downgrade
pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
yes, if you get a firmware version matching the one last installed on your device, itll go right thru and boot just fine. Goodlock is finally working on all modules for A10 as well. Maybe we will see more development occur with this shutdown going on. Let us know if you run into any trouble, the error you were getting is totally resolvable!
at the end I give up on it..! my internet 2 slow 4 go downloading & trying rom after rom.! i am from venezuela.
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
I have S20+ running Android 11 with U7 Binary. I tried downgrading to Androi 10 which has Binary U5. Now I have downloaded the Binary U5 file. But in some video, he is telling that you should download the Binary File with the same number as it is currently installed in your phone, which in my case is U7. So? Am I supposed to download U7 Combination Binary file and flash it in order to downgrade to Android 10
OR
Should I flash the U5 Combination File and flash the Android 10 AP, CSC, BL, HOME ???
Someone has Combination file to G960F with bootloader SF (Version 15)?

Categories

Resources