Database Develop

Convert UL00 to L09 and Update to B303

Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.

Tuerkay said:
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Click to expand...
Click to collapse
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09

brumgav said:
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
Click to expand...
Click to collapse
change oeminfo back to dualcu/cn or leave as hw/meafnaf?

Tuerkay said:
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Click to expand...
Click to collapse
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post

brumgav said:
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
Click to expand...
Click to collapse
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version

Tuerkay said:
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Click to expand...
Click to collapse
Have you done a factory reset during any of the above?

brumgav said:
Have you done a factory reset during any of the above?
Click to expand...
Click to collapse
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.

Tuerkay said:
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Click to expand...
Click to collapse
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on

brumgav said:
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
Click to expand...
Click to collapse
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
i currently have no permission manager and no mobile data manager

Tuerkay said:
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
Click to expand...
Click to collapse
I think I wrote CRR-L09C432B114

@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.

bgx said:
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
Click to expand...
Click to collapse
tried many different things but nothing worked. Now i´m back at C433B114 until someone finds a solution.
I´m missing so many functions but i won´t change back to C00B160 because my main language isn´t supported well enough

Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?

Iverom said:
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Click to expand...
Click to collapse
European version only supports 1 SIM

Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?

plantunes said:
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
Click to expand...
Click to collapse
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.

Tuerkay said:
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Click to expand...
Click to collapse
Do you have a CL00 converted into a L09?
If you do, you could change that string "ro..dual.sim.phone" into TRUE and see what happens. It would be absolutely great if that was possible!

I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.

Lightofdarkness666 said:
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Click to expand...
Click to collapse
Flashed all files and then tried a clean update. Didn´t work. My Mate S shows the right Build and Vendor but i´m still not able to use the C432 Update.app´s.
Are you able to update manually?
Is your phone originally an L09 or UL00 device? If it´s an UL00 Mate S, could you tell me exactly what you did?

My phone is originally an L09, but i broke it in UL00C00, can't get back to L09, recovery don't boot, flash via fastboot lead to freeze at boot

P9 Lite (VNS-l21 single SIM) CUSTC change

Yesterday I figured to debrand my VNS-l21. Everything is fine, updated manualy to latest ROM B130. But, CUSTC has changed from C02 (Vodafone EU) to C900 (Global). In P7 thread there someone posted small update.app file (around 18 kb, http://forum.xda-developers.com/ascend-p7/help/p7-l10-defect-report-reminders-t2952124) that after flashing will change the CUSTC back to C432 (EU open market).
Have someone idea where to get this file for VNS-l21?

Ghouless said:
Yesterday I figured to debrand my VNS-l21. Everything is fine, updated manualy to latest ROM B130. But, CUSTC has changed from C02 (Vodafone EU) to C900 (Global). In P7 thread there someone posted small update.app file (around 18 kb) that after flashing will change the CUSTC back to C432 (EU open market).
Have someone idea where to get this file for VNS-l21?
Click to expand...
Click to collapse
Heyho,
u can do this also on the VNS-L21.
Hope i could help u
Regards,
Sebastian

k1ll3r8e said:
Heyho,
u can do this also on the VNS-L21.
Hope i could help u
Regards,
Sebastian
Click to expand...
Click to collapse
Nice work with the toolkit Years before I had unlocked & rooted every of my smartphones but, last two years I need to work with some apps that recognizing rooted device and won't work (bank app etc.). So if there no chance to change the region back to C432 without rooting the device, I will stay on that Global CUSTC (after two days of deep testing, there's no problem with it). Maybe later someone will do that update.app file or will be included in future update ROM.
Thread that I'm talking about http://forum.xda-developers.com/ascend-p7/help/p7-l10-defect-report-reminders-t2952124

Ghouless said:
Nice work with the toolkit Years before I had unlocked & rooted every of my smartphones but, last two years I need to work with some apps that recognizing rooted device and won't work (bank app etc.). So if there no chance to change the region back to C432 without rooting the device, I will stay on that Global CUSTC (after two days of deep testing, there's no problem with it). Maybe later someone will do that update.app file or will be included in future update ROM.
Thread that I'm talking about http://forum.xda-developers.com/ascend-p7/help/p7-l10-defect-report-reminders-t2952124
Click to expand...
Click to collapse
Heyho,
THX for ur warm words and the hint
-
About the build id, the only problem which happened to me while i was on the Asia build is, that u don't get any updates...
About the update.app, i just downloaded the file u linked me, i'll have today a look at it. Maybe we can produce such an file also for our L21/L31.
Regards,
Sebastian

k1ll3r8e said:
Heyho,
THX for ur warm words and the hint
-
About the build id, the only problem which happened to me while i was on the Asia build is, that u don't get any updates...
About the update.app, i just downloaded the file u linked me, i'll have today a look at it. Maybe we can produce such an file also for our L21/L31.
Regards,
Sebastian
Click to expand...
Click to collapse
First, if you can build that update.app for l21/l31, it would be amazing, because that will be BIG help for everyone who want only to debrand our P9 Lite's without lose warranty or brick it.
Second, nice to have there someone, who taking care of this phone :good:

Hello dear developers...Recently I bought a used Huawei p9 lite vns-l21c150b106 single sim...It is cosmote branded and I want to debrand it cause I found out by searching that there are several updates such as b150...When I try to update my phone it says that has the latest updates...I wanted to ask if there is a way to debrand it and return to official Europe stock rom without void my warranty...I found a way in the internet through local update via sd card but I don't find the stock rom Europe(I live in Greece)for my single sim vns-l21...I found only vns-l21c432b160 which is for dual sim...I think that vns-l21c150b160 must be for my single device,i suppose that the difference is c150 and c432...any solution please???

P9 Firmware update issue

Hello all, new here.
I've been looking all over in the past couple of days but unfortunately couldn't find answers so decided to post a thread and try my luck.
Recently I've had an issue with my P9 - to make a long story short, after a factory reset the phone booted with many central functions missing (camera, keyboard, etc...). Anyway, I sent my phone to a nearby mobile repair shop where they burned a new version - EVA-L09C900B167.
It runs Android 6.0 and EMUI 4.1.1, and I remember having Android 7 and EMUI 5.0 before all the problems began.
After consulting with the official Huawei vendor in my country, they said that this software is not supported in my country and therefore will not be receiving updates - and that my warranty is void for installing an "unofficial" version.
Anyway - in my search for the ability to update my device I came across a whole lot of information, but haven't really been able to understand everything thoroughly.
I have unlocked bootloader and rooted the device, I have TWRP installed.
Tried using a firmware version from Firmware Finder, without success.
Can anyone please explain to me ("Like I'm a four year old" ) how I can update my device?
Again, if a guide exists and I've missed it, my apologies and feel free to delete this thread.
Thanks !

ShiverJT said:
Hello all, new here.
I've been looking all over in the past couple of days but unfortunately couldn't find answers so decided to post a thread and try my luck.
Recently I've had an issue with my P9 - to make a long story short, after a factory reset the phone booted with many central functions missing (camera, keyboard, etc...). Anyway, I sent my phone to a nearby mobile repair shop where they burned a new version - EVA-L09C900B167.
It runs Android 6.0 and EMUI 4.1.1, and I remember having Android 7 and EMUI 5.0 before all the problems began.
After consulting with the official Huawei vendor in my country, they said that this software is not supported in my country and therefore will not be receiving updates - and that my warranty is void for installing an "unofficial" version.
Anyway - in my search for the ability to update my device I came across a whole lot of information, but haven't really been able to understand everything thoroughly.
I have unlocked bootloader and rooted the device, I have TWRP installed.
Tried using a firmware version from Firmware Finder, without success.
Can anyone please explain to me ("Like I'm a four year old" ) how I can update my device?
Again, if a guide exists and I've missed it, my apologies and feel free to delete this thread.
Thanks !
Click to expand...
Click to collapse
Debranding to European c432 - it will lead to OTA updates up to b395 with Android 7, EMUI 5.0.1:
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Little old, starting off c900 b136 - you may ask in that thread about debranding from yours b167.

zgfg said:
Debranding to European c432 - it will lead to OTA updates up to b395 with Android 7, EMUI 5.0.1:
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Little old, starting off c900 b136 - you may ask in that thread about debranding from yours b167.
Click to expand...
Click to collapse
Hey thanks a lot!
Will try it later today.
I'm guessing it won't be possible to just follow this guide as it is, even though I'm on 167?

MOTO G6 - IMEI 'Unknown', Baseband 'Unknown' - NEED HELP PLEASE!

Hello everyone, I am new to all of this development stuff for Android devices and I know I screwed something up big time.
I had an update recently on my Moto G6 XT1925-6 phone to Pie and there were several bugs happening from calls dropping, data and service dropping erratically, youtube videos would skip forward several times or not download at all. I found the post on here to downgrade from Pie to Oreo Stock ROM and followed it exactly as I could. Everything went according to the guide, but now after rebooting the phone and going through the setup, the phone wont detect my SIM, and there is no service. Under the IMEI Information, everything is 'Unknown' and under SIM status everything says 'Not Available'. Also, under Mobile Network, Data Roaming, Preferred network type, and System select is greyed out. CDMA subscription is the only thing available to tap. The issue with that is, this phone is originally GSM.
Please, I am not knowledgeable in messing with Android systems and I know I shouldn't be messing with something I know nothing about. I do have ADB Minimum installed on my PC, the phone is unlocked bootloader but is currently not rooted after the stock ROM was flashed.
Stock ROM: ALI_RETAIL_8.0.0_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
One more thing to add, I did the fastboot IMEI check command and it came back with one IMEI so it is still present in the phone somewhere.
Any help would be greatly appreciated! Thanks in advance!

Angelo Della Morte said:
Hello everyone, I am new to all of this development stuff for Android devices and I know I screwed something up big time.
I had an update recently on my Moto G6 XT1925-6 phone to Pie and there were several bugs happening from calls dropping, data and service dropping erratically, youtube videos would skip forward several times or not download at all. I found the post on here to downgrade from Pie to Oreo Stock ROM and followed it exactly as I could. Everything went according to the guide, but now after rebooting the phone and going through the setup, the phone wont detect my SIM, and there is no service. Under the IMEI Information, everything is 'Unknown' and under SIM status everything says 'Not Available'. Also, under Mobile Network, Data Roaming, Preferred network type, and System select is greyed out. CDMA subscription is the only thing available to tap. The issue with that is, this phone is originally GSM.
Please, I am not knowledgeable in messing with Android systems and I know I shouldn't be messing with something I know nothing about. I do have ADB Minimum installed on my PC, the phone is unlocked bootloader but is currently not rooted after the stock ROM was flashed.
Stock ROM: ALI_RETAIL_8.0.0_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
One more thing to add, I did the fastboot IMEI check command and it came back with one IMEI so it is still present in the phone somewhere.
Any help would be greatly appreciated! Thanks in advance!
Click to expand...
Click to collapse
What version of Pie did you upgrade to and when you downgraded did you flash the bootloader and gpt.bin files? Can you link the post that you followed?

kc6wke said:
What version of Pie did you upgrade to and when you downgraded did you flash the bootloader and gpt.bin files? Can you link the post that you followed?
Click to expand...
Click to collapse
First, thank you for your reply and help in this matter!
After the update from the phone itself, it said it was Android Pie v9.0.0. I don't know anything further than that on which version of Pie if there are several.
When I attempted to flash the bootloader and the gpt.bin during the steps on the forum guide, adb gave me the 'couldn't open' and the 'Failed' result for those two things. Reading one of the replies to this guide, someone stated that they didn't flash either of those and it worked perfectly.
Here is the guide: https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228

Angelo Della Morte said:
First, thank you for your reply and help in this matter!
After the update from the phone itself, it said it was Android Pie v9.0.0. I don't know anything further than that on which version of Pie if there are several.
When I attempted to flash the bootloader and the gpt.bin during the steps on the forum guide, adb gave me the 'couldn't open' and the 'Failed' result for those two things. Reading one of the replies to this guide, someone stated that they didn't flash either of those and it worked perfectly.
Here is the guide: https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Click to expand...
Click to collapse
I have successfully downgraded from Pie PPSS29.55-24-2 to Oreo without flashing those files but today when I flashed the newest Pie PPS29.118-11-1, I got these results.
Only solution was to reflash the latest Pie. If you took the OTA update as it appears you did you are most likely in the same boat I'm in stuck on the latest Pie.

kc6wke said:
I have successfully downgraded from Pie PPSS29.55-24-2 to Oreo without flashing those files but today when I flashed the newest Pie PPS29.118-11-1, I got these results.
Only solution was to reflash the latest Pie. If you took the OTA update as it appears you did you are most likely in the same boat I'm in stuck on the latest Pie.
Click to expand...
Click to collapse
Okay, thank you for the information. Unfortunately I will have to reupdate to P.O.S. Pie. Could you point me to the correct version of Pie that will work? It was the OTA update to PIE that I did so if you could let me know which one you labeled would work, then I can get started. Maybe point me to a guide if you know of one to do it properly.
Thanks a million!

Angelo Della Morte said:
Okay, thank you for the information. Unfortunately I will have to reupdate to P.O.S. Pie. Could you point me to the correct version of Pie that will work? It was the OTA update to PIE that I did so if you could let me know which one you labeled would work, then I can get started. Maybe point me to a guide if you know of one to do it properly.
Thanks a million!
Click to expand...
Click to collapse
I can't tell you exactly which firmware to download, but It looks like you are using the Retail version by your post mentioning "Stock ROM: ALI_RETAIL_8.0.0_OPSS27.104-92-4-5-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". If so I would flash this one.
As for a guide some people use RSD lite but I prefer this method.
download the attachment and extract it
extract the firmware to the folder Place_Extracted_Firmware_Here.
double click 2-rsd-flash-flashfile-windows.bat, this will create a file called flashfile.bat (It will Wipe your data).
boot your phone to bootloader, connect it to pc.
double click the flashfile.bat and let it run
reboot
hope this helps
View attachment RSD_Lite_Motorola_XML_To_Batch_Script.zip

351849091444336

SM-G900F - Need original firmware

Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex

Access to the original/official firmware for SM-G900F would be extremely helpful for me as well.
I'm running LOS 16 with pico GApps very happily on my S5, however I have mobile data connectivity issues. Data connects and disconnects at random; this is device-dependent (swapping the SIM into other devices gives fully functional data connectivity).
My baseband is G900FXXU1BOA3; I believe updating the modem might fix this?

kwajongen said:
Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Click to expand...
Click to collapse
Fox, you may download the official firmware at https://samsung-firmware.org/model/SM-G900F/
Select your region to get the right ***.md5.tar file to flah via Odin latest.
This will reset your handheld to out of box - original recovery reinstalled - you must reflash it also via Odin if you want to go back to custom Rom..
Good luck
.

Thank you.
What would be my region?
I purchased it in the US unlocked, but US is not a choice when it comes to region.
Would I be able to see the region the phone is from from the baseband #?
Alex

kwajongen said:
Thank you.
What would be my region?
I purchased it in the US unlocked, but US is not a choice when it comes to region.
Would I be able to see the region the phone is from from the baseband #?
Alex
Click to expand...
Click to collapse
If your reference to the baseband version# is correct -> G900FXXU1ANCE, then the region is BTU -> check this address to download the original firmware:
https://samsung-firmware.org/downlo...agon-__/1806/BTU/G900FXXU1ANCE/G900FOXA1ANCE/
After flash via Odin, reboot and optional reinstall TWRP via Odin to use other custom Roms.
Are you sure you did everything before resuming to scratch. Personaly I would have done the following:
- back up in TWRP (at least data) + back up in google drive if you use google or titanium, (anyway save your picts, ...) if rooted, it is possible to save the file containing SMS, ... search in XDA,
- format (not wipe) !!!! WARNING THIS WILL ERASE ALL !!!!!
- clean install the ROM (lineageOS or else) + optional Gapps (I use Pico),
- reboot and restore data (as shown in 2 above)
(The Roms I use on my two KLTE by personal preference order are Havoc, DotOS, Bootleggers, Resurection Remix, MSM-Extended. I also use LineageOS.

Captain Kangaroo said:
If your reference to the baseband version# is correct -> G900FXXU1ANCE, then the region is BTU -> check this address to download the original firmware:
https://samsung-firmware.org/downlo...agon-__/1806/BTU/G900FXXU1ANCE/G900FOXA1ANCE/
After flash via Odin, reboot and optional reinstall TWRP via Odin to use other custom Roms.
Are you sure you did everything before resuming to scratch. Personaly I would have done the following:
- back up in TWRP (at least data) + back up in google drive if you use google or titanium, (anyway save your picts, ...) if rooted, it is possible to save the file containing SMS, ... search in XDA,
- format (not wipe) !!!! WARNING THIS WILL ERASE ALL !!!!!
- clean install the ROM (lineageOS or else) + optional Gapps (I use Pico),
- reboot and restore data (as shown in 2 above)
(The Roms I use on my two KLTE by personal preference order are Havoc, DotOS, Bootleggers, Resurection Remix, MSM-Extended. I also use LineageOS.
Click to expand...
Click to collapse
That site is very buggy, if I search my model and enter all the other info I get to Lollipop 5.0, if I click your link, although I am registered, it does not allow me to the link you provided, I mean I can get to it but when I try to login, it takes me back to the home page, so there is no way to get to your same link while being logged in.
How do I get do the download page it is a mystery to me.
Also, how do you know from the base band that it is BTU region?
Thank you
Alex
PS: I managed to use your link in IE, this site is stone age! Unbelievable, never seen a website like this, there are bugs everywhere.

kwajongen said:
That site is very buggy, if I search my model and enter all the other info I get to Lollipop 5.0, if I click your link, although I am registered, it does not allow me to the link you provided, I mean I can get to it but when I try to login, it takes me back to the home page, so there is no way to get to your same link while being logged in.
How do I get do the download page it is a mystery to me.
Also, how do you know from the base band that it is BTU region?
Thank you
Alex
PS: I managed to use your link in IE, this site is stone age! Unbelievable, never seen a website like this, there are bugs everywhere.
Click to expand...
Click to collapse
Men, the subject of resuming to firmware has been discussed and is described in the net literature! e.g. in XDA Q&A.
This discussion is now not a thread anymore but a dialog and I’m sure it will be closed by XDA moderator for redundancy.
The warnings given when you flash a custom Rom are clear. It also implies “before all” to backup, but also keep all materials to resume to original firmware, …. Now I cannot help anymore because you have problem with downloading the firmware.
Last advice – google baseband# - there are probably other web options or torrents
!!!!Also use the thanks button!!!!

kwajongen said:
Hi guys,
My S5 was on 6.0 and have upgraded to 9 Pie but something went wrong (or I screwed up something) and I need to re-upload the original firmware, unless you have better suggestion.
Currently, I have TWRP installed as well as Android 9, however, when I turn my S5 on, I get: Set Warranty Bit:Kernel
It stays there for 30 secs then the phone boots up and everything looks fine, it connects to wi-fi etc.
One other strange thing is that I get a message on the home screen saying: unsupported SanDisk SD Card
I tried a new one, same message.
Before I started this process, I connected the phone to my PC and copied both the Phone and the Card folders, so I am good, data wise.
Basically I was thinking to go back to the very first OS, I think 4.4.2 and then re-load Lineage 16 using TWRP.
If I read the baseband version # is: G900FXXU1ANCE
If the procedure above is correct, would you be able to provide me a link to download the firmware?
I tried all the known sites, but their speed sucks, so I thought to ask here as somebody may have a link.
I will use Odin latest version to install it.
Thank you!
Alex
Click to expand...
Click to collapse
1. Its normal to have the "Set warranty: kernel" text. As my device does too. Just simply ignore it. It won't harm your device.
2. Basically you can search websites that had official Samsung stock firmware. Search your region of your device and (IMPORTANT!) your model, in your case, is G900F. (Wow same as mine but different region, Snapdragon rocks).
3. To your network problem, I think you need to wait. There is no other option.
Thanks!
Edit: https://forum.xda-developers.com/showthread.php?t=2715487
XDA forums has one. Tip: if your region isn't there, the replies have all the filmwares you can have.

Captain Kangaroo said:
Men, the subject of resuming to firmware has been discussed and is described in the net literature! e.g. in XDA Q&A.
This discussion is now not a thread anymore but a dialog and I’m sure it will be closed by XDA moderator for redundancy.
The warnings given when you flash a custom Rom are clear. It also implies “before all” to backup, but also keep all materials to resume to original firmware, …. Now I cannot help anymore because you have problem with downloading the firmware.
Last advice – google baseband# - there are probably other web options or torrents
!!!!Also use the thanks button!!!!
Click to expand...
Click to collapse
I have downloaded the firmware and this evening I will try to upload it and see what happens.
I still I have no answer to my question: how did you figure out that my firmware is BTU?
I mean, I gave you my baseband version #: G900FXXU1ANCE and when you eventually find it in any firmware sites you are given the choice to choose among many countries, expect USA and Canada.
Since I bought the phone in the US I still wouldn't know which country the firmware is from.
Would you mind to shed some light on this?
Thank you!
Alex

OfficialJohnGL4 said:
1. Its normal to have the "Set warranty: kernel" text. As my device does too. Just simply ignore it. It won't harm your device.
Click to expand...
Click to collapse
Thank you for your feedback John.
I am not sure that message is normal, if you google it they all say it is an issue with the firmware and that you need to go back to the stock one to fix it.
Is there anyone else with lineage having that same message?
Also, when I try to format my SD Card, it gets stuck to 40% and then it goes to the homepage.
I tried also a brand new card, same story.
It gives a message but it goes away after a few secs., I believe it is a Java message, but I can try again and take a picture of it.
Thank you,
Alex

kwajongen said:
I have downloaded the firmware and this evening I will try to upload it and see what happens.
I still I have no answer to my question: how did you figure out that my firmware is BTU?
I mean, I gave you my baseband version #: G900FXXU1ANCE and when you eventually find it in any firmware sites you are given the choice to choose among many countries, expect USA and Canada.
Since I bought the phone in the US I still wouldn't know which country the firmware is from.
Would you mind to shed some light on this?
Thank you!
Alex
Click to expand...
Click to collapse
I tell you my experience:
No matter the country you bought your device. As example, I leave in France, I bought mine in Hong-Kong, but choose an international device (G900F).
Before flashing anything, I checked all information in settings and recovery.
Pict below is original out of box G900FXXU1BOC7
Recovery information after latest update G900FXXS1CQD1
It happened recently 2 times my device was stuck because encription issues – I recover by reflashing original G900FXXU1BOC7 via Odin
I personally downloaded firmware as G900F – BTU, because I check the version at each updates and this sticked to BTU ONLY.
May be the site SamMobile will be more meaningful for you, because you see Countries/Operators and updates history.
https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900F/BTU/
For your device, you have to grab the search to find the closest original (which you have) to latest update (if you have it).
For the Kernel yellow tag at warmup, this is done when you flash TWRP. No issues since 2 years operation with that using LineageOS, Havoc, DotOS, AOSP, Bootleggers, RR, ViperOS. If you flash original firmware, it will disappear because twrp is erased and original stock recovery flashed.

kwajongen said:
Thank you for your feedback John.
I am not sure that message is normal, if you google it they all say it is an issue with the firmware and that you need to go back to the stock one to fix it.
Is there anyone else with lineage having that same message?
Also, when I try to format my SD Card, it gets stuck to 40% and then it goes to the homepage.
I tried also a brand new card, same story.
It gives a message but it goes away after a few secs., I believe it is a Java message, but I can try again and take a picture of it.
Thank you,
Alex
Click to expand...
Click to collapse
When it said that you go back to stock one to fix it. Then want if it is not stock? The message is still there. Its normal if you want to install a custom ROM other than the stock one. I reinstall the stock and install custom ROM again once. It still happened.
I don't know how to remove the text but still have a custom ROM tho.
As for the SD card message, I encountered times before. Maybe you need to format using the computer.
Captain Kangaroo said:
I tell you my experience:
No matter the country you bought your device. As example, I leave in France, I bought mine in Hong-Kong, but choose an international device (G900F).
Before flashing anything, I checked all information in settings and recovery.
Pict below is original out of box G900FXXU1BOC7
Recovery information after latest update G900FXXS1CQD1
It happened recently 2 times my device was stuck because encription issues – I recover by reflashing original G900FXXU1BOC7 via Odin
I personally downloaded firmware as G900F – BTU, because I check the version at each updates and this sticked to BTU ONLY.
May be the site SamMobile will be more meaningful for you, because you see Countries/Operators and updates history.
https://www.sammobile.com/samsung/galaxy-s5/firmware/SM-G900F/BTU/
For your device, you have to grab the search to find the closest original (which you have) to latest update (if you have it).
For the Kernel yellow tag at warmup, this is done when you flash TWRP. No issues since 2 years operation with that using LineageOS, Havoc, DotOS, AOSP, Bootleggers, RR, ViperOS. If you flash original firmware, it will disappear because twrp is erased and original stock recovery flashed.
Click to expand...
Click to collapse
When I reflash the stock ROM TWRP is still there. However no "Set warranty: kernel" appeared. Maybe its just when you install a custom ROM or something, I don't know.

OK guys,
Lineage 16 is installed, everything went smoothly, however when I connect the USB, the phone just shows as 'SM-G900F' on my W10 PC and cannot be expanded, basically no Phone and SD Card folders.
I can see them in the phone no problem, but once I connect it, I am not prompted with the usual message on what I want to do, like file transfer etc. and on the left menu appears only the model of the phone.
I had no issues when I flashed the original firmware, so it must be related to Lineage.
I also installed the Android USB drivers, but no go.
Changing the USB Preferences, to PTP or File Transfer only allows me to see the phone, no SD.
I also tried a new SD, no success.
I am stuck again... Jeez it takes days to get this stuff to work, you do one step ahead and another back
Ideas?
Alex

Anyone?
Shall I ask the question in the Lineage section?

'Set warranty :kernel' means you are running a custom kernel. Any modified boot.IMG can cause this message. It doesn't mean you need to use stock room. This appears even in stock rom with magisk or SuperSU.