Hello all. I have been at this for a few weeks trying to get it figured out on my own before I posted here, but I am a little lost now. I've been following guides by Chainfire & jrkruse and I (after many attempts and researching threads on here) successfully rooted & unlocked my bootloader (thanks goes out to them, as well as phhussen and everyone else on this forum who has posted results on getting this type of stuff done, I could not have done it without you). Now I'm trying to get safteynet to pass (so I can play pokemon go with root) - this is where I am getting stuck.
I'm trying to use a suhide solution, but I could never get the phone to pass safetynet after I unrooted (so naturally, suhide isn't going to do me much good based off of the instructions, I was just trying it as a last resort to see if I could get it to work anyway with it installed). I think I need a stock rom, but I want to keep my recovery (so that way I can easily flash a rooted rom of MM or any other changes like suhide in there). Is there a way to do this? I can't seem to find any solution other than reformatting the device and flashing a stock image posted by jrkruse of lollipop (then upgrade to marshmellow via Verizon Desktop Agent). Is there no way to just flash a stock version of the OS, but keep the recovery / bootloader unlocked?
TL;DR: I am trying to get a close to stock OS installed (without root) and get safetynet passing. Then I will attempt to follow the suhide tutorial. I want to keep my bootloader unlocked and to keep my recovery. Is this possible to do? I have TWRP (latest version) installed on my Samsung Galaxy S5 G900V.
Yeah just flash in odin all partitions except recovery and sbl aboot and rpm download the firmware you want to be on then use 7 zip file manager and extract tar file and add to and choose all other partitions and make it a tar file and Flash it in Odin
Sent from my SM-G900F using Tapatalk
So I understand what odin is and extracting selective files by using 7zip, but I'm still not quite sure where I would get the stock image of everything. I can't seem to find an unmodified version of the entire MM image. I can only find the lollipop one from jrkruse.
EDIT: If it helps any, I am already on a version of MM with MM firmware.
Pd1 firmware is available on Sammobile. Com
Sent from my SM-G900F using Tapatalk
---------- Post added at 04:11 PM ---------- Previous post was at 04:11 PM ----------
Pd1 mm firmware
Sent from my SM-G900F using Tapatalk
[email protected] said:
Pd1 firmware is available on Sammobile. Com
Sent from my SM-G900F using Tapatalk
---------- Post added at 04:11 PM ---------- Previous post was at 04:11 PM ----------
Pd1 mm firmware
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Does it matter that I am PBF4? I'm assuming PD1 is lollipop firmware? I'm looking for Marshmellow. I could flash in Odin the lollipop stock everything right now. But then since I couldn't find a stock marshmellow image (at the moment), I would be stuck on lollipop.
Pd1 is marshmallow firmware
Sent from my SM-G900F using Tapatalk
I downloaded the PF4 version from sammobile.com (that is the current version I have on my phone now). Thanks for the link for that site. The way I am understanding you is just to take that compressed file, extract all but aboot.mbn, rpm.mbn, and sbl1.mbn, and then take those extracted files and create a .tar file; then flash with Odin - is this correct?
Yes that is true
Sent from my SM-G900F using Tapatalk
When I did that nothing changed (although odin said it flashed everything successfully in the logs, but all my apps and SuperSU remained). I wiped my system next time and flashed everything and this time TWRP came up and said that it could not stop the stock ROM from deleting TWRP. I thought I was in the clear, but so far the first attempt has left the phone on the Verizon checkmark screen. I restored my old image and am trying one more time. I'm not sure if it is supposed to take long? I flashed a .tar with the following in it:
- boot.img
- cache.img.ext4
- modem.bin
- NON-HLOS.bin
- sdi.mbn
- system.img.ext4
- tz.mbn
Before I flashed this .tar, I wiped the System, ARK=dalvik/cache, internal storage, and cache if that helps any.
You have to do a wipe after flash
Sent from my SM-G900F using Tapatalk
Related
I made these odin flashable firmwares for those who need them. This is only the stock firmware for Lollipop 5.01 build OB7. (NO system or data partitions) If you need to flash the stock OB7 firmwares then this will do that for you. This will not wipe your system or data.
Once you flash the "OB7-FW.tar.md5" you must reroot and flash a custom recovery if you want to flash custom roms etc. Simply odin flash cf-auto-root and the latest recovery by TWRP and you'll be back in business.
The OB7-modem.tar.md5 requires no extra steps... it's just the modem.
I have tested these packages on my Note 4 running OB7 firmware. Note: If you are on OE1 firmware, you will NOT be able to flash this OB7 firmware successfully due to new security measures in the OE1 bootloader.
OB7-FW.tar.md5 This tar package includes all of the stock OB7 firmware including kernel,modem, recovery, bootloader, etc. Please flash this in odin on your PC ONLY!
OB7-modem.tar.md5 This tar package includes only the modem and HLOS patch. Can be flashed with odin on your pc and also mobile odin.
Gonna try
tx_dbs_tx said:
I made these odin flashable firmwares for those who need them. They are the stock firmware for Lollipop 5.01 build OB7. If you need to go back to the OB7 firmwares then give this a try. This will not wipe your system or data.
Once you flash the "OB7-FW.tar.md5" you must reroot and flash a custom recovery if you want to flash custom roms etc. Simply odin flash cf-auto-root and the latest recovery by TWRP and you'll be back in business. The OB7-modem.tar.md5 requires no extra steps... it's just the modem.
I have tested these packages on my Note 4 running OB7 firmware. OE1 bootloader/recovery may not allow flashing back to older firmware. (I haven't tested with OE1 firmware) Please report your success or failure when flashing this over your OE1 firmware.
OB7-FW.tar.md5 This tar package includes all of the stock OB7 firmware including kernel,modem, recovery, bootloader, etc. Please flash this in odin on your PC ONLY!
OB7-modem.tar.md5 This tar package includes only the modem and HLOS patch. Can be flashed with odin on your pc and also mobile odin.
Click to expand...
Click to collapse
I just tried this and I got the following error:
UDC START
SW RED CHECK FAIL : [tz]Fused 2 > Binary 1
I am using Odin 3.07, running Windows 7.
tx_dbs_tx said:
I made these odin flashable firmwares for those who need them. They are the stock firmware for Lollipop 5.01 build OB7. If you need to go back to the OB7 firmwares then give this a try. This will not wipe your system or data.
Once you flash the "OB7-FW.tar.md5" you must reroot and flash a custom recovery if you want to flash custom roms etc. Simply odin flash cf-auto-root and the latest recovery by TWRP and you'll be back in business. The OB7-modem.tar.md5 requires no extra steps... it's just the modem.
I have tested these packages on my Note 4 running OB7 firmware. OE1 bootloader/recovery may not allow flashing back to older firmware. (I haven't tested with OE1 firmware) Please report your success or failure when flashing this over your OE1 firmware.
OB7-FW.tar.md5 This tar package includes all of the stock OB7 firmware including kernel,modem, recovery, bootloader, etc. Please flash this in odin on your PC ONLY!
OB7-modem.tar.md5 This tar package includes only the modem and HLOS patch. Can be flashed with odin on your pc and also mobile odin.
Click to expand...
Click to collapse
ive been searching but can you help me put stock 0e1 recovery back on my phone i forgot to factory data reset after i updated to 0e1 and rerooted and now my phone is super buggy and i think its because i didnt wipe on stock recovery which usually fixes my problems. thanks if you can help or not. ive wiped on twrp of course but my stock rooted 0e1 rom just isnt right idk but like i said the stock recovery to me really wipes evrything. ive tried aosp roms but there even more buggy can you please help thanks
No one has it yet
Right. There is no official tar ball available for OE1 firmware. OTA is the only way right now and nobody has pulled and uploaded the update zip for OE1. Im afraid you're gonna have to try the OB7 official rom tar or else you're stuck until a tar pops up somewhere. And that may not happen for OE1.
PeteSeiler2010 said:
I just tried this and I got the following error:
UDC START
SW RED CHECK FAIL : [tz]Fused 2 > Binary 1
I am using Odin 3.07, running Windows 7.
Click to expand...
Click to collapse
Thanks for the report. Which software version are you currently on? Extension OB7 or OE1 ??? You must be on OE1 because it flashed successfully on my OB7 software. I will upload another version for you to test.
Yes, I am on OE1, I will gladly test for you. Just keep me posted.
So just to clarify, if I am on KK, I can ODIN this then cf auto root then TWRP? And don't take the update to OE1 because it's not worth it?
Sent from my SM-N910P using XDA Free mobile app
beezar said:
So just to clarify, if I am on KK, I can ODIN this then cf auto root then TWRP? And don't take the update to OE1 because it's not worth it?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Ok, don't mess with this, it's for a different purpose. Read the OP in @tx_dbs_tx 's hybrid X 2.2 rom thread here:
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully as there is a VERY specific procedure (it's easy) you MUST follow to move up to lollipop.
Stock tar in the OP here:
http://forum.xda-developers.com/showthread.php?t=3056478
If you'd rather have a stock rom instead of hybrid x download the stock tar and follow tx's instructions to the T in his Hybrid-X OP before flashing it or any lollipop based rom.
Remember, you MUST flash the stock OB7 tar BEFORE flashing any lollipop rom.
EDIT: If you decide to go stock, do not take the ota. Once you cf-auto-root & odin twrp you won't have to worry about it anymore. The same with Hybrid-X. Once you flash that no more OTA worries.
Did u find the hidden image ??
I'm not going to pursue the OE1 secured bootloader thing. We will have to wait for an official tar ball and rebuild roms from it. Until then I'm staying on my OB7 rom.
I dont quit but thanks for your efforts
pbedard said:
I dont quit but thanks for your efforts
Click to expand...
Click to collapse
Have at it... Keep us posted.
Meh sourcecode is out
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
gus_zernial said:
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
Click to expand...
Click to collapse
Flash Stock Rom via ODIN.
Joku1981 said:
Flash Stock Rom via ODIN.
Click to expand...
Click to collapse
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Check this thread http://forum.xda-developers.com/showthread.php?t=3335065 I don't know if you have experience with Odin process. Google it preferably look at YouTube video, if you feel shaky on Odin concepts.
Sent from my SM-G935F using Tapatalk
gus_zernial said:
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Click to expand...
Click to collapse
1. "I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC." Reflash this FILE via ODIN coz you flashed wrong one and boot in it. Go to next step if doesn't work.
2. Flash Stock ROM via ODIN. SM-G935FD use the same firmwares that SM-G935F.
Careful with ODIN. Make sure you are running on the latest version, as I myself has problems using it for the Galaxy S7 Edge on an offer version
Sent from my SM-G935F using Tapatalk
maybe my question will be weird lol...how can i sofbrick a s7 g930p to be exact and then i can just unbrick flashing the U firmware? thanks.
Hi everyone,
I am running stock G920FXXU4DPIL (6.0.1) and I want to go back to stock G920FXXU3COI9 (5.1.1).
When I try to flash G920FXXU3COI9 with Odin, it fails at sboot.bin with error "sw rev check fail device 4 binary 3", which is quite normal because Samsung prevents flashing older bootloader over newer bootloader.
So I extracted the content of the stock firmware, removed sboot.bin, cm.bin, modem.bin and repacked a new .tar using android unified toolkit.
Then I flashed the resulting file with Odin.
Flashing worked but now I am stuck at Samsung logo. I cannot enter recovery either.
Only way to soft unbrick the phone is flash stock G920FXXU4DPIL again.
Why ??
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
qasim799 said:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
Click to expand...
Click to collapse
So do you know where I can find SM-G920F engineering bootloader?
I have searched hundreds of pages and it's nowhere to be found :'(
Thanks!
qasim799 said:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
Click to expand...
Click to collapse
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
OK i managed to find a combination firmware:
COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02
However there is a pit file inside. Does this mean I have to repartition the device?
Seems tricky since I want to be able to flash a stock firmware afterwards.
Can I extract and flash only sboot.bin from combination firmware?
From my understanding, once I have the engineering bootloader, it will let me flash an older one...
couitchy said:
OK i managed to find a combination firmware:
COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02
However there is a pit file inside. Does this mean I have to repartition the device?
Seems tricky since I want to be able to flash a stock firmware afterwards.
Can I extract and flash only sboot.bin from combination firmware?
From my understanding, once I have the engineering bootloader, it will let me flash an older one...
Click to expand...
Click to collapse
there is no problem with it. You can go back to any MM or N firmware.
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
ilDuceo said:
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
Click to expand...
Click to collapse
Maybe I"m fed up from N grace ux as before N was released i was using note 7 grace ux port. Lollipop is so responsive if you used it then you can feel that is pretty obvious.
It worked!
I flashed COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658 768_QB10183466_REV02 to get the engineering bootloader rev4.
Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME but it failed at sboot.bin device 4 binary 3 which prooves that even engineering bootloader prevents downgrade.
Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME without sboot.bin, cm.bin and modem.bin => it worked (not stuck at Samsung logo anymore).
My fingerprint scanner is not working but baseband is here (IMEI ok).
So I have kind of a "hybrid Lollipop" G920FXXU3COI9_G920FXXU4BPF1 but that's ok for what I wanted to do
EDIT: CF-Auto-Root-zeroflte-zerofltexx-smg920f doesn't seem to work when using engineering bootloader => I guess I'll have to find a new way to root the phone :-S
so any good way to do it ? because nougat is bad
Finally I got it rooted using TWRP and flashing SuperSU
So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):
(my guess is it will also work with Nougat)
1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free
2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)
3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin
4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files
5. Flash combination firmware with Odin
6. Let it boot once and then go back to Odin
7. Flash repacked stock firmware with Odin
Additional steps to get root:
8. Download SuperSU (flashable zip)
9. Download TWRP
10. Flash TWRP with Odin
11. Enter recovery (TWRP) and flash SuperSU
Voilà !
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
Okay I downgraded my S6 edge sucessfully to 5.1.1!
I missed that old UI soo mucchh thanks for your guidance
halloo7 said:
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
Click to expand...
Click to collapse
Actually there is a reason Samsung doesn't want you to downgrade bootloader: I noticed that every bootloader update usually comes with modem/baseband update, which implies some modifications in the /efs partition as well. An older bootloader would then be unable to read new /efs partition, resulting in a null IMEI. That is why the correct way to downgrade is to flash the old system files but keeping current modem/baseband.
The real stupid thing here is that the stock MM bootloader prevents stock LP image to boot. Fortunately the engineering bootloader can bypass this
halloo7 said:
Okay I downgraded my S6 edge sucessfully to 5.1.1!
I missed that old UI soo mucchh thanks for your guidance
Click to expand...
Click to collapse
Cool !
:good:
Sometimes I get a Kernel Problem. The phone crashes randomly after the downgrade. How to fix this?
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
qasim799 said:
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
Click to expand...
Click to collapse
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying:
couitchy said:
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying:
Click to expand...
Click to collapse
i flashed latest cm.bin from nougat it boots up but fingerprint sensor is still not working and with engineering bootloader, the rom crashes at certain apps and get really snapier when unlocking phone with pin or pattern. So i am back to nougat i gave up downgrading almost downloaded whole sammobile 5.1.1 firmwares non of them is having a B:5 K:2 S:2 bootloader I was expecting such rom because on Verizon S6 , there is a 5.1.1 firmware that successfully allows to get down with same latest sboot.bin and i still believe there is a firmware like that for our model too but it is really hard to find it.
couitchy said:
Finally I got it rooted using TWRP and flashing SuperSU
So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):
(my guess is it will also work with Nougat)
1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free
2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)
3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin
4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files
5. Flash combination firmware with Odin
6. Let it boot once and then go back to Odin
7. Flash repacked stock firmware with Odin
Additional steps to get root:
8. Download SuperSU (flashable zip)
9. Download TWRP
10. Flash TWRP with Odin
11. Enter recovery (TWRP) and flash SuperSU
Voilà !
Click to expand...
Click to collapse
I've tried flashing the firmware without the binfiles but It just gets stuck on file analysis.
Hi XDA community, i want try to downgrade in my A310f from Android 6.0.1 to 5.1.1. It's possible? I try to download the 5.1.1 from Sammobile, but when i flash the firmware with odin i get the error "SW Rev Check Fail" in my phone and "md5 error" from odin.. there are some method?
MMBB29K.A310FXXU3BQC2 is my model. Tell me please here
allenbtc said:
MMBB29K.A310FXXU3BQC2 is my model. Tell me please here
Click to expand...
Click to collapse
If your bootloader also is upgraded to A310FXXU3 then it won't be possible to downgrade to 5.1.1 through odin.
Maybe with a modified package without cm.bin, modem.bin, sboot.bin. Otherwise, make it flashable and use twrp.
With Odin you'll only be able to downgrade to the latest 6.0.1 which is also A310FXXU3.
how i can flash with twrp?
---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------
tys0n said:
If your bootloader also is upgraded to A310FXXU3 then it won't be possible to downgrade to 5.1.1 through odin.
Maybe with a modified package without cm.bin, modem.bin, sboot.bin. Otherwise, make it flashable and use twrp.
With Odin you'll only be able to downgrade to the latest 6.0.1 which is also A310FXXU3.
Click to expand...
Click to collapse
how i can flash with twrp?
tys0n said:
If your bootloader also is upgraded to A310FXXU3 then it won't be possible to downgrade to 5.1.1 through odin.
Maybe with a modified package without cm.bin, modem.bin, sboot.bin. Otherwise, make it flashable and use twrp.
With Odin you'll only be able to downgrade to the latest 6.0.1 which is also A310FXXU3.
Click to expand...
Click to collapse
I can confirm this method is working, I have successfully downgraded an A3 2016 from A310FXXU3BQD2 to A310FXXU2BQA3.
I used the Tar tool from this thread with all the files from the update I wanted to downgrade to, except sboot.bin, cm.bin and modem.bin. It's very important to NOT copy those files to the tool folder because otherwise your phone will be laggy and SIM unusable (if you use the old modem) or you will not be able to flash like with the original tar (if you use old sboot or cm).
So after I ran the batch file, I did a wipe data/factory reset using original recovery and then I flashed the "all files" tar the tool created using Odin in AP (only Auto Reboot and F. reset time checked) and the phone in download mode, and It worked like a charm.
With this method you can likely have any old update flashed while keeping the latest secure bootloader, cm and modem. (Notice that after the downgrade, the phone cannot find any new updates, maybe it's related to the bootloader being the latest or the fact I only downgraded to the previous update...)
dealth645 said:
I can confirm this method is working, I have successfully downgraded an A3 2016 from A310FXXU3BQD2 to A310FXXU2BQA3.
I used the Tar tool from this thread with all the files from the update I wanted to downgrade to, except sboot.bin, cm.bin and modem.bin. It's very important to NOT copy those files to the tool folder because otherwise your phone will be laggy and SIM unusable (if you use the old modem) or you will not be able to flash like with the original tar (if you use old sboot or cm).
So after I ran the batch file, I did a wipe data/factory reset using original recovery and then I flashed the "all files" tar the tool created using Odin in AP (only Auto Reboot and F. reset time checked) and the phone in download mode, and It worked like a charm.
With this method you can likely have any old update flashed while keeping the latest secure bootloader, cm and modem. (Notice that after the downgrade, the phone cannot find any new updates, maybe it's related to the bootloader being the latest or the fact I only downgraded to the previous update...)
Click to expand...
Click to collapse
Thanks for confirming. I've never tried it myself but I figured those bins are the U1/U2/U3 binary files that are protected for downgrade, so it should probably work without them
Now we know how to easily downgrade without errors.
Downgrade
Hello,
With my sm-a310f I downgraded from Nougat to Marchmallow but could not get back to Lollipop.
I used TWRP and Odin.
I saw that there were solutions but they are not universal. Can someone point me?
Thank you
menuisier3 said:
Hello,
With my sm-a310f I downgraded from Nougat to Marchmallow but could not get back to Lollipop.
I used TWRP and Odin.
I saw that there were solutions but they are not universal. Can someone point me?
Thank you
Click to expand...
Click to collapse
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
flash combination rom before flash full 4 file stock rom 5.1 , u can downgrade your phone.
Tanle11 said:
flash combination rom before flash full 4 file stock rom 5.1 , u can downgrade your phone.
Click to expand...
Click to collapse
No! You can't downgrade bootloader even if you use a 4 file repair firmware.
As far as I am aware of, this is the only possible way to downgrade to 5.1.1 if you are on new bootloader/modem (tested by me - works fine, I am on the newer bootloader/modem combo) :
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
(consider this however ONLY if you are willing to trade 5.1.1 for the warranty as you would need to flash TWRP in the process first)
Null baseband, imei, etc. Tried flashing with 3 different roms via odin. I cannot connect it into abd mode when powered on, only via odin, otherwise I would try samsung tool pro or samfix.
download mode:
current binary samsung official
system status custom
knox warranty void 0
When booting it shows "custom" at the bottom with an unlocked padlock. despite searching for original firmware. I have flashed back to the nl1 (4.4.2) but I still get the custom logo, even after ticking nand erase and re partition while adding a pit file. Perhaps I should try to downgrade to the NC2 or upgrading to a new original? Does anyone have a link to the newest original? I searched for hrs. This phone has to be one of the least supported models out there. So far I have flahsed: n900aucudnL1, n900aucueoc2, and lastly N900AUCSEOC3_CL4335446_QB11749532_REV03. I have flashed a couple modem files as well.
Flashing a new original probably won't work as this is an efs issue. I thought about rooting and flashing a custom rom since sometimes they can restore the efs. This phone has many steps to root from the posts I found so if there's an update let me know, if not, I'll have to follow suit.
Any helpful ideas on repairing this would be appreciated. Thanks.
Root using Towelroot
Sent from my SM-N935F using Tapatalk
---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------
What is your build number? If you are on Kitkat you can use towelroot and it doesnt involve alot of steps you load the apk click it and root is installed. Make sure you have busybox installed before installing towelroor. I would then find the correct version of Safestrap recovery.
Sent from my SM-N935F using Tapatalk
This is not the forum for your model .
Suggest the AT&T forum .
https://forum.xda-developers.com/galaxy-note-3