Related
How might one apply the DJ05 update without using Odin v3?
Clearly the ROM and Kernel can be updated through CWM, but all searchable info seems to indicate that the modem file can only be altered via Odin on M$ Windoze. What is the methodology behind applying this kind of change using only tools available on a Linux platform?
Can I just overwrite a file on the Fascinate via adb?
cheers
I have only ever heard of modem.bin being flashed via Odin. I could be wrong, but I think it occupies its own partition, hence the need to actually flash rather than copy an individual file.
You can use redbend_ua to flash without Odin, but I recall (perhaps incorrectly) reading in IRC that redbend doesn't work for modem flashes in practice, at least not yet.
Hopefully someone can give more authoritative info, but I think you are stuck with Odin for good reasons. Just be nice to one of your friends with a PC. Don't have any? Shame! Windows users need love too ya know.
Swyped w/ XDA App. When in doubt, mumble.
Google search keyword: heimdall
Sent from my SCH-I500 using XDA App
Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
Awesome. That's a good question, why don't we just speak in terms of Heimdall in general... and use that instead? Strangely more soothing to say anyway, like "goos fraba"
You might find post 3 here useful as well.
That thread Soba49 posted is about 60 pages now, but reading through it all will give you a lot of good info on how it works. About page 56 or 57, you will see some specific questions I posed regarding flashing DJ05 modem.bin onto the Fascinate. It's almost too simple to use, so best to understand it as this is also the tool that will be saving your arse if you 'almost' brick your phone.
Heimdall actually emulates Odin in some areas & Kies in others and aims to eventually do more than either of those tools, w/o all the buggy Samsung coding. I believe the modem.bin is flashed using Kies methodology, FWIW.
So, I've been searching all over this forum and through the 60 pages of the Heimdall thread, but can't find an answer to this simple question - how do I just flash DJ05 onto my fascinate from OSX 10.6? When I try to connect in download mode and turn on Heimdall frontend, I just get "no compatible device connected" Do I need to flash bootloaders too or some other complicated stuff? Or am I just missing something easy?
SupraLance - What happened when you commanded: "heimdall flash --verbose --modem modem.bin"?
That command flashed the new modem for me. I am running DJ05 now and my phone has never been violated by a Windows device, lol.
I just re-read a bit of that thread regarding OSX, and it seems that Samsung released these phones with a crappy secondary boot loader. It will communicate with Linux and Windows, but not OSX. The only way around this is to flash a fixed boot loader through Linux or Windows, then you can use OSX from there out. Big problem is the only fixed boot loader verified to work with Heimdall & OSX is for the International Galaxy S. You need one specific for the Fascinate.
So this leaves American OSX users hoping that Samsung fixed this in the 2.2 Froyo code they have released. Heimdall & Odin cannot be made to work on OSX without it and boot loaders are not something you want to experiment with. Messing with the boot loader = quickest way to truly brick your phone.
If I was at your computer trying to do this, I would set up a dual-boot on your Mac with Ubuntu (completely free and similar to OSX interface) and do it through Ubuntu.
Heimdall Success!
fragmented post
Code
fragmented post
Notes on Code.
fragmented post
Next step.
fragmented post
fragmented post
Heimdall Success!
Installed Heimdall 1.1.0 for Debian.
http://www.glassechidna.com.au/products/heimdall/
Flashed modem using:
Code:
heimdall flash --verbose --modem modem.bin
Making sure that SF is in DL mode and the current directory contains "modem.bin" file.
Then flash ROM (and Kernel) via CWM.
Additional possibly helpful info here:
http://mobiletech.knguyentu.com/2010/12/fascinate-rom-dj05-and-beyond-all-you.html
Cheers
Hey there, folks. I'm a noob that managed to get himself into a bind (imagine that). I bought the SGH-i437 from Cricket.
I successfully rooted the phone and attempted several varieties of backups - each of dubious utility since I had no idea what I was doing. I can't use them now, for reasons unclear to me, but certainly due to user error. Not knowing this, and continuing on a foolish trajectory, I went on and flashed CM11-20140829NIGHTLY. It's been working very, very well.
I would have been trouble free, in the clear and happy, but I moved to London and had to change my Cricket service to a local carrier. To do that, I have to unlock the SIM (or rather, network unlock). I have an unlock code. When I go to unlock it, it doesn't work because in CM11 you can't access the debugging screen from the dial pad (those were the instructions sent to me). The kind people helping me unlock my phone suggested I flash back to stock ROM. Then, they tell me, I can follow the instructions. This is where my story stops.
I have a macbook, so I'm using JODIN, and I've installed heimdall on my macbook. I connect, I put the .tar file that I found on the internets into PDA and click start. J ODIN says it needs to find me a PIT file, and it tries but doesn't manage to find one. http: / / pastebin . com / 5DpJjyk8 - Hopefully that will link to the incredible string of code and whatnot generated by JODIN. I put in spaces because XDA won't let me post URLs.
I'm not sure what I need to do, now. Am I supposed to be out there looking for a mysterious PIT file, or doing something different with JODIN? I eagerly await returning to the crappy stock ROM, unlocking the SIM, then returning to the sweet blissful CM11. Please, please can you help me?
SGH-i437
CM11 - JB 4.4.4
(original stock was JB 4.1.2)
Still confusing...
When searching for ".pit file for SGH-i437" I found a thread where a guy with an S4 flashed S3 stuff and was having problems. People directed him to KIES, which I've been trying. Only problem is that Kies doesn't recognize my phone with CM11. So I'm still out to dry, here, with a functioning phone locked to a US carrier. BOOOOO!!!!!! I'm about ready to gravity test this phone over a London high street.
days of research - nothing
I can't find any other discussion of people having a similar problem with ODIN/JODIN! I can't flash my stock ROM because JODIN can't find the PIT file. I'm genuinely troubled by this - please help if you have any notion of what to do!!!
I can't seem to figure out how to downgrade back to a stock ROM after installing this:
lineage-14.1-20170331-UNOFFICIAL-trltetmo.zip (can't post link yet)
I believe it's the Nougat 7.1.1
I want to downgrade to 6.0.1 or 5.1.1
One message I see is "Recovery is not Seandroid Enforcing". Seems like all fixes suggest reinstalling stock ROM, which I'm trying to do, but can't.
Phone is a Samsung Note 4 SM-N910W8 (Rogers)
What's your steps to downgrade to 6.0.1? Did you download Rogers ROM and ODIN it(google is your best friend)?
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
If ODIN starts and stops immediately, you have a different problem. Did you install the Samsung Android USB driver properly. Anyway, you have a software issue, fix it first. I suggest you watch a few related video on youtube.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
Currently no response.
In the freezer... I'm waiting.
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
SUREFACE said:
It Sounds that You have a "FULL BRICK" !
The Only way, that REALY can Help is a "USB-JIG".
And Hope, that this One Brings Your Device back in Download-Mode!
You can Build Your Own One, see here : https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
Or Buy One! See Here: https://www.amazon.de/Download-Repair-Stecker-Samsung-Galaxy/dp/B004VN5ZYS
And You need a REPAIR ROM ! Take A Look here for Your Variant : https://mega.nz/#F!Ax0gxSzZ!Qq_eJWX678bQHBhn7BHNDQ
Hope that this will Work!
Click to expand...
Click to collapse
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Is your phone booting up and functioning? If it is, why are you talking about debrick? I'm assuming that you're "new" to all this. I suggest you read up(especially the stickies) and be comfortable before you go further.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
ziggy1971 said:
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Click to expand...
Click to collapse
No, it doesn't boot up at all now.
I know I initially said "I" installed the custom ROM, I didn't, I bought it that way. The previous owner won't do anything to help. The only thing he did was provide a link to the ROM he had installed, nothing more, not even the tutorial related to it, I found that on my own (wait, he's made it more than clear how incompetent/ignorant I am as a person).
I've been searching and reading for 3 days straight now. Getting to the point again where I accept defeat, assume the money lost.
Moving on... I've rooted other phones before without issues.
I follow a tutorial on how to downgrade to a stock ROM.
http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
Odin stops with various errors.
I could still boot device into TWRP-3.1.0
Reflashed LineageOS 14.1 ROM from SD to get it working again.
LineageOS 14.1 ROM would boot up, run for almost a minute and a half and shut down.
Pull battery, reboot into LineageOS 14.1 ROM, same thing.
Run Odin, connect device to computer, try to flash stock ROM, error again (different one). Somehow, it says "There is no PIT partition"
I followed this tutorial: https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Odin says FAIL.
Now, it does NOTHING.
I follow this tutorial: Debrick here: https://forum.xda-developers.com/not...k-img-t3488114
Yes, the whole freezer thing overnight.
I have the latest USB drivers installed.
When I connected to the PC, an error popped up saying "...drivers not installed properly..." so I let Windows Update install the correct drivers.
I can connect to the PC now, press the power button for more than 10 seconds, eventually a popup message says "USB Device Not Recognized by Windows"
I've tried the following stock ROMs, 4.4.4, 5.1.1. I finally managed to download 6.0.1, but haven't been able to try it.
All I can say is that if you can boot into TWRP(I assumed you install the N910T version), then your phone is not bricked. All these "debricking" you're doing is potentially harming than fixing.
You assume the risk, when you buy 2nd hand. But based on what you're saying, it sounds like it may also have hardware issues(I don't think software will fix). Was it working when you got it? If you can return it, I suggest you do.
Another pc or windows version may work
A more trustworthy guide on using ODIN:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
mnopy said:
Another pc or windows version may work
Click to expand...
Click to collapse
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
ziggy1971 said:
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
Click to expand...
Click to collapse
QualcommDrv
this is the Qualcomm Drivers(x86 and x64, choose your system's version and install) .
Without that your pc will not recognize your phone.
Uninstall everything related to samsung from your pc.
Kies, smart link, usb drivers. Use revo-unistaller for this to be sure nothing have left behind.
Go to control panel>system>device manager and remove anything that is related to your phone . If prompt delete drivers associated with that, say yes. Reboot your pc
Have saved QualcommDrv, samsung usb drivers and Odin. These are the tools you are going to need and must have.
after uninstall everything, unzip and install QualcommDrv.
Take off your battery, press power buton for 10 sec . Connect the phone to pc (without battery)
QualcommDrv will install the correct drivers for your phone. After that If in devices and printers it is recognized as Qualcomm 8084 .... its ok to proceed . if not , check again drivers and their installation
If windows says device drivers are not correctly installed and prompt to download and install, stop and cancel it.
IT will replace the QualcommDrv and you will not be able to see your phone correctly.
You need to keep QualcommDrv installed. When this is done and you are sure its correct and working, unplug your phone and install Samsung usb drivers. Reboot pc
unzip odin in desktop (or where ever its easy to access).
with your phone freezed and battery charged try to go to download mode. If succeed, connect to pc and with odin try to flash stock rom. If not ......
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
That what you need to have correct and working in order to START. THIS IS ONLY THE FIRST STEP
YOU HAVE TO UNDERSTAND
this is a hardware failure of the motherboard and will never will be completely fixed. These steps will only help you resurrect your phone and maybe give you the chance to be able to use it again.
It has nothing to do with software that failed to install. It was just the result and not the real problem, which is a diffect motherboard like thousand others. Sadly this is a common problem with Note 4 that happened to many users.
I have the same problem and I also bought it second hand knowing its problematic but not how much.
After that I realized the problem and the solutions to it. Every one of us is having a slightly different behavior of the phone.
I, for example cannt use the phone without the ext sdcard with unbrick image in it. When I take it out phone, will not start, reboot , do nothing.With the card in it its working almost perfect.
So have patience and read and search to know what you are dealing with.
Good luck
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
ziggy1971 said:
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
Click to expand...
Click to collapse
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
dicksteele said:
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
Click to expand...
Click to collapse
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
ziggy1971 said:
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
Click to expand...
Click to collapse
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
dicksteele said:
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
Click to expand...
Click to collapse
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
ziggy1971 said:
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
Click to expand...
Click to collapse
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
logosA said:
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
Click to expand...
Click to collapse
Those are good.
Some more are here
https://forum.xda-developers.com/general/xda-university
https://forum.xda-developers.com/chef-central/android
https://forum.xda-developers.com/showthread.php?t=1272270
https://forum.xda-developers.com/showthread.php?t=2069130
https://forum.xda-developers.com/showpost.php?p=5626301&postcount=4
https://forum.xda-developers.com/showthread.php?t=1590192
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
There are essentially two ways to do what you want.
Use the unpack tool above, extract the system.img from a Stock ROM
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
I get my stock ROMs from here
http://updato.com/firmware-archive-select-model?q=n910c&rpp=15&order=date&dir=desc
Remove the bloatware or apps you don't want.
Use the app same app that you used to extract the system.img to repack it.
Use the https://forum.xda-developers.com/chef-central/android/tool-afaneh-tar-kitchen-t3603649
to build a tar and flash with ODIN.
Second option use a kitchen. I'm testing the one below today to see if it works.
https://forum.xda-developers.com/ch...0-0-deluxe-kitchen-graphic-interface-t3579100
SuperR works great. But you need a Linux environment to run it.
I use virtualbox on my Win10 machine. I use premade images from here
http://www.osboxes.org/virtualbox-images/
Personally I use the Ultimate Edition.
Or use cygwin. I gave you plenty of links to learn how that works. It's a pain that's why I use virtualbox.
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
jumam21 said:
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
Click to expand...
Click to collapse
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Re
rudimenta said:
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
I mean How can I make ADB enable file from combination File.
jumam21 said:
I mean How can I make ADB enable file from combination File.
Click to expand...
Click to collapse
Exynos? I hope so because there is no sboot file for snapdragon ?
You don't need the factory boot for exynos. Just enable OEM unlocking
partcyborg said:
Exynos? I hope so because there is no sboot file for snapdragon
You don't need the factory boot for exynos. Just enable OEM unlocking
Click to expand...
Click to collapse
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
noidodroid said:
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
Click to expand...
Click to collapse
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
partcyborg said:
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
Click to expand...
Click to collapse
This has also been told to me by a mod ive spoke with time to time but the others really don't seem to mind as long as it is to help others and such. Which is what i do when i put up a manual tutorial. I usually do all by freestyling (no looking into anything unless really needed). If the same PartyCyborg from Android Forum Community. We don't know each other but I have used your work past and present and had a swell time finding through archives but this i enjoy. Very cool work man esp the last bit i asked you about on i believe an older Samsung 2014? device to action with your Rom's latest. Alright back to AndroidForum Community I have explained my whole outlook & debated the whole FRP issue with phones today. It's a challenge and it's helpful to those that aren't running masses of stolen phones through boxes (hey even stolen hardware once seized returns back to the community and has to be delt with.. i as do others get some devices from LEA property) and also that huge majority of people who quickly create accounts without jotting down and remembering info. Then i could go back into bulk onto stores who legally obtain (auction for example) then have to either a) find a way to fix frp and or 2) resell these devices 3) part out as google locked LB's etc. Google Lock and FRP in general is a VERY good thing IMHO. I want to see us make a move to more secure reliable FRP locks such as iClouds. We also have a security section here on XDA where all sorts of the latter and even deeper is discussed. Win Win for Security overall if you think about it all and take it in. I've said this before in other Areas of the internet I am from and I will say it again in similar words "they build it, we bypass it, they improve it.......(reversing.. updating.. learning.. phase) and the process continues.". We are improving security on everything be it my old days email filters (especially the old ways) or be it Google Lock Security & FRP and the countless other companies small and big across the globe with related protection put in place. Don't put a dark hat on it all.. at least just yet. -not directed toward you by any means or anyone else.. just my quickie worth of that whole 2 cents for what its worth.
Hello,
I’ve been browsing these forums endlessly in an effort to find an answer to my problem, however I feel like I am at my wit’s end so I am trying to find anyone that could help me here.
I have Samsung A5 (2016) with Android 7.0 and October 1, 2018 Security patch level.
I’m trying to flash an older version of 6.0 Android with an older Security update level, however I am facing the “SW REV CHECK FAIL ERROR” - from what I understand I cannot downgrade to a version that has lower security patch. Is there ANY way around this besides trying to flash 6.0 with newer security patch?
I’ve been browsing here a lot and found a few mentions of this being possible by unpacking the .tar.md5 file and removing all files ending with .bin and packing it up as .tar.md5 again, however my attempts at this have failed - Odin will still give me “Fail” and I will still get the same SW REV CHECK FAIL error. I’ve found a post saying that removing the .bin files from the .tar.md5 file that I want to flash and replacing them with newer .bin files should work as to trick the bootloader to think the version is the same as my current one and essentially leaving the newer version of bootloader still on my phone but with downgraded android version of a lower sec. patch. I’m a bit skeptical about this approach and I fear it will not work - I am afraid to try.
I have been trying to find an anwser for days - any help will be truly appreciated! ^^
Armageddon8 said:
Hello,
I’ve been browsing these forums endlessly in an effort to find an answer to my problem, however I feel like I am at my wit’s end so I am trying to find anyone that could help me here.
I have Samsung A5 (2016) with Android 7.0 and October 1, 2018 Security patch level.
I’m trying to flash an older version of 6.0 Android with an older Security update level, however I am facing the “SW REV CHECK FAIL ERROR” - from what I understand I cannot downgrade to a version that has lower security patch. Is there ANY way around this besides trying to flash 6.0 with newer security patch?
I’ve been browsing here a lot and found a few mentions of this being possible by unpacking the .tar.md5 file and removing all files ending with .bin and packing it up as .tar.md5 again, however my attempts at this have failed - Odin will still give me “Fail” and I will still get the same SW REV CHECK FAIL error. I’ve found a post saying that removing the .bin files from the .tar.md5 file that I want to flash and replacing them with newer .bin files should work as to trick the bootloader to think the version is the same as my current one and essentially leaving the newer version of bootloader still on my phone but with downgraded android version of a lower sec. patch. I’m a bit skeptical about this approach and I fear it will not work - I am afraid to try.
Is there any way to do this?
Click to expand...
Click to collapse
The fifth character from the right end of your firmware build number is the Binary version.
You are getting that failure error because the firmware that you are trying to flash has a Binary version that is lower than the Binary version of the firmware that you had on the device before you tried to downgrade it. You can not flash any firmware that has a lower Binary version, you can flash a firmware that has the exact same Binary version as what was already on the device or a higher Binary version. You can't go backwards, you can only stay where you are or go forward, but, if you go forward, you also can't go back to what you had before you went forward, and so on and so on....
Yes, you can try to swap the .bin files, but, that may not be the only things that need to be swapped or modified. You'd have to do some research for yourself and use a little trial and error.
Sent from my SM-S767VL using Tapatalk
Yeah I know about all that, apparently my bootloader is 7.
What I’m trying to do is to find a workaround for the “can’t go back to older version” roadblock.
I was hoping someone here might be experienced in this regard as to help me with the editing process. I’ve also heard that flashing custom ROM and then flashing the old version Android might work.
Anyone with any ideas? :/
Armageddon8 said:
Yeah I know about all that, apparently my bootloader is 7.
What I’m trying to do is to find a workaround for the “can’t go back to older version” roadblock.
I was hoping someone here might be experienced in this regard as to help me with the editing process. I’ve also heard that flashing custom ROM and then flashing the old version Android might work.
Anyone with any ideas? :/
Click to expand...
Click to collapse
Flashing a custom ROM then trying to flash the older version isnt going to work either because even though you would have a custom ROM installed, the bootloader that is blocking the downgrade is still there "under" the ROM.
As I stated, swapping files between the older version and the newer version "might" work. But, the problem is, there is no definitive guide that works for every user or every device. It is always a case by case scenario where the modifications required depend on but are not limited to exactly which device you are working with, what android versions are you working with, what bootloader versions you are working with and whatever other software security measures may be incorporated into your device.
As I said, on this subject, you will have to do your own research and use trial and error. In other words, you will have to try for yourself and experiment until you find something that works. There are no instructions or guides that any of us can specifically give you and say "do this" that will 100% work for you because results are different from one device to the next.
I realize that this doesn't help you as much as you would like it to, but, it is the reality whether you choose to accept it or not.
All I can say is do some searches for how to modify Samsung firmware in order to downgrade or how to modify Samsung firmware in general. Then it's a matter of using trial and error to find the right recipe of firmware parts to get a firmware that will successfully flash on your device. It isn't easy because it doesn't always come down to just the bootloader or its binary version, sometimes, the bootloader or the binary is also looking for(for example but not limited to) a modem, system and kernel that has the same binary version as the bootloader that is being flashed. No one can definitely say which parts you can or can't use together from the different firmware available for your device. This makes it very hard to help you to the extent that you are hoping for.
This website really functions by the user searching for answers and doing the work for themselves. We answer questions here, but we don't spoonfeed anyone, we don't hold anyone by the hand and lead them step by step nor will we do it "for" you. You must be willing to put the time and the work into it for yourself, after all, it is your goal to achieve, not ours.
Sent from my SM-S767VL using Tapatalk