Develop Bugs

[Q] Help Rooting 2.2.1 - I've tried that edition.

I, for the life of me, being a compute tech since the mid 90's, can't root this mytouch g3 slide. I have android 2.2.1 installed, I know I know, I hate it when people don't RTFM, I have tried the following:
(USB Deugging is on, charge mode only when plugged in, full android SDK kit installed and working. PDAnet drivers installed, I have superoneclick 1.9 computer see the phone fine, Goldcard works perfectly.)
1. I've tried Cyanogenmod's instructions (wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide)
-Nothing happens after 2nd to last command line of step 8
{
"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"
}
2. I have tried this "New way to downgrade from 2.2 to 2.1" (http://forum.xda-developers.com/showthread.php?t=1108316)
-4a. , It does not give me the option to "hit vol up to update"esrpimg" just flashes error no image found error messages:
3/ I have tried ULTRA EASY ROOTER (http://forum.xda-developers.com/showthread.php?t=999121)
same problem as #2's problem, just error messages.
4. And I have tried this: "How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root" (http://forum.xda-developers.com/showthread.php?t=1025336)
-Everything goes smooth until I type in this line "chmod 04755 *" which I get a bank carraige return, and I can type to my hearts content, nothing happens, can't exit, etc, have to CRTL + C to get out out of it. similar problem as #1's problem. I have tried again and again and again.
Help.

Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly

thanks for the reply poormanq45. I did make a goldcard, maybe it doesn't like my MicroSD card? Which image do you want me to install from the bootloader? Which instructions should I be following?
Which set of instructions talk about having a swap partition as your 3rd partition on the SD card?
poormanq45 said:
Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly
Click to expand...
Click to collapse

I don't remember which img I used. IIRC there are three different ones. Just try each one until one works.
It's possible that your MicroSD card isn't capable of being a goldcard. I had to try two different ones
sent from my MT3GS running CM7 nightly

My Stock 2.2.1 Process
My warranty replacement came with stock 2.2 and all of the tutorials here and elsewhere fell short. I did notice a lot of the other guides were based on "if you upgraded to 2.2"; that did not completely apply in my situation. I to am an industry professional with 14 years experience and am a stickler for detail. I had the gold card created on a SanDisk 2gb micro sd acquired from Walgreen's. I had followed all the steps in order, but the update on the first reboot never happened, it never asked and selecting the update.zip failed signature verification. I knew S-ON was set (which is the whole problem) but the guides I saw to disable it required you already be rooted (which I wasn't).
This past week I did something different. Using the official HTC MyTouch 3G Slide Froyo installer (not selecting anything just having RUU opened) I copied the folder structure (a crazy GUID looking thing) that was in my %TEMP% directory to another location. I closed out of the installer and went to that copied folder. I moved the existing "rom" file and copied the 2.1 "ESPRIMG" image there and renamed it to rom.zip. I then executed the RUU from that folder. It being an HTC official rom did allow the RUU to complete and the slide was officially downgraded to 2.1. After the reboot I verified the ROM was the older version and went ahead with what I was used to.
After that; some of my previous attempts to root were evident because I already had the "#" prompt in the adb shell. Regardless, I did repeat some of the documented steps (just in case my eyes deceived me) from the exploid method (what I used on my previous phone that was an original build). I originally flashed the CM 7.03 while the goldcard (2gb) sd was still in there. I then installed my 32GB card, then hit a nightly, then hit a few more older CM builds (had issues with sd-ext, couldn't find the original guide i used to set it up - new card as well). I did format boot, data, system, sd-ext, and the cache from the clockworkmod recovery screen before settling on CM 7.1 RC 1
If you find it necessary to create the sd-ext partition, format the fat partition in windows, format the other two in the shell. I do not recommend logging (app sync) on the first rom. Build the sd-ext first; re-rom, before doing all the account/app setup. While the phone is USB debugging mode you can use DriodExplorer to shortcut some things (especially if u have all your apks in a backup folder on your computer). I do not recommend using certain busy-box commands from the DriodExplorer terminal. The output can be out of sync at times. I have a 32gb SD and have about 29.3G on FAT, 896MB on SD-EXT (ext3 file system), and the rest on cache. After that Simple2Ext will allow for you to tell CM7 to use the SD-EXT. I do not use .android secure (the froyo apps2sd) because that causes issues when using the fat partition as disk in windows and you have something like a theme installed. Because of themes, games, and other apps I am now using 62% of the sd-ext partition. And an earlier comment I saw on the thread is right. The partition order is FAT, SD-EXT, CACHE. Where the guide is I don't recall.
Also note: If you are doing ADB commands and notice it often says the process is stale; uninstall the HTC sync (this does not affect the drivers, drivers are installed as a pre-req before HTC Sync is installed).
My only outstanding issue is the radio version might have been affected; it's not showing a version number on my info app. So I need to find a guide on verifying/upgrading the radio (one that does not involve installing the htc froyo rom).

Stuck... help.
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
-----
Okay, I have made sure my phone has 25MB free. (it told me I needed this)
I have Turn USB Debugging on.
The phone is set to charge mode only.
The phone is plugged in and drivers installed. PDANet is not running.
I've tried it with a goldcard in it and out of it.
tagr.org/ScreenShot084.jpg
I Downloaded "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here the website, (I can't post the links)
I ran setup, and left it open while I went to the temp folder and copied it all out to another location.
I went to the NEW location and deleted "rom.zip" and replaced it with the 140 MB "ESPRIMG.zip" into that folder and renamed it rom.zip
In the new folder, I ran "ARUWizard.exe", agree, agree, okay, etc.
All goes okay, I get to this screen:
tagr.org/ScreenShot091.jpg
I say next, About two minutes into it, the phone reboots, put the HTC logo on it. Then on the computer, I get to this screen:
tagr.org/ScreenShot089.jpg
The phone is stuck on the "HTC" logo when the USB is plugged in. When USB is unplugged, the screen turns to this:
tagr.org/ScreenShot090.jpg
Stuck meaning, can't reboot, turn off, etc. So I have to pull the battery. When it turns on, all seems okay, it's still at 2.2.1 though.
Thoughts?

What the... why could I post pics my first post, but not my third...new policy?
eckre said:
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
Click to expand...
Click to collapse

Okay I've figured it out and wrote up a NEW Guide: http://forum.xda-developers.com/showthread.php?t=1189485
No goldcard is needed, no console typing ADB shell etc. blah blah blah, so easy now.

[Q] Gaining S-ON Again

Hi
Recently was experimenting with RevolutionN Data ++ but something went wrong and market access was lost, no signal and the phone was not functioning (happened with many different ROMs actaully too).
Anyway tried flashing RUU but got an error 152, successfully reflashed the stock hboot through fastboot and then reflashed RUU which worked (thank god).
I though this would completely revert the phone back to stock however when I enter hboot it still says AlphaRev S-OFF.
Please help

geenius said:
Hi
Recently was experimenting with RevolutionN Data ++ but something went wrong and market access was lost, no signal and the phone was not functioning (happened with many different ROMs actaully too).
Anyway tried flashing RUU but got an error 152, successfully reflashed the stock hboot through fastboot and then reflashed RUU which worked (thank god).
I though this would completely revert the phone back to stock however when I enter hboot it still says AlphaRev S-OFF.
Please help
Click to expand...
Click to collapse
look at the sticky, 1st post in the Q&A thread...

It's not a design element, it really works:
{
"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"
}

MatDrOiD said:
It's not a design element, it really works:
Click to expand...
Click to collapse
I've an idea... the mods should build in a feature, that if you have under 15 posts, the search button is lit up like a Christmas tree, and is 10x larger, or plastered everywhere on the screen.. so that you simply CAN'T miss it... or, before someone signs up, they are MADE to watch an entire video explaining to them how to search, or read a long document detailing how to do so... think my idea would really save us lots of time and wasted thread space...

don't you think I've tried that...which is why I was looking for another solution

Okay, so you searched, and yet you didn't find my guide which is a sticky right on top of the Q&A section which addresses your issue directly.... *sigh*
Troubleshooting Guide said:
[8]STILL S-OFF AFTER RUU
"I want to return my phone for warranty, I used a RUU but I'm still S-OFF"
Cause:
- Alpharev's Hboots are write protected, so that they can not be overwritten by a RUU
HOW TO S-ON
METHOD 1#
[STEP1]- Visit Alpharev and download the "Downgrader"
[STEP2]- Flash the downgrader over fastboot. This can be done with Android Flasher, cmd, or fastboot commander (Note: android flasher is the only program that does not require third party software such as Android SDK or Java JDK)
[STEP3]- You should now notice the title on the bootloader screen is "Alpharev Unlock", run the RUU again and you will have S-ON'd your device.
#METHOD 2#
[STEP1]- Instead of running the RUU again, and putting your phone at risk once more, you can simply upgrade just the bootloader manually, with the PB99IMG.zip method.
[PHASE1]- we need to extract rom.zip from the RUU.
[P1/STEP1]- Run the RUU (BUT DO NOT PLUG IN YOUR PHONE OR CONTINUE), move it to the side as it cannot be minimised.
[P1/STEP2]- go to start menu, and use the "run" feature. Type in %temp%
[P1/STEP3]- select "date modified" to "today" (to make it easier to find). There are should now be 2 folders with long names of random characters.
[P1/STEP4]- search the folders for rom.zip and extract it to the desktop.
[P1/STEP5]- delete everything EXCEPT "hboot_8x50_0.93.0001_20100810.nb0" and "android-info.txt"
[P1/STEP6]- rename the zip to PB99IMG.zip (make sure it is not PB99IMG.zip.zip)
[PHASE2]- now we need to update the bootloader
[P2/STEP1]- put the file in the ROOT of your sd-card (not in any file or folder) and boot into bootloader (poweroff, hold VOLUME DOWN and POWER). After a few seconds, you will be prompted to update bootloader. Select Yes. DO NOT INTERRUPT THE PROCESS, OR YOU WILL BRICK YOUR PHONE.
[P2/STEP2]- Once the process is finished, you will now be S-ON.
Click to expand...
Click to collapse

bortak said:
I've an idea... the mods should build in a feature, that if you have under 15 posts, the search button is lit up like a Christmas tree, and is 10x larger, or plastered everywhere on the screen.. so that you simply CAN'T miss it... or, before someone signs up, they are MADE to watch an entire video explaining to them how to search, or read a long document detailing how to do so... think my idea would really save us lots of time and wasted thread space...
Click to expand...
Click to collapse
I like your idea and I totally agree. My suggestion for the video is this one:

MatDrOiD said:
I like your idea and I totally agree. My suggestion for the video is this one:
Click to expand...
Click to collapse
That would work!
over at bit-tech they have a system that if you've under 10 posts, each post (up to 10) has to be approved by a forum moderator... Imagine how many useless posts that would save

bortak said:
That would work!
over at bit-tech they have a system that if you've under 10 posts, each post (up to 10) has to be approved by a forum moderator... Imagine how many useless posts that would save
Click to expand...
Click to collapse
Would be a nice christmas present by XDA.

Bloody bell some people just don't understand. Only just seen the replies and cheers for the useless help.
Turns out my phone was genuinely ****ed so had to buy a new one!!!
Sent from my HTC Desire using xda premium

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!

Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.

Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz

I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?

Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.

confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus

error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz

djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm

mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App

edit: got it thanks

Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium

whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?

bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?

oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks

so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it

|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,

Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"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"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat

when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be

When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

How to up date LeEco Le Pro3, no root, no TWRP, 100% Stock

I am a New Pro3 owner, and a old XDA flasher. These days I just want stability and battery life. So given no one is getting OTA updates because the LeEco US office are... well about to close doors? Or at a minimum they are not maintaining the OTA servers as of today (09/06/2017 MM/DD/YEAR). I took it on myself to figure out how to get the updates and how to do them.
What you need:
These three files, nothing else.
5.8.019_sta.zip
5.8.020_sta.zip
5.8.021_sta.zip
Found here.
https://drive.google.com/open?id=0B2EAg2WU3OwpSHRMdEZ0Tks0a3M
It is very simple, but also very finicky.
1. Download 5.8.019_sta.zip, rename to update.zip
2. Place the update.zip on the root directory of your phone storage
3. Go to Settings -> System update (about 3/4 the way down)
4. Top right corner will see three vertical dots, tap the dots and select "local update" (see image)
{
"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"
}
5. When you select "local update" if you did everything correct it should say "Update package found bla bla bla". Click continue.
That's it, it will load the file, reboot in to recovery and flash the file.
Then just follow this process for each file 19s->20s-21s. Make sure you remove the last update.zip before you put the new one in place.
Now, here is how it can be "finicky". For some reason using an android file manager to rename the files to "update.zip" corrupts the file in some way... and the update once you get in to the recovery section of the auto update fails. BEST PRACTICE IS TO DOWN LOAD THE FILES TO YOUR PC, THEN RENAME IT ON YOUR PC TO update.zip AND TRANSFER TO YOUR PHONES ROOT STORAGE.
Why? no clue, but you can try it either way... but if you find it failing try ^^

Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?

bethe said:
Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/0B2EAg2WU3OwpSHRMdEZ0Tks0a3M?usp=sharing
made a new sharable link

Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?

dallorsj said:
Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?
Click to expand...
Click to collapse
Just google "5.8.019_sta" (for each one)
You should be able to find the change-log somewhere.

Edward,
Works great! Just some notes for everyone else.
1) Make sure phone is set to MTP (Media Transfer Protocol).
2) If you are using Windows and are 'dragging and dropping' onto the device just copy to the phone icon in file explorer, that will put it at / which is where it needs to be.
3) When I did this and used the local update option, it didn't even prompt for 19S, it just moved forward and started the upgrade and rebooted the phone. All it asked me to confirm was right when I selected local update to 'make sure' I wanted to do it. No version check, etc. I was on 18S, btw.

Are you saying you went straight from 18s to 21s? Without the intermediary updates? Are you bootloader locked or unlocked?

Thanks for all of those OTAs. I was restoring my device to stock and every update kept failing when I tried to manually update it. Note: Update will fail if your OTA is not called update.zip.
IT IS CASE SENSITIVE; in other words, it will fail if you name is 'Update.zip'.
Thanks again and this post should be stickied tbh.

If my phone has twrp and on a custom rom could i use the same steps to go back to stock?
Sent from my LEX727 using XDA-Developers Legacy app

Ugh
I could not resist the $199 sale on Amazon despite knowing all the shortcomings. I am starting to regret this decision ... somewhat ... especially since Amazon no longer lets you return phones & can only exchange within 10 days.
Anyhow, I was excited when I got this phone the next day after I ordered it but my 1st frustration was that I could not do any system updates. I read about all the improvements like app drawer & really wanted them but no, it kept saying my system was up to date (still on 18 mind you). Which led me to this thread ... but now my computer will not recognize the Le Pro 3 when I connect it. I tried different USB ports & cords and no luck so far. I also cannot download the above links from my phone so I am kind of stuck @ the moment ...
I do, however, think that I got the work around for the notification issue as they seem to be coming in now, so that's good.
Overall, the phone mostly works so I am not totally mad at this purchase but getting the updates would be nice.
Quick Question: if I try to install Lineage OS, will the phone still have the T-Mobile wifi calling?
Thank you all for this super helpful forum for basic users like me.
UPDATE: Rebooting the phone got my computer to recognize the phone. However, I have followed all the instructions above (downloaded the file, renamed it update.zip, dragged & dropped it right on the phone in explorer, but it still will not find it with the local update.
I downloaded the Cheetah File Manger which shows you the Root Directory, which did not look like where I put mine. So I tried to move it over to the Root Directory but it would not let me paste it there. So close ...................................... calling it a night ...... sigh

i wanted to follow your guidelines but there is no system update in settings in my device. i ve bought it from banggood if that info is useful.

Could you please add check sums for these files.
Thanks in advance!

Try to update my X727 from 5.8.018s to 5.8.019s:
1. Renamed 5.8.019_sta.zip to update.zip and copied it to phone root.
2. From File Manager pressed on update.zip and choose "Upgrade", it has started updating "Upgrading, do not power off the phone".
3. The phone rebooted and entered to Recovery with an error message: "Failed to update! Cause: Installation failed"
4. Presses Back-button and tried again "Update system" and got an error message "Failed to update! Cause: APK not found"
What's wrong?

[GUIDE] Flash 'fastboot ROMs' for Lenovo Z6 Pro

Disclaim
All steps described here have been many times tested and proved to be safe but, you may know that sometimes in life unexpected things happen. I'm not responsible for any damage in your devices, do things at your own risk.
Introduction
Thanks to xda user @alexeei we can install almost every Z6 Pro stock ROMs using the Fastboot Mode. You always should check the package content and the installation script(s) to be sure that you know exactly what is gonna be installed. You can find all the ROMs listed and linked in this index.
Let's go with the guide.
0. Pre-requirements
- The Bootloader must be unlocked.
- Lenovo drivers installed in your computer. You can download them here . Thanks @benjieb
1. Download and extract the ROM
You cand find many of them here. Extract the downloaded file and a folder will be created with these contents:
- All the files required for the installation in Fastboot Mode.
- The ROM files.
- The .bat file(s) which contain(s) all the actions that will be performed during the installation.
{
"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"
}
You always should check the content of the .bat file(s). Read post #2 to get more info about this.
2. Reboot your device in Fastboot Mode
Shut down your device and boot it holding pressed both Volume Down + Power buttons until the Fastboot Mode menu appears. You can navigate in the Fastboot Mode menu with volume buttons to choose the options and the Power button to confirm, but at this point you don't need to do any action in this menu.
3. Connect the device to the computer with USB cable
4. Execute the .bat file
Just execute the .bat file with a double click and a CMD window will be opened and the installation will start. Only a few lines will appear at the beginning and then nothing will happen, it will seem to be stopped but actually it's not, just be patient because this screen could last around ten minutes. So despite of the 'Invalid sparse file format at header magic", keep the faith and don't do anything but wait.
The device will reboot once the installation is done.
5. Errors in the log. No voice in calls.
Some errors may appear in the CMD window during the installation, this is because some partitions are 'critical' and we're not allowed to modify them via fastboot. Usually this is not a problem because these "small partitions" don't prevent the new ROM to work normally, except if you're installing Android 10 from Android 9. If you change Android version with this method you will find that your micro doesn't work in calls. You can fix it installing these "small partitions" from TWRP.
Any correction, info or advise about this post will be very welcome.

About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.

descarao81 said:
About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.
Click to expand...
Click to collapse
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom

hilary trump said:
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom
Click to expand...
Click to collapse
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
Thanks. The rom has not released yet. I just pre-ordered a chinese variant tablet P11 pro TB-J706F

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
I found the link as follows
mirrors.lolinet.com/firmware/lenovo/ Tab_P11_Pro/TB-J706F/TB-J706F_S210002_201015_ROW.zip
But inside the package there is no BAT file though