Database Info

[ROM][STOCK]{UPDATED} Lenovo Tab 3 8/TB3-850F Android 6.0 Stock Firmware Images

Lenovo Tab 3 8/TB3-850F -
Android 6.0 Stock Firmware Images
DISCLAIMER: As always, flashing your device - with either stock or custom firmware - involves an inherent risk of bricking or otherwise rendering your device inoperable. I am not responsible for any good or bad resulting from your use of these firmware images or this thread.
DEVICE SPECIFICATIONS:
Model: Lenovo Tab 3 8"(TB3-850F)
Android Version: 6.0 Marshmallow
Kernel Version: 3.18.19
Board Platform: MediaTek MT6735m (1.0 GHz)
Build No: TB3-850F_S100031_171010_ROW
Software Version: TB3-850F_160412
SDK Version: 23
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Build Date: 10/10/2017
NOTE:
First & foremost, these partition images will not restore your device completely back to factory/stock condition. They will restore your Android OS, boot logo, boot image & recovery to stock condition. Other vital partitions of your device, such as /lk (the primary bootloader) are not restored by flashing these images. To revert to an unmodified factory state, you will need to visit @r&xp's thread mentioned below and flash your device with stock firmware using the SP Flash Tool, which will also re-lock your bootloader.
This firmware thread is not intended as a tutorial or guide for flashing or restoring your Lenovo Tab 3 back to stock condition. Rather, this is intended as a resource for stock images, device drivers, etc. However, some rudimentary instructions are provided, which will enable you to install these images and restore your device back to mostly stock condition. NOTE: IF YOUR DEVICE IS BRICKED (UNABLE TO BOOT INTO EITHER RECOVERY OR FASTBOOT MODE), THESE FIRMWARE IMAGES WILL BE OF NO BENEFIT. INSTEAD, PLEASE VISIT THE FOLLOWING THREAD BY XDA MEMBER @r&xp , WHICH WILL GIVE YOU THE NECESSARY FILES AND PRECISE INSTRUCTIONS FOR UNBRICKING & RESTORING YOUR DEVICE. https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
There are any number of available procedures to flash these stock partition images to your device. The simplest option is to use a custom recovery like TWRP to flash them. Store these images to your external micro SD (or internal storage if you do not intend to wipe internal storage or format /userdata). In TWRP's main menu, select "WIPE", "ADVANCED WIPE", and select Dalvik Cache, Cache, System, & Data. (For a clean install, it is recommended to format Data as well, by selecting "WIPE", then "Format Data.") Reboot Recovery (often necessary for proper mounting of the data partition). Now, select "INSTALL", then select "INSTALL IMAGE" in the bottom right of the menu, navigate to the storage location of the firmware images, and flash them in any order you choose. If you do not have TWRP installed on your device, XDA Senior Member @Hemphiz has a simple & comprehensive thread here: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786/page1. In any event, whichever option you choose, please do your homework and research the threads here on XDA relating to your choice. These images may also be installed via fastboot mode. You will need to install Minimal ADB & Fastboot (v1.4 or later) on your PC, ensure the proper Lenovo device drivers & ADB drivers are installed on your PC, and connect your device to your PC via the stock (or quality equivalent) micro USB to USB data sync cable. Once in fastboot mode, open a command prompt in the adb/fastboot directory, and execute the following command lines:
fastboot devices (if you are properly synced, your device serial # will be shown)
fastboot oem fb_mode_set
fastboot flash logo logo.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img (this will overwrite any custom recovery)
fastboot flash system system.img (fastboot will automatically sparsechunk this image)
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
fastboot reboot
STOCK PARTITION IMAGES:
The link below provides the following stock firmware images:
/system.........................Size 3.0 GB
/boot..............................Size 16 MB
/recovery........................Size 16 MB
/logo...............................Size 8 MB
Also included in the link are some helpful files like Minimal ADB & Fastboot v1.4.3, the official Lenovo USB Drivers for the TB3-850F (v1.1.21), a general partition index of the tablet, the ADB driver installer for Windows, and the latest PC version of LenovoSuite Mobile Assistant v1.4.1.14199.
I have made a full & complete partition dump of this device, including sensitive firmware partitions such as /oemkeystore, /nvdata, /seccfg, /lk, etc. In the event any members have corrupted these partitions, just request and I will upload these as well. (/nvdata contains device identifiers such as MAC Address, ESN, etc. The device from which these images were taken has since been hardware damaged & salvaged for parts. Therefore, I have no issue with sharing these images. However, as a disclaimer, you are fully responsible for the manner in which you use device ID partitions. Modifying a device's identifiers delves into matters of legality and ethical guidelines, all for which you are solely responsible.)
CREDITS:
Thanks to XDA Senior Member @Hemphiz for his hard work & development on this device, and his thread on TWRP & rooting. Also, huge thanks to @r&xp for his lifesaving tutorial on recovering this device from a soft or hard brick. His guide has revived many devices from the Android cemetery. You guys visiting either of these threads mentioned, be sure and hit the "THANKS" button for their hard work.
DOWNLOAD LINK:
TB3-850F_S100031_171010_ROW
Stock Firmware Partition Images: https://drive.google.com/folderview?id=1vRLwQ2mCD3CwYQZKGHyykDvBd2yGHisT
Sent from my Lenovo Tab 3 8/TB3-850F using XDA Forums Pro Edition.

Hi:
I have a Tab3 8 TB3-850F which bough in China. It's a 2G+16G version.
I have successfully install TWRP and root.
I'm wondering can I install this ROM to my TAB3?
Thanks!

tsaibru said:
Hi:
I have a Tab3 8 TB3-850F which bough in China. It's a 2G+16G version.
I have successfully install TWRP and root.
I'm wondering can I install this ROM to my TAB3?
Thanks!
Click to expand...
Click to collapse
I don't see why you couldn't. But, to clarify some info, what is your Build No and Software Version? Look under Settings, About Device

Build number:
TB3-850F_S100026_161221_PRC
Software version:
TB3-850F-160425
Thank you very much!

tsaibru said:
Build number:
TB3-850F_S100026_161221_PRC
Software version:
TB3-850F-160425
Thank you very much!
Click to expand...
Click to collapse
Based on your Build & Software Version info, I can see no compatibility issues with this Stock ROM & your device. You seem to simply have a Chinese variant of the TB3-850F that is not available for retail in the United States.
In any event, use TWRP to backup all partitions of your tablet before proceeding henceforth with flashing this ROM. Also, do not flash the stock recovery from my link...keep your TWRP fully intact & accessible in case anything goes south as a result of the flash. Accordingly, you should be able to fully restore your partition backups via TWRP in the event my Stock ROM doesn't boot up. But, like I said, I can see no adverse consequences to flashing it. Should you decide to give it a go, please update us on this thread as to the results.
Thank you...

The reason why I would like to flash this ROM is to get full Google service which Chinese Rom does not offer.
Even though I have root and install Google service on it. Some of apps I downloaded from play just won't install.
So I dowbloaded this ROM and flash system-002.img, it works.
Now I have all Google service I needed, and all apps I download are able to install.
But after I reset the tab I've build number S100026_160923_ROW, software version TB3-850F_160412.
It will try to download the update to 161209 but after reboot it just go in TWRP not doing anything.
I'm very satisfied with this, and I will keep searching and wait for a way for me to update to S100030_161209_ROW.
I do really appreciate your work to help me solve my problem and save this tab from goes to trash can.

​
tsaibru said:
The reason why I would like to flash this ROM is to get full Google service which Chinese Rom does not offer.
Even though I have root and install Google service on it. Some of apps I downloaded from play just won't install.
So I dowbloaded this ROM and flash system-002.img, it works.
Now I have all Google service I needed, and all apps I download are able to install.
But after I reset the tab I've build number S100026_160923_ROW, software version TB3-850F_160412.
It will try to download the update to 161209 but after reboot it just go in TWRP not doing anything.
I'm very satisfied with this, and I will keep searching and wait for a way for me to update to S100030_161209_ROW.
I do really appreciate your work to help me solve my problem and save this tab from goes to trash can.
Click to expand...
Click to collapse
Trying a system update will not work with a custom recovery installed. In spft you can select only to flash the stock recovery then you should be able to update it, when you have done the system update just flash TWRP again.
@MotoJunkie01 I did send you a PM the other day, maybe like for you it did not send or was it my noobishness? :laugh:

stonedpsycho said:
​
Trying a system update will not work with a custom recovery installed. In spft you can select only to flash the stock recovery then you should be able to update it, when you have done the system update just flash TWRP again.
@MotoJunkie01 I did send you a PM the other day, maybe like for you it did not send or was it my noobishness? :laugh:
Click to expand...
Click to collapse
Try sending another PM please. I could have deleted your PM by mistake.

boot. logo and recovery.img worked but system.img did not .the system.img downloads with the explorer or e symbol not a disc like the others do.don't know if that has anything to do with it not working? need the system.img to work pls.

chico2016 said:
boot. logo and recovery.img worked but system.img did not .the system.img downloads with the explorer or e symbol not a disc like the others do.don't know if that has anything to do with it not working? need the system.img to work pls.
Click to expand...
Click to collapse
Not sure. The /system image is an unmodified dump taken from a brand new TB3-850F. It works for me and other members. Be sure you are running version 1.4 or later on minimal adb & fastboot. That could be your issue.

MotoJunkie01 said:
Not sure. The /system image is an unmodified dump taken from a brand new TB3-850F. It works for me and other members. Be sure you are running version 1.4 or later on minimal adb & fastboot. That could be your issue.
Click to expand...
Click to collapse
ok will try again thank you.
---------- Post added at 01:19 AM ---------- Previous post was at 01:15 AM ----------
is it possible to use the platform tool ,like it says for the twrp for the system image?

chico2016 said:
ok will try again thank you.
---------- Post added at 01:19 AM ---------- Previous post was at 01:15 AM ----------
is it possible to use the platform tool ,like it says for the twrp for the system image?
Click to expand...
Click to collapse
Sure. Minimal ADB & Fastboot is merely a bare essentials utility in contrast to the Android SDK & other platform tools packages. You may also flash the /system image using TWRP.

MotoJunkie01 said:
Sure. Minimal ADB & Fastboot is merely a bare essentials utility in contrast to the Android SDK & other platform tools packages. You may also flash the /system image using TWRP.
Click to expand...
Click to collapse
target reported max download size of 134217728 bytes.
invalid sparse file format at header magi ? Not enough room.
need help with tb3-850f flashing system.img.

Thanks!!! Saved my soft bricked Tab3 8 850F

chico2016 said:
target reported max download size of 134217728 bytes.
invalid sparse file format at header magi ? Not enough room.
need help with tb3-850f flashing system.img.
Click to expand...
Click to collapse
If you use minimal adb & fastboot v1.4, the /system image will automatically be converted into a series of smaller sparsechunk image files, which will be flashed to your device one at a time until complete.

wow dont know what i am doing wrong.
invalid sparse file format at header Magi
erasing 'system'...
okay[0.032s]
sending sparse 'system' 1/21...(129476kb) okay[14.824s] writing 'system'1/21...
failed(remote: uknown chunck type)
finished. total time: 14.904s
need some help adb fastboot file says 'system.img is to long?

wow dont know what i am doing wrong.
invalid sparse file format at header Magi
erasing 'system'...
okay[0.032s]
sending sparse 'system' 1/21...
failed(remote: uknown chunck type)
finished. total time: 14.904s
need some help adb fastboot file says 'system.img is to long?

chico2016 said:
wow dont know what i am doing wrong.
invalid sparse file format at header Magi
erasing 'system'...
okay[0.032s]
sending sparse 'system' 1/21...
failed(remote: uknown chunck type)
finished. total time: 14.904s
need some help adb fastboot file says 'system.img is to long?
Click to expand...
Click to collapse
What version of Minimal ADB & Fastboot are you using?

i am using the 1.4 version adb fastboot from the same link i got the images on this very helpful post
boot img -logo.img-recovery.img say flash on ,and the tablet marks ok that they have flashed---but no luck with the system.img even though i have re downloaded twice same thing .do you have a link that would go through a step by step instalation process you could help me with.

chico2016 said:
i am using the 1.4 version adb fastboot from the same link i got the images on this very helpful post
boot img -logo.img-recovery.img say flash on ,and the tablet marks ok that they have flashed---but no luck with the system.img even though i have re downloaded twice same thing .do you have a link that would go through a step by step instalation process you could help me with.
Click to expand...
Click to collapse
I don't have a tutorial posted per se on installation. Here's a thought. Boot your tablet into TWRP (fastboot boot TWRP.img) and flash my system.img via TWRP. In TWRP main menu select INSTALL, then select the .img file option in bottom right hand corner of screen. (You will need to put the system.img on an ext micro SD)

TWRP For Mate 10 lite 8.0 Oreo Version For RNE-L21C185

Here is twrp for HUAWEI MATE 10 LITE.
Who want?
Comment Here.

i need Android 8 for mate 10 lite !

yes i need thanks

100% tested every thing work just mtp does not work..
Still working on it.

Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk

Azan Mughal said:
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Click to expand...
Click to collapse
Officall oreo emui8 This is working twrp?

Taha0194 said:
Officall oreo emui8 This is working twrp?
Click to expand...
Click to collapse
Yep
I am using but not officiall.

Not compatible with Official Oreo
Taha0194 said:
Officall oreo emui8 This is working twrp?
Click to expand...
Click to collapse
I tried it on official Oreo.
It does not work.
Error received -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (18199 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.493s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.028s

prasanthkb said:
I tried it on official Oreo.
It does not work.
Error received -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (18199 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.493s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.028s
Click to expand...
Click to collapse
Bro. Offical oreo emui 8 working
adb command
fastboot flash recovery_ramdisk RECOVERY-V2.img
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk

Taha0194 said:
Bro. Offical oreo emui 8 working
adb command
fastboot flash recovery_ramdisk RECOVERY-V2.img
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Click to expand...
Click to collapse
Hi,
Many thanks. Flashed it finally
I want to take the TWRP backup of my Oreo.
Is it fine if i take the backup of all partitions and restore when needed ?
Some forums said not to restore OEMInfo and Product partitions with TWRP since its not 100% functional !!
I tried to backup to external SD and received error message saying "Cannot create folder, permission denied".
The same error when i used internal SD.
Can you please provide some information on this ?

prasanthkb said:
Hi,
Many thanks. Flashed it finally
I want to take the TWRP backup of my Oreo.
Is it fine if i take the backup of all partitions and restore when needed ?
Some forums said not to restore OEMInfo and Product partitions with TWRP since its not 100% functional !!
I tried to backup to external SD and received error message saying "Cannot create folder, permission denied".
The same error when i used internal SD.
Can you please provide some information on this ?
Click to expand...
Click to collapse
He's not backing up the data partition
It gives an error because of it
Remove sign from data when backing up
Also memory card format must be NTFS
*4GB does not support fat32
achievements

Azan Mughal said:
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Click to expand...
Click to collapse
so, this twrp can all save except data.
But we can restore data from emui 5.1 in emui 8.0?
merci

New Version is coming of twrp.

Azan Mughal said:
New Version is coming of twrp.
Click to expand...
Click to collapse
Great, and cant wait, when it is coming ?

Coming Soon
Coming Soon Every thing work and Now tell about it after view whats we need more.
You can unlock frp with this recovery and backup of frp
And backup every partition.

Chisetdel31260 said:
so, this twrp can all save except data.
But we can restore data from emui 5.1 in emui 8.0?
merci
Click to expand...
Click to collapse
I have not tried yet to retrieve data from emui 5 to emui 8 but you know about Android versions emui 5 is 6.0, 7.0 and emui 8 is 8.0 so its possible to retrieve but i think apps were creating problem so its your choice what to do.

Azan Mughal said:
I have not tried yet to retrieve data from emui 5 to emui 8 but you know about Android versions emui 5 is 6.0, 7.0 and emui 8 is 8.0 so its possible to retrieve but i think apps were creating problem so its your choice what to do.
Click to expand...
Click to collapse
OK, thanks
I will test it and tell you if all is well.
thank you for your work.

Azan Mughal said:
Coming Soon Every thing work and Now tell about it after view whats we need more.
You can unlock frp with this recovery and backup of frp
And backup every partition.
Click to expand...
Click to collapse
When you are releasing the new version? I am waiting to install because I tried the V2 but it is not working phone and FAILS to install.

LINK is Here.
Download the file extract the Folder and Go to fastboot mode and double click on TWRP.bat file and you have successfully installed TWRP.
https://drive.google.com/file/d/1DkU-2c4qCm_cGzr-aaDFoFEn0YlLl6fh/view?usp=drivesdk
If anyone like my work can donate. :good:

Azan Mughal said:
Download the file extract the Folder and Go to fastboot mode and double click on TWRP.bat file and you have successfully installed TWRP.
https://drive.google.com/file/d/1DkU-2c4qCm_cGzr-aaDFoFEn0YlLl6fh/view?usp=drivesdk
If anyone like my work can donate. :good:
Click to expand...
Click to collapse
The link is only accessible by your own account. Kindly share a proper link or provide access individually bcoz I already sent you a permission request.
Download Message:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
Somehow managed to download it...
Thank you

Unofficial twrp for Elephone u pro v3.2.1.0

{
"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"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Notice1:
U Pro has A/B partitions. to prevent issues its good to flash it in both slot, because i/we can not know on which partition you are
Notice 2:
This version only working on Eragon roms
Maybe soon I'll manage it to work on stock rom
Notice 3: Sdcard now working
DOWNLOAD
TWRP for 20180227 Base via Qfil Flashtools:
Go here : https://drive.google.com/file/d/1JZ59mO07Zc1a9kdA6j7LJvrgc9g2kf5d/view?usp=sharing
TWRP for 20180511 Base and newer:
Go here: https://drive.google.com/file/d/1RrWuncXsH8GtCTbaEgGpDffRUDK9fMVv/view?usp=sharing
INSTALLATION
if you use the old 20180227 Base you have to use Qfil Flashtools , because fastboot commands dont work in that Build.
we have a good guide of how to use FLashtools already
look here: https://forum.xda-developers.com/android/development/guide-elephone-pro-user-manual-t3775895
if you are on 20180511 Base and newer you can use fastboot commands
required : ADB and fastboot
enable usb debugging in developer settings.
do this:
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a twrp.img
after that we flash it also in slot b
Code:
fastboot flash boot_b twrp.img
Special thanks to
teamwin for this awesome custom recovery
And @skeleton1911 for his help

Reserved 1

I loaded up all my usual apps and settings and was going to do twrp backup and strange thing happened: the recovery doesn't see my external SD. I can see sd card's files from the phone but it's invisible in twrp. Funny, because someone couldn't flash ROM from sd yesterday and I did, I still have the ROM files there on SD. I tried to pick the sd storage for the backup and that's how I found out it's missing. The trwp was flashed per instruction: fastboot, 'a' & 'b' then I did a total wipe in twrp and flashed the ROM twice - that was it. Probably some conflict between a an b again? It can wait, am not in the hurry, this Rom otherwise looks really good, it boots faster then the stock, nice.

mzsquared said:
I loaded up all my usual apps and settings and was going to do twrp backup and strange thing happened: the recovery doesn't see my external SD. I can see sd card's files from the phone but it's invisible in twrp. Funny, because someone couldn't flash ROM from sd yesterday and I did, I still have the ROM files there on SD. I tried to pick the sd storage for the backup and that's how I found out it's missing. The trwp was flashed per instruction: fastboot, 'a' & 'b' then I did a total wipe in twrp and flashed the ROM twice - that was it. Probably some conflict between a an b again? It can wait, am not in the hurry, this Rom otherwise looks really good, it boots faster then the stock, nice.
Click to expand...
Click to collapse
It's fixed now i uploaded the new twrp now everything working very well

Maherabed1986 said:
It's fixed now i uploaded the new twrp now everything working very well
Click to expand...
Click to collapse
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space.
Hey Guys, we have two parallel Upro Universes here, two seperate threads on "Unofficial twrp for Elephone u pro v3.2.1.0", would that be _a and _b?

mzsquared said:
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space.
Hey Guys, we have two parallel Upro Universes here, two seperate threads on "Unofficial twrp for Elephone u pro v3.2.1.0", would that be _a and _b?
Click to expand...
Click to collapse
Can you join us on Telegram group plz
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg

Maherabed1986 said:
Can you join us on Telegram group plz
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
Click to expand...
Click to collapse
opened my acct in telegram, so, what next?

mzsquared said:
opened my acct in telegram, so, what next?
Click to expand...
Click to collapse
Tab the link again then join the group

mzsquared said:
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space
Click to expand...
Click to collapse
same problem here

jimibxl said:
same problem here
Click to expand...
Click to collapse
reinstalled, reflashed, flashed and reinstalled and still no show for extSD in TWRP. But am all set for now, placed Eragon v.5 and Magisk Mgr on microSD/USB C OTG dongle and installed the ROM(zip) + Magisk(zip) from there via TWRP. Everything's good 'xept that 0 extSD. I was also able to do TWRP nandroid sys backup which went on that OTG dongle, some 3.8GB, that'll save me some time in the future I'd think :laugh: So, with the Springtime weather outside am gonna leave my computer stuff now and go out to ejnoy some of that Spring! See you later!

Hi Skeleton my problem is:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
Can you help me??
Thanks

Enrique602012 said:
Hi Skeleton my problem is:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
Can you help me??
Thanks
Click to expand...
Click to collapse
You are on build 20180227 so the flash commands not available you must use Qfil flashing tools to flash twrp

mzsquared said:
reinstalled, reflashed, flashed and reinstalled and still no show for extSD in TWRP. But am all set for now, placed Eragon v.5 and Magisk Mgr on microSD/USB C OTG dongle and installed the ROM(zip) + Magisk(zip) from there via TWRP. Everything's good 'xept that 0 extSD. I was also able to do TWRP nandroid sys backup which went on that OTG dongle, some 3.8GB, that'll save me some time in the future I'd think :laugh: So, with the Springtime weather outside am gonna leave my computer stuff now and go out to ejnoy some of that Spring! See you later!
Click to expand...
Click to collapse
On last build of twrp everything is working perfectly

Thanks but I run now Eragon V6. Each time start the Rom appear yellow !.

Enrique602012 said:
Thanks but I run now Eragon V6. Each time start the Rom appear yellow !.
Click to expand...
Click to collapse
It's because the unlocked bootloader it's normal

The problem is when I try to install TWRP now run V6:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567
Thanks again

Hi Skeleton now I try to install TWRP and first no problem with boot_a and boot_b.
I run V6.
When restart the phone initial appear ! yellow........next appear TWRP and nothing hapen. Each time restart phone appear the same thing. Many times.
I try to install TWRP with QPST and nothing happend
I reinstall V5 by zip file and reinstall V6 by QPST and all ok.
What can I do to install TWRP without problem.
Thanks so much

Maherabed1986 said:
fix this command from
Code:
fastboot falsh boot_b twrp.img
to
Code:
fastboot flash boot_b twrp.img
Click to expand...
Click to collapse
And thanks dude. :good:

powergo said:
And thanks dude. :good:
Click to expand...
Click to collapse
Thanks dude but there's no difference between the two codes ?

Maherabed1986 said:
Thanks dude but there's no difference between the two codes
Click to expand...
Click to collapse
i mean falsh to flash
:good:

Oukitel WP5 flashing AOSP 10

Just wanted to write a report on the successful flashing Oukitel WP5 (version 4/32 Gb) with Mediatek MT6761 + PowerVR Rogue GE8300
I have used instructions in this thread with some modification.
disclaimer (short version): Do not do any of the following unless you are prepared to lose your warranty or brick your phone. Everything that you do with your phone is at your own risk, and no one but you is responsible for it.
For flashing i used adb and fastboot. In Debian 10 it's easy to install:
sudo apt install adb fastboot
How to do that in other systems you my read on this forum or do some googling.
System image from phh's you can download here. I have used system-quack-arm64-ab-floss.img.xz image.
The steps of the procedure are almost the same as for WP6, except for one important point:
1. Battery must be charged. Unlock the bootloader as usual (developer options - enable USB debugging and OEM unlock). Connect phone to computer with USB cable
2. Type:
adb devices
ADB should now detect your device, and a request for access will pop up on your phone asking to allow permission. Allow it.
Next type:
adb reboot bootloader
The phone will reboot into fastboot mode, wait a few seconds until "fastboot mode" is shown on the bottom left of your phone's screen.
Next type:
fastboot devices
Fastboot should detect your device
Next type:
fastboot flashing unlock
Fastboot and your phone will ask you to confirm that you want to unlock your bootloader, confirm it using the volume buttons on your phone according to the instructions on your phones screen.
After the bootloader has unlocked successfully you need to format your device, type:
fastboot erase userdata
You'll receive a confirmation that data has been formatted.
Type:
fastboot erase system
You'll receive a confirmation that system has been formatted.
3. Next, you need to disable protection from booting non-factory firmware or whatever it is called - let the experts correct me. For that i flashed vbmeta partition with blank one (see attached file):
fastboot flash vbmeta vbmeta-blank.img
This is important step! If you do not do that - you will get phone infinity cycle trying to boot and rebooting
4. Final step, flashing the system image, that you have previously download and unpack:
fastboot flash system system-quack-arm64-ab-floss.img
and reboot after process is finished:
fastboot reboot
P.S. After booting everything works like a Swiss watch

I note that there is an AOSP 11 available since a few days. Any reason to avoid trying that on my WP5?
https://github.com/phhusson/treble_experimentations/releases/download/v302/system-roar-arm64-ab-floss.img.xz

I have tried AOSP 11 on Oukitel WP6 - it was slow (compared to AOSP 10) and, as i remember, on AOSP 11 does not worked some applications, that i need.
But you can try it yourself. Since there was several new releases - may be something was improved.

I went ahead and installed phh's AOSP 11 ndklite vanilla on my WP5 and it all seems to work ok. I'm confused at having superuser preinstalled and unsure how that affects trying to install magisk. but anyhow, for anyone wondering, it worked.

I'm kind of confused by the AOSP install. I wanted to change /system/etc/hosts but it is RO and can't be mounted RW despite superuser root. Online searches suggest I need magisk with systemless enabled. however unlike playing with the stock rom, i can't figure out how to get my boot.img to patch. i thought i'd find it in the AOSP image file but I can't locate it. I thought I could perhaps us SP flashtool to readback, but I don't have the scatter file, unless it's the same as stock. Perhaps the boot.img is the same as stock. I'm out of my depth.

gringobenuk said:
I'm kind of confused by the AOSP install. I wanted to change /system/etc/hosts but it is RO and can't be mounted RW despite superuser root. Online searches suggest I need magisk with systemless enabled. however unlike playing with the stock rom, i can't figure out how to get my boot.img to patch. i thought i'd find it in the AOSP image file but I can't locate it. I thought I could perhaps us SP flashtool to readback, but I don't have the scatter file, unless it's the same as stock. Perhaps the boot.img is the same as stock. I'm out of my depth.
Click to expand...
Click to collapse
.
The thumb rule of applies to all operating systems. DON'T use them, if you can't control them. Meaning, if you have no root control and firewall for what goes in and out. How do you know what's going on in the background?. My point is... Using a system you are rooted in and can control, rather than using the latest Bling Bling systems, for the sake of trend ore popularity. You should use an older proven and rooted system....
I guess your curiosity and search for knowledge is the reason why you hang out here with us at XDA.
XDA is the epicenter of public knolitsh for smartphones and technology...
Millions of brains combined into a singularity for problem solving and solutions...
.

Took me the better part of a day to figure all this out, but I've finally got phh's A11 GSI running on my 3GB model. I've added a brief guide at https://github.com/adil192/OukitelWP5TrebleTips/ if anyone with this phone stumbles across this in the future.

Risbele94 said:
I've added a brief guide at https://github.com/adil192/OukitelWP5TrebleTips/ if anyone with this phone stumbles across this in the future.
Click to expand...
Click to collapse
I have WP5 3 GiB RAM model and flashing ARM32 images ( like mentioned on this site: system-roar-arm32_binder64-ab-vndklite-gapps.img ) results in a boot stuck.
ARM64 images (AOSP9, AOSP10, ...) works.
I can confirm - with Android 10 stock firmware from https://oukitel.com/pages/download-center phone constantly restarts itself. (I wrote about this to Oukitel but appears that they don't give a sh*t...)
Why sometimes *.img uploading speed is ~20 MB/s :
>fastboot flash system system-roar-arm32_binder64-ab-vndklite-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/15 (131060 KB) OKAY [ 6.349s]
Writing 'system' OKAY [ 1.811s]
Sending sparse 'system' 2/15 (131048 KB) OKAY [ 6.309s]
Writing 'system' OKAY [ 1.794s]
Sending sparse 'system' 3/15 (131068 KB) OKAY [ 6.299s]
Writing 'system' OKAY [ 1.788s]
[...]
and another time only ~3 MB/s ?
>fastboot flash system system-roar-arm64-ab-gapps.img
Sending sparse 'system' 1/18 (131068 KB) OKAY [ 42.548s]
Writing 'system' OKAY [ 1.799s]
Sending sparse 'system' 2/18 (131068 KB) OKAY [ 42.618s]
Writing 'system' OKAY [ 1.821s]
Sending sparse 'system' 3/18 (131068 KB) OKAY [ 42.647s]
Writing 'system' OKAY [ 1.824s]
[...]

[OOS13] IN2023_11_F.62 Patched boot.img

Hello guys !
F.62 update is rolling out on the OnePlus 8 Pro, and I managed to download the full OTA zip package through the OxygenOS Updater app.
I extracted the boot.img file thanks to the payload_dumper_go tool on this thread.
This post is inspired from this one from @bebop80 (thank you !) since it is very simple, and we love what is simple here
Steps :​> Make sure your device is a OnePlus 8 Pro running on IN2023_11_F.62 Official version, with an unlocked bootloader.
> Download _IN2023_11_F62-Patched.img from https://pilou.org/OxygenOS/IN2023_11_F.62/ and vbmeta.img below.
> Connect your device to your computer, and make sure it is recognized when typing adb devices
> Enter into fastboot mode using the command adb reboot fastboot
> flash the patched boot image using fastboot flash boot _IN2023_11_F62-Patched.img
> (Optionnal, recommended by Magisk) flash the vbmeta image using fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
> fastboot reboot
> Open magisk app (If not installed, install the apk located in your internal storage root) and hit Install then use the recommended method.
> Reboot, your device is rooted

thanks gor the share.
have you been able to install the update with inbuild updater "Local install"
for me it will fail at 27%, no matter what i updater i use( inbuild or updater apks from oneplus). downloaded update already 3 times... pretty strange

SchWeinSAuG said:
thanks gor the share.
have you been able to install the update with inbuild updater "Local install"
for me it will fail at 27%, no matter what i updater i use( inbuild or updater apks from oneplus). downloaded update already 3 times... pretty strange
Click to expand...
Click to collapse
I received the update through the phone settings, before Oxygen Updater app released it. I installed it without any issue. I was on IN2023_11_F.15 software version. That's strange it doesn't work for you ..
The only thing I can recommend is a factory reset, but I understand it's annoying

Great post (even though I don't own the Pro). I like the idea of having pre-patched images available instead of going through the whole process for every new phone (which can be time-consuming on some models).
Funnily enough, my Oneplus 8, with great zeal, tried to install this update but of course it failed since its for the wrong model

i get
fastboot: error: Failed to identify current slot
i tryed
fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.000s
later tryed again and i have slot a as active
fastboot --set-active=a
< waiting for any device >
Setting current slot to 'a' OKAY [ 0.009s]
Finished. Total time: 0.012s
fastboot flash boot patchedF62.img
fastboot: error: Failed to identify current slot
---
after some more trials i could flash it

how to get rid of the info at start - yellow status - phone is unlocked

Google pay is recognize the root.