Develop Bugs

Solved -- I managed to really break this one... help appreciated.

Solved
DEVICE INFO: LG-V521 - LG G Tab X 8.0 T-Mobile
I can get my tablet into fastboot, that is it.
What happened?
* I could not get custom roms to boot(like not even the boot screen for them, it would just reboot into TWRP over and over no matter what rom I tried to install.
* I then reflashed my recovery via TWRP to a different version of TWRP(now TWRP wont load at all either).
Now my tablet only shows LG logo screen, and fastboot..... I don't know what to do.
Any and all help is appreciated.
PS C:\Users\admin\Downloads> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (14106 KB)...
OKAY [ 0.458s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.464s

PlasmaStrike is my roommate and he must have been logged on already when I originally posted. Okay sorry this is a bit confusing to me, I managed to get the tablet into Download Mode after holding volume up and fanatically pressing and depressing power button at the same time (This tablet is horrible about acknowledging the commands to put it in its menu's). It finally went into download mode(Thank the gods it wasn't soft bricked). I was successful in getting the stock ROM installed and re-applied TWRP successfully. So basically the reason I couldn't get fastboot to apply TWRP to recovery is that, LG the device manufacture doesn't actually have fastboot... so you have to do exploits in the stock ROM to get the boot-loader and all of the nity gritty stuff online through that instead, really stupid if you ask me but ehh i'm not LG.
So for sanity sake should anyone ever need the files, drivers and instructions to fix this type of problem in the future:
The following contain a mirror of: stock ROM, Flashing Software, Instructions, Drivers, & one Custom Rom I have used.
One is Mega and the other DIAU.NET is my own server, if you have a really fast connection just use mine so you get it faster.
Mega: LINK
DIAU.NET(Fastest): LINK

Lenovo K8 Note Red State Bootloop After Flashing Custom Recovery

Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/android/help/lenovo-k8-note-stuck-boot-logo-flashing-t3751324/post75974342#post75974342" and found this
The bootlogo issue.
Hey! I read your post regarding your k8 note being stuck at the bootlogo.
Consider that you can still use TWRP, boot into it.
Then go ahead and download the SuperSU zip on your PC/laptop and connect your phone with a USB. You might be able to see the SD card folders on your PC, then you can just copy and paste it to the internal sd and flash it. You'll be good to go. If that doesn't work, in the TWRP Mode, go to advanced and select ADB sideload. You can now flash using ADB sideload.
Search for tutorials on ADB sideload. It's easy and that should work.
Click to expand...
Click to collapse
solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks

beingfhd said:
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/an...-flashing-t3751324/post75974342#post75974342" and found this solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
Click to expand...
Click to collapse
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.

Thanks
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?

beingfhd said:
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
Click to expand...
Click to collapse
No you can't

k8 note stuck on bootloop...??
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....

DeepRBasak said:
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
Click to expand...
Click to collapse
This might be helpful https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839

thank u somuch am also mobile sevice man it help full for me
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse

I have the same problem. please help us!

HARDROCK2614 said:
I have the same problem. please help us!
Click to expand...
Click to collapse
What problem do you have, please describe

I have lost all my mind and need serious help.
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.

custom619 said:
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
Click to expand...
Click to collapse
I couldn't find more about the problem online, can you please upload a screenshot of the error. Try using the latest version of SP Flash Tool and see if the problem persists

I have lost all my mind and need serious help.
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd

custom619 said:
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
Click to expand...
Click to collapse
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033

Anas Rahman said:
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.

I have lost all my mind and need serious help.
custom619 said:
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
Click to expand...
Click to collapse
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.

custom619 said:
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
Click to expand...
Click to collapse
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds

Anas Rahman said:
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Click to expand...
Click to collapse
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:

custom619 said:
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
Click to expand...
Click to collapse
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official

Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
I Already tried this thread you suggested. No outcome.

Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
This group is possibly dead. No one has responded till today...

Rooting Blackview A20

I have a blackview A20 which is a low spec phone running android oreo go.
I would like to use this phone for experimentation with android development and learning about android on a cheap device without risk of breaking my main phone. To do this I would like it rooted and as a bonus with a custom recovery so I can test custom ROMs.
State of device:
Unlocked bootloader
Unchanged ROM
Unchanged Recovery
OEM unlocking enabled
USB debugging enabled
What I have tried:
Flashing recovery images with fastboot
Using fastboot flash recovery recovery.img with some TWRP and CWM recovery images all yield:
target reported max download size of 134217728 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.169s]
writing 'recovery'...
OKAY [ 0.276s]
Click to expand...
Click to collapse
finished. total time: 0.448s
or similar. Then I restart phone and select boot into recovery mode. The phone hangs for a small while before restarting and booting into the normal OS. On restart into recovery the unchanged recovery is there still.​
Various 'one-tap' methods
All of which were unsuccessful. If needed I can give details.​
Installing SuperSU zip from recovery
In a futile attempt I tried to use the android recovery to push a SuperSU zip with its update from zip option. I knew this wouldn't work but I found something interesting. On the Apply update from SD card option I get an error saying couldn't mount /sdcard​
Booting recovery images with fastboot
I have tried the fastboot boot recovery.img command to try to boot directly into the images. I get this
downloading 'boot.img'...
OKAY [ 0.211s]
booting...
OKAY [ 0.047s]
finished. total time: 0.261s
Click to expand...
Click to collapse
output but the device just restarts and boots normally into the normal OS.​
What I would like from this question (In order of importance):
A way to root the device
A way to access a custom recovery (even if temporary)
Ability to install custom ROMs
A permanent custom recovery

mejakep said:
I have a blackview A20 which is a low spec phone running android oreo go...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads helpful because they, apparently, are compatible with your specific device. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3709659
https://forum.xda-developers.com/showthread.php?t=3767690
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Hello,
I'm also trying to root the Blackview A20 with no success. Where you able to find a way?
Thanks!!

I'm afraid I still haven't found a way. Other than TWRP or something making a custom recovery specifically for this phone I don't see a way to root it at all. Sorry

I have a Blackview A20 Pro (note this is probably different in specification to the A20) - Here is how I rooted it by using Magisk on a boot image read and written using SPFlash tools. I had previously unlocked the bootloader on the phone by using the Developer option for OEM unlock and then fastboot unlocking as standard.
- Obtain the MT6739_Android_Scatter file from an archive of the a20 stock rom available by googling
- Install Magisk manager apk on the phone
- Run the latest version of SP Flash tools on the PC with the associated drivers. Load the scatter file in to it.
- Work out the size of the boot partition by subtracting the start value of the next partition (Logo) from the start position of (Boot)
- I did using Windows calculator in programmer mode - set to hex, subtract the two values. Note the start position of the boot partition
- Go to the Read Back page, add an item to read back, enter a filename to save it like a20-stock-boot-image.img and then enter the start position of the boot partition and the size you calculated. Make sure to get them exactly correct and avoid changing the number of digits in the entry box as I don't know how fussy sp-flash tools is.
- Unplug the phone from PC if it is plugged in and remove the battery.
- Tell SP Flash tools to start the read-back
- Plug the phone in, within a few seconds it should read and save the boot partition from the phone. Keep this backed up. File should be something between 8-25mb I would expect.
- Put the battery in the phone and power it up and unplug/plug it in to the PC via usb and then in the notification area on the phone select "Transfer Files" from the very bottom so it appears to your PC as a drive.
- Drag over the stock boot image from your PC somewhere on the phone - like the Downloads folder.
- On the phone open magisk and select install - when prompted select to use local boot image, select the stock boot image file you transferred
- Magisk should now patch this file - make sure the text it outputs looks like it recognized the boot image and is working.
- Now unplug and replug the phone to PC as I found PC doesn't seem to see new files on the phone. Pull over the patched boot image Magisk has made. Don't worry if this is smaller than the original file. The extra bytes were likely just zeros.
- Using SP Flash tool, go back to the Download screen and select the patched boot image for the boot partition. This will write the new boot image to your phone.
- Power down the phone and remove the battery.
- Tell SP flash tool to start and then plug the phone in with no battery. It should then flash the patched boot image.
- Put the battery back in and boot the phone. When you open magisk app on the phone now it should say you are rooted.
Enjoy!
If it doesn't work, repeat the download process with the stock boot image you saved and that should restore things to how they were before. I assume if it doesn't work it will just be because you need to unlock the bootloader or because your phone is different to the scatter file, but in that case I would expect Magisk to fail to patch it before you get to that stage.

How do you remove the battery? Have I missed something?
Sorry, wrong phone!!

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?

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