[GUIDE][FIX] Bricklooping Lettuce (YU Yuphoria) , No IMEI , Corrupt EFS

[GUIDE][FIX] Bricklooping Lettuce (YU Yuphoria) , No IMEI , Corrupt EFS - YU Yuphoria

Hello Good People !!!
So yesterday,I encountered a brickloop on my lettuce and after around 10 hours of trying almost all methods,I was finally able to solve it.Though,mainly I was able to try all these as I had already got my replacement request from Amazon approved...
For those who don't know,brickloop is a situation when the device bootloops just after the YU logo and this bootloop isn't resolved even after factory image flash or any other ROM flash .
I cannot guarantee that this will work for everyone. However It has proven to be a solution for almost everyone that have used it. So if it does not work I ask that you be respectful in posting as such.
I am making a package for you to download which contains all files needed to make this happen (You need three more files,modemst1.img and modemst2.img and latest CM nightly but I am not going to give you those as I don't want everyone to have my IMEI on their lettuce . Though I will definitely tell you how to get those two files.) Download the package here :- https://www.androidfilehost.com/?fid=24052804347796818
So inside it you will have these files:
persist.img
adb 1.0.32
INSTRUCTIONS :-
Please note that any commands run in fastboot mode require you to have an unlocked boot loader. If you are not sure if you are unlocked then that means you aren't! So to unlock the bootloader,follow this guide :- http://forums.yuplaygod.com/threads/official-how-to-unlock-bootloader-on-the-yu-yuphoria.13785/
Step 1 :- You need to have proper adb/fastboot drivers installed.If you have unlocked bootloader ever or did so by the above guide,you already have these drivers with you.Else,use this guide to get drivers working :- http://forums.yuplaygod.com/threads...-drivers-pack-drivers-for-adb-fastboot.15025/ After you have made the drivers to work,continue to the next step.If you have issues in making drivers work,tag me in the thread and I will try my best to help you out.
Step 2 :- Extract the downloaded Zip on the Desktop .
Step 3 :- Open the adb1032 folder extracted on the desktop and put the latest CM nightly,modemst1.img and modemsr2.img inside it.Open Command Window by pressing Shift Key + Right click anywhere inside the folder and then selecting Open Command Window here.Boot your phone to fastboot mode.
Step 4 :- Now type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 erase persist
Wait for the process to complete (Should take less than 5 seconds).
Step 5 :- Type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 flash persist persist.img
Wait for the process to complete (Should take less than 5 seconds).
Step 6 :- (In most cases,the issue is solved in the Step 5 only.But still I recommend following all these steps.If you,by any chance,don't have modemst1.img and modemst2.img with you,DIRECTLY SKIP TO STEP 7) Type the following commands one by one :-
Code:
fastboot -i 0x2A96 erase modemst1
Code:
fastboot -i 0x2A96 erase modemst2
Code:
fastboot -i 0x2A96 flash modemst1 modemst1.img
Code:
fastboot -i 0x2A96 flash modemst2 modemst2.img
Step 7 :- If you don't have TWRP flashed,flash it from this thread :- http://forums.yuplaygod.com/threads/recovery-twrp-2-8-7-0-for-yu-yuphoria-01-08-15.13974/
Step 8 :- DON'T DO fastboot -i 0x2A96 reboot BUT instead remove the battery and then put it again and boot to recovery by pressing Power+Vol. Down button.
Step 9 :- Inside recovery,in the advanced folder,select ADB Sideload and select "Wipe Dalvik Cache" and "Cache" and swipe to start ADB Sideload.
Step 10 :- In the command window on your pc,type (Replace xxx with the correct Nightly name ) :-
Code:
adb sideload cm-xx-xxxxxxxx-NIGHTLY-lettuce.zip
Wait for the nightly to flash.
Step 11 :- From inside the recovery,reboot to system.
Your phone will be back now ....... Yayyyyy !!!!
And yeah,how to get modemst1.img and modemst2.img :-
Step 1 :- Download this app on your phone :- https://play.google.com/store/apps/details?id=ma.wanam.partitions
Step 2 :- Grant root access and in the settings,select storage to external sdcard and backup format to .img .
Step 3 :- Backup all partitions by selecting them and pressing a download like button at the bottom right . (Though we need to backup only modemst1 and modemst2 but I recommend you to backup all ... But yeah,first backup modemst1 and modemst2 and then backup others.The main reason I was able to restore my phone was because I had backup of all partitions,)
Step 4 :- In your external sdcard,find the modemst1.img and modemst2.img and save them inside the specified folder and also at as many secure places as you can so that these files never get lost.)
Please Note :- Most of the times,even a corrupt EFS is solved just by erasing and flashing persist.So don't worry much if you forgot to take its backup.Also,sometimes,a brickloop might be caused due to any other partition getting corrupted and that too can be solved but that is very rare.If this guide doesn't help in solving brickloop,tag me here,and I will help you out.

Reserved to improve the look of the post ... And also my story of how I arrived to this solution ..
And teaser : Another great guide coming soon ...

im having a weird situation here....i flashed aicp rom it bootlooped...then i restored my twrp backup of stock...its also stuck at boot animation......can you help me out..

sdnavale said:
im having a weird situation here....i flashed aicp rom it bootlooped...then i restored my twrp backup of stock...its also stuck at boot animation......can you help me out..
Click to expand...
Click to collapse
here you go bro.

Hi.. I'm new to Snapdragon chipsets..
Can I know what are these images for: persist.img, modemst1.img and modemst2.img
I mean, what are these partitions used for?

GokulNC said:
Hi.. I'm new to Snapdragon chipsets..
Can I know what are these images for: persist.img, modemst1.img and modemst2.img
I mean, what are these partitions used for?
Click to expand...
Click to collapse
These store the IMEI of your phone and some more important stuff... But IMEI is the most important of those...
Sent from my YU5010 using Tapatalk

@Naman Bhalla can u make a guide for hardbrick also? If you can?
Sent from my YU5010 using Tapatalk

Code:
target reported max download size of 268435456 bytes
sending 'persist' (32768 KB)...
OKAY [ 1.034s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 1.430s
i get this error
Bootloader UNLOCKED Successfully though

Zeehan said:
i get this error
Bootloader UNLOCKED Successfully though
Click to expand...
Click to collapse
Restart into bootloader and then see , if it works

Same Error
TheDemon12 said:
Restart into bootloader and then see , if it works
Click to expand...
Click to collapse
Hi Pal,
I tried restarting into the bootloader as well and am still getting the same error!! Please help!

Step 4 :- Now type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 erase persist
Wait for the process to complete (Should take less than 5 seconds).
Step 5 :- Type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 flash persist persist.img
Wait for the process to complete (Should take less than 5 seconds).
Click to expand...
Click to collapse
I encountered
FAILED (remote:flash write failure)

xmertrans said:
I encountered
FAILED (remote:flash write failure)
Click to expand...
Click to collapse
Looks like partitions are corrupt.

Naman Bhalla said:
Looks like partitions are corrupt.
Click to expand...
Click to collapse
Yes I tried formatting with help of twrp it showed format successful but still twrp showed memory as 0mb

Code:
C:\adb>fastboot -i 0x2a96 erase modemst1
erasing 'modemst1'...
FAILED (remote: failed to erase partition
)
finished. total time: 0.034s
I am getting this error while erasing the modemst partitions. Can I continue with the flashing the modemst partitions directly?

Naman Bhalla said:
Looks like partitions are corrupt.
Click to expand...
Click to collapse
Is there a way to correct the partitions?

"FAILED (remote: flash write failure)"
When I try to flash persist, using the following command -
fastboot -i 0x2A96 flash persist persist.img
I get the error -
"FAILED (remote: flash write failure)"
Please help !

@Naman Bhalla,
I knew you from the OnePlus forums unbrick tool for 1+3.
I loved your work and it really saved my ass a lots of time.
I hope you're the same person and I Thank you very much
For that tool.
Coming to Lettuce,
I have installed this ROM: https://forum.xda-developers.com/yu-yuphoria/general/rom-lineage-os-14-1-lettuce20170108-t3538332
And suddenly my phone got blank. I can't access anything..
And all I can see is a ? icon what ever I restart the phone to, every reboot to bootloader/ recovery or even when connected to PC.. it's just the battery icon. The device is not even detected as any type of device in PC.
I tried the emmc dump method using first 200MB dumb, no luck there.
Can you provide me any other method to make my phone work again?
Please help me..

@Naman Bhalla
Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
*
But after going through some of your posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
************************ USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
*
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.
*

How can i find modem files as i dont have their backup?
Is their any way of getting volte on yuphoria 5010?

not working bro plz help

Related

[FLASH][ROOT]Android 4.3 Stock[Nexus 7 grouper/nakasi]

How to Flash Android 4.3 on your Nexus 7 nakasi/grouper (wifi only)
Code:
/*
* I am not responsible for bricked devices
* or something else you do with this toturial
*
* Every 60 Seconds In Africa A Minute Passes.
* Even for that I'm not responsible!!
*/
Needed:
Android SDK
Factory Image from Google
ChainFire SuperSU
ChainFire SuperSU [Uploaded.net Mirror]
TWRP Recovery
TWRP Touch Recovery v2.2.1 [Uploaded.net Mirror]
or
CWM Recovery
CWM Touch Recovery v6.0.3.1 [Uploaded.net Mirror]
Attention: Bootloader MUST be unlocked.
Step by Step Instructions flashing Rom without loosing Data:
Download the Stuff up there.
Unzip the Factory Image "nakasi-jwr66v-....tgz". In there you will find another Archive named like this "image-nakasi-jwr66v.zip". Unzip it.
Open file explorer on computer and change to the "Android SDK" directory and change to platform-tools folder
Press [SHIFT] + Right Click and click "Open Command Window Here", then Commandline should appear
Be sure all your data is backed up. If you don't have done already, do it NOW!!
Switch to the device and shut it down.
Press [POWER]+[VOL-] button to start into bootloader
Now switch to the PC again and in the command line type:
Code:
fastboot flash bootloader <path_to_bootloader-grouper-4.2.3>
But instead the <...> type the path to the bootloader!!
After that you can run following command
Code:
fastboot reboot-bootloader
Your device will reboot now with new bootloader.
After it write following commands
Code:
fastboot flash system <path_to_system.img>
fastboot flash boot <path_to_boot.img>
fastboot flash userdata <path_to_userdata.img>
Now you have flashed your Devices System, Kernel and Userdata partition.
Then
Code:
fastboot reboot
for rebooting your device into System (this could take a couple of minutes)
Step by Step Instructions Rooting Android 4.3:
Copy the ChainFire SuperSU (.zip) to the root of your sdcard
Shutdown device and boot into bootloader again. ([Power]+[Vol-] Buttons)
In Command Line now Type following command
Code:
fastboot flash recovery <path_to_TWRP.img_or_CWM.img
for flashing the Recovery.
After flashing the Recovery navigate to the "Start Recovery" Section with the Vol Up/Down keys.
Now the Recovery sould start.
For CWM Recovery do following steps:
Switch to the "Flash ZIP from sdcard" item and press power button one time in case you have the CWM Recovery without touch.
After that switch to "Select zip from sdcard" and press power button again.
Now select the ChainFire SuperSU zip file in the root of your sdcard, which you copied in step one.
The Recovery will now flash the .zip file. After flashing has finished, reboot into system.
For TWRP Recovery do following steps:
Tap the "Install" Button in the Recovery
After that you have to select the ChainFire SuperSU zip file in the root of your sdcard, which you copied in step one.
After that swipe to flash the zip file
The zip will be flashed and after that you can reboot into system again
Now you are done.
Have Fun

yeahhhh

Code:
fastboot flash data <path_to_userdata.img>
should be
Code:
fastboot flash userdata <path_to_userdata.img>

any idea how this comes?
Code:
F:\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\pla
tform-tools>fastboot flash bootloader F:\nakasi-jwr66v-factory-d341d356\nakasi-j
wr66v\bootloader-grouper-4.23
error: cannot load 'F:\nakasi-jwr66v-factory-d341d356\nakasi-jwr66v\bootloader-g
rouper-4.23': [B]No error[/B]
F:\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\pla
tform-tools>c

decat said:
any idea how this comes?
Code:
F:\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\pla
tform-tools>fastboot flash bootloader F:\nakasi-jwr66v-factory-d341d356\nakasi-j
wr66v\bootloader-grouper-4.23
error: cannot load 'F:\nakasi-jwr66v-factory-d341d356\nakasi-jwr66v\bootloader-g
rouper-4.23': [B]No error[/B]
F:\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\pla
tform-tools>c
Click to expand...
Click to collapse
The file extension is missing!!
Sent from my Nexus 7 using xda app-developers app

These instructions worked perfectly for me! Thanks for putting this guide together!

I've been trying for a while to get 4.3 installed and this finally worked.

trestevenson said:
These instructions worked perfectly for me! Thanks for putting this guide together!
Click to expand...
Click to collapse
So using these directions will preserve data? I thought when you flash userdata you are wiping your data partition?

Followed your instructions to the letter and everything worked great, however, my device is only showing I have 6GB of total space on a 32GB model! I've never run into this problem before with all the roms and restores that I've done. Any suggestions?

docangle said:
So using these directions will preserve data? I thought when you flash userdata you are wiping your data partition?
Click to expand...
Click to collapse
I just noticed the same. I'm going to see if rooting and doing a complete wipe helps.

my 16GB nexus 7 shows only 6 GB storage when I connect it to PC

cerisk said:
my 16GB nexus 7 shows only 6 GB storage when I connect it to PC
Click to expand...
Click to collapse
same here

docangle said:
same here
Click to expand...
Click to collapse
cerisk said:
my 16GB nexus 7 shows only 6 GB storage when I connect it to PC
Click to expand...
Click to collapse
I plugged mine in and it showed up as 4 gb left. I went through and deleted the old back ups that I had and I was back up to 10 or so free, or something like that.

I finally got my drive space back by running these commands before I flashed:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Now the only problem that I am having is that I am getting a supersu error: "there is no su binary installed, and supersu cannot install it." But I still have cwm recovery.

Reformatting through recovery fixed the showing only 6/27.5GB available.

I have the same "supersu error" problem as well.
Even after I wiped everything and flash a stock-rooted ROM (in another thread), this problem happens again ...
--edited--
Thanks @scoopman,
The "supersu error" problem is solved after I re-flash the whole ROM and answer "NO" on exiting CWM (NOT "YES")
calbrs said:
I finally got my drive space back by running these commands before I flashed:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Now the only problem that I am having is that I am getting a supersu error: "there is no su binary installed, and supersu cannot install it." But I still have cwm recovery.
Click to expand...
Click to collapse

icephreaq said:
Followed your instructions to the letter and everything worked great, however, my device is only showing I have 6GB of total space on a 32GB model! I've never run into this problem before with all the roms and restores that I've done. Any suggestions?
Click to expand...
Click to collapse
cerisk said:
my 16GB nexus 7 shows only 6 GB storage when I connect it to PC
Click to expand...
Click to collapse
docangle said:
same here
Click to expand...
Click to collapse
poda13 said:
I plugged mine in and it showed up as 4 gb left. I went through and deleted the old back ups that I had and I was back up to 10 or so free, or something like that.
Click to expand...
Click to collapse
Here Is The Answer!
I if you are paying attention during the flash you will notice the extra Partitioning.
http://forum.xda-developers.com/showthread.php?t=1781250

kevin0164 said:
I have the same "supersu error" problem as well.
Even after I wiped everything and flash a stock-rooted ROM (in another thread), this problem happens again ...
Click to expand...
Click to collapse
Okay I found this, don't know why this one works and the other doesn't. But try the link on this page https://plus.google.com/app/basic/st...l1aoor5ezninhc
I flashed a complete wipe which took out the root from the original 4.2.2 version. Installing the above link worked perfectly to get me root back on the 4.3 version.
All credit goes to danvee posting the link in section http://forum.xda-developers.com/showthread.php?p=43913405

3oudreaux said:
Here Is The Answer!
I if you are paying attention during the flash you will notice the extra Partitioning.
http://forum.xda-developers.com/showthread.php?t=1781250
Click to expand...
Click to collapse
I still got this problem after following the step:crying:

tommykwan222 said:
I still got this problem after following the step:crying:
Click to expand...
Click to collapse
same here. cwm says it can't open the zip file ???

[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)

How to root the Huawei Mate 10 Lite RNL-23

There are a lot of tutorials for rooting method for the RNL-21 but nothing for the RNL-23. I use some preexisting work to finally root my Huawei Mate 10 Lite.
I want to share my experience with the community. (This is my first thread! )
Tutorial:
1) Follow this tutorial for unlocking the bootloader :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
Try to fulfill all the instruction (I was personally stuck at fastboot boot .., I had the error : FAILED (remote: Command not allowed))
2) Dowload a working TWRP
https://mega.nz/#!WVplUBrK!eZ1O3nOXN6NKMgNLa0nzKxDBu2GH_jDj-xpoarN3JkY
(I used the version from Elemental KangVip Tools : https://forum.xda-developers.com/ma...om-emui-5-1-huawei-mate-10-lite-dual-t3751864)
3) Extract the .zip, locate the twrp.img file
4) Reboot to fastboot mode, and execute :
fastboot flash recovery [PATH_TO_YOUR_FILE]/twrp.img
With my phone, fastboot boot twrp.img doesn't work, I have the error :
FAILED (remote: Command not allowed)
So to be able to boot into recovery :
5) Reboot the phone (fastboot reboot)
6) adb reboot recovery
If it is a success, you are in the TWRP recovery.
7) Download on your computer : https://forum.xda-developers.com/attachment.php?attachmentid=4353046&d=1512485623
(It is from : https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535)
8) If your data is encrypted (like me), use USB OTG (with the mount menu) or micro sd card to be able to flash supersu.zip
9) Flash it in TWRP and reboot
10) Enjoy
If you have any question, please ask me. I hope that would help someone

Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO

I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is on my old Samsung A50. I honestly don't know the first thing about the root program that android runs on so I am looking for someone that has patience that can help a noob.
I have watched many youtube videos on this topic but I have found nothing on my specific phone.
Thanks in advance

Anubis2002 said:
I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is on my old Samsung A50. I honestly don't know the first thing about the root program that android runs on so I am looking for someone that has patience that can help a noob.
I have watched many youtube videos on this topic but I have found nothing on my specific phone.
Thanks in advance
Click to expand...
Click to collapse
About ROOT: https://forum.xda-developers.com/t/...attery-charge-limit-root-application.4251443/
About GSI: You not need TWRP. But if you want backup your userdata so need install that.
All depend about your decision: I'm install GSI and test. I chose the perfect GSI for me; so I don't need the backup => you not need custom recovery so use stock recovery.
I want GSI and need backup => need TWRP.
In the true both recoveries [stock & TWRP] has the fastbootd implemented!
So you need:
1- unlock bootloader;
2- stock or specific vbmeta file;
3- know how use fastboot commands for flash GSI;
4- Every time is more security flashing Custom ROMs if you have stock ROM!
Are you ready for flash GSI??!
Even if something goes wrong and you can't "revive" the device again?
Do you have everything it takes to feel relaxed if something goes wrong or successful?!!
I can put the instructions myself. But I will never be responsible for your actions and choices.So make up your mind!

lopestom said:
About ROOT: https://forum.xda-developers.com/t/...attery-charge-limit-root-application.4251443/
About GSI: You not need TWRP. But if you want backup your userdata so need install that.
All depend about your decision: I'm install GSI and test. I chose the perfect GSI for me; so I don't need the backup => you not need custom recovery so use stock recovery.
I want GSI and need backup => need TWRP.
In the true both recoveries [stock & TWRP] has the fastbootd implemented!
So you need:
1- unlock bootloader;
2- stock or specific vbmeta file;
3- know how use fastboot commands for flash GSI;
4- Every time is more security flashing Custom ROMs if you have stock ROM!
Are you ready for flash GSI??!
Even if something goes wrong and you can't "revive" the device again?
Do you have everything it takes to feel relaxed if something goes wrong or successful?!!
I can put the instructions myself. But I will never be responsible for your actions and choices.So make up your mind!
Click to expand...
Click to collapse
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.img
{
"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"
}

EdsterX71 said:
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
Click to expand...
Click to collapse
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
EdsterX71 said:
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.imgView attachment 5337319
Click to expand...
Click to collapse
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
Flawless instructions , thank you so much! TRWP & Root!
i had to flash Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
then follow your instructions .
Because firmware BLU_G0370WW_V10.0.04.03_GENERIC the WIIFI and Bluetooth did not function when using older version boot.img .

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks

EdsterX71 said:
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
Unfortunately in the compiling TWRP time I haven't MicroSD to testing.
But now I know about and need fix so easy. The fix is not easy because my time and the issues about different adress/partition of MicroSD in G90 Pro. So I needed more knowledge and informations to fix that and need only write correct adress/partition. That's is to mount/start MicroSD automatically in the TWRP. But....
I not remember now because I not using MicroSD or OTG in the TWRP or ROMs. But maybe worked with the option in the TWRP - Wipe - FORMAT DATA; Reboot - Recovery. Test!
I have PBRP (other awesome Custom Recovery) if you want test too.
EdsterX71 said:
Flawless instructions , thank you so much! TRWP & Root!
i had to flash Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
then follow your instructions .
Because firmware BLU_G0370WW_V10.0.04.03_GENERIC the WIIFI and Bluetooth did not function when using older version boot.img .
Click to expand...
Click to collapse
It's a shame you didn't try to remove the boot.img file from version 10.0.04.03 because it would be interesting to know the kernel changes. But as far as I know it was a security update and the fix for call volume I think.
I not using Xposed a very time ago. Sorry. You need search/ask in the Xposed forun.

lopestom said:
Unfortunately in the compiling TWRP time I haven't MicroSD to testing.
But now I know about and need fix so easy. The fix is not easy because my time and the issues about different adress/partition of MicroSD in G90 Pro. So I needed more knowledge and informations to fix that and need only write correct adress/partition. That's is to mount/start MicroSD automatically in the TWRP. But....
I not remember now because I not using MicroSD or OTG in the TWRP or ROMs. But maybe worked with the option in the TWRP - Wipe - FORMAT DATA; Reboot - Recovery. Test!
I have PBRP (other awesome Custom Recovery) if you want test too.
It's a shame you didn't try to remove the boot.img file from version 10.0.04.03 because it would be interesting to know the kernel changes. But as far as I know it was a security update and the fix for call volume I think.
I not using Xposed a very time ago. Sorry. You need search/ask in the Xposed forun.
Click to expand...
Click to collapse
Yes I would like to try PBRP , Thanks, I really like the specs on the Blu G90 Pro... But to be honest the camera is crap.

EdsterX71 said:
EdsterX71 said:
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
n TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.

EdsterX71 said:
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
Click to expand...
Click to collapse
EdsterX71 said:
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.imgView attachment 5337319
Click to expand...
Click to collapse
ANy error with 10.0.04.02?
As your message and picture had BLU_G0370WW_V10.0.04.03_GENERIC
Update: Yes the kernel was changed with more informations and need new Custom recovery with that to work with new stock ROM.

EdsterX71 said:
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
Click to expand...
Click to collapse
Sent in PM to you.

I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team

lopestom said:
I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team
Need gsi link
Click to expand...
Click to collapse

Lopestom im having lags, overheat issues and system slow downs , why??
with or without gsi
my guess is hardware issue (emmc chip)

DarkeEmpire said:
I want a gsi link
Click to expand...
Click to collapse
Any GSI-Treble A10 arm64 ab - https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/

Can I use pixel experience

sometimes when transferring file from pc to the device it fails over 1mb files like what????

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
Whenever I go into fastboot mode (with the text on the bottom left) no fastboot commands will work on my G90 Pro. Therefore I can't follow the rest of the instructions. Any possible solutions? Thanks.

[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.

Database Info

welcome