Database Info

Help! New firmware for Oukitel C3 needed!

Hi all,
I bought Oukitel C3 3 months ago and tried to root it, but in vain. I found my kernel was very new. July or June 2017. (alas, I forgot!). And my phone seems to be built in December 2016 because its serial number is 2016120100940.
I thought in order to root this device, downgrading the firmware was necessary, and tried to downgrade to official ones with SP flashtool. However my phone doesn't boot with any version(except for Nov 16 2016 version, because it can not be downloaded due to corrupt scatter file)!! My phone only lights dimly when holding power button for 5 seconds.
Noticing my hardware is new, I tried to get back to the original state, but I hadn't make a backup copy, so I cannot recover!
Where can I find the latest firmware for Oukitel C3? At least made in this year!
Thanks in advance!
-Tetsuji

Addition:
Exactly speaking, I haven't tested the latest firmware because SP Flashtool gives an error. STATUS_SCATTER_FILE_INVALID (0xC0030001). This firmware was built on Nov 16 2016. This may be the problem.

I experienced the very same problem, but the solution is very simple.
1. Extract your OUKITEL-C3-V1.3-20161114.rar firmware to the desired location (never mind the error message)
2. The extracted files reside inside TWO folders (one inside the other), named "16-11-16 w800d-oq-80A-s06-SD_OUKITEL-C3-V1.3-20161114_多国语言量产软件".
3. Rename BOTH folders. It is sufficient to just delete the Chinese characters from the folders' name.
4. That's all. Flash your phone with SP_Flash_Tool.

Flashing more recent stock rom from sammobile

Hi
Apologies for what is quite a basic question for I'm just trying to get things straight in my head before proceeding.
I have a UK retail S7 G930F, current running stock
Build G930FXXU1DQC4
Baseband G930FXXU1DQC2
Despite the fact this build only has Android security patch level February 2017, and the latest build is from 2018, my device and Smart Switch insist I am up to date, I want to actually make this the case while remaining on stock firmware.
I have used Odin to flash Galaxy phones before but not since I had a Note 2 and Note 3 so I'm a little rusty.
I have Odin 3.13.1 and the zip download from sammobile for build G930FXXS2DRAA for the same CSC region I'm currently on which is XEU.
All the guides for Odin flashing say to only use the AP file and option in Odin. However as my BL, CP and CSC will all be older as well, and I'm simply going from stock to stock can I (or should I) also flash these parts as well?
Thanks.

I need more information. 6 mm and 7 nougat use the same BL and require no upgrade where if you were on lollipop somehow you would need the bl. Please DO NOT run off and start flashing things like BL without help from here first. I have bricked a samsung device so bad I had to replace the motherboard, so I learned the hard way.

Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.

y2kgecko said:
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
Click to expand...
Click to collapse
I get that a lot. I upgraded my s7 to latest n release today and it worked ok.

So, do I just flash AP or everything?

y2kgecko said:
So, do I just flash AP or everything?
Click to expand...
Click to collapse
You need to flash all 4 files: BL / AP / CP / CSC
I do recommend that you flash CSC* and not HOME_CSC*. That way you will reset the phone to factory defaults and it will be ready for future OTA updates.
Backup your files first that you think are important and then start from scratch to configure the phone, install your apps, update the ones on the phone.

[Resolved] #Solved# Any Possible Solution to Downgrade Back to Nougat?

Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:

tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.

spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:

tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse

tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk

I bypassed 360hr Boot unlocking period, maybe it'll work for some of us here

I bypassed the 360 hr period to unlock Bootloader. I made a new Mi a/c and used a older software to do bypass the period. Older softwares have a error asking them to update the unlock tool to the latest version, but this software didn't prompt for such updates, rather unlocked my bootloader the same day I got my device.
Also, Official TWRP didn't recognize my Internal storage, and would get replaced by stock recovery even after flashing lazyflasher. So, I extracted the recovery image form Orangefox zip and flashed via the fastboot mode, and then flashed custom ROM over it, and finally it worked. I am currently on Havoc os v3.8 without google services and Agni Kernel 9.7. I couldn't get any version of Gcam working, although mine is not Indian Whyred version, so am currently using TRcam v7 clone. Everything is working well. I am getting 8-10 hours of SOT, depending on use.
I am not a developer, and am just a newbie, and If this thread could help other newbies like me, I'd be glad. Thanks.
dl.mi-globe.com/dl/rdAy5/mi-globe.com_Xiaomi_Mi-UnlockTool_3.5.1108.44.zip ( I can't attach hyperlink because I have a new account)

Help downgrading encrypted bootloader samsung phone.

Hi all !
Hope everyone have a great day, i have got a samsung galaxy A6 US variant TMB, (SM-A600T) with android version 9, I was trying to root the phone but didn't have the knowledge that this phone can't be rooted because of locked bootloader which can't be unlock with any procedure. So i gave up and just updated my phone to the latest version available of PIE . (Android 9), To tell you more, before it was also on the same version of android 9 but earlier date. I have not updated a whole version of android but just to a latest date of android 9, Android 10 is also available for this phone but i haven't done that yet. The main problem with my phone is that before this update i just needed to charge my phone once in 24 hours, and now after update i need the same phone with same demands to charge it 3 times in 24 hours, Did every optimization for battery, unused apps, extra apps uninstalled, just one google account left, synchronization is off, NFC and near scanning is off, Bluetooth / Wifi is off, GPS is off. Auto update for apps and system software is off. Battery saving mode is enabled, clear cash has been done, factory reset is already done with flashing this version of android with odin tool, and etc every other thing has been tried with no luck, please don't advise for these things as the main problem for me is just the android version itself which i have newly flashed. Because of locked bootloader i can't flash back my older version of android 9 with odin tool, phone gives error of bootloader :
sw rev check fail device 2 binary 5​something like above after many tries the same result. tried my old firmware with the new bootloader but still no luck. (Same error). Any help or suggestions will be greatly appreciated. I am thinking what if i extract the AP of the new flashed firmware and replace the system.img.lz4 with my old firmware's system.img.lz4 to trick the phone and reflash with the new firmware but old system image file, Can this be done ? or i may brick my phone for ever ? what if i take my phone to the outside market and request a z3x flash for the old firmware version ? will that work ?
Please give any accurate solution i really want my old phone back, this locked bootloader has become a really annoying thing for me. I will never buy a phone like this which bootloader's can't be open again. Or if i wasn't able to flash this to my old version i will never use android again in my life, Better option will be to buy an iphone after 17 years of android use.
Thanks in advance.