Database Users

Marshmallow factory images are available.

Yeah, I think the title is enough. The factory images are live now for volantis and volantisg. Maybe we can collect here some first impressions. I am unfortunately not able to flash atm.

https://developers.google.com/android/nexus/images

Flash-all script worked like a charm, setting everything up right now

But it's not February yet.

maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Cool man , I'm waiting for your review, , but I'm sure to flash this into my N9 tomorrow . I'm just too eager to wait any longer

Good thing I reverted my n9 back to stock. Will flash tonight. No Ota also.

Flash.sh fail
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!

I'll be flashing my 9 tonight too.
I kept my 6 on Lollipop rather than running the preview on it, but yesterday I did flash the preview so that it would use M's auto backup. That way I can flash it this week and not worry about signing into apps.....which is nice during tax season.

PhoenixIce22 said:
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
Click to expand...
Click to collapse
Do u have latest fastboot? That error was happening to others because of old fastboot. Otherwise maybe just make sure the hash matches and u have a good download and usb debugging is on.
Sent from my SM-G900V using Tapatalk

Anybody tried flashing yet? I keep getting 'system cannot be loaded' error whilst carrying out manual flash. i.e. fastboot flash system system.img etc etc

I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here

I was on 5.1.1 (Latest Image). I applied the 6.0 update, now I am just sitting at the black Google Screen and it won't boot. Any suggestions???

Diesel779 said:
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
Click to expand...
Click to collapse
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk

Is the installing process for rooted devices the same as for the former builds?
like here:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img

gt43aw said:
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
You don't need FED patcher if you flash an already un-force-encrypted kernel. FED patcher just takes the stock kernel and un-force-encrypts it.

Haven't updated my flashing VM in a while, so likely not. I know my ADB is 1.0.32, not sure what version of fastboot I have on there. I'm a bit of a Ubuntu noob, so I'm doing lots of web researching, LOL

Be sure to update the bootloader if getting a system partition size error! For M-preview this went from 3.44.1.0123 (LMY48M) to 3.48.0.0135 (confirmed the factory image is still this for MRA58K)... Otherwise you get system partition size errors (BIG update).
I will be making a rooted/no-force-encrypt ROM and kernel as soon as I see the newer manifests on googlesource... I am assuming selinux to permissive is still required for root. Once you have it unpacked:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
fastboot reboot-bootloader
Then flash the system and boot images:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
DO NOT DO THIS if your device is using a no-force-encrypt kernel! You WILL have to factory reset! Back up OFF the device to a PC or OTG FIRST... Then you can restore.
While flashing SYSTEM it will send the update in 5 chunks - from my device:
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.869s]
sending sparse 'system' (499853 KB)...
OKAY [ 26.326s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.701s]
sending sparse 'system' (495930 KB)...
OKAY [ 25.524s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 20.212s]
sending sparse 'system' (495450 KB)...
OKAY [ 25.732s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.792s]
sending sparse 'system' (443364 KB)...
OKAY [ 22.984s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.222s]
sending sparse 'system' (310634 KB)...
OKAY [ 16.188s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 12.593s]
finished. total time: 209.162s

NOOB Question:
where can I get the Information if my kernel is "no-force-encrypt kernel"?
I'm using the stock kernel 3.10.40 (28.jul) build LMY48M (rooted)
UDPATE:
in Settings -> security -> enrcypt tablet-> encrypted: means "force-encrypt kernel"?

Deleted

No force encryption stock kernel
For those who want to flash Marshmallow immediately but wanted to keep the device un-encrypted, download this zip, extract the boot image and flash through fastboot.

[Solved] P8 Lite ALE-L21 HI6210SFT bootloop

Hi all,
Interesting problem. I've been updating some P8 Lite units that were shipped to us with a single SIM ROM with dual SIM ROM. I've already done two phones without issues (both ALE-L21). Onto the third phone (also ALE-L21), and this time there's a problem.
I'm not quite clear if the HiSilicon Kirin 620 and HI6210SFT are the same chipset or not. An answer to this would be helpful!
Steps taken:
Unlocked bootloader via Huawei website. Fastboot says PHONE Unlocked and fastboot oem get-bootinfo replies: (bootloader) unlocked
Flashed boot, recovery, cust, and system.img via fastboot following the guide (using dual SIM unbrick files)
Phone does not boot past Huawei logo, I get a black screen and then after a minute or so it reboots
Pretty odd, since I've done this on two other phones of the same model and the process worked without any issues.
TWRP 2.8.7 does not boot on the phone (black screen and reboot to Huawei logo)
TWRP 3.0.2 does boot.
Unfortunately I didn't think to take a backup of the system before I started this since I'd done it twice before without problems.
Here's what I've tried to do to get this phone to boot again:
Took TWRP backup of another ALE-L21 running B584 and restore it. Result: bootloop/not booting past Huawei logo
Flashed B052 via fastboot from here. Result: bootloop/not booting past Huawei logo
Flash recovery.img from the guide (not sure which OS version this is based on) and put UPDATE.APP for B052 on sdcard\dload\UPDATE.app. Result: black screen after Huawei logo, no activity
Tried the above with UPDATE.APP from B584. Result: black screen after Huawei logo, no activity
Using Huawei eRecovery from fastboot. Result: "getting package info failed"
I know the phone isn't bricked, because TWRP 3.0.2 still boots.
However, I cannot for the life of me get any Huawei OS to boot on this phone anymore. I'm using fastboot for everything (Linux) and I don't have any problems to flash:
$ fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.887s]
writing 'boot'...
OKAY [ 1.692s]
finished. total time: 2.580s
$ fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 1.420s]
writing 'recovery'...
OKAY [ 2.615s]
finished. total time: 4.036s
$ fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 8.815s]
writing 'cust'...
OKAY [ 5.691s]
finished. total time: 14.507s
$ fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 24.211s]
writing 'system'...
OKAY [ 10.338s]
sending sparse 'system' (460385 KB)...
OKAY [ 23.630s]
writing 'system'...
OKAY [ 10.617s]
sending sparse 'system' (460747 KB)...
OKAY [ 23.682s]
writing 'system'...
OKAY [ 11.319s]
sending sparse 'system' (457010 KB)...
OKAY [ 23.684s]
writing 'system'...
OKAY [ 10.537s]
sending sparse 'system' (443304 KB)...
OKAY [ 23.432s]
writing 'system'...
OKAY [ 10.011s]
finished. total time: 171.461s
My next step would be to try a custom ROM, but there isn't much choice here of flashable zips, and all the custom ROMs seem to be broken or missing features. what I really want is to get this phone back to booting the Huawei OS, but this is seeming impossible.
I'm using Ubuntu 16.04 amd64 and have no issues with adb/fastboot or drivers.
Does anyone have any ideas why this phone refuses to boot after the attempted dual SIM conversion?

I don't really know about this stuff but
After flashing those .img files, have you tried to go stock recovery and tried factory reset there. I think I had something similiar problem (might have been different can't quite remember) but after that I got device to boot.

keikari said:
After flashing those .img files, have you tried to go stock recovery and tried factory reset there. I think I had something similiar problem (might have been different can't quite remember) but after that I got device to boot.
Click to expand...
Click to collapse
How do you access factory recovery? With Power + Vol UP + Vol DOWN?
I've tried this key combination after flashing via fastboot, I get a black screen after the Huawei logo and no recovery.
I'm assuming the factory recovery is supposed to look like what you see during an UPDATE.APP installation?

icewewe said:
How do you access factory recovery? With Power + Vol UP + Vol DOWN?
I've tried this key combination after flashing via fastboot, I get a black screen after the Huawei logo and no recovery.
I'm assuming the factory recovery is supposed to look like what you see during an UPDATE.APP installation?
Click to expand...
Click to collapse
Power + Vol UP
---------- Post added at 07:41 PM ---------- Previous post was at 07:34 PM ----------
Also you can test updateflaher.zip from this thread to use TWRP to install stock rom https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702. I'm not sure will it work for p8lite, but it can install p8lite firmware to honor4x so maybe it can also install p8lite firmware to p8lite. No idea will it help though.

I suspect you did not factory reset before trying to boot. Get into twrp, then factory reset, clear cache, wipe data EVERYTHING YOU CAN clean. No previous data/cache should remain.
Then flash system files using adb (follow the guide to the letter). Reboot. Give it some time, it should come back.

keikari said:
Power + Vol UP
Click to expand...
Click to collapse
Does nothing. I get the Huawei logo and then a black screen.
bumjrah said:
I suspect you did not factory reset before trying to boot. Get into twrp, then factory reset, clear cache, wipe data EVERYTHING YOU CAN clean. No previous data/cache should remain.
Then flash system files using adb (follow the guide to the letter). Reboot. Give it some time, it should come back.
Click to expand...
Click to collapse
What guide are you referring to? The one I linked to doesn't use TWRP and flashes the system via fastboot, which doesn't require a wipe.

Okay, I fixed the issue. I'm really not sure why it didn't work before.
Here are the steps I took:
Restored a TWRP backup I took of another ALE-L21 running B584
Wipe Data/Cache
Flash RECOVERY.img from B584 UPDATE.APP
But then I had the Balong bug. I figured out this is because the oeminfo partition contained data from somewhere. Lollipop or the single SIM build, I don't know.
The UPDATE.APP containing the fix for Balong wouldn't flash in the Huawei recovery. Probably because it's intended for Lollipop and B584 is MM. Or something. Whatever.
So I flashed TWRP and using adb created /data/custom.bin with
Code:
hw/eu
and permissions 0666. This got rid of Balong build, but neither SIM card was recognized by Android.
Then what I did was take a copy of oeminfo from another hw/eu phone, one I had successfully converted earlier, and flashed that. For others reading, oeminfo partition is /dev/block/mtdblk0p8. It's 32MB but almost entirely 0's, so the zip compressed version is really small (80KB).
So here are the steps again:
Restore TWRP backup of another phone running B584
Wipe Data/Cache
Flashed oeminfo for hw/eu from another phone running B584
Flashed Huawei stock recovery from B584
Performed a system update using Huawei recovery with B584 UPDATE.APP
Now the phone recognizes both SIM cards correctly, and has the correct region/oeminfo.
If anyone else has problems with Balong build and you're running MM, here is the oeminfo I used to fix the phone. You will need to unzip and flash in TWRP (or Android if you have root) using the dd command listed above.
Example:
Code:
unzip oeminfo-eu.zip
adb push oeminfo-eu.bin /tmp/
adb shell
dd if=/tmp/oeminfo-eu.bin of=/dev/block/mmcblk0p8

[GUIDE] How to Flash Android 8.1/9.0 on Lenovo Z5 (WiFi and Data also working now)

Hi Guys,
I have finally successfully flashed a phh AOSP 8.1 provided in the following thread to Lenovoz5
Before proceeding, here are the basics,
Do not Ever ever ever EVER flash zui_3.9.075_Z5_L78011_multi
Bootloader needs to be unlocked only if you wantto flash custom Android 9.0 Pie roms,
If you want to stick to stock Lenovo rom, then you do not need to unlock bootloader.
If you start your phone and it says "Your device is corrupt" then your phone has zui_3.9.075_Z5_L78011_multi.
This rom is a dirty version of stock rom, that Chinese sellers sells your phone with. This is not the original rom.
Always use "L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst" for unlocking bootloader, 075, this version is the only version that allows unlocking bootloader.
With other versions like L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst, L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.200_ST_180809_qpst
This option is hidden by manufacturer under Developer options.
If you start your phone and you dont get option to activate via Wifi or Network, then your phone doesnt have stock rom and it has been tweaked by your seller.
Here is the download link for stock rom, do not use the rom that has _multi in its name.
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
If you get Sahara error when flashing through QFIL
1) Make sure your phone is in edl mode, follow the video for that
2) Make sure the config is correctly set in Settings within QFIL
3) Try changing USB ports on your PC, It only works on USB 2.0, will throw error on USB 3.0 and 3.1
Make sure you go through this thread, each and every question is answered already.
If you have any questions, make sure to list out everything you did and what you are trying to do,
My phone doesnt start
I cant proceed
I cant flash
I am stuck
I cant unlock bootloader
This doesnt help, please post full description with screenshots , what you have done to your phone after your received it from your seller, what you want,
Google the basics, bootloader unlocking, stock rom, custom rom, Android 8.0, Android 9.0 etc
I have created Lenovo z5 group on telegram, pls post there if you have any questions, i dont check xda, but i will respond on telegram whenever i can.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
Go through this thread and read all the posts, most of your questions is probably already answered.
I would recommend if you are not good at flashing then back up all partitions on external sd card. (WIFI and data working now )
To backup stock partitions,
1. Unlock bootloader
2. Flash TWRP through fastboot
3. Boot to TWRP and do a full back up of all partitions.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
Flashing guide for Android 8.1: (Everything is working on Android 9.0, check out second post in this thread.)
What you will need:
ADB: https://www.mediafire.com/file/8j84x6j1g2xb8z6/adb.zip/file
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - system-arm64-ab-gapps-su.img from the above link
superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1w0PHZFvfYvExBAEnyDyqBpBjMGLBoLes
superuser apk(not necessary to install) https://drive.google.com/open?id=1XU9pydDRPOZ2weq14j6S-hveM98C8zHe
Procedure to Flash custom rom on Lenovo Z5:
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a system-arm64-ab-gapps-su.img
6. fastboot -w flash system_b system-arm64-ab-gapps-su.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash superuser flash file(mentioned above)
10. Do not clear any data or cache, we already did that, Start and Enjoy!
After completing these steps please wait for about 25 to 30 mins
(My logs when i flashed the rom)
c:\adb>adb reboot bootloader
c:\adb>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.018s]
Writing 'vbmeta' OKAY [ 0.037s]
Finished. Total time: 0.079s
c:\adb>fastboot flash boot_a boot.img
Sending 'boot_a' (52261 KB) OKAY [ 1.795s]
Writing 'boot_a' OKAY [ 0.037s]
Finished. Total time: 1.842s
c:\adb>fastboot flash boot_b boot.img
Sending 'boot_b' (52261 KB) OKAY [ 1.798s]
Writing 'boot_b' OKAY [ 0.036s]
Finished. Total time: 1.843s
c:\adb>fastboot flash system_a system-arm64-ab-gapps-su.img
Sending sparse 'system_a' 1/3 (524284 KB) OKAY [ 18.954s]
Writing sparse 'system_a' 1/3 OKAY [ 0.006s]
Sending sparse 'system_a' 2/3 (488160 KB) OKAY [ 20.940s]
Writing sparse 'system_a' 2/3 OKAY [ 0.005s]
Sending sparse 'system_a' 3/3 (514508 KB) OKAY [ 21.349s]
Writing sparse 'system_a' 3/3 OKAY [ 0.010s]
Finished. Total time: 68.562s
c:\adb>fastboot flash system_b system-arm64-ab-gapps-su.img
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 12466167 4k blocks and 3121152 inodes
Filesystem UUID: 98e2d366-b46f-11e8-9d3d-3d9d543f2291
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending sparse 'system_b' 1/3 (524284 KB) OKAY [ 19.159s]
Writing sparse 'system_b' 1/3 OKAY [ 0.037s]
Sending sparse 'system_b' 2/3 (488160 KB) OKAY [ 20.708s]
Writing sparse 'system_b' 2/3 OKAY [ 0.007s]
Sending sparse 'system_b' 3/3 (514508 KB) OKAY [ 21.250s]
Writing sparse 'system_b' 3/3 OKAY [ 0.007s]
Erasing 'userdata' OKAY [ 3.849s]
Sending 'userdata' (4348 KB) OKAY [ 0.167s]
Writing 'userdata' OKAY [ 0.007s]
Finished. Total time: 73.993s
c:\adb>fastboot flash boot twrp.img
Sending 'boot_a' (58524 KB) OKAY [ 2.021s]
Writing 'boot_a' OKAY [ 0.007s]
Finished. Total time: 2.041s
c:\adb>adb reboot bootloader
c:\adb>fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
Finished. Total time: 0.013s
Not working:
Notification LED (Thanks to DarkerMaster)
Pictures taken by camera are always 90 degrees rotated
Google Camera app is crashing
Working on Android 8.1:
Call
Camera
Fingerprint reader
WIFI
Mobile data ...
Almost everything
I am still testing the device. I will post details later.
Android 8.1
https://drive.google.com/open?id=1k1bgp3sLedy-e5vqYKZF47WXRIVfO-tN
https://drive.google.com/open?id=11RAiDNS-1_bv7ceYJDLriOuGtMIkfbXt
https://drive.google.com/open?id=1hDrJHaKKHhowWJSvVUN3Y9scZeCMMLIz
https://drive.google.com/open?id=1bvKErzYwF9qH87Leie_acnwElINM8qxQ
https://drive.google.com/open?id=1Sg5mHLgm6_Bl4xz3ZBrgq7sLDbrveGWg
https://drive.google.com/open?id=1XxaiVKaImXZ64mH-TwuXcXNEFaTn2ydK
https://drive.google.com/open?id=1ABII2x3hWMKwgTr8mVxI-cYTiej1lVlN
https://drive.google.com/open?id=1rn7CXYnhiiiDBYoF_K1us9vXjgTMOigq
Imp:
If you have flashed one of these Roms, and you can boot in to it successfully, please do not use Factory reset. If you do, then the rom wont boot, since Magisk/SU is installed.
If you still do, then boot to Bootloader, flash vbmeta, boot_a, boot_b, twrp, Magisk(Android 9)/SU(Android 8).
If you have unlocked bootloader, do not relock it, ever
Special Thanks to phhusson for his [AOSP 8.1] [2018-08-16] Phh-Treble
Experimental:
Zui FM Radio app (Not working yet!)
Please note this is still under development, i am only posting it here, if anyone wants to work on it.
https://drive.google.com/open?id=1raHCHhMxOQVM8L0rbSjoKeTVLmbtBSIc
Don't forget to hit that Thanks button !
Cheers

Android 9.0 flashing guide
Back up all partitions on external sd card.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Rom: PixelExperienceP-arm64-ab.zip
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
What you will need:
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - PixelExperienceP-arm64-ab.img from the above link
Magisk superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1FV_ogrSU488bpI_hhuyA8rHm3Fj_xLqb
Magisk superuser apk https://drive.google.com/open?id=1hi_58d1nJ-PNe3aPKb_0YsLrh5ElOXVn
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash Magisk flash file(mentioned above, once this is done take pictures of the TWRP logs)
10. Do not clear any data or cache, we already did that
11. On first boot install Magisk apk mentioned above. That's it !
Not working:
Notification LED
Working on Android 9:
Call
Camera
Fingerprint reader
WIFI
Mobile data(4G not sure about 3G)
Google Camera (If app crashes then follow procedure in this thread https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-enable-camera2-api-t3419579 )
Almost everything
Android 9.0
https://drive.google.com/open?id=1L_q2b8V0V7lIafcQsMVbKgqyRq3Tt2Hp
https://drive.google.com/open?id=1grkAu-FhZ56LKN82ubXYN3163ChTUVwr
https://drive.google.com/open?id=1yd5B0HN9Bund6UbJrEScbRsvrofExtT2
https://drive.google.com/open?id=1lWnH408p6aIREmEzl8IIKyE4UKS5V0Nk
https://drive.google.com/open?id=12EDJRbNm_4KVPD72FJ4Yem0gt3XE-BVr
https://drive.google.com/open?id=1RBt2miHzcvC9punEytJd_9aRyDwwhtV9
https://drive.google.com/open?id=1saTXcINKgbjw4HKxvRrSlbPrYk6GJfRr
https://drive.google.com/open?id=1QfLT5_gUk6k3U7o6ZJig8skn7Ckr--GK
https://drive.google.com/open?id=1pWJxmxO-ZzdNdGCK4LVO_zqxKpCQV5fG
Some snaps taken from the phone
https://drive.google.com/open?id=1w0GCNHKjuhE3x_A6xAwVgkYua0pMWGj-
https://drive.google.com/open?id=1GZ4LXyBHOL-zWEXrJVSMRPc07Nabg-eB
https://drive.google.com/open?id=1kTyVHk2Gr8LHekjvn7AwtnC92xrj0_7G
https://drive.google.com/open?id=1qgADqYoePMN9B5OMcpXw2pUc5DYXPCLI
If Windows doesnt detect phone in File Transfer mode:
Enable Developer options, turn off USB debugging.
If Mobile data doesnt work:
Settings > mobile data > Preferred network type = 4G and Choose your network providers Access point, if there is none then create one.
Special Thanks to EnesSastim and phhusson for their [9.0][GSI] PixelExperience P - UNOFFICIAL
Follow this process if you want to remove encryption:
This will delete the os and data on your phone. please backup everything before proceeding. External SD card will be untouched.
Flash L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst via qfil (This step is to flash latest persist, firmware, vendor etc images available in 390, if you want to stay on 075 and you already have this stock image flashed, then you can skip this step)
TWRP: https://forum.xda-developers.com/an...overy-lenovo-z5-special-edition-twrp-t3850041
boot.img and persist.img are from version 390 of stock rom. (you can also use 075 images)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash boot recovery-TWRP-3.2.3-1002-LENOVO_Z5-CN-wzsx150.img
Press volume down button twice and go to Recovery
(change language to english if needed)
In recovery backup all of your partitions on to External SD card.
Mount system, persist, firmware
Advanced > RM Forceencrypt
Select Remove DMVerity and Remove Forceencrypt
Swipt to confirm
(This should not throw any error in red fonts, should show Done in the end)
(If it says failed to mount Persist, then reboot to bootloader, fastboot flash persist persist.img)
In recovery goto Wipe
Select Format Data
type Yes (This will remove the encryption)
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash persist persist.img
fastboot -w flash system_a PixelExperienceP-arm64-ab.img
fastboot -w flash system_b PixelExperienceP-arm64-ab.img
fastboot flash boot twrp.img (older version of TWRP)
Boot to TWRP and flash Magisk
Here is the link to the video
https://www.youtube.com/watch?v=brS5tqfx2BQ&index=3&list=PLNqXvI29Azcg9lxA_n6ltytf9aFhn3T1d&t=1081s
download for 075
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
Return to Stock:
Downloads : ZUI5 https://drive.google.com/open?id=1IL8Pu3Ame9gu6jqAAkBQrEiRL1a93rHK
ZUI10 https://drive.google.com/open?id=1ANAZXbbygyZHAVNGmgoPimJ1fIKbK38D
Credits for ZUI 5 and Zui 10 goes to @M.Z.F and the original developer of the images in these zip files.
https://forum.xda-developers.com/android/development/lenovo-z5-custom-roms-pie-t3904607
Steps to return to stockbackup your data or everything will be wiped)
IF you are on Android 9.0
1) go to TWRP and back up all partitions on SD card (persist, vendor, system, data, boot, firmware, ... )
Step 2 and 3 will turn encryption on, so if u want to disable encryption, after step 3, flash recovery-TWRP-3.2.3-1020-LENOVO_Z5-CN-wzsx150.img and disable encryption. v 474 has new firmware and i have seen better call reception and data connectivity.
2) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst through QFIL
3) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.474_ST_190118_qpst through QFilL
4) Boot to bootloader
5) go to Zui5 folder (link is above) and click on Batch.bat file
6) Press 2, Hit enter, enter, enter
7) phone will automatically restart and boot to ZUI5
8) go to ZUI10 folder and click on Batch.bat
7) Press 2, Hit enter, enter, wait for phone to restart.
Congrats you are back to stock ZUI.
Don't forget to hit that Thanks button !
Cheers

Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!

nfraccar said:
Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!
Click to expand...
Click to collapse
Thanks for letting me know about the broken link, i have updated it.
I have everything working on Android 8.1 , not tried 9 yet. I will test camera quality tomorrow during day time. But camera does work.
Second link is the boot image.

GREAT!
Wanna go home quickly and play with my Z5!!!

Thank you for your work!!
Notification led work?
Did you tried Google Camera?

Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks

nfraccar said:
Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks
Click to expand...
Click to collapse
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.

rendroid15 said:
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.
Click to expand...
Click to collapse
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support

nfraccar said:
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support
Click to expand...
Click to collapse
Unless you mess with Vendor and stock firmware partitions, you can always go back to ZUI.
For flashing stock ZUI, please see below thread, it has all the information you need including downloads
https://forum.xda-developers.com/android/help/help-lenovo-z5-chinese-updates-t3812110

DarkerMaster said:
Thank you for your work!!
Notification led work?
Did you tried Google Camera?
Click to expand...
Click to collapse
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.

rendroid15 said:
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.
Click to expand...
Click to collapse
Of course you enabled camera 2 API right?

Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.

Cirus61 said:
Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.
Click to expand...
Click to collapse
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.

I have tried flashing the 8.1 and it has given me error in all files by fastboot

rng30 said:
I have tried flashing the 8.1 and it has given me error in all files by fastboot
Click to expand...
Click to collapse
can you post the screenshots?
Its most likely you dont have adb installed,
You can get it from here https://forum.xda-developers.com/showthread.php?t=2317790

nfraccar said:
Of course you enabled camera 2 API right?
Click to expand...
Click to collapse
not yet, i am testing stock rom right now.

rendroid15 said:
not yet, i am testing stock rom right now.
Click to expand...
Click to collapse
Then Google Cam can't work. Activate camera 2 API if you have time and try again Google Cam!

rendroid15 said:
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.
Click to expand...
Click to collapse
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.

Cirus61 said:
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.
Click to expand...
Click to collapse
try this, copy all files directly in adb folder, get rid of folder "Minimal adb drivers", the spaces in that folder name may be the problem.
If that doesnt work then just rename the rom name to rom.img and use that in fastboot command.

Need low level format by second hand Mi 9T ... to fastboot loop!

Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s

Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Never format persist partition u will be stuck in a fastboot loop, flash this twrp with the pc it has its own script and boot into twrp i guess u just have a missing vbmeta that can cause twrp to disappear in some cases
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159

Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Also you can use MiFlash and fastboot rom file to flash stock rom from scratch from fastboot.

Deaddo6 said:
Good evening everyone. I needed a deep format and in the twrp wipes I selected Internal Storege ... before installing Lineage 17 ... now the twrp is gone too and it's in loop on Fastboot and I can't get out. Which flash software should I use?
I tried to install via fastboot all the twrp that I found on the various sites ... but after the usual two steps ... ok .... ok write ... succes .... reboot with up key and power. ... and back to fastboot
i use twrp 3.4.0, 3.3.1.8, 3.3.1.3, 3.3.1.0
....Desktop\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.504s]
Writing 'recovery' OKAY [ 0.348s]
Finished. Total time: 2.852s
Click to expand...
Click to collapse
Flash stock rom using miflash,
Uncheck clean and lock

finally I used mi flash ... I modified the "format all and lock" file, to circumvent anti-rollback.
I installed miui 11. Now everything is fine ... thanks

Install Android 12 Beta

Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!

Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson

Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson

speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.

A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...