Hi folks, (newbie here, so not sure what I'm doing here, (or with my Phone).
According to the info in About Device, I have an S5 (SM-G900F), Build No: G900FXXU1ANE2, Baseband V: G900AUCU2AND3
I've been trying' to 'Return to Stock', (Alliance ROM on Phone when I bought it, practically brand new).
Have read shed loads of tutorials on flashing the device with the use of ODIN and Firmware based on above Build No, but ODIN fails every time, exceptionally quickly, (like 3 seconds in).
I decided to give KIES a go, but KIES will not even attempt anything unless I put the device in as SM-G900A, then it will offer to download and install Firmware G900UACU1ANCE (ATT), but even that fails early during download. (Incidentally, when in Download Mode, the top of the Screen displays ODIN Mode, then Product Name: SM-G900A. In Download Mode, info also says: Reactivation Lock (kk): Off KNOX Warranty Void: 0x0 Secure Check Fail: [aboot] (sometimes with Fixed 2 > Binary 1 after [aboot].
KIES says the following F/W is installed: G900FXXU1ANE2/G900FOXU1ANE2/G900AUCU2AND3/G900FXXU1ANE2 (BTU)
The back of my phone does have an AT&T logo on it, (I assume therefore my phone is AT&T International version, hence the ATT Firmware suggestion in KIES? Would the locked Bootloader therefore stop me from flashing the ROM on it and returning to stock?
Have been proffered some further info elsewhere, perhaps you developers may have a solution. read the following:
It looks as though someone has done some very heavy duty modding to get Alliance ROM v4 for KitKat, NE2, to work on the AT&T carrier minority variant, G900A. This would seem to include flashing a stock G900F KitKat firmware to it after, possibly, altering the .PIT file/s. This would account for KIES not being able to upgrade it and Odin not being able to flash it as it is now neither a G900A or a G900F and the CSC codes and Product codes will not match. See 40 Galaxy S5 models - Dummies Guide for details of the models mentioned and CSC codes. Unfortunately, without knowing how or which mods were used to enable Alliance ROM v4 to run on a G900A, I cannot comment further.
Thanks for any assistance/answers folks, Andy
Related
OK, clearly I missed something when I did all my reading. I've got an SM-N9005, LTE, 32GB.
I downloaded an XSA ROM from Sammobile, N9005XXUBMI7_N9005XSABMI1_XSA.zip then unpacked it and ran Odin to flash it. My plan was to have an AU ROM before I tried RDLV root process.
Instead I got an Odin error on system.img.ext4 followed by the error screen. (phone - yellow exclamation - PC. The list there says:
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox Kernal: 0x0
Knox Warranty Void: 0x0
Qualcomm Secure Boot: Enable
RP SWREV:S1, T1, R1, A1, P1
Write Protection: Enable
Nothing I have been able to do since then has helped. Even tried DL'ing Heimdall but it uses tar.gz packages and I don't have one. I downloaded Kies3 and it tells me my phone is not supported by v3. Clicking Confirm doesn't help nor does the 'Checking' link. The other Kies give a connection error and the Troubleshoot Connection option doesn't help.
The only thing I can think I might have got wrong is trying to install an Aussie package over a TGY (Hong Kong) system, but there are plenty of comments saying that is OK.
I found a PIT file that is supposed to be OK, (CSB_signed_HLTE_EUR_OPEN_32G_0718) but I am not sure a pit is the answer, and if that was the cause, I think I'd need a PIT to match my ROM... right?
By preference I'd like to keep under the level where I trip Knox, but if I have to use a Recovery or CF-Root to get my phone working I'll do it.
Any advice please? Also, any ideas on what went wrong?
With some difficulty in downloading (I have a PC problem where it just seizes up for no traceable reason - going back to shop as soon as I can get it to Melb) with it taking 4 times to DL, and after some dismay that XDA'ers hadn't responded to my problem (how dare you lot sleep when my phone isn't working! :laugh I tried the Hong Kong version this morning and it ran beautifully. :victory: Not only that, my phone set up is intact.
So, what did I just learn?
Was it that, on an unrooted phone you cannot flash a stock from a different country?
Is it that HK ROM's are just different?
Or was it that some ROM's, even from Sammobile, don't run?
I am fairly sure it wasn't just a corrupt DL; IIRC Odin checks the MD5 number before flashing - pretty sure I saw that in a thread while I was trying to work out what had gone wrong. And my PC problem didn't happen when I was DL'ing the XSA version.
On a brighter note, I have my RDLV setup mostly ready to go. RDLV was going to be the next thing I tried to fix the problem so I have CYGWIN and the files all set up. Better not tell the missus I am about to do it - she's already upset enough with me for bricking my brand new phone. :laugh:
I'd like some advice if you don't mind. In the future I may have to unroot my phone, either for warranty purposes or to sell it. I'd like to be able to put the XSA stock version on it at that point. I'm presuming I could run it over a rooted phone (& lose root) to produce an Aussie phone? But was it reasonable to expect the XSA version to run on my phone while it was not rooted?
Journyman16 said:
With some difficulty in downloading (I have a PC problem where it just seizes up for no traceable reason - going back to shop as soon as I can get it to Melb) with it taking 4 times to DL, and after some dismay that XDA'ers hadn't responded to my problem (how dare you lot sleep when my phone isn't working! :laugh I tried the Hong Kong version this morning and it ran beautifully. :victory: Not only that, my phone set up is intact.
So, what did I just learn?
Was it that, on an unrooted phone you cannot flash a stock from a different country?
Is it that HK ROM's are just different?
Or was it that some ROM's, even from Sammobile, don't run?
I am fairly sure it wasn't just a corrupt DL; IIRC Odin checks the MD5 number before flashing - pretty sure I saw that in a thread while I was trying to work out what had gone wrong. And my PC problem didn't happen when I was DL'ing the XSA version.
On a brighter note, I have my RDLV setup mostly ready to go. RDLV was going to be the next thing I tried to fix the problem so I have CYGWIN and the files all set up. Better not tell the missus I am about to do it - she's already upset enough with me for bricking my brand new phone. :laugh:
I'd like some advice if you don't mind. In the future I may have to unroot my phone, either for warranty purposes or to sell it. I'd like to be able to put the XSA stock version on it at that point. I'm presuming I could run it over a rooted phone (& lose root) to produce an Aussie phone? But was it reasonable to expect the XSA version to run on my phone while it was not rooted?
Click to expand...
Click to collapse
1st step, exit Kies... It will stuff up an ODIN flash...
2nd, what was the original rom on the HK phone? If it's MJ3 or above it had the new bootloader on it that won't allow you to go back to an earlier version...
ultramag69 said:
1st step, exit Kies... It will stuff up an ODIN flash...
2nd, what was the original rom on the HK phone? If it's MJ3 or above it had the new bootloader on it that won't allow you to go back to an earlier version...
Click to expand...
Click to collapse
I may have written it wrong but I wasn't running Kies and Odin at the same time; they were alternative ways to try to get things going.
MI7 was the original and also the one I used to finally get things working again. Then I figured I'd try the RDLV process but still had issues with files - I posted all that on the RDLV thread.
Currently I am all working but unrooted, Knox = )x) and I am waiting for an updated HK version to DL.
I eventually got root on my Note. Had to DL the same country version of an update (MK1) and run RDLV process on that, then it all worked flawlessly. I'm still puzzled as to why I couldn't do the equivalent on an Aussie ROM version and use that. Only thing I can think of is the partition size is different for Hong Kong versions so it give the errors as you try to flash a different version.
Annoying but it doesn't appear to have happened to others - maybe they are content to use ROMs from the country their CSC is set to?
I rooted my phone two weeks ago with towelroot and disabled Knox with supersu.Note: my device status said official I'm still running stock firmware. Have to send my phone back for warranty problem so I unrooted with supersu and reset my phone. So now when I look at my device status it says custom (never flashed any roms or nothing) so I factory reset and notice unlock padlock and custom on my reboot startup screen. I also put phone in Odin mode the binary still said Samsung official but now the other say custom. And Knox says 0×0. I was told to use Odin so I installed odin3v3.09, drivers, stock firmware on the PC tried to flash it but got a Auth: Fail in the left lower box.
My replacement phone will be here today and will send the old back Monday to give me a couple more days to figure this out. What did I do wrong?
PLEASE HELP!
UPDATE
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Try going to the sammobile website (cant post link because I'm a new member). It should be there
Sent from my SM-G900F using XDA Premium 4 mobile app
tmadekush said:
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Click to expand...
Click to collapse
Your warranty should be honoured because it still shows Knox 0x0. But it would be prudent to resolve the custom message as you are trying to do. It's showing custom because you disabled Knox. Flashing a full stock firmware should restore Knox and resolve the custom message.
Odin flashes can fail for many reasons e.g. trying to flash non-Odin versions of firmware, bad signatures, poor quality USB cables, wrong firmware version e.g. one meant for a different phone, et cetera.
Back up your files, then do a full system reset from the settings menu. Then put your phone into download mode and use Odin to flash a full stock firmware. Ideally use the latest firmware version for carrier that the phone originally came from (i.e. it should match the baseband). Google will find many firmware repositories e.g. sammobile, samsung-updates and this site.
.
Hello everyone, I'd like to start off by saying I am a complete newcomer to all this so please explain literally all of the terminology/jargon you intend to use and correct me when I use it wrong.
I have a Chinese version of the Samsung Galaxy Note 4 SM-N9109W and up until yesterday it was running out of the box on android 4.4.4. I care not for any of the data on the phone nor the warranty as there was none to begin with when it was gifted to me.
I attempted to "root" it as I didn't want any of the Chinese apps/restrictions on it but have failed miserably and now my phone is stuck in a bootloop.
I was following this guide if it helps: http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948 and downloaded the appropriate Snapdragon version (SM-N9109W).
I cannot enter recovery mode by holding down *power+vol up+home* as it just keeps on rebooting. I can, however, get into the downloader by holding down *power+vol down+home*.
I have tried for the entirety of today to find a specific guide for the Chinese note 4 on xda, youtube and google but to no avail - nothing that I can find is identical to my situation and I am hesitant to do anything further to it by following a similar guide in case I make it worse.
I have repeatedly seen suggestions to "flash" stock rom and as I can get into the downloader I believe this would be a great starting point, but once again I am afraid to do anything without a specific guide for the N9109W.
A few people have referred to SamMobile to download stock rom, but a search for SM-N9109W lists 8 files for 4.4.4 and I believe I have no way of working out my PDA or CSC, yet again I don't know what these even are and they might not be relevant?
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience,
Ryan
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
ithehappy said:
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
Click to expand...
Click to collapse
Thank you ithehappy for the reply,
When I search for the stock firmware on SamMobile, I type in my exact model number (SM-N9109W). This search returns with a list of multiple different versions for my phone, of which 8 are 4.4.4 (my initial version).
Does it matter which version I download and install?
To my knowledge, I have no way of finding my CSC or PDA unless you know of a database I can use to search the information that is physically on my phone? Once again, does it matter that I know what these are or can I simply download, for example, version 5.1.1 and flash that on instead of my original 4.4.4? Or, will this just cause further possibly unfixable problems?
Thank you for your help
Anyone?
No, you can download any one you want.
Thank you for the help, ithehappy. I now have a working phone!
For future readers, I downloaded the latest version of 4.4.4 that SamMobile had (2015-03-27) for my model (SM-N9109W):
PDA: N9109WKEU1ANL3
CSC: N9109WCTC1ANL3
It failed the first time I tried flashing with Odin 3.10.7, but whilst I was hastily taking screenshots of my problem to post here I accidentally started the transfer again and it successfully installed that time.
I followed the instructions on SamMobile for the installation.
This version of the firmware I installed does not have any google services (thank China for that), so keep that in mind.
Thank you
Hello, All!
I have a G930V (Verizon S7) Non-EDGE, and I wan't to convert it to a G930U Unbranded (Or at least bloat free).
## BY THE WAY ##
Yes, I have seen other threads on this topic. Doesn't answer my confusions though.
Threads by:
tvm2487 (G930U Firmware)
James.Markham0757 (Can someone send me in the right direction...)
DeathAngel66669 (Using SamFirm to download SM-G930U-G930UUEU2APG9...)
## BY THE WAY ##
So anyways here are my questions.
##
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
7. Chances of bricking the phone? Would it be reversible?
##
My current S7 VZW Details:
Model: SM-G930V
Ver: 6.0.1
Patch Level: October, 1, 2016
Baseband Ver: G930VVRU4API3
I appreciate the help and your time. Thanks !
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
I don’t think it would flash as it is bootloader 2(5th character from right) latest firmware is 4!
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
From what I understand all the USA variants of the Galaxy S7's are the same hardware
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
I have an AT&T branded S7 SM-G930A and have flashed the U firmware and used it for a while. I have now switched carriers to T-Mobile used the U firmware without issues and now flashed the T-Mobile firmware and it works fine. KNOW IS NOT TRIPPED.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
Not sure, Odin may just fail to complete install?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
I never had luck flashing the HOME-CSC file, had to use straight CSC.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
One thing I did notice is the visual voicemail app tends to work better when using the specific carrier firmware(both AT&T & T-Mobile).
I'm using T-Mobile and I don't see a need to go back to U at this time as their is not much bloat on the T-Mobile firmware.
7. Chances of bricking the phone? Would it be reversible?
##
I just installed T-Mobile Nougat on my phone and got the error on phone and it was stuck on “You will need to use Smart Switch Recovery” to fix phone! SCARY!!! I managed to finally get firmware installed and running!
Understood.
When I get home today I'll try to install a newer version from SamMobile.
Updato has older versions. Sammobile has the latest which is.
G930U with code (VZW) on
G930UOYM4APL2
(https://www.sammobile.com/firmwares/download/118975/G930UUEU4APL2_G930UOYM4APL2_VZW/)
Would this be compatible?
G930UUEU4APL2 is the latest U-firmware. Everything flashes correctly, it won't trip KNOX, and it is super easy to go back to G930V firmware if you decide you want to send it back for warranty. You can't brick the phone by flashing signed files with Odin. The bootloader won't allow Odin to flash anything that could brick it.
I had already started replying before you posted above me. I'd recommend using my link to the firmware, as Sammobile downloads take FOREVER.
I see, I'm glad.
So, What would i need to make sure to do and not do in Odin 3.11.1?
AP/BL/CP/CSC from your zip? Just flash everything or only certain things?
Re-partition tick box? yes or no?
Flash all four of those files and DON'T CHANGE ANY Odin settings.
Okay. I just flashed it and now my phone repeatedly keeps booting into recovery.
The recovery logs and the red text at the bottom says:
dm-verity verification failed
Need to check DRK first...
Any ideas?
##PREVIOUS##
I think it might have to be because I used HOME_CSC rather than CSC.
What's the difference between both? Can i revert later?
##PREVIOUS##
@CVertigo1
I reflashed with the CSC file rather than the HOME_CSC file as according to your instructions in your thread (Latest G930U Firmware) and it worked perfectly fine!
KNOX is still at 0x0 and warranty void is fine.
( https://forum.xda-developers.com/verizon-galaxy-s7/how-to/g930u-firmware-pl2-g930v-success-t3558214 )
No bloat, amazingly fast, and some features i like are present. I'll report back to your thread on the battery life when i get more time with it.
I appreciate your patience.
(Will post screenshots later).
Home_CSC doesn't wipe user data, which causes issues when swapping firmware. That's what caused your bootloop.
Followed this, today, was sick and tired of the damn Verizon bloat slowing the phone down.
The phone runs faster - notably faster.
After installing the SIM, the phone returns, "Your device will restart to configure features supported by the new SIM card."
And then" It's useless. If I hard-power reset it, and take out the SIM, it's viable - it's just useless otherwise.
Phone is a G930V, flashed to G930U.
Any Suggestions? The phone is *NOT* rooted, so I can't easily take out or rename the AutoPreconfig.apk package.. Argh.
Will I get the android nougat update on this ROM?
Just converted G930V to G930U, all 100% working here in the UK. Fully debranded and no verizon warning about sim change. perfect
Mind telling me what thread you used to find the latest firmware? This forum for the phone is so rarely used anymore, it's hard to tell what info to go even go on anymore.
Is PL2 the latest for 930U? I'm VZW but US, not UK
Hi there.
Apologies in advance if I have posted this in the wrong forum.
I would appreciate any help that the knowledgeable people on here can offer for the following issue.....
I recently purchased a supposedly new Samsung Galaxy A20e here in the UK (from eBay) for my girlfriend. After a few weeks of getting used to it she noticed that she wasn't able to install any secure apps on it such as banking apps nor could the phone access any OTA updates (error message: "Your current software version isn't supported"). Other than that the phone is totally usable and works with her UK mobile provider SIM.
Upon further investigation I discovered that the phone appeared to be rooted (it has a MAGISK app on it). To make matters worse it appears that the phone may not be a A20e (i.e. model number SM-A202F) after all and may in fact be a Galaxy Jean2 (i.e. model number SM-A202K) - I believe that this is how the A20e was branded in Korea. All of the relevant information under Settings > About Phone points to it being a A20e, e.g. Model Number (as does the branding on the box) but when I put the phone into Download Mode it shows the model number as SM-A202K. I also believe that the Bootloader is unlocked.
The phone is currently running the following:-
Android 9 (One UI 1.1)
Baseband version: A202FXXU3ATB1
Service provider SW ver: PRT/PRT/KTC
Android security patch level: 1 January 2020
Current version (visible if I attempt to perform an OTA Software update): A202FXXU3ATB1/A202FPRT3ASL3/A202KKKU3ATA1
The seller we bought it from does not respond to my queries and eBay haven't been much help either.
No problem I thought as I would attempt to flash the latest A202F firmware (i.e. UK firmware - BTU) to it via ODIN (and thereby remove ROOT?) but this is where I need help. I must admit that I'm not an expert in any of this so please excuse my ignorance and naivety.
I have made numerous attempts at flashing what I believe to be the correct firmware (all starting A202FXXU3***) - all to no avail. I have even tried a A202K version.
The first issue I encountered was an ODIN fail with "SECURE CHECK FAIL (PIT)". After investigation I discovered that it might be possible to resolve this by downloading the PIT file and explicitly referencing this in ODIN (I downloaded separate PIT files for both A202F and A202K). Using the A202F PIT version didn't resolve this particular problem however using the A202K PIT did however I then encountered the next problem. Using the A202K PIT file and any variation of firmware via ODIN now fails with "SECURE CHECK FILE (BOOTLOADER)" and this is where my limited knowledge runs out.
Can anyone on here offer any advice as to how I can resolve this issue please? Ideally I'd like to get the phone to a state where it is not rooted; is running SM-A202F firmware; is able to get OTA updates and be unlocked to UK SIMs.
Many thanks in anticipation.
SenorValasco said:
Hi there.
Apologies in advance if I have posted this in the wrong forum.
I would appreciate any help that the knowledgeable people on here can offer for the following issue.....
I recently purchased a supposedly new Samsung Galaxy A20e here in the UK (from eBay) for my girlfriend. After a few weeks of getting used to it she noticed that she wasn't able to install any secure apps on it such as banking apps nor could the phone access any OTA updates (error message: "Your current software version isn't supported"). Other than that the phone is totally usable and works with her UK mobile provider SIM.
Upon further investigation I discovered that the phone appeared to be rooted (it has a MAGISK app on it). To make matters worse it appears that the phone may not be a A20e (i.e. model number SM-A202F) after all and may in fact be a Galaxy Jean2 (i.e. model number SM-A202K) - I believe that this is how the A20e was branded in Korea. All of the relevant information under Settings > About Phone points to it being a A20e, e.g. Model Number (as does the branding on the box) but when I put the phone into Download Mode it shows the model number as SM-A202K. I also believe that the Bootloader is unlocked.
The phone is currently running the following:-
Android 9 (One UI 1.1)
Baseband version: A202FXXU3ATB1
Service provider SW ver: PRT/PRT/KTC
Android security patch level: 1 January 2020
Current version (visible if I attempt to perform an OTA Software update): A202FXXU3ATB1/A202FPRT3ASL3/A202KKKU3ATA1
The seller we bought it from does not respond to my queries and eBay haven't been much help either.
No problem I thought as I would attempt to flash the latest A202F firmware (i.e. UK firmware - BTU) to it via ODIN (and thereby remove ROOT?) but this is where I need help. I must admit that I'm not an expert in any of this so please excuse my ignorance and naivety.
I have made numerous attempts at flashing what I believe to be the correct firmware (all starting A202FXXU3***) - all to no avail. I have even tried a A202K version.
The first issue I encountered was an ODIN fail with "SECURE CHECK FAIL (PIT)". After investigation I discovered that it might be possible to resolve this by downloading the PIT file and explicitly referencing this in ODIN (I downloaded separate PIT files for both A202F and A202K). Using the A202F PIT version didn't resolve this particular problem however using the A202K PIT did however I then encountered the next problem. Using the A202K PIT file and any variation of firmware via ODIN now fails with "SECURE CHECK FILE (BOOTLOADER)" and this is where my limited knowledge runs out.
Can anyone on here offer any advice as to how I can resolve this issue please? Ideally I'd like to get the phone to a state where it is not rooted; is running SM-A202F firmware; is able to get OTA updates and be unlocked to UK SIMs.
Many thanks in anticipation.
Click to expand...
Click to collapse
Check if the phone has any custom recovery installed by previous user, like (TWRP, OrangeFox..). If it does do a full wipe and via ADB check for device info. I doubt it will show the same information as you listed in your post. From there i would download this firmware if its a202F
Download Samsung Galaxy A20e SM-A202F BTU United Kingdom A202FXXU3CVC1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from United Kingdom with A202FXXU3CVC1 and Android version 11
www.sammobile.com
Try using ODIN that i attached on this post and flash the firmware.
[Guide] TWRP and ROOT for A20e (A202f) [Updated]
My way of installing TWRP and ROOT on A20e (only tested on a202f). Everything is working both on TWRP and MAGISK. Versions: -Magisk (v24.3) -MagiskManager (v24.3) -TWRP (3.6.1_9.0) _________________________________________________ Download...
forum.xda-developers.com
@SerbianGeekster
Many thanks for responding.
Excuse my ignorance but how do I tell if the phone has any custom recovery installed?
FYI - it has a MAGISK app installed on it.