Develop Bugs

Flashing 5.1.1. DOH 6 failed, bootloop, no recovery mode, ODIN wont flash

The phone does not boot - just shows "an error has occurred while updating the device software" screen.
I got this issue due to unsuccesful flashing DOH6 firmware via Odin
"Download mode" is available, "Recovery mode" is not
I triyed to flash firmware again, but, unfortunately, have no success.
When it boot in "download mode" it shows:
"ODIN MODE
PRODUCT NAME: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0304)
RP SWREV: B:2 K:2 S:2"
It can only go to download mode when charger or pc is plugged in. Boot loop also only accures when plugged in otherwise no sign of life.
I have tried reflash FW several times with this result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then tried this method:
originally Posted by samanbabah
Ok everyone. here is the fix for those stuck at Samsung logo after 5.1.1 update thanks to this person "Tuandung.tran". I had to go to a Vietnamese site and download the file that took me 7 hours to download, I had a hard time translating the site since it was in Vietnamese, so now I want to contribute and help others by saving them time with straight forward tutorial on how to fix the problem that they have.
Ok so here it is:
1) download this file and extract it to your PC ==========> https://mega.nz/#!vIEEBQyT!U5AzPE4iR...__4qiFTfkBupp0
2) go to recovery and delete system files and cache
3) go to download mode
4) open Odin on your PC and click AP to add AP_G925TUVU2COF6.tar that you extracted earlier to your PC
5) with Odin still open add BL_G925TUVU2COF6.tar by clicking BL button
6) click start
7) After Odin is finished, it will reboot your phone. just wait a few minutes and you'll be all set.
Here is the result:
Don't know what the "CM" means at the beginning of the last line, it wasn't there before.
Then tried the same without boot img., it started to flash but during flashing system img. failed again.
Without BL and AP everything flashes nicely.
Flashed S6-UniBase_BOG8_v2.tar kernel with no problem, wich made the triangle with the text "an error has occurred while updating the device software" disappear and took me to the samsung powered by android logo, where it loops for several minutes, then goes black.
Flashed g925t_of6_aou_twrp_recovery_v13.tar, but, it gave me the red text "Recovery is not Seandroid Enforcing"
When i flash G925T_Stock_Recovery_ZiDroid.com.tar text disappears, but still can't go to recovery mode.
I still have hope since frp lock is off and there is at least download mode, the phone reacts, still, am kind of stuck here, no idea, how to proceed.
Any help will be greatly appreciated.

Tried this too, with no success:
originally posted by uniphase
If you continue to have boot up problems after flashing any type of newer stock firmware to your phone using Odin and Smart Switch, like I did, you will have to perform something similar to this fix and break up the files in the firmware tarball into the BL and AP tar.md5 files. I split the COF8 firmware from SamMobile and flashed the reconstructed tar.md5 files to the BL and AP sections in Odin, and it worked!
Procedure:
1. Download the latest stock firmware from SanMobile or another source.
2. Rename the filename extension from xxxxx.tar.md5 to xxxxx.tar and open the tar file with WinRAR, 7zip or another utility that can extract tar files.
3. You should see the extracted files below:
- boot.img
- cache.img
- cm.bin
- modem.bin
- recovery.img
- sboot.bin
- system.img
4. Download the attachment in this XDA thread and extract it somewhere.
5. Place the boot.img, system.img, sboot.bin, and cm.bin files in the bin folder, extracted from the attachment in the XDA thread in step 4.
6. Open notepad or another text editor and create this batch file in the same bin folder. Save the filename as convert.bat or whatever you filename you prefer with a .bat extension.
Code:
tar -H ustar -c sboot.bin cm.bin > BL.tar
md5sum -t BL.tar >> BL.tar
mv BL.tar BL.tar.md5
@ECHO off
timeout /t 3 /nobreak @ECHO on
tar -H ustar -c boot.img system.img > AP.tar
md5sum -t AP.tar >> AP.tar
mv AP.tar AP.tar.md5
7. Run the bat file and BL.tar.md5 and AP.tar.md5 will be subsequently created.
8. Open Odin on your PC and click AP to add AP.tar.md5 that was created in Step 7.
9. With Odin still open add BL.tar.md5 by clicking BL button.
10. Click Start.
The phone should be working after the reboot and get past the Samsung Galaxy S6 edge logo!
This method looked very promising, but flashing failed again, just like anything else i've tried so far.
I took the tar files apart and turned out that the two bin files stops flashing immediately, and the system image goes on flashing till a certain point, then flashing fails.
If i leave out these three files, everything goes fine, if any of them is present, flashing fails.
Also tried kies emergency recovery with serial number, but, it went on till 15%, then failed.
Any ideas?

Are you sure it says "RP SWREV: B:2 K:2 S:2" ?
And not "B:3" in there?
It almost sounds like you're on DOI1 firmware, and can't downgrade to DOH6. At least from what I've been seeing elsewhere. Based on all the symptoms, it really, really sounds like you're stuck on DOI1 firmware.
Considering you're pretty much dead-in-the-water at the moment, I might suggest you just download the DOI1 Odin and flash it. If you're not already locked into DOI1 (as mentioned, can't downgrade DOI1 -> older), then you will be after a successful flash/boot.
But hey, if that brings your device back, then so be it, right?
Good luck, friend. I'm still on OH6, so I can't really speak from experience on this one.

Aou said:
Are you sure it says "RP SWREV: B:2 K:2 S:2" ?
And not "B:3" in there?
It almost sounds like you're on DOI1 firmware, and can't downgrade to DOH6. At least from what I've been seeing elsewhere. Based on all the symptoms, it really, really sounds like you're stuck on DOI1 firmware.
Considering you're pretty much dead-in-the-water at the moment, I might suggest you just download the DOI1 Odin and flash it. If you're not already locked into DOI1 (as mentioned, can't downgrade DOI1 -> older), then you will be after a successful flash/boot.
But hey, if that brings your device back, then so be it, right?
Good luck, friend. I'm still on OH6, so I can't really speak from experience on this one.
Click to expand...
Click to collapse
Yea, you are right mate, it is B:3 indeed.
I'm downloading DOI1 as you suggested, gonna flash it and report back.
Really have nothing to loose with a $600 paperweight...
Thanks for your help, i keep up hope and report back soon!

This is probably the main cause of all the "stuck in animation logo" "bootloop" scenarios, downgrading.
Pp.

I have done everything possible to fix this phone. I was sure this was a excellent and sure fix. I pass ODIN ever time and yet still see a blinking logo.

That's Samsung's firmware protection in action, there just improving security on there phones so that stolen phone's can't be re-flashed and activated.
Pp.

pederzen said:
Yea, you are right mate, it is B:3 indeed.
I'm downloading DOI1 as you suggested, gonna flash it and report back.
Really have nothing to loose with a $600 paperweight...
Thanks for your help, i keep up hope and report back soon!
Click to expand...
Click to collapse
I have downloaded and flashed DOI1.
Unfortunately it is no success, though that funky little green line has never got as far as this time...
It also kooks like cm.bin, boot.img, and recovery.img flashes without problem.
It's very promising.
Attempt #1:
Attempt #2:
Attempt #3:
Sometimes process goes almost till the end. It always hangs while system image flashes.
Dodn't understand why it gets stuck at different points though.
After a few more attempts, i decided to try kies recovery again.
I left the PC on for night since the DL of FW is very slow.
It recognised that device needs DOI1 FW.
It failed again and still, leaved me with no recovery number to use for another attempt on another PC, what normally comes up when such a recovering procedure goes down with no success.
ODIN mode sais "Current binary: OFFICIAL" now.
What would be the next move?
Somebody wrote somewhere to install TWRP recovery, try to reboot into and flash a ROM from there.
Frankly, i'm getting out of ideas, i'm no expert in android or linux, at this point all i do is repeating the few methods that i have found so far, in different order wich, apparently gives me no luck.
Maybe some lower level process could wake my little black darling up from her deep sleep?

OMG!!!!View attachment 3502850
Now waiting to see if it boots up...
4 minutes have passed so far...
Well it seems like stuck on the powered by android screen.
26 minutes passed.
OK, flashed again, passed again and still, it is stuck on samsung screen.
This is great progress, i feel like only the last tiny piece is missing from the puzzle...
I wonder how long it can take the phone to boot after a FW reflash.
Anyways i leave it be for the time being, we'll see what happens.
An hour has passed, nothing happens.
Phone is warm feels like it's working on something or maybe only because of charging.
It doesn't seem like a bootloop since the samsung screen is continously on, it doesn't disappeare and come back.
It just stays.
Strange.

I had read in one the threads that one guy in similar kind if situation deleted the cache partition from the tar file, repacked and flashed and it booted up. According to him cache partition was preventing it from booting. May be worth a try..
Sent from my SM-G925T using Tapatalk

Alex9090 said:
I had read in one the threads that one guy in similar kind if situation deleted the cache partition from the tar file, repacked and flashed and it booted up. According to him cache partition was preventing it from booting. May be worth a try..
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Sounds like a plan
Give it a shut and report back soon.
Thanks for your help!

PanchoPlanet said:
That's Samsung's firmware protection in action, there just improving security on there phones so that stolen phone's can't be re-flashed and activated.
Pp.
Click to expand...
Click to collapse
Correct me if i'm wrong but if it was Samsung's firmware protection, FRP lock would be ON.
In my case it sais OFF.
Otherwise i agree with you these cases are 95% FW/downgrade related.

@pederzen, that's awesome that you've made progress, but I'm starting to question some things...
Are you sure you've got a good cable, and that it's well-connected to the device? To be sure, maybe snag a different cable, and don't touch it while flashing.
The fact that it's passing the md5 check suggests that the file did not get corrupted upon download, but I'm wonder if something is breaking it while it's flashing? How's your RAM/memory, are you overlocking or anything? Also, you might disable all antivirus/antispyware and disconnect from your network(s)/internet before even opening Odin.
Be sure you've got the correct version of Odin. Last I knew, v3.10.6 was working great for OH6.
Got drivers? Might double-check your device drivers for the device and such. A long shot on this one, because it's usually all-or-nothing.
Maybe just try a different computer if you can.
The fact that it's failing during system partition is the most disturbing thing. I'm doubting that your last "Pass" was actually successful.

@Aou
Tried two computers, several cables still the same.
When flshing hangs, a few seconds pass, unknown USB device sign comes up.
Went to samsung page, DL-ed, installed latest driver.
Now it sais in device manager:
'Device USB\VID_04E8&PID_685D\5&106f75ea&0&4 requires further installation.'
Whether it is connected in Odin mode or in normal mode when the screen with the triangle is on saying that installation went wrong...bla-bla
Checked events after driver installation, it sais:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-10-12T11:05:28.095021600Z" />
<EventRecordID>7178</EventRecordID>
<Correlation />
<Execution ProcessID="5172" ThreadID="6744" />
<Channel>System</Channel>
<Computer>PUDVAS</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>ssudbus.inf_amd64_6c8cd03f9c562c7a\ssudbus.inf</DriverName>
<DriverVersion>2.11.10.0</DriverVersion>
<DriverProvider>SAMSUNG Electronics Co., Ltd.</DriverProvider>
<DeviceInstanceID>USB\VID_04E8&PID_685D\5&106F75EA&0&4</DeviceInstanceID>
<SetupClass>{36FC9E60-C465-11CF-8056-444553540000}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>true</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>SAMSUNG Mobile USB CDC Composite Device</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>
Maybe those two lines with 'false' at the bottom are supposed to be 'true'.
Might this be the cause of all the problems or, this is normal.
Shall i try to solve this driver issue first?
(If there is an issue at all.)
The rest what you wrote seem to be in working order.

pederzen said:
Correct me if i'm wrong but if it was Samsung's firmware protection, FRP lock would be ON.
In my case it sais OFF.
Otherwise i agree with you these cases are 95% FW/downgrade related.
Click to expand...
Click to collapse
In order to mess with your phone the option should be "on" , that denotes that Samsung's "FRP" with be deactivated and no interference will take place or bricking.
If it's "off" then you run the risk of borking your phone.
Off, no good.
On, ok.
Another thing running Windows 7 on my Asus, my device manager recognises my (stock) phone as a Samsung device.
Pp.

This is what you want in developer options.
Pp.

pederzen said:
@Aou
Tried two computers, several cables still the same.
When flshing hangs, a few seconds pass, unknown USB device sign comes up.
Went to samsung page, DL-ed, installed latest driver.
Now it sais in device manager:
'Device USB\VID_04E8&PID_685D\5&106f75ea&0&4 requires further installation.'
Whether it is connected in Odin mode or in normal mode when the screen with the triangle is on saying that installation went wrong...bla-bla
(snip)
Maybe those two lines with 'false' at the bottom are supposed to be 'true'.
Might this be the cause of all the problems or, this is normal.
Shall i try to solve this driver issue first?
(If there is an issue at all.)
The rest what you wrote seem to be in working order.
Click to expand...
Click to collapse
Well, the fact that you've tried two different computers does narrow things down a tad, except the antivirus/antimalware thing, if you happened to be running the same on both PCs.
As for that specific driver (the CDC one), I've got 2.12.0.0 on my computer, but this is on Win10 at the moment. I could probably check my Win7 installation, but I'm not physically in front of my computer at the moment and can't reboot into Win7 from here.
Usually Samsung Smartswitch (Kies) will force you to get the latest/proper drivers for the device. Do you have the latest version of SmartSwitch?
As for the "false" parts there, that shouldn't matter, I wouldn't think. Odin itself does have an option about rebooting after a successful flash, though.
I believe the behavior you're seeing - where upon an unsuccessful flash you see another device show up - is the device trying to go into some sort of emergency download mode. Like, a more fundamental download mode that Samsung can use to forcefully flash things to the phone to try to revive it. I've had some older Samsung phones do that before upon a bad flash of firmware.
Are you familiar with how to tarball an image for Odin? I'm thinking you might try to re-package only the system.img into a new tarball, and flash that alone. From a CygWin terminal, or in a Linux environment (say hello to VirtualBox and Ubuntu!), you'd do something like this:
Code:
tar -H ustar -c system.img > DOI1_system.tar && md5sum -t DOI1_system.tar >> DOI1_system.tar && mv DOI1_system.tar DOI1_system.tar.md5
Or you could skip the md5 generation and just do:
Code:
tar -H ustar -c system.img > DOI1_system.tar
Of course, the above implies that you extracted the system.img from the Odin package. The .zip file contains the .tar.md5 (of course), and you can use a tool like 7-zip to open that md5'd tarball. You'll probably see warnings/errors about an improper ending to the tarball, but that's because of the md5 hash that's been literally just slapped onto the backside of the tarball. Safe to ignore that.
Let me know if you need me to do this and upload it, but it would take me a little while.

Here is the system.img tar file according to Aou's instructions. You have to unzip it.
System.img

Thank you friends! You guys are wonderful.
I'll give it a shot when i get home this afternoon (EU time)
Let's hope this will give it the final push!

Alex9090 said:
Here is the system.img tar file according to Aou's instructions. You have to unzip it.
System.img
Click to expand...
Click to collapse
Mega requires a key for the download, can you give it please?
Tried 'Don't look back in Anger' but didn' work

[HELP] Unbrick Huawei GR3 (TANGO) - TAG-L23

Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)

COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck

Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.

antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520

I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.

I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?

Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)

Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.

srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?

cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.

Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.

GUIDE: How to unbrick your Zenfone 6 (ZS630KL)

Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.

Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...

Thanks for the link to that service firmware!

_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?

Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!

Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?

For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.

Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.

This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?

kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem

sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?

kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10

Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.

CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.

_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/

CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?

_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds

Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.

After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?

Installing Custom ROM on Cubot KingKong Mini

UPDATE 2021
The original post was for the first King Kong Mini, for instructions for the King Kong Mini 2 go to page 9 in this thread:
https://forum.xda-developers.com/t/...-on-cubot-kingkong-mini.4050815/post-84445303
======================
The Cubot King Kong Mini was released in Q4 2019. It is one of the smallest Android phones on the market with a 4" screen. Like many cheap Mediatek devices, one cannot be sure of how "safe" or "secure" these devices are, so the security/privacy conscious may want to consider installing a custom ROM. Here are the instructions for installing Android AOSP on the Cubot King Kong Mini. Note: I am not responsible for any bricked devices.
Download the Stock Rom from here and SP Flash Tool just in case you need to reinstall Stock. Download a system image, note you need to use an A/B arm32 image with 64 bindings. For example AOSP 9 is here.
This process probably can be done with SP Flash Tool but I wasn't able to manage it due to the disable-verification flag required.
Unzip the stock ROM and reboot the device to bootloader, connect via USB and unlock via:
Code:
sudo fastboot flashing unlock
Note this will erase all data. Then on your computer navigate to the folder with the unzipped ROM (for me was NA_mt6761p_d936p_9101cmp_chuanqi_cc_256gbitp24d3_p_lte_3m-fdd-cs_mul_20191121-210020_songlixin_PC) and type
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you do not do this it seems to work without it but then it will bootloop when you try to switch it on. From here on it's standard.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Unzip the .xz image file you wish to use and type:
Code:
fastboot flash system SYSTEM.img
where SYSTEM is the name of whatever image downloaded.
Root
For root install magisk manager and you have to patch the recovery to get root (not just boot as flashing boot alone doesn't give you root). So in magisk get it to patch you boot and recovery images and then put those on your computer, go to bootloader and use:
Code:
fastboot flash boot magisk_patched_boot.img
fastboot flash recovery magisk_patched_recovery.img
You can read more about magisk from recovery here.
To get root then you need to reboot to recovery, hold power button + volume up and select Recovery. This will appear to boot as normal but you will have root when you do it this way and not when you boot normally. Unfortunately I do not have reception when I do this but do have root, other users have this problem but I have not found a solution.
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
What doesn't work
Battery usage doesn't work, this can probably be fixed following this guide. If I get time I will attempt this.
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
The battery life is definitely worse using AOSP GSI than stock, maybe that vendor overlay would help with that though.
I hope that helps others.

TWRP+Encryption Disabling+Magisk Root
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.

well well, finally and serranoltexx successor?
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]

moctir said:
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
Click to expand...
Click to collapse
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/

robrazil said:
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/
Click to expand...
Click to collapse
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!

Tom Mix said:
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
Click to expand...
Click to collapse
I did it to replacement my old Samsung J1 ace, very similar of S4 Mini, and I'm not regretful for that.
---------- Post added at 01:37 PM ---------- Previous post was at 01:08 PM ----------
moctir said:
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
Click to expand...
Click to collapse
I understood but the point is if the TWRP source is confiable. I asked the official TWRP Team about the unofficials TWRP on websites in my last post, and they answer: "Hello, we do not run that site, so I cannot confirm the validity of their images."
So, I wonder how safe the unofficial TWRP images are.

moctir said:
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
Click to expand...
Click to collapse
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:

robrazil said:
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:
Click to expand...
Click to collapse
Yes, indeed there were three times I thought I had totally bricked and each time I was so annoyed with myself! The key is to not charge it much until you are happy with the ROM you put on.
The amount of drivers I tried to use for different OS' when I got that "unknown USB device" on Windows and Linux didn't detect it was all a waste of time!

Well... the battery image appeared again and I uploaded firmware again. I installed the Magisk in the boot recovery, because this only way to install the Magisk on devices that are using system-as-root, but the Magisk disable my 2 SIM cards. When I boot without Magisk, all back to normal.
I serched for any solution for that but I didn't find.
So, my conclusion is that the Magisk not works to Cubot King Kong Mini. How can I stay with a phone with no SIM card?
I give up.

For me I can only get root when I patched Magisk to Recovery and then boot to Recovery and it doesn't see my SIM card but I have root, so I reboot every time I need root which is a bit annoying...

It is very complicated everytime when need "root", to have power off and on the mobile in recovery boot mode. Besides that, run out of SIM card working is not an option.
I will try to get support of this issue with Magisk Team.
Thank you for share your experience.

Ce3apyc said:
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.
Click to expand...
Click to collapse
Hello,
Does anybody can confirm, that this is working with the new firmware?

I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.

moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?

Ce3apyc said:
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
Click to expand...
Click to collapse
I'm using treble AOSP Android 9 so not the latest firmware. I thought disabling the verification when installing that would be enough but maybe I do need to do those other steps. I can see the /system directory through TWRP so that's probably because that's the one I flashed, but I can't see the internal storage otherwise.

moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

robrazil said:
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
Click to expand...
Click to collapse
Thanks, I'll check it out!

Anyone else having problems with sensors on this phone? Rotating and compass do not work for me. That's what you get for buying a cheap Chinese phone, I guess.
EDIT: Downgrading firmware back to CUBOT_KINGKONG_MINI_9101C_V06_20191121 seems to fix some problems, rotation works, but compass is still buggy.

Never tried compass but haven't had any problems with rotation.

Tried to install root on a friends kkm but I can't get it working in the os. Is there any chance to get it working there? I am only able to get root access in twrp. Maybe an gsi with root is that possible?

Help to unlock OEM on Samsung Galaxy 10.1 (2014) SM-P605 ?

I am unable to unlock OEM on my Samsung Galaxy 10.1 (2014 edition) SM-P605 Tablet and I am looking for help.
Details:
This old Samsung Galaxy 10.1 2014 Tablet (European SM-P605) has the stock 5.1.1 Android (Android security patch level 2017-04-01). I would like to replace the old android with LineageOS, but first I need to unlock the bootloader, which requires me to unlock the OEM.
However I have failed to unlock the OEM, despite following various internet guides (ie putting tablet into developer mode, and if OEM unlock doesn't show up try various Date/Time changes (to the past) + Auto Software update disable, plus trying this many times if it fails to work the first time). OEM unlock never shows up.
wrt seeing the Tablet from my PC, I have tried over a dozen USB cables between PC and Tablet where a few cables will let me see the tablet on my PC (ie I obtain a USB notification and adb can see the Tablet).
As noted, I have adb installed on my GNU/Linux PC and when Samsung Galaxy 10.1 2014 Tablet is running nominally with the cables that work connected between Tablet/PC, in a bash shell on my PC I can see:
Code:
corei7:/home/user # ./adb -d devices
List of devices attached
6fa80ec0 offline
However fastboot, of course, can not see the Tablet as the Tablet is not in download/odin mode.
But when I hold power and volume-down button to successfull reboot to odin mode from that point and on, I can no longer see the Tablet with adb nor can I see it with fastboot (in the bash shell on my PC - the Tablet is also no longer a detected USB device).
Regardless, I do not believe/speclate this to be a PC issue (ie not a Linux nor MS-Windows issue) but rather I think/speculate this issue of fastboot (and adb) not seeing the Tablet in downoad/boot mode is because OEM is still locked. But I can't unlock OEM.
Is there an app I can install to unlock the OEM ?? ... because following the recommended developer/date-time/software-update/reboot sequences on the Tablet all fail (in all orders of combinations), despite many dozens of attempts.

Further to the above, I also tried clearing the cache, and tried a Factory reset, then repeating the advised (from internet searches) recommended developer/date-time/software-update/reboot sequences on the Tablet, which all also still fail (in all orders of combinations), despite various attempts. The OEM lock still does not show up under ' general > developer options '.

Researching this I learned finding the OEM unlock is nominally simple with a Eyxnos CPU in this Tablet, but purportedly difficult (not possible? < unsure > ) with a Snapdragon CPU. My Tablet has a Snapdragon 800 (2.27 GHz) which may be part of the reason I havent solved this.

oldcpu said:
Researching this I learned finding the OEM unlock is nominally simple with a Eyxnos CPU in this Tablet, but purportedly difficult (not possible? < unsure > ) with a Snapdragon CPU. My Tablet has a Snapdragon 800 (2.27 GHz) which may be part of the reason I havent solved this.
Click to expand...
Click to collapse
afaik this old device (same as mine) has no OEM unlocking option.
I just flashed TWRP and carried on.

bmwdroid said:
afaik this old device (same as mine) has no OEM unlocking option.
I just flashed TWRP and carried on.
Click to expand...
Click to collapse
Interesting. Thanks for the note on your experience.
Its old and unused, so I guess I do have nothing to lose. I am currently charging it up, and once its fully charged I will give it a try.

Hello,
I was looking for the same information as you for my Galaxy Note 10.1 SM-P600 and I also think that there is simply no OEM unlock.
However, I can't flash TWRP via Odin, I get a "FAIL" message every time I try. I have to reflash the official firmware to reboot the tablet otherwise I get an error telling me to connect it to Kies....
Can anyone know where my error comes from? (the tablet is not rooted)

Mkj76000 said:
... However, I can't flash TWRP via Odin, I get a "FAIL" message every time I try. I have to reflash the official firmware to reboot the tablet otherwise I get an error telling me to connect it to Kies....
Can anyone know where my error comes from? (the tablet is not rooted)
Click to expand...
Click to collapse
Gotta provide more info.
Which Odin version?
Complete! TWRP filename?
I read it's recommended not to have KIES installed when using Odin but standard Samsung phone drivers only.

Sorry. I have Odin 3.14.4 It looks like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As for TWRP, this is the latest version that I have downloaded here : https://eu.dl.twrp.me/lt03wifiue/
The file is twrp-3.6.0_9-0-lt03wifiue.img.tar
I haven't installed Kies, I was just quoting the error message displayed on the tablet. I restored it via Odin with the latest version of 5.1 from February 2019 (XEF France)
I did manage to install CWM touch from this link (latest version) via Odin. I then tried to install TWRP from CWM via a zip file (also found on the TWRP site link above but it's version 2.8.7). I was able to boot into TWRP but the touchscreen doesn't work so it's unusable.
I am out of ideas, thanks in advance for your help.

Mkj76000 said:
Sorry. I have Odin 3.14.4 It looks like this : View attachment 5531771
As for TWRP, this is the latest version that I have downloaded here : https://eu.dl.twrp.me/lt03wifiue/
The file is twrp-3.6.0_9-0-lt03wifiue.img.tar
I haven't installed Kies, I was just quoting the error message displayed on the tablet. I restored it via Odin with the latest version of 5.1 from February 2019 (XEF France)
I did manage to install CWM touch from this link (latest version) via Odin. I then tried to install TWRP from CWM via a zip file (also found on the TWRP site link above but it's version 2.8.7). I was able to boot into TWRP but the touchscreen doesn't work so it's unusable.
I am out of ideas, thanks in advance for your help.
Click to expand...
Click to collapse
Did you reinstall stock as one(if available at all) or multiple part file?
I always use multiple parts after having trouble with a one part file.
You've put twrp in Odin AP didn't you?
Never worked with philz-touch so idk if it can replace itself with/by flashed TWRP...zip.
Tested older TWRP...tars as well?
Btw: On these old devices I always use Odin 3.09 which always worked.

I was only able to download a rom in one file. If you have a site where I can find a rom with several files I can try.
I also tried to flash an old version of TWRP (2.8) via Odin but it doesn't work.
I have just tried again with Odin 3.09, same error.
Every time I use the AP box

Mkj76000 said:
..... If you have a site where I can find a rom with several files ......
Click to expand...
Click to collapse
Using samfirm_reborn_0.3.6.3 checking "binary nature" and "automatic decryption" will give you a zip file containing the 4 files.

bmwdroid said:
afaik this old device (same as mine) has no OEM unlocking option.
I just flashed TWRP and carried on.
Click to expand...
Click to collapse
Thanks again. After following your advice I finally managed to install LineageOS. I stayed with the older LineageOS v.14.1 with android 7.1.1 as I wanted the tablet's camera to work.
Because I am only a GNU/Linux user (I don't do Windows ) I strugged a bit with various guides as almost all are for MS-Windows users to install TWRP.
Installing TWRP from Google Play store, without Tablet rooted did not give sufficient permissions for me to Flash that was consistent with various guides I read. I could not get Magisk (a program that is supposed to give root permissions) to give me full root permissions for TWRP. And for a while it seemed like I was stuck in a 'chicken before the egg' situation (as some guides suggested installing Magisk from TWRP).
Connecting my PC to the Tablet, I also tried adb and fastboot from GNU/Linux - where adb worked but fastboot did not. In the end I installed heimdall and that worked for me under GNU/Linux. To get to this point I had to try various USB cables and use a USB-2.0 port (instead of a USB-3.0 port) on my GNU/Linux PC.
Trying to flash with " --RECOVERY" specified in heimdall did not work for me, but after downloading from Tablet to PC, and looking at the Tablet's PIT contents, I noted 'RECOVERY' (with recovery.img) in "Entry-14" on my specific tablet. Armed with that information, when instead I specified "14" in heimdall (instead of "RECOVERY") I was pleasantly suprised to discover on a Tablet reboot that TWRP installed in the Tablet's boot loader.
Once TWRP was installed it was simple to then flash with TWRP the files for lineage-14.1-20210320-UNOFFICIAL-lt03lte and open_gapps-arm-7.1-stock-20220122 (clearing cache ... etc ... as appropriate per various web instructions). I prevously had placed those ZIP files on the Tablet's storage.
It was quite the adventure and took some time, however eventually success.
If it had not been for your recommendation / observation that there was no OEM unlocking option I would still be stuck there. Many thanks for your help !!

For the record (in case anyone with same Tablet is curious) this is what I did to install TWRP and LineageOS on my Samsung Galaxy 10.1 (2014) SM_P605 (Snapdragon 800) tablet (after obtain helping on this forum not to worry about OEM mode).
I used openSUSE LEAP-15.2 GNU/Linux to flash TWRP-3.2.3-0 on to the tablet. Once TWRP was installed I booted the Tablet to TWRP and used TWRP to flash lineage-14.1-20210320-UNOFFICIAL-lt03lte and open_gapps-arm-7.1-stock-20220122.
Details:
On openSUSE-LEAP-15.2 GNU/Linux I installed android-tools ( https://software.opensuse.org/package/android-tools ) and heimdall ( https://software.opensuse.org/package/heimdall ).
I pre-installed in the Samsung tablet storage (root location) the files: lineage-14.1-20210320-UNOFFICIAL-lt03lte.zip and open_gapps-arm-7.1-stock-20220122.zip . In hindsight I should also have pre-installed a TWRP.zip version, but I failed to do so.
I spent some time checking my various USB cables to pick the best one wrt reliability for copying data/charging devices, and I used a USB-2 port, and not a USB-3 port for connecting my GNU/Linux PC to the Tablet. I previously read that could make the difference in ensuring a successful effort.
I note this was the previous Tablet state when booting to ODIN mode:
Code:
ODIN MODE
PRODUCT NAME: SM-P605
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENBALE (CSB)
RP SWREV: S2, T2, R2, A2, P2
SECURE DOWNLOAD : ENABLE
UDC START
As near as I could determine, there was no custom bootloader (boot loader may even have been locked ?? ) and the tablet was not rooted.
With the Tablet running I plugged the USB cable into the Tablet. I noted a popup in KDE desktop on my GNU/Linux detecting the Tablet.
I prepositioned in my GNU/Linux PC, in a directory (in which I was to open a bash shell) the TWRP file: twrp-3.2.3-0-lt03lte_20180923.img
On my GNU/Linux PC I opened a bash shell and I typed:
Code:
sudo adb reboot bootloader
That rebooted the Tablet to "Download" (I think also refered to as "FastBoot mode" ). There was no KDE popup this time. However typing :
sudo heimdall detect
gave me an indication that the Tablet was detected by heimdall.
In that same bash shell I then typed:
sudo heimdall print-pit
I scolled through the resultant "pit" output and I found an entry with "RECOVERY" and "recovey.img" (Entry-14). ie
Code:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 268288
Partition Block Count: 26624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
Seeing 'Recovery' in 'Entry-14', in that same bash shell I then typed:
Code:
sudo heimdall flash --14 twrp-3.2.3-0-lt03lte_20180923.img --no-reboot
The Tablet seemed to hang there with a blue line indicating flashing ? I waited a few minutes and there was no further indication on the Tablet display. I thought the flash failed, so I held down the power off to shut down and restart the tablet.
The Tablet to my surprise, rebooted to TWRP. I don't know precisely what caused that (as I described what I did above with a power-off to restart), but I decided to immediately take advantage of the tablet booting to TWRP.
At that point I followed the regular instructions on the Internet for flashing LineageOS on the Tablet from TWRP ... ie using TWRP, to WIPE data, clear CACHE, and flashed lineage-14.1-20210320-UNOFFICIAL-lt03lte.zip with NO reboot specified. I cleared CACHE again (possibly not needed) and then flashed open_gapps-arm-7.1-stock-20220122.zip . Unfortunately I did not have a "TWRP.ZIP" prepositioned on the Tablet, so I was not able to flash that next. I suspect this was a mistake on my part, and if I wish to update again, I will again need to go through the above to put TWRP on the table.
I then rebooted the tablet (disconnecting from PC) and it booted to LineagOS-14.1 (with android-7.1.2).
I am pleased the Tablet camera functions with v.14.1.
I believe with the current flash that TWRP is no longer installed. I have not checked the Tablet's updated PIT output.
I do note the ODIN mode on the table is almost the same, except for Knox warranty void entry which reads "KNOX WARRANTY VOID: 0X1 (1)"
Hopefully the above may help someone - although no guarantees as it could brick your device for all I know. Fortunately it did not brick mine.
==== =====
Prior to the above, what did not work for me with stock Samsung Android 5.1.1:
- fastboot, that came with Android tools, would not work for me when the Tablet was in 'Download'/'ODIN mode'. That is why I switched to using heimdall.
- I tried to root the Tablet prior to installation with Magisk (downloading from the web) but that rooting failed. I tried installing (from Google playstore) TWRP on the Tablet, but it kept saying no root permissions and would not give me flash capable options. I was unable to install Magisk with TWRP (from Google playstore) as I had no root permissions on the tablet. I did not want to use other 3rd party root apps as I was concerned about possible maleware. That is why I ended up using a PC to flash TWRP.
- I tried to flash TWRP with
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-lt03lte_20180923.img
and also with
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-lt03lte_20180923.img --no-reboot
and neither worked.
The first gave an indication that the PIT file was successfully downloaded and that RECOVERY upload was successful, but in fact if failed, as the Tablet would not go to TWRP during a reboot.
In the case of the second heimdall, the tablet just hung for over 10 minutes with a blue bar, so I simply restarted the tablet.
Only by specifying the "14" (from Entry-14) was I able to get heimdall to work for me (having previously determined the RECOVERY was in entry-14).

Hello,
I finally managed to get around my problem.
I managed to install TWRP 3.4.0 via the official TWRP application after flashing CWM with Odin...
I haven't tried to update TWRP to 3.6.0, it's an old tablet that will be replaced soon so I'm not going to procrastinate on it.
So I finally managed to install Lineage OS 17 without any problem (and Magisk). Laborious but functional.

Mkj76000 said:
Hello,
I finally managed to get around my problem.
I managed to install TWRP 3.4.0 via the official TWRP application after flashing CWM with Odin...
I haven't tried to update TWRP to 3.6.0, it's an old tablet that will be replaced soon so I'm not going to procrastinate on it.
So I finally managed to install Lineage OS 17 without any problem (and Magisk). Laborious but functional.
Click to expand...
Click to collapse
Is your version the Verizon? I've been trying to flash a rom for years now