The purpose of this thread is to hopefully limit the number of repeat questions / calls for help in Q&A.
(if I see one more request to help fix a boot loop I'm going to strangle someone! )
The first place you should always look for information is the Beginners Guide. Tons of good stuff there.
If anyone has any additional helpful information, post below and I will add it to the OP.
If you find that any of the links are broken, please let me know so I can fix them.
If files are not available at the linked resource, they are available at the bottom of this post.
And always remember xda rule #1:
"Search before posting: Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news."
ADB not connecting to / can't find device:
Check to make sure you have the correct drivers installed on your PC.
Try disconnecting then reconnecting USB cable from PC.
On your PC open task manager, kill all instances of adb.exe, then start again.
Battery won't charge to 100%
1) Pull battery while charging
2) Wait for the question mark, then replace battery
3) Let battery charge for 1-2 hours
4) Wipe battery stats in CWM
Or try ravilov's Battery Fix app.
Battery too Low to Recover from Problem
Charge your battery with a wall charger, or use a USB cable.
Boot Loop
1) Pull battery
2) Replace battery while holding the volume down button
3) Use volume down to navigate to either recovery or fastboot, then press volume up
Once in:
Recovery - restore your backup or re-flash ROM
Fastboot - flash newer version of recovery or re-flash ROM
Fastboot Information
See post #2
Hard Brick
Consider using your device as a paperweight or doorstop. (or donate it to a dev)
Maybe if you are really lucky, something here might help.
Ram Low After Bootloader Unlock
Ramfix
Recovery Not Working (Just Rooted & Unlocked Bootloader)
You most likely followed a guide or used an automated tool with an outdated version of recovery.
Download the most recent version of CWM, then flash with fastboot (see post #3).
Return to Stock
The best and safest way to return to stock is by restoring the nandroid backup you made when you first installed CWM.
The next best way to return to stock is by flashing a fruit cake with CWM. Fruitcakes can be found here, and at the two links on the bottom of this post. There are some international fruit cakes available at the Atrix Reboot Project.
The third option is to fastboot flash a boot and system image (see post #4) from a fruit cake (links below). Or, fastboot flash a stock nandroid backup.
The least safe and least desirable method is to flash an sbf. This should only be used as a last resort (see entry for Hard Brick).
Rooting
The easiest way to root: Link
The way that you will learn something: Link1 Link2
There is not an established method for rooting the newest OTA (4.5.145). Exiting methods are hit or miss.
Sleep of Death (SOD)
Some users have had success with doubling the minimum CPU clock speed.
With CM7/9/10 you can adjust the clock speed in settings. Otherwise, try SetCPU.
This problem is not well understood, and usually the only real cure is returning to stock.
Soft Brick (Failed to boot XXXX)
Read this post, install software (Iinked below), select option 3.
Soft Keys not Working
Try Button Savior from the Play Store
Touchscreen - Dead Spot Quick Fix
Link
Touchscreen Replacement
Link
YouTube Video
_______________________________
Information Resources:
Atrix 4G Information Repository
_______________________________
File Resources:
A lot of the links in this forum are dead. But thanks to SamCripp and Zeljko1234, many of the files can be found below.
Atrix Reboot Project
[Fruit Cakes] Kernel, Unlock - Backup links
_______________________________
Downloads:
My AFH Atrix Folder
_______________________________
Setting up fastboot and ADB
Useful fastboot info and commands: Link1 Link2
1) Download and install 7Zip
2) Download and extract attached fastboot & ADB file
3) Download and install Motorola drivers
4) Create a new folder on your hard drive named "Android" (c:\Android)
5) Place all contents of the fastboot & ADB folder (5 files) in "Android" folder
6) Attach your phone to the PC via USB (use a port closest to the power supply)
7) In the USB settings make sure USB Mass Storage is selected
8) Reboot phone while holding volume down until you see "fastboot"
9) Press volume up to initiate fastboot
10) On your PC click the Start menu, then in the search box type "cmd"
11) In the command prompt type the following commands (no quotes, hit enter after each command)
11a) "cd c:/android"
11b) "fastboot devices"
If fastboot is working properly you should see something that looks like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>
Flashing recovery with fastboot
1) Set up fastboot as described in post #2
2) Download the most recent CWM available Link
3) Place recovery image in c:\Android
4) Type the following commands (no quotes, hit enter after each command)
4a) "fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img" (note: the name of your recovery image may be different)
4b) "fastboot reboot"
If everything was successful, you should see something like this:
Code:
c:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img
sending 'recovery' (4824 KB)... OKAY [ 0.575s]
writing 'recovery'... OKAY [ 0.592s]
finished. total time: 1.169s
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.002s
c:\Android>
Fastboot flashing boot and system images - Returning to Stock
1) Set up fastboot as described in post #2
2) Download one set of boot and system images from post #1, or unzip a fruit cake and use those images.
3) Place boot and system images in c:\Android
4) Type the following command (no quotes, hit enter after each command)
4a) "fastboot erase cache"
4b) "fastboot erase userdata"
4c) "fastboot flash boot boot.img"
4d) "moto-fastboot flash system system.img"
4e) "fastboot reboot"
If successful, you should see something like this:
(Note: If you forget to use moto-fastboot to flash the system image (like I did), you will see the "INFOImage too big" error.)
Code:
c:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 2.073s]
finished. total time: 2.073s
c:\Android>fastboot erase userdata
erasing 'userdata'... OKAY [ 5.393s]
finished. total time: 5.394s
c:\Android>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.979s]
writing 'boot'... OKAY [ 0.610s]
finished. total time: 1.591s
c:\Android>fastboot flash system system.img
sending 'system' (327680 KB)... INFOImage is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.001s
c:\Android>moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 29.155s]
writing 'system'... OKAY [ 13.965s]
sending 'system' (65536 KB)... OKAY [ 7.582s]
writing 'system'... OKAY [ 3.442s]
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.010s
c:\Android>
Miscellaneous
All:
Set up fastboot as described in post#2
Place .img in c:\Android
Fastboot flash radio
fastboot flash radio radio.img
fastboot reboot
Fastboot flash boot logo
fastboot flash logo logo.bin
fastboot reboot
Reserved 3
Reserved.
Thank you so much for sharing these with us!!!!!:good:
Awesome post!
a lot of useful information =) this help me a lot
Excellent compilation !!
This is a one stop thread for those Atrix owners looking to get their doubts and queries about the bootloader unlocking procedure answered comprehensively. It sure did that for me!!
In Atrics (CM9) - 14/11/12, every time the super user privileges to provide a program, get the reboots when the screen turns off. The super user is already updated and nothing!
freezerj said:
In Atrics (CM9) - 14/11/12, every time the super user privileges to provide a program, get the reboots when the screen turns off. The super user is already updated and nothing!
Click to expand...
Click to collapse
Reinstall the rom
Enviado desde mi MB860 usando Tapatalk 2
HDMI Problem
hello guys, sorry if i didn't follow rules, but maybe some1 can answer me.
i have HDMI mirroring problem. when i attach phone on Lapdock, it says No Signal, Input : HDMI.
any solutions?
I'm using a jb custom rom and the 3g sometimes turns itself on without me initiating it! Any ideas?
Spilled from my Atrix4g utilizing Tapatalk
This is not a help thread.
Questions go in Q&A.
Please keep the discussion relevant to info in the OP.
Thanks!
Incoming Calls no contact Names
I have recently installed miui android version 4.1.2(MIUI 2.12.7)
However I everytime i get a call, the caller's name is not shown and instead i get to see only the number in the format +254722XXXXXX!! This despite having saved the contacts name and number in my google account which is synced. Im using a motorola Atrix (MB860),Carrier is Airtel Kenya
thanks in advance for any help
In case of infinite loop - Alternative method
Yeah,
I tried another method that worked like a charm for me :
- Start in fastboot mode (maintain power + volume down --> repeat down to choose fastboot --> validate with up volume)
- On your computer, open "cmd" command (windows + R --> CMD)
- Type : "fastboot -w" this command will erase user data
- Type : "fastboot reboot"
That is all.
Hi all,
I understand there is loads of this stuff online but found nothing related to Z1, please bear with me. So, after successfully installing TWRP my Z1 is always loading the cm recovery.
I'm with CM 12.1 yog4pap25i, update CM recovery is off.
After flashing TWRP is there specific actions I need to do? I've always rebooted into recovery with fastboot or the advanced reboot in the phone, but I'm always having CM recovery installed.
Thanks for your help
badyards said:
Hi all,
I understand there is loads of this stuff online but found nothing related to Z1, please bear with me. So, after successfully installing TWRP my Z1 is always loading the cm recovery.
I'm with CM 12.1 yog4pap25i, update CM recovery is off.
After flashing TWRP is there specific actions I need to do? I've always rebooted into recovery with fastboot or the advanced reboot in the phone, but I'm always having CM recovery installed.
Thanks for your help
Click to expand...
Click to collapse
You unlocked bootloader and checked oem unlock im sure.
But which command did you use to flash the twrp?
Output should be like this:
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY
Please post your output
Hi @strongst, I'm on mobile now but yes, the response is ok. Also I've checked what you suggested. The problem is I think I did everything well, but somehow I'm not rebooting correctly
after that command type fastboot boot twrp.img (twrp is the name of recovery img) and it will booted into recovery
badyards said:
Hi @strongst, I'm on mobile now but yes, the response is ok. Also I've checked what you suggested. The problem is I think I did everything well, but somehow I'm not rebooting correctly
Click to expand...
Click to collapse
I would say, after installing twrp, directly type fastboot reboot recovery and boot to recovery immediately.
Booting into system will replace the stock recovery
Sent from my Lenovo Zuk Z1 using XDA Labs
Sharma_Ji said:
I would say, after installing twrp, directly type fastboot reboot recovery and boot to recovery immediately.
Booting into system will replace the stock recovery
Sent from my Lenovo Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
Hi, this is the message received after flashing:
PS C:\platform-tools> fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (9578 KB)...
OKAY [ 0.340s]
writing 'recovery'...
OKAY [ 0.138s]
finished. total time: 0.594s
then I digit this
PS C:\platform-tools> fastboot reboot recovery
< waiting for device >
if i switch off it is booting automaticaly into CM12. If I exit the shell and try power + volume down it opens a plain recovery, neither the CM revocery nor the twrp. Any idea of what I'm doing wrong?
edit: also tried this
PS C:\platform-tools> adb devices
List of devices attached
cb02ec72 device
PS C:\platform-tools> adb reboot bootloader
PS C:\platform-tools> fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (9578 KB)...
OKAY [ 0.330s]
writing 'recovery'...
OKAY [ 0.134s]
finished. total time: 0.467s
PS C:\platform-tools> fastboot boot recovery.img
< waiting for device >
looks like the fastboot is gone after flashing
hi everyone, sorry for the newbie question above. Eventually I've managed to install TWRP, I just missed the right key combination to reboot.
Thanks
I got my OnePlus 5 back from the OnePlus support people the other day (I'll provide background for that if requested, I don't want this to get too long), and just yesterday sat down to install TWRP and root it. I unlocked the bootloader with no issues, but then when it came time to install TWRP, I ran into the issue. So I'll be in fastboot, and will enter in the command prompt:
"fastboot flash recovery [the recovery file]"
Which will return the following:
"target reported max download size of 536870912 bytes
sending 'recovery' (25860 KB)...
OKAY [ 0.557s]
writing 'recovery'...
OKAY [ 0.007s]
finished. total time: 0.566s"
Which seems to indicate that everything works, right? But when I then enter the command:
"fastboot boot [recovery name]"
It returns:
"downloading 'boot.img'...
OKAY [ 0.530s]
booting...
OKAY [ 10.104s]
finished. total time: 10.638s"
and boots back into fastboot mode.
I have tried this on both my HP laptop which is running Window 8.1 and my Dell laptop which is running the most recent version of Debian (I used sudo), and to the same results. I have tried multiple tool kits such as the one mentioned in this thread:
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
and the one mentioned here:
https://www.teamandroid.com/2017/07/12/download-oneplus-5-toolkit/
which (to the best of my knowledge) only seem to enter the same commands I do.
I have also tried unplugging the phone after flashing the recovery and using the button combos to enter the recovery. It always takes me to the default recovery instead of TWRP.
Some miscellaneous details:
The phone is unlocked.
I have developer options enabled and OEM unlocking is enabled.
I have done no modifications besides unlocking the phone.
I checked to make sure the phone is fully updated. It is.
I have no problem with erasing everything on the phone if need be.
I apologize in advance for any weird grammar usage, spelling mistakes, and/or formatting issues. Any and all help is much appreciated. I really have no clue what's going wrong here.
What TWRP are you trying to use?
I tried using version 3.2.2.0. I grabbed it from here: https: // twrp.me / oneplus / oneplus5. html
Nunna the Insane Gerbil said:
I tried using version 3.2.2.0. I grabbed it from here: https: // twrp.me / oneplus / oneplus5. html
Click to expand...
Click to collapse
It's not a good version. It's broken, in fact.
I'd recommend codeworkx 3.2.1-0
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
It works, thank you so much!
Nunna the Insane Gerbil said:
It works, thank you so much!
Click to expand...
Click to collapse
You're welcome. :good:
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.