Ok so I bought this Samsung S6 Edge here in Italy for my wife (the phone model is SM-G925F, carrier free). Yesterday I downloaded and flashed with Odin the last firmware available for my country (5.1.1) but unfortunately this firmware doesn't have the Traditional Chinese language in it (my wife is from Taiwan). So I tried to downloaded a firmware of another country hoping that I could get more languages (I downloaded the Malaysian firmware 5.1.1, *maybe* that could have more asian languages in it). Anyways, I tried to flash this firmware with Odin but near the end it failed on the "hidden.img" file (luckily, flashing again the italian firmware recovered the phone, no brick). Searching on this Forum I read some people suggesting to delete the "cache.img" and "hidden.img" files from the firmware archive and this should solve the "hidden.img" error on Odin. But before doing this I need some clarification:
- Why do we need to delete those files from the (official) firmware archive? What are they for and why they are there if we can delete them safely? Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
- In case I need to delete those files, is it better to use Total Commander (like someone said) or the Unified Android Toolkit? Will this "custom" .tar firmware trip KNOX on my phone (I read some people had this problem)?
Thanks!
DDJ75 said:
Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
Click to expand...
Click to collapse
Also I'm wondering, deleting those .img files from the .tar will delete also some additional rom languages? As I said I want to try an Asian rom (like Malaysia) in the hope that I can find Chinese language on it... that's the only thing I need otherwise the italian firmware would be fine.
DDJ75 said:
Ok so I bought this Samsung S6 Edge here in Italy for my wife (the phone model is SM-G925F, carrier free). Yesterday I downloaded and flashed with Odin the last firmware available for my country (5.1.1) but unfortunately this firmware doesn't have the Traditional Chinese language in it (my wife is from Taiwan). So I tried to downloaded a firmware of another country hoping that I could get more languages (I downloaded the Malaysian firmware 5.1.1, *maybe* that could have more asian languages in it). Anyways, I tried to flash this firmware with Odin but near the end it failed on the "hidden.img" file (luckily, flashing again the italian firmware recovered the phone, no brick). Searching on this Forum I read some people suggesting to delete the "cache.img" and "hidden.img" files from the firmware archive and this should solve the "hidden.img" error on Odin. But before doing this I need some clarification:
- Why do we need to delete those files from the (official) firmware archive? What are they for and why they are there if we can delete them safely? Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
- In case I need to delete those files, is it better to use Total Commander (like someone said) or the Unified Android Toolkit? Will this "custom" .tar firmware trip KNOX on my phone (I read some people had this problem)?
Thanks!
Click to expand...
Click to collapse
Hi, i´m not an expert in dev or codes, but recently I soft bricked my phone, and I did a lot of research here, and tried almost everything to solve my problem.
In my case, my S6 was stuck on android 5.0.2 with bootloader in 5.1.1 and the stock firmware 5.1.1 for my specific device wasn´t released yet. So I couldn't turn on or get the emergency recovery from Smart Switch.
When I flash the firmware from other variants, the process always fails. So I´ve tried everything to flash a 5.1.1 firmware.
First I removed the hidden, then I try to remove the cache... with more research, One guy said to remove the sboot.bin e cm.bin. I try this and fails too...
Than I remove all the files, (hidden, cache, sboot e cm.bin) and works!
Even if fails in Odin, this doesn´t mean that the file is the problem... Maybe the cable is in bad conditions, or the PC itself... Try more than 2 times to flash the same .tar before discard that solution.
- Why do we need those files? Good question, don´t know either.
You can try to delete 1 and flash, try both and flash. A lot of variables are in this situation.
- I advise you to use Total Commander, very easy and fast.
And man, why don´t you simply try to download the language package? For sure you have this option somewhere, or someone knows how to.
rafaelrgm said:
And man, why don´t you simply try to download the language package? For sure you have this option somewhere, or someone knows how to.
Click to expand...
Click to collapse
Well, on Google Play there's an app called "MoreLocale2" which adds more system languages. Problem is that this app needs root access and I want to avoid that...
simply delete hidden img from framework
How to delete a file from framework pls explain how to acces
Please help! I have the galaxy s6 sprint variant and I can not get this to work. The stock firmware does not have any hidden.img files it hasy system,cache,boot,cm,modem,sboot, and rocovery.img.tar.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Related
Hi Guys after some help.
Ended up with a s6 edge, it was originally dropped in a bath, sent off for repair via a 3rd party shop, stayed there for 3 months and came back with factory binary installed on it! I know very little info on it other than it was on 5.02 and passed all hw tests I could do. It was brought from argos unlocked, used on O2 (assuming the same phone that went out came back!)
Just thought it needed a new rom flashing, so downloaded ODIN 3.10.6 and downloaded a 5.02 H3UK stock rom, failed at <ID:0/020> NAND Write Start!!
then I tried a 5.1.1 Vodafone rom and did the same. I then tried a 6.01 rom and it fails at <ID:0/020> cm.bin and now wont even boot into factory binary.
I tried the recovery via smart switch and it doesn't recognise the device to tell me what version of software I need!
I have also tried 2 different computers and a few different usb leads.
Any help would be much appreciated!
Phil750123 said:
Hi Guys after some help.
Ended up with a s6 edge, it was originally dropped in a bath, sent off for repair via a 3rd party shop, stayed there for 3 months and came back with factory binary installed on it! I know very little info on it other than it was on 5.02 and passed all hw tests I could do. It was brought from argos unlocked, used on O2 (assuming the same phone that went out came back!)
Just thought it needed a new rom flashing, so downloaded ODIN 3.10.6 and downloaded a 5.02 H3UK stock rom, failed at <ID:0/020> NAND Write Start!!
then I tried a 5.1.1 Vodafone rom and did the same. I then tried a 6.01 rom and it fails at <ID:0/020> cm.bin and now wont even boot into factory binary.
I tried the recovery via smart switch and it doesn't recognise the device to tell me what version of software I need!
I have also tried 2 different computers and a few different usb leads.
Any help would be much appreciated!
Click to expand...
Click to collapse
If it was bought from argos unlocked it will have generic firmware on it.
Flashing a 3 or Vodafone rom will not work as the partitions are different which is why you are getting fail.
https://www.sammobile.com/firmwares/download/106963/G925FXXS4DPJ2_G925FBTU4DPH1_BTU/
Try to flash this and keep me updated.
Use odin 3.10.6 and ensure odin options are
Auto reboot checked
Repartition UNCHECKED
F.reset time checked
Try to use original Samsung cable.
Hey thanks for the help, i had to flash the 4dp recovery flash (https://forum.xda-developers.com/galaxy-s6-edge/help/downgrade-flash-4dpg2-official-rom-t3419745) then i tried that rom and got further but stuck on hidden.img, removed it from the zip, repacked and its now working fine thanks for the help
Hello. Having read a bunch of threads for this matter, i haven't yet encountered a solution for my particular problem. It may be impossible altogether.. but i thought i'd hopefully ask anyway.
My device is the Samsung Galaxy S6 Edge(SM-G925F, international variant, not carrier branded). I have MM 6.0.1 running on it, with the latest security patch and bootloader that is available in my country, that is:
S6 edge SM-G925F ROM Romania - G925FXXS5DQC1 - downloaded and flashed via ODIN 3.12.3 from sammobile
However, recently i wanted to downgrade to LP 5.0.2(or 5.1.1 - and from there my target is 5.0.2), as i like the look and feel of it more. But, as i have said, upon researching around the forum and on the whole internet i haven't found a positive solution, and i decided to make an account on here and hopefully get lucky.
I've tried multiple ODIN versions, multiple 5.0.2 and 5.1.1. ROMs found on the internet for different countries, but the end result is always the same: download mode says SW REV DEVICE 5 BINARY 1(or 2,3,4)
As for ODIN:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It doesn't matter to me if i have to root, flash custom roms and custom recoveries all over, i just want to know if there is a way to get my phone on the old bootloader and flash stock 5.0.2 rom.
Any info/advice is appreciated. Thank you all!
android2819 said:
Hello. Having read a bunch of threads for this matter, i haven't yet encountered a solution for my particular problem. It may be impossible altogether.. but i thought i'd hopefully ask anyway.
My device is the Samsung Galaxy S6 Edge(SM-G925F, international variant, not carrier branded). I have MM 6.0.1 running on it, with the latest security patch and bootloader that is available in my country, that is:
S6 edge SM-G925F ROM Romania - G925FXXS5DQC1 - downloaded and flashed via ODIN 3.12.3 from sammobile
However, recently i wanted to downgrade to LP 5.0.2(or 5.1.1 - and from there my target is 5.0.2), as i like the look and feel of it more. But, as i have said, upon researching around the forum and on the whole internet i haven't found a positive solution, and i decided to make an account on here and hopefully get lucky.
I've tried multiple ODIN versions, multiple 5.0.2 and 5.1.1. ROMs found on the internet for different countries, but the end result is always the same: download mode says SW REV DEVICE 5 BINARY 1(or 2,3,4)
As for ODIN:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It doesn't matter to me if i have to root, flash custom roms and custom recoveries all over, i just want to know if there is a way to get my phone on the old bootloader and flash stock 5.0.2 rom.
Any info/advice is appreciated. Thank you all!
Click to expand...
Click to collapse
The only answer for your query is unfortunately no. You can not downgrade from mm to lp. It is impossible. Sorry its not the news you wanted.
I suppose the only way it could be done is to buy a new motherboard that is on lp firmware and replace the full board.
Other than that there is no way.
Understood. Thanks for the info!
I bought an unlocked T-Mobile Note 10 and didn't want to see their stupid logo and bloatware and wanted to install the unlocked firmware. I downloaded the latest firmware as well as ODIN from Sammobile (https://www.sammobile.com/samsung/galaxy-note-10/firmware/#SM-N970U1). I ran into two problems:
1. Getting stuck on the setupconnection step
2. <ID:0/007> FAIL! Model mismatch fail
I wanted to post my experience and how I overcame these problems. I hope it helps someone else facing these issues. I'm sure these are obvious to the experts, but for newbies like me, it took a some trial and error.
For the setup connection issue, what worked for me was:
1. Start Odin as admin
2. Start Odin first, then enter download mode on device and connect to the computer. Doing this the other way around always failed in getting stuck on setupconnection. If Odin fails, I had to redo this step, or I'd get this problem again.
For the FAIL! Model mismatch fail issue:
- Don't use Odin from SamMobile. Use the patched one. This is the one I used Odin3 v3.13.1_3B_PatcheD from here https://androidfilehost.com/?fid=11410963190603883035
thanks for the warning/link. i just started looking at info to flash my verizon one to unlocked firmware.
edit2:
used yours and it gave me a missing INI fialure. used the one in here and it gave me the model mismatch fail...confused
edit2:
now it's failing with FAIL! (Auth)
My phone is Rev B2. I think the problem may be that the firmware I found is from Aug so it's probably an older revision ..FML
edit 3 ( or 4? who knows anymore):
I had another one which did have the B1 revision (I didn't take the fimrware update, on the other one, samsung shoved it down my proverbial throat). the one that worked has RP SWREV B1(1,1,1,1,1,1) K1S S1
The one that did not work has B2. I guess I need newer stock ROM files.
SDRebel said:
thanks for the warning/link. i just started looking at info to flash my verizon one to unlocked firmware.
edit2:
used yours and it gave me a missing INI fialure. used the one in here and it gave me the model mismatch fail...confused
edit2:
now it's failing with FAIL! (Auth)
My phone is Rev B2. I think the problem may be that the firmware I found is from Aug so it's probably an older revision ..FML
edit 3 ( or 4? who knows anymore):
I had another one which did have the B1 revision (I didn't take the fimrware update, on the other one, samsung shoved it down my proverbial throat). the one that worked has RP SWREV B1(1,1,1,1,1,1) K1S S1
The one that did not work has B2. I guess I need newer stock ROM files.
Click to expand...
Click to collapse
Did you ever get a successful flash to another firmware for your Verizon Note 10? I also have the Verizon model.
Thanks.
I think you need to download a Odin patched version, I have similar problem with a samsung s20+, try that and see it works
Extremely sorry to post this thread again - actually I referred all the threads in XDA Developers Forums but though a few of them matched my requirement but it was closed since 2013 - hence reopening again...
I have a Samsung GT-P1000 - Made in Korea (I don't live there - live in India though) - FCC ID: A3LGTP1000 - S/N: R2DB129469E
I will provide complete details to make it coherent to you...
CURRENT STATUS -- Soft Bricked (Symbol: A mobile - A yellow triangle with exclamation - A desktop) - (The only thing I see in the tab now!!!)
BEFORE -- Android 2.3.3 Gingerbread, no mods (no root, no custom boot-loader, etc...) -- Complete Original Tablet
What I tried to do --
Install Android 6.0.1 Marshmallow (Following this guide: https://www.droidthunder.com/galaxy-tab-gt-p1000-android-marshmallow-rom/) but soon failed in the rooting step itself, precisely, while installing cwm13...
Now, what I want to do --
After some research, which I must have done earlier, not sure, but maybe people are trying to say that installing Android 6.0.1 Marshmallow is not possible... I did not go deeper...
Anyway, I thought we will revert back to what it was... to Android 2.3.3 Gingerbread...
The problem I face doing this --
To install Android 2.3.3 Gingerbread back I used,
-- Odin3_v1.83
-- And the PIT, PDA, and Phone files are here (https://drive.google.com/drive/folders/1CLrfcUdk-oZ1N6ZZ90LbDCdMW5KYkHnV?usp=sharing) - (I got these while referring to a YouTube video:
)
-- And also installed the USB drivers (updated)
And then, following the above YouTube video, I came up with this, (After connecting the device with the PC - after around 15 mins the brick screen appears - It shows a yellow color port in odin - and I start), And stops after this log,
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Then I switched the ports aswell, and the only difference from the above error is the id changes from 7 to 6...
Also, tried with Odin_v3.07, Odin_v3.13.1, Odin_v3.09, Odin_v3.12.3, but the same logs...
And then, started researching this error but no answer was up to my requirement (there are same threads in this forum but the answers for them did not work for me)
Any help would be highly appreciated,
Thank You
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
It_ler said:
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
Click to expand...
Click to collapse
Thank You for replying @It_ler , this was my 1st question in this forum and waiting since a month or more, I am glad you put your precious time in this thread.
I am new to this forum, and I see you are pretty experienced in here, I would really really appreciate if you can help me gather more minds into this. I have memories linked with this tab, and all these days I have been eagerly waiting for a reply.
As you said, to check the re-partition in Odin, I see that it automatically gets checked once I start flashing, but the logs remain the same...
hey guys, so i am trying to downgrade my samsung galaxy note 20 5G to android 10 from android 11. i am not sure which files i need to download from sammobile.com because when i try to find my verizon phone that has a baseband version number of N981USQS2DUE2 well there is none under sammobile firmwares. so i looked around and found it under the usa/cha xfinity mobile i think it was firmwares. oh and by the way my service provider software version is SAOMC_SM.N981U_OYN_VZW_RR_0014 VZW/VZW/VZW. so clearly its a verizon phone not a cha infinity one.. so why is my baseband version coming up under the other section and not under verizon section. well i went with some research i did and chose to do the android 10 vzw download for the AP BL CSC CP files and this is the output i get in odin 3.14.4 .... please help me ... i dont know what is wrong.. and on my phone it says sw rev error (abl) then i forget the numbers.. ill have to run it again and see to confirm.. but if anyone could please help me out that would be much appreciated.. thanks and have A GOOD DAY..
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 9172 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hainguyenthao said:
You can't downgrade bootloader and you already updated to N981USQS2DUE2 and android 10 is N981USQU1DUB7
Click to expand...
Click to collapse
As Admiral Akbar said:" It's a trap!"
i had same problem...
sctvnn said:
i had same problem...
Click to expand...
Click to collapse
It's not a problem it's device security. Called anti rollback. The whole point is to make your device more secure with each incremented bit
TheMadScientist said:
It's not a problem it's device security. Called anti rollback. The whole point is to make your device more secure with each incremented bit
Click to expand...
Click to collapse
Exactly how does that bootloader OS version lockout serve the consumer?
It's not like it can be remote flashed without your knowledge...
blackhawk said:
Exactly how does that bootloader OS version lockout serve the consumer?
It's not like it can be remote flashed without your knowledge...
Click to expand...
Click to collapse
It really don't. It serves the company more than anything we find exploits. Some severe enough. The increment so we can't exploit that exploit. It hurts consumers more than not in my opinion.
So Sony just released update 9.0 for ps4. And is in some cases even bricking consoles. Nothing we can do. Same implementation. Anti rollback. Be easily fixed if we could rollback to the previous firmware.
Their answer is. If you didn't already update we suggest you hold off til we patch it. So what now I can't play ps4s on most games because they require internet and psn access. Which I don't have due to not being updated.
It's to prevent Theifer Sutherlands from downgrading to remove FRP lock.. since I believe there's currently no workaround for Android 11.
TheMadScientist said:
It really don't. It serves the company more than anything we find exploits. Some severe enough. The increment so we can't exploit that exploit. It hurts consumers more than not in my opinion.
So Sony just released update 9.0 for ps4. And is in some cases even bricking consoles. Nothing we can do. Same implementation. Anti rollback. Be easily fixed if we could rollback to the previous firmware.
Their answer is. If you didn't already update we suggest you hold off til we patch it. So what now I can't play ps4s on most games because they require internet and psn access. Which I don't have due to not being updated.
Click to expand...
Click to collapse
Just saw your post, oops. Yeah the lockouts and even the updates many times serve the manufacturer's interests more than the end user's. That's my conclusion.
Been true on all my Samsung's for 8 years. My N10+'s never get upgrades or updates and run like bats out of hell. Current load on this one still running on Pie will 3 yo in June. Very stable and security is not an issue. No vax, no upgrade... still here running wild and free