Database Users

[Q] Ideapad K1: Creating .img files from OTA

Alright, now I realize this is the Thinkpad section but there doesn't seem to be an Ideapad one. I've been out of the Android game for a very long time, and finally came back with a Lenovo K1 Ideapad.
My big issue is I don't know how to create a system.img, boot.img or recovery.img from the Canadian OTA zip on the Lenovo site so I can flash them onto my tablet. I managed to use the root tool available in the development section to root my tablet with a US firmware. However after experiencing a lot of freezing and my tablet not responding, I felt as if I should revert back to the Canadian firmware. My problem is I forgot to create backups for the previously mentioned images so I can't flash them back and restore my tablet.
If someone could please explain or even direct me to where I can learn the steps in creating them (I just installed linux because so far it seems like that would be the first step), it would be a great help. I took the img files from a different root tool and tried those, they changed the system to a chinese firmware but I at least know it works if I could get the Canadian ones. I can go back to the US one if I really wanted but what I want is to just put this thing back into its original state that it came in.
Even if someone could just post those files, it would be greatly appreciated. I've been scouring the internet for days to try and gain some enlightenment, but it isn't happening. Probably since development on this thing isn't as hyped as others.
Thank you.

I'm still stock and not rooted so I would like to know how to back up my current system before rooting .....maybe I can be of some help if I can get my sys backed up
Sent from my HTC EVO 3D X515a using XDA App

***method doesn't appear to work***

maek_it_happen said:
I'm still stock and not rooted so I would like to know how to back up my current system before rooting .....maybe I can be of some help if I can get my sys backed up
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
On the K1 you cannot. Lenovo has it locked down so there's no way to back it up without root. The only way to root it is to flash it which wipes it clean. Thee ole catch 22.
Now, if you read through the leaked keys and rooting tips, they talk about fastbooting to ASUS boot.bin and then backing up before you start rooting. It definitely works to backup, but I haven't found anyone that has successfully used them to restore from and I could not get them to restore. So, in my opinion, that backup method is worthless because you cannot use them.
TD
---------- Post added at 07:53 AM ---------- Previous post was at 07:48 AM ----------
MrZombieAndMe said:
Alright, now I realize this is the Thinkpad section but there doesn't seem to be an Ideapad one. I've been out of the Android game for a very long time, and finally came back with a Lenovo K1 Ideapad.
My big issue is I don't know how to create a system.img, boot.img or recovery.img from the Canadian OTA zip on the Lenovo site so I can flash them onto my tablet. I managed to use the root tool available in the development section to root my tablet with a US firmware. However after experiencing a lot of freezing and my tablet not responding, I felt as if I should revert back to the Canadian firmware. My problem is I forgot to create backups for the previously mentioned images so I can't flash them back and restore my tablet.
If someone could please explain or even direct me to where I can learn the steps in creating them (I just installed linux because so far it seems like that would be the first step), it would be a great help. I took the img files from a different root tool and tried those, they changed the system to a chinese firmware but I at least know it works if I could get the Canadian ones. I can go back to the US one if I really wanted but what I want is to just put this thing back into its original state that it came in.
Even if someone could just post those files, it would be greatly appreciated. I've been scouring the internet for days to try and gain some enlightenment, but it isn't happening. Probably since development on this thing isn't as hyped as others.
Thank you.
Click to expand...
Click to collapse
In Linux, you just mount system.img and then read and write to it. If you are using Windows then you can download drivers that let you mount the the system.img as a disk drive.
I use Windows for everything, no need to use Linux. For cooking, Google Cygwin which runs on Windows and is kitchen for 'cooking ROMS'.
TD

Alright thanks timmyDean for the answers. I noticed you uploaded a tool to revert back to stock. So I was thinking of giving it a shot. I'm just hoping it won't be too much of an issue if I install the US rom. I'm thinking it won't let me use OTA updates since I'm in Canada, but I can probably just do the manual method for installing the updates. The box for my K1 says US, and we usually get the same pieces of hardware as the states with just a modified OS.
Hoping this works, fingers crossed

MrZombieAndMe said:
Alright thanks timmyDean for the answers. I noticed you uploaded a tool to revert back to stock. So I was thinking of giving it a shot. I'm just hoping it won't be too much of an issue if I install the US rom. I'm thinking it won't let me use OTA updates since I'm in Canada, but I can probably just do the manual method for installing the updates. The box for my K1 says US, and we usually get the same pieces of hardware as the states with just a modified OS.
Hoping this works, fingers crossed
Click to expand...
Click to collapse
I loaded a tool to goto CA stock too and already tested it for you.

Thank you so much man, I just used your tool. Flashed the stock US, then put my CA one and it worked like a charm. You've honestly made me so happy.
Too bad the K1 in Canada is still at 3.1 and doesn't look like it'll get 3.2 (fingers crossed we for sure get ICS).
Anyway I am very thankful. I've looked over the tools but I don't see a lock thread option, hopefully a mod will do so promptly.

Safestrap Recovery Not Responding (Different Than Most Issues)

Hey guys, I've been trying out ROMs for the past couple weeks and finally decided I wanted to replace my stock ROM with the energy rom to save space. I wiped all files from my stock ROM and then tried to flash the energy rom. I got an error so decided just to leave it for another day and created a second partition for the energy rom. Forgetting to flash my recovery back to my stock slot, I booted in to the energy rom. Now my recovery buttons don't work, probably due to the fact that they were installed on the stock rom. I don't have any way of getting in to the recovery and that kind of worries me. I've been reading up on fastboot, but don't know were to be begin or get ahold of rsdlite since all of the links send me to spam. Any help would be greatly appreciated!
I am currently using Safestrap 3.1.2 and do have a backup image of my stock ROM on my external SD card (at least I was smart enough to remember that).

Figured it out
Figured it out! Just in case anybody else has this problem, use RSD to fastboot the stock image to your phone. I know everything I read was talking about this, but I couldn't find detailed instructions anywhere. Most time consuming part for me was editing the xml file due to "oem" command lines that weren't recongnizable. There is a fixed xml file on droidrazr forums for those who need it!

Please help same issue
bgregs514 said:
Figured it out! Just in case anybody else has this problem, use RSD to fastboot the stock image to your phone. I know everything I read was talking about this, but I couldn't find detailed instructions anywhere. Most time consuming part for me was editing the xml file due to "oem" command lines that weren't recongnizable. There is a fixed xml file on droidrazr forums for those who need it!
Click to expand...
Click to collapse
PLEASE HELP ME
I am in the same trouble you were in here is my thread.

[STOCK] VERIZON Nexus 6 [5.1][LMY47E] Firmware Image

For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.

So the difference in between whats out there and this is? I'm curious as the build is different.

coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.

Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app

Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.

Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.

Well no worries this all but confirms vzw is rootable and unlockable

Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx

Is there a rooted version??

Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition

Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.

Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?

How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat

mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).

Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!

mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?

elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:

mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA

Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone

Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?

From Root to Pure Nexus (7.1.2)

Requesting guidance before I brick my phone.
I currently have bootloader unlocked, twrp installed, and my nexus 6p rooted. I'm running 7.1.2. I've also changed a line in the (build.prop) provisions in order to tether free (since I am on at&t)
Basically, I'm wanting to install pure nexus. I have the custom rom file and the vendor image file.
Before I install from, I'm wondering if I need to unroot first? Also curious if how "shamu" will affect things since I'm on Angler.
Thanks!

Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.

help
RoyJ said:
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
Click to expand...
Click to collapse
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:

Filly2 said:
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Click to expand...
Click to collapse
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.

..
RoyJ said:
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
Click to expand...
Click to collapse
Sorry I don't mean to bug man but I'm so lost. I'm trying to find what you are referring me to but I'm not finding the info I need I haven't been on here too often so this is like a pain in my rear so far. Plus I'm a very hands on kinda learner so I need some like handicapped help lol If you don't mind I don't want to pester anyone...

I was able to load pure Nexus. I didn't realize there was a pure nexus rom with Angler on it.
My main question was if I had to reverse the root. But I'm good to good now.
Rom loaded, vendor image loaded, and Google Apps loaded.

(HELP NEEDED) Onn 8" gen 2, 100011885 no boot

So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!

Two things, I got access to my old account after a password reset
and, I got my tab back up and running, as well as root & xposed + gravitybox
I'm working on a guide as we speak.

Also, I will be dumping my firmware and adding the 10001885 to the list of stock image dumps on the main onn thread.

Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
Ankylo'sburner said:
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Click to expand...
Click to collapse
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do

bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse

Hey, i've had that same issue but have since fixed it by flashing the rom to the 100011886. I used some of the posts here to flash both vbmeta.img and boot.img to gain root, with success https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing . i eventually went too far and currupted my rom and had a hard time finding the stock ROM. I found the stock ROM to the 100011886 and flashed that to fix the problem, now i run that as my system and it boots up just fine. https://www.mediafire.com/file/107jp6gwbiwq87q/MT8168_ONN_Gen2_100011886.zip/file
fastboot erase super
fastboot flash super super.img

Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22

onn. said:
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
Click to expand...
Click to collapse
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT

KMerrimanJr said:
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
Click to expand...
Click to collapse
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.

onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though

KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
I wish I would have waited until I read this today instead of further messing with it yesterday. It looks like everything you have is what I need, but now I am battling trying to get the COM port to stay active when the device is plugged in. I'll tinker with it and see if I can get back to the state I had it in yesterday where it was staying connected.

KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
Would you happen to know/remember all the settings you checked in SP Flash Tool (I assume you used that) when you flashed things to get it working? It seems that my PC is able to communicate with the device again, but I'm unsure of how to proceed next.

Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file

KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
It's hard bricked at the moment unfortunately, so there's no appearance of life to it. Attached picture is the error I get. https://www.gizmoadvices.com/list-sp-flash-tool-error-codes-solution-fix/ appears show info about the error, but it's not something I know how to fix yet.
The only way I can get the tablet to make moves in device manager (which I assume is a sign that the PC can at least partially recognize/see the device) is to click on Download in SPFT, connect tablet to PC via USB cord, and then hold down power button, which led to the error. Errors in SPFT I've received so far are 0xC0060001 and 0xC0060003.
When the tablet is active in the device manager, I assume that the device is in a powered state. However, when the device is grayed out, I assume it's in a powered off state (see other pic). I've yet to find away to actually flash anything to it.

KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
Also, apologies if I'm being a bother, but do you know what version of SPFT you used as well as which DA file?

bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
where did you get this? did you dump it? if so how?