Database Users

Little Flashtool tutorial

This is an ancient tutorial. Stop frying me with PM's about it.

Outdated

Outdated

Thanks for this helpful guide!
Kudos!

I can get into flashboot mode but can't get into fastboot mode. I do it many times but it only charges my phone

I was never sure about using the fastboot toolbox until i read thru this. I would usually use the cmd window. I'll be flashing another of doom's test kernels later so i'll try it then. Thanks for going thru it
Sent from my R800i

I tried flashing my Xperia R800x back to stock with flashtool. The drivers installed fine but where I connect the phone flashtool says "ERROR FLASHING: Aborted"

thanks mate...help me alot

Thanks, great tutorial! Much appreciated.

Logseman said:
And now that we've covered flashing ROMs, we'll give our attention to the Fastboot Toolbox. Fastboot is a tool which can only be used normally through the command-line interface. This toolbox is basically a (quite raw) graphical shortcut to the relevant commands for our purposes.
We can activate it if we run Flashtool, click on the Flash icon, and select the Fastboot Mode.
{
"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"
}
I'll comment the buttons' functions and the equivalent fastboot command if it exists . That is for the benefit of the people who use Fastboot in non-Windows desktops.
Check current device status: this checks the status of your device, to see if it's on, off, in Flash mode or Fastboot mode.
Reboot into fastboot mode (via ADB) (adb reboot bootloader): with your device switched on, it will try to reboot directly into Fastboot mode. I'm not sure if it works...
Reboot into fastboot mode (via Fastboot) (fastboot reboot-bootloader): with your device on Fastboot mode, it will reboot in Fastboot mode again. It's mostly useful for testing purposes, but the common user won't need that too much.
Select kernel to HotBoot (fastboot boot X.img): this command will prompt you to select a certain kernel in order to boot it (NOT install it). This is helpful mostly again for testing purposes, but there are cases when it might come handy.
Select kernel to Flash (fastboot flash boot X.img): This is the command you'll be using most likely. You'll be prompted to choose a kernel, exactly like before, but in this case the kernel you choose will be INSTALLED. Unless you're a tester, make sure to flash kernels which are safe to install.
Here comes an example of flashing a kernel (DoomKernel v08):
Get Ver Info (fastboot getvar version): this is a pretty pointless command by itself as it will give you the Fastboot version installed, but the "fastboot getvar" command is pretty powerful, giving you information about a lot of the internals of the phone. Of course, those informations make sense to developers, while common users can largely ignore them.
Get Device info (fastboot devices): this command will output the Fastboot ID of your phone.
Reboot device into system (fastboot reboot): this command will reboot your phone.
With all these bases covered, you can happily operate with your Xperia Play. Have fun!
Click to expand...
Click to collapse
i unable to boot unlocker using bootflash
pls advice

Screw yourself.

Logseman said:
Screw yourself.
Click to expand...
Click to collapse
If you are referring to the last post on page 1 dated Sept. 23rd of this year, you could have said something nicer then that.
priteshc:
Easiest method is to got to Wotan Server and download their Xperia PLAY Drivers:
http://www.wotanserver.com/en/page/download
Download the X-Unlock Client and install first, it will install the fastboot and S1 drivers. Then install the Xperia PLAY Flash Driver file and install. After that you should be golden to flash away.
Good luck.

I could. And he could have not undug a thread 2 years old quoting a full post to post unintelligible crock. How does one even come here? I wrote this when we were in an ancient version of FlashTool...

Logseman said:
I could. And he could have not undug a thread 2 years old quoting a full post to post unintelligible crock. How does one even come here? I wrote this when we were in an ancient version of FlashTool...
Click to expand...
Click to collapse
True, not trying to argue or anything. And I am too a bit curious to see a thread revived after all this time. I would venture that said member did a search online and it pulled this thread up so he left a reply.
Anyways, lets consider this thread done as the information while helpful is dated. Still though despite its age thank you for posting this tutorial out 2+ years ago. I know it helped me 2+ years ago when i got my first PLAY (R800x), now R800at.

Thanks!!
Thank you with all my heart, for unraveling this blessing unto me and guiding me! :good:
I might just add that for unbricking/flashing, as these links are old, i founded out new ones:
flashtool: mediafire.com/u8i5kui5b8lg/5cz5nda84565ahb/flashtool-0.5.3.0-windows.exe
tft file for xperia play: htaaatp://download2141.mediafire.com/jbnc50uejxsg/pbh253qd2dv355b/R800i_4.0.1.A.0.283_%281247-6212%29.zip (remove "a")

You sir, are a ****ing disgrace!
I jsut followed your guide from this link
Then you forward me to this page, to download Android..
The funny thing is, the first guide is for Linux, but you end up, on a download site, where you need to install a ****ing iLivid.. And that's for Windows only.
Logseman said:
Why-and-how-to use Flashtool
Flashtool is your warranty, basically. Whereas PC Companion and SEUS are fairly limited about the kinds of reparations they can do ("no can do" with modified firmwares of any kind), Flashtool is your unbricking tool of choice. And if you have unlocked your bootloaders, it's the only 100% safe way to upgrade to new builds, as OTA and PC Companion updates can bring trouble.
In order to use Flashtool, we need FTF files with entire builds to flash. No problem: here they are, all of them. Once we have downloaded the one we want, we must put it in the "firmwares" folder of Flashtool so that it can be flashed.
Now we can fire up Flashtool, click on the left icon (the lightning bolt):
Choose Flash mode:
Select the firmware we wish (note that you have a couple of options for newer builds such as keeping your user data, but you better know what you're doing or you'll probably screw up the firmware):
Wait until the files are prepared...
And connect our device in Flash mode as specified before.
Once AND ONLY ONCE the process is finished, we can disconnect the USB cable and restart our phones.
Click to expand...
Click to collapse

This tutorial is three years old. I have not maintained it since I made it. How am I to know what's been of the links?

[SOLVED] Wiped wifi tablet, can't complete stock flash

The first part of this story is a little convoluted, so I'll start with my current situation and then start from the beginning.
I have a Nexus 7 WiFi tablet. I wanted a completely clean, back to factory reset. I followed the instructions here:
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
When I get to step 7 I get FAILED (command write failed (Invalid argument))
When I try to carry on past step 7 I continue to get FAILED messages. Screenshot below. Please note that I renamed bootloader-grouper-4.18.img to recovery.img for this attempt.
{
"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"
}
I have been Googling all afternoon to try to get past this but have not found a solution.
The longer, messy story. After I installed the 4.2.2 update everything seemed fine until one app, I think it was SD Maid, complained that it was lacking permissions. A bit of poking around revealed that SuperSU didn't seem to have permissions either and was giving the dreaded binaries error. Apparently 4.2.2 had removed the rooting. I waited until Nexus Root Toolkit v1.6.3 was released so it would have the right goodies for dealing with 4.2.2. Today I downloaded it and went to work.
Before I began anything with the toolkit the tablet was already showing as Unlocked. I applied the Root through the Toolkit and for some reason it would not apply. I installed Root Checker from the Play store and it confirmed that the tablet was not Rooted. I wasn't getting error messages during the procedure. I tried Googling this but didn't find anything that appeared to match my problem.
I next did a Factory Reset. When the tablet was done reloading it recovered all of my apps from backups saved to the Google servers. Still no root, still unrootable. So I do a Factory Reset but instruct it to not recover the backups. Still can't root the tablet.
At this point I'm thinking it's time to go back to a clean start instead of trying to fight the software. I'm picturing this as being like dealing with my desktop pc - no matter how bad things get I can always wipe the drive and reinstall Windows.
I next try Flash Stock + Unroot from the Nexus Root Toolkit. It appears to go smoothly and doesn't throw any errors, EXCEPT when the Toolkit says the tablet is rebooting out of fastboot mode and that the tablet may behave like it's stuck in a bootloop, the tablet just sits in fastboot mode.
So I next try the Android Central Forums link that I posted above. Maybe if I do it myself instead of using automation I'll be able to see what the problems are. As mentioned, everything goes fine until Step 7.
Other info...
This is the information that is currently displayed in the bootloader:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - something tells me I should post this here
SIGNING - not defined yet
LOCK STATE - UNLOCKED
Since product name, varient and bootloader version all seem to stem from the bootloader-grouper-4.18.img file, does this mean that the attempt to apply the image through fastboot actually succeeded despite the FAILED message?
Also, while in the bootloader, if I try to select Recovery Mode I get, "Booting failed" up where the notification bar would be. I'm interpreting that as meaning that I have in fact wiped (or at least rendered unusable) the OS.
At the bottom of the image above you can see where I tried Step 8. It is followed by the messages that the archive does not contain boot.sig, recovery.sig and system.sig. When I open image-nakasi-jdq39.zip using WinRAR I find this:
The files seem to be there but with .img extensions. What is going on?
I'm putting my efforts on hold while waiting for some feedback in this thread. To be clear; I am 100% fine and happy to wipe the tablet and install 4.2.0 or 4.2.1 or whatever else and then upgrade through the Play store. I just want my Nexus 7 working again, rooted and unlocked and I'll be smiling and back to business as usual.

success on short fastboot commands (those that send only a command) and failures on those that send files (large amounts of data) suggest data corruption - marginal cabling or a damaged USB port.
Try a different USB port on the same PC and/or a different cable and repeat the same commands. You should prefer the OEM cable instead of aftermarket cables unless it is damaged. Also, I would avoid flashing the bootloader while you are having communications difficulties. If you can do the full ROM install successfully, you can follow that up with a bootloader flash (the factory ROM is 50x larger; if you can get it to work, then the bootloader flash should also go off without a hitch)
good luck

just from looking at the text file with in system images from google, your missed step looks to be this
fastboot flash bootloader bootloader-grouper-4.18.img
your line in the command prompt just has flash bootloader recovery.img
try that then do the
fastboot reboot-bootloader
fastboot -w update image-nakasi-jdq39.zip
just leaving this here for some searchable info, there is a file called flash-all.sh inside of the zip you download the system images from google, in there has all the commands you need todo word for word. not really viewable from notepad on windows but notepad++ is able to open them and view them

bftb0 said:
success on short fastboot commands (those that send only a command) and failures on those that send files (large amounts of data) suggest data corruption - marginal cabling or a damaged USB port.
Try a different USB port on the same PC and/or a different cable and repeat the same commands. You should prefer the OEM cable instead of aftermarket cables unless it is damaged. Also, I would avoid flashing the bootloader while you are having communications difficulties. If you can do the full ROM install successfully, you can follow that up with a bootloader flash (the factory ROM is 50x larger; if you can get it to work, then the bootloader flash should also go off without a hitch)
Click to expand...
Click to collapse
I went from the tower's front usb ports to the back and it wasn't until I used a '3x USB Power" port that it worked. The cable was brand new with the tablet and hasn't even left this room since I unboxed it; I was confident it wasn't damaged.
It gave the "archive does not contain 'boot.sig' series of messages again but that didn't seem to hinder it. Following the update it booted into the OS on its own. Android 4.2.2. I went through the setups and first installed Root Checker. Device is not rooted. Next we'll find out if it roots this time. Perhaps my staying with this powered USB port will let the root operation complete properly this time.
[edit] Root success! Root Checker reports the device is now rooted. Also, during Toolkits procedures the Nexus 7's screen displayed the installation of TWRP, something it didn't show previously.
BrianDigital said:
just from looking at the text file with in system images from google, your missed step looks to be this
fastboot flash bootloader bootloader-grouper-4.18.img
your line in the command prompt just has flash bootloader recovery.img
Click to expand...
Click to collapse
Actually, if you look again you'll see it's there. I looked back and forth between the cmd window and the guide about half a dozen times to make sure I had it correct. I did *not* want to create a whole new headache due to a typo.
just leaving this here for some searchable info, there is a file called flash-all.sh inside of the zip you download the system images from google, in there has all the commands you need todo word for word. not really viewable from notepad on windows but notepad++ is able to open them and view them
Click to expand...
Click to collapse
It would appear I won't be needing this.
Thank you both very much for your replies. :good:

[UNBRICKING] Research on Unbricking Method for Zenfone 2

TESTERS NEEDED
The main intention of the threat was to find a way to restore a completely bricked zenfone 2. It is apparent that we are not having a spare bricked device to test upon.
Anyone with a Bricked Zenfone 2, A PC, and willingness to devote time, please participate.
Otherwise, this thread is going no where as we people who are searching for methods do not have bricked devices(And do not want to specially brick them for testing)(Obviously!!!) and all talks are in taking us nowhere.
Click to expand...
Click to collapse
"Bricked Devices" is a regularly heard phrase on XDA. Sadly, Asus devices dont come with a dedicated PC Companion or PC Suite software which can safely unbrick a Zenfone just in case someone is able to damage fastboot.
That Said, there have been Zenfone 2's that have been Hard Bricked in the past months. Fortunately, many of them may have got replaced as the device comes with a One Year Warranty. But what after that...???
So, i wanted to do some research upon this unexplored topic.
On successfully Hard Bricking your device, you will see something like this :highfive:
{
"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"
}
( credit to the one who bricked and clicked)
I do not have a bricked device, but if anyone can get one and test stuff, we may end up getting something concrete to restore in future.
So, i came across a page: http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
But soon i understood that all these things are foreign to me ( So far ).
Also, The drivers for the SOC are for CloverView Plus Devices.
It would be seriously great if we can successfully recover from corrupt fastboot. As without fastboot we can do absolutely nothing.
I request senior members, Devs and all others to provide inputs and links and keep this thread productive.
Who knows, someday we may end up in a situation without warranty and with a corrupt fastboot.
I will keep on updating this thread with updates from your side
Lets Start.

So that method in the link is like the Odin for Samsung, or the NvFlash for nvidia. Except that it is for Cloverview (32 nm SOC) vs Moorfield (22nm SOC) which is what we have.

cmendonc2 said:
So that method in the link is like the Odin for Samsung, or the NvFlash for nvidia. Except that it is for Cloverview (32 nm SOC) vs Moorfield (22nm SOC) which is what we have.
Click to expand...
Click to collapse
Exactly!!. We need something that works on Moorefield

[email protected] said:
Exactly!!. We need something that works on Moorefield
Click to expand...
Click to collapse
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.

cmendonc2 said:
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
Click to expand...
Click to collapse
I think we first need drivers for the moorefield SOC ( SOC Drivers) to access the partitions without fastboot support.
I havent read the PDF that you linked. Will read and revert back.

Great job guys
Better be prepared now than panic later haha
Hope i can help but im totally new in this kind of stuff
This makes me want to take a course related to this stuff cause its amazing how u brainstorm with each other

tactician10 said:
Great job guys
Better be prepared now than panic later haha
Hope i can help but im totally new in this kind of stuff
This makes me want to take a course related to this stuff cause its amazing how u brainstorm with each other
Click to expand...
Click to collapse
Well, thats what XDA is here for.
Learning is a never ending process. And i have learnt a lot from others in this place.
And regarding this thread being inactive.
I have got a few things, but they seem irrelevant to me. Searching for something really solid in this regard. No point in posting irrelevant findings from my side and bumping up the thread.
I am going to get a bricked Zenfone 5 (Sure) and Zenfone 2(Hopefully) from a local repair shop.
Will try doing serious software damage to the Zenny 2 and will then try to recover. Lets See!!

i have this problem, broke my fastboot

Does your phone bootup???? Does Android bootup?
If it doesnt, you are currently out of luck
As already said by @cmendonc2 , we need someone senior to extract some files

@edit@
I solved it.
I reflashed recovery via Adb in screen selection "recovery mode/bootloader/normal"
I'm very happy

test subject..
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks

Seoulja said:
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Click to expand...
Click to collapse
Can you boot into Android????
What is your device model?? ZE550ML or ZE551ML??

Seoulja said:
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Click to expand...
Click to collapse
[email protected] said:
Can you boot into Android????
What is your device model?? ZE550ML or ZE551ML??
Click to expand...
Click to collapse
ZE551ML / ZOOA
It bootloops when i try to boot it. I get the usb symbol when i try to fastboot. I wanna try using intel phone flash tool but require .xml flash file within a stock Rom .zip file. I looked everywhere but i can't find a zip with .xml flash file.

moorefield driver
[email protected] said:
I think we first need drivers for the moorefield SOC ( SOC Drivers) to access the partitions without fastboot support.
I havent read the PDF that you linked. Will read and revert back.
Click to expand...
Click to collapse
Hello, if you install the Intel phone flash tool lite, the tool install also the moorefield driver. When you open the xfstk downloader the tool looks the phone but in stock rom from asus i can not found the ifwi os dnx os image files. If anyone will find the files please tell to me.
Thans for your help.

We need some experienced dev to extract these files for us
Without that, there is no option

levi1232005 said:
Hello, if you install the Intel phone flash tool lite, the tool install also the moorefield driver. When you open the xfstk downloader the tool looks the phone but in stock rom from asus i can not found the ifwi os dnx os image files. If anyone will find the files please tell to me.
Thans for your help.
Click to expand...
Click to collapse
Hey there!!
Check out this page: http://forum.xda-developers.com/general/xda-assist/intel-phone-flash-tool-t3129091. Its for Zenfone 5
The Guy has stated that he found the Necessary files by unpaking the boot.img,which can be found in the firmware zip available on Asus Support website.
Alternatively, you can get it from Here. But these are older ones. I would recommend the Asus website though.
The Intel Phone falsh tool is available at https://01.org/android-ia/downloads/intel-phone-flash-tool-lite . Try it out.
I have wiped my Linux and windows partitions as i am installing Windows 10. So this is all i can help you with. If you need any information, Just Ask. I will do my best to help.
As for extracting the boot.img, do a quick google search. XDA has a thread for that. You need either Linux or cygwin.
All the best!!!!
Disclaimer: I have not tested these things. Try at your own risk

cmendonc2 said:
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
Click to expand...
Click to collapse
Hey,
I just stumbled upon something.
I downloaded the latest OTA zip package (20MB) of the ze551ml
I opened the ifwi folder
And i found the bin files. DNX FW etc of various zenfone variants.
Can you throw some light on this???
P.S.
Folder screenshot attached!!

Here's some more info I found on the IFWI images:
Two special IFWI images are used for booting in this mode: _dnx_fwr.bin and _dnx_osr.bin. These comprise a simple flash tool that writes a raw image to the eMMC boot partitions and another to the main eMMC space. xFSTK is provided with paths to the IFWI image and a eMMC image. The eMMC image contains an OSIP header (location/size of U-Boot in eMMC, load address, and entry point), a partition table, and partitions with U-Boot and the U-Boot environment.
Click to expand...
Click to collapse
So the dnx_fwr.bin is probably this file:
Code:
dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
The ifwi.bin is probably this file:
Code:
ifwi_ann_a0-mofd_v1-ze551ml.bin
I checked the MD5sums of the different versions and they are different. I guess we need a bricked ZF2 to test and see. Although we still don't have the OSR files. Perhaps @shakalaca can help us.

Okay right
I just had one last week. I tried everything i could. Finally i gave it back.
And Today i stumbled upon this.
Ill see if the guy still has that bricked zen.
Thanks for your reply
Sent from my ASUS_Z00AD using XDA Free mobile app

Good day sir, i was just wondering if this reseach is still going. Still unable to find any solution to my hard bricked zenfone 2 ZE200ml. Im somehow counting on this. Goodluck!

Lineage OS 17.1 Post Installation Issues

Hi
I recently completed installing official LineageOS 17 on my 6T using TWRP, not the recovery on Lineage wiki page. Restarted the phone a few times and playing with it for a couple of days. Things seem to be working well. I do have a few doubts though:-
(1) About the A/B partition thing. I did a simple wipe prior to installation and I am not sure I have installed it on the correct partition. How can I check to make sure ? Can I copy partitions now and if so, how ?
(2) I do not plan to use payment apps on the phone but I do plan to use the protonmail apk which I have already installed. How safe is it to leave the bootloader unlocked especially when the "Automatic System Updates" is on ?
Thanks

1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
2. You can't lock the boot loader unless you make your own build and sign it. So it must remain unlocked. There is a guide for doing this if you want in the guide section.

OhioYJ said:
1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
Click to expand...
Click to collapse
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.

anuk221 said:
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.
Click to expand...
Click to collapse
On a clean / first install of Lineage you would typically install it twice to get it on both A/B partitions. The other option is to use the copy partitions zip. The zip is mentioned in the Lineage wiki I believe
It's not a safety block, you just will come up as not certified, which likely is already the case. This will not cause you any problems other than certain apps won't appear in the play store. (Such as Netflix, things like that).
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
The other partition would only try and boot if Lineage failed to boot. If you didnt install it twice, it would be an easy fix now to just install it again, or use the copy partitions zip. Usually I just update or install without worry, but I would backup just to be safe in this case since your steps are a little out of order. Always better to be safe than sorry.

OhioYJ said:
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
Click to expand...
Click to collapse
Thanks for the link. I had checked your guide amongst others prior to installation.
I was getting the following startup screen on boot and it didnt lead into TWRP recovery or bootloader even when I used the "volume up+power" combination at startup :-
{
"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"
}
Which is what led me to think that I hadnt done a clean/proper install. I had used "Tool ALL IN One" to unlock the bootloader and I had deviated from wiki and gone the TWRP route for recovery since I was not sure if selecting "Apply Update" in recovery and then "Apply from ADB" would work.
Anyways, I redid the whole thing again last night using Lineage OS recovery. I still get the above screen at startup but now when I select the power button, it takes me into LineageOS recovery.
Again everything seems to be working well prima facie, except that this time when I insert a Sandisk USB C Dual Drive, I get a message "Issue with Sandisk USB Drive. Tap to fix". The drive works fine on my 8T !

anuk221 said:
Thanks for the link. I had checked your guide amongst others prior to installation.
Click to expand...
Click to collapse
Different devices have different kernels with different things enabled / disabled, giving them different capabilities. Honestly I've never tried thumb drives on my phones, I guess I could try one on my 6T and 8T and see what I get later. I'll see if I can find an adapter cable, as I don't have a USB C drive.
You do have to let go of the power button for a moment to get into fastboot. It will pause when it gets to that bootloader unlocked screen. At least that's always been my experience.
Every time you install LOS on the 6T it replaces TWRP with LOS recovery. TWRP must be re-flashed everytime if that's what you prefer to use. That's why that step is in my guide.

OhioYJ said:
Different devices have different kernels with different things enabled / disabled, giving them different capabilities.
Click to expand...
Click to collapse
That is correct. The drive in question is a 64GB drive formatted in exFAT. I tried another drive, 32GB formatted in NTFS and it was being detected by both the 6T and the 8T ! Probably an issue with the exFAT kernels as you pointed out.
I am surprised though that some very basic features which I had assumed would be available seem to be missing - No option of ungrouping/declubbing sms conversations, no option of exporting to SIM, no option of getting timestamp in call log. In that sense LOS appears to be more of a de-googled version of android than a standalone OS.

Bought a Samsung Tab A SM-T387V, apparently has doordash on it, how can I wipe it and use it as a normal tablet?

EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"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"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!

Which Android version did you flash? Did you finally get rid of MobiControl?

XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!

genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?

I had no luck. I can't flash anything, got error "MDM mode, can't download ".

XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.

genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?

XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3

genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?

XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.

genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?

XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.

Any idea where you downloaded it from? I cant seem to find a link.

quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/

"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50