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)

[GUIDE] How to Change Boot Logo (Splash Screen) of Razer Phone (cheryl)

Note:
This is not bootanimation, this is the splash screen (the boot logo which is displayed when device is switched ON)
This is for Razer Phone Only.. (codename: cheryl)
(For other devices, please send me your splash.img so that I can create a tool for you too..)
Requirements:
1. Rooted Razer Phone (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Razer_Phone_Cheryl_Splash_Maker.zip
2. Make sure you have a picture with resolution 1440x2560px.
Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
3. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@game_guy who provided the stock splash.img of Razer Phone (cheryl)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..

You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.

RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Splash screen is different from boot animation. The one which appears before boot animation

Oops sorry, brain fart.
I guess I wasn't paying attention all that well.

@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?

linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed

eoghan2t7 said:
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
Click to expand...
Click to collapse
Nope, the splash screen is just a BMP picture (in RGB24 format) with an empty 16kB header before the picture.
You could see that in the batch file's code.
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
The warning message actually is from the bootloader itself.
Most probably, it will be present in the 'aboot' partition, but it's not as easy as changing splash screen.
The same issue was also present in Nextbit Robin. (a company acquired by Razer)
Because, the bootloader is just a raw file when dumped, which needs to be checked using hex editor or whatever tool to see if it has an image and find its offset and patch the image accordingly, or even, it might be possible to find the location of where the amount of warning time is present and make it 0.
But the problem is, since it's a raw dump and the bootloader is the code that brings up the kernel, it's highly possible that if we do something wrong, the device might be hard-bricked (even fastboot mode is from bootloader). Also, today's bootloaders might even be signed, so patching the bootloader for warning picture might not necessarily work since the device won't be able to verify the integrity of bootloader partition after its contents change.
So, if there's a tool with which you can flash and recover a hard-bricked phone, and if you're willing to test the modified bootloaders that I create, send me the bootloader partition dump. I'll take a look at it

@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)

linuxct said:
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
Click to expand...
Click to collapse
Lol I remember doing stuff with my Droid RAZR and Bionic for dhacker back in the day. It was worth it in the end, but took time for the recover from hard brick processes to come about.

RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Hi, can you please upload and share the default bootanimation here? I have deleted mine and would like to get it back.

[TWRP] TWRP 3.4-0-0 For Blu G90 G0310WW [MT6765][Android 10]

First released twrp for BLU G90 phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
**Solved with new tree file**--data decryption is not working, so not able to read or backup internal storage.--
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device Tree :
New
GitHub - mrmazakblu/device_PBRP_BLU_G90_G0310WW at TWRP
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Download :
Releases · mrmazakblu/device_PBRP_BLU_G90_G0310WW
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Old
https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW
Download : https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW/releases

ADB Sideload is also broken.

Shananiganeer said:
ADB Sideload is also broken.
Click to expand...
Click to collapse
Most likely due to no able to read/ write to /data there is no place to temp store the zip.
Working on alternative options at the moment, as I am having trouble getting build correct to make decrypt.
Alternative is a modified /vendor.img, so device is not encrypted. But this of course is less secure.

I reformatted /data so it was unencrypted, but still couldn't use adb sideload. I was able to use adb push to put files onto the phone, but that didn't end up mattering as without rw to /system I can't install gapps XD. I'll have some time this weekend to take a look at things and try and help debug the decryption.

Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.

mrmazak said:
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
Click to expand...
Click to collapse
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.

Ivisibl3 said:
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Click to expand...
Click to collapse
To modify it "live" yes maybe.
You can modify the extracted system, as I did , using linux mount, and flash the system back modified, just like a gsi rom.
But for root, can't say.

On the latest build, was able to mount /system r/w. And successfully change the contents of it.
The patches in twrp source is not finished yet, so normal zip installs are not coded. But using adb shell (or TWRP terminal ) seem to be working.
This New build to be uploaded on github device source, as release "test build 9"

I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Well, the first thing I'm concerned with here is , I'm not sure if THIS TWRP will work on the g90 pro.
But it might be possible. I was able to mount system as r/w on my g90 in TWRP.
You would need to fastboot flash --disable-verity vbmeta and vbmeta_system to prevent red state bootloader lockout.

Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.

Shananiganeer said:
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Click to expand...
Click to collapse
The stock /product partition is not needed in non stock roms. Google gsi flashing guide tells show to delete logical partition product.
Code:
fastboot delete-logical-partition product
This is probably what is needed.
Don't know about your plan to increase stock super.img. no idea about why you mention boardconfig.mk

This TWRP is before the patch for TWRP fastbootd, so it is not included. I have resynced source, and will see if new build works, or not. If it does will post new release.

I mentioned BoardConfig.mk because the size of the super partition is listed there, but you were totally right about the product partition and I was able to flash LOSQ+gapps after deleting it. Thanks for the assist, and your work on porting TWRP to this awesome device! Will continue to keep an eye on your work as TWRP finalizes their support for Android 10.

Will this work for the G90 Pro? My guess is not but figured I'd ask

KryptekKnight said:
Will this work for the G90 Pro? My guess is not but figured I'd ask
Click to expand...
Click to collapse
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.

mrmazak said:
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
Click to expand...
Click to collapse
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide

KryptekKnight said:
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
Click to expand...
Click to collapse
I have no idea about gcam

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Sorry OP.....
I need to get 01 post of your topic to report on custom recoveries on the G90 Pro.
For new users, you should know about the Android 10 permission structure.
In TWRP or PBRP, through the File Manager, it is not possible to copy files to the superpartition. But you can copy files from the superpartition to the internal SD card.
Therefore, to modify files from the super partition, it will be necessary to extract the super partition and extract system-product-vendor to then carry out the modifications and repackage.
Using Havocv3.11 the volume issue dissapears...........

Well all, thanks to @lopestom , we may soon have a new device tree to build recovery from , and data decryption is working on first test img. New recovery would be pbrp instead of twrp.

no any system in TWRP (wipe)

Hello,
Why are the no system in TWRP->Wipe->Advanced Wipe
See the photo added.
But i got 2 Storage. and i can't fix (Repair or Change File System)
questions is, how can i get system back?
i'm in mediatek / umidigi power
Can you help me out?
Thanks for your time

inside TWRP (Wipe) 2xStorage,
1. Storage: Size 0MB
2. Storage: Size 0MB
But inside Data:
1. Storage: Size 53801MB
Mabye thats why, there is no system?
But how can i Change Data to System

Here is the log if the TWRP/Phone

The /system partition is the area on the Android device's internal memory that contains the operating system, i.e. Android itself.
Wondering why you want to wipe this partition?

jwoegerbauer said:
The /system partition is the area on the Android device's internal memory that contains the operating system, i.e. Android itself.
Wondering why you want to wipe this partition?
Click to expand...
Click to collapse
why not?

007fred62 said:
Here is the log if the TWRP/Phone
Click to expand...
Click to collapse
you provably using a TWRP with issue or you actually manage to delete your /system partition wtf??
how do people manage to fuvk up so bad like this

Why i try to format the device is i can't install custom OS
Then i try to flash the system.img i got Boot Loop in system logo
And i can't install OS
So i think if there is a partition "system" i can install the OS
But how can i install OS on the phone ?

007fred62 said:
Why i try to format the device is i can't install custom OS
Then i try to flash the system.img i got Boot Loop in system logo
And i can't install OS
So i think if there is a partition "system" i can install the OS
But how can i install OS on the phone ?
Click to expand...
Click to collapse
what custom rom you are trying it install??

ineedroot69 said:
what custom rom you are trying it install??
Click to expand...
Click to collapse
How to Install Lineage OS 17.1 for UMIDIGI Power | Android 10 [GSI treble]
Today we will guide you on how to install the Lineage OS 17.1 on the UMIDIGI Power device by following our guide.Lineage OS 17.1 GSI
www.getdroidtips.com

what model of umidigi you have?

ineedroot69 said:
what model of umidigi you have?
Click to expand...
Click to collapse
(UMIDIGI Power) not 3 just (UMIDIGI Power)​

007fred62 said:
(UMIDIGI Power) not 3 just (UMIDIGI Power)​
Click to expand...
Click to collapse
btw what is your concern? is your device able to boot at this point or no?

ineedroot69 said:
btw what is your concern? is your device able to boot at this point or no?
Click to expand...
Click to collapse
Yes i can start it on with official ROM for umidigi website

007fred62 said:
Yes i can start it on with official ROM for umidigi website
Click to expand...
Click to collapse
read this https://www.getdroidtips.com/how-to...eneric-System-Image-on-Project-Treble-Devices it clearly say you don't need to wipe your system partition you just need to factory reset and fastboot flash commands

ineedroot69 said:
read this https://www.getdroidtips.com/how-to...eneric-System-Image-on-Project-Treble-Devices it clearly say you don't need to wipe your system partition you just need to factory reset and fastboot flash commands
Click to expand...
Click to collapse
Hello,
i read the guide,
and i'm stuck here
Select the ‘Install Image’ button at the bottom > Navigate to the storage and select the IMG file.
See photo i added
Not system to flash too.
as i say early up no system partitions

007fred62 said:
Hello,
i read the guide,
and i'm stuck here
Select the ‘Install Image’ button at the bottom > Navigate to the storage and select the IMG file.
See photo i added
Not system to flash too.
as i say early up no system partitions
Click to expand...
Click to collapse
do it via fastboot not twrp ... just follow the guide carefully

ineedroot69 said:
do it via fastboot not twrp ... just follow the guide carefully
Click to expand...
Click to collapse
I have try that mabye times,
Only stuck on system logo booting and nothing helps

007fred62 said:
I have try that mabye times,
Only stuck on system logo booting and nothing helps
Click to expand...
Click to collapse
perhaps your system partition is read-only so you can't modify it ?
most Android version 9, 10 and 11 have read-only system partition

ineedroot69 said:
View attachment 5263709
Click to expand...
Click to collapse
I can't find that in my TWRP recovery.

Solve fastboot: error: the boot partition is too smaller

I am trying to root my tecno f1 pro with magisk manager soon i was flashing the magisk_patched.img renamed boot.img i got an error
code:
C:\Program Files\platform-tools>fastboot flash boot boot.img
fastboot: error: boot partition is smaller than boot image
How can I fix this?

Re-partition Android of your phone so the boot.img fits.

jwoegerbauer said:
Re-partition Android of your phone so the boot.img fits.
Click to expand...
Click to collapse
How do I do that? My boot partition is 233kb and my Magisk patched image is 32mb.

Beelzebub6 said:
How do I do that? My boot partition is 233kb and my Magisk patched image is 32mb.
Click to expand...
Click to collapse
You have a wrong file patched. Normally the patched file can with 10MB or more.
Since you wrote the patched file have ONLY 233KB so never you can flash that!

DragonPitbull said:
You have a wrong file patched. Normally the patched file can with 10MB or more.
Since you wrote the patched file have ONLY 233KB so never you can flash that!
Click to expand...
Click to collapse
lol, my phone has updated since then, your right.
But then I downloaded my new stock rom which is android 11 and tried to continue with that but it still says the boot partition is too small. How would I re-partition so then my patched file can fit?
And also the original boot file straight outta boot.img.lz4 is 32.0mb same as patched but inside the .lz4 file it says that it is 16 bytes, should I worry about that?

Beelzebub6 said:
lol, my phone has updated since then, your right.
But then I downloaded my new stock rom which is android 11 and tried to continue with that but it still says the boot partition is too small. How would I re-partition so then my patched file can fit?
And also the original boot file straight outta boot.img.lz4 is 32.0mb same as patched but inside the .lz4 file it says that it is 16 bytes, should I worry about that?
Click to expand...
Click to collapse
I think thats just compression saying that but if u need try backup the boot partition via another method