{
"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"
}
Confirmed working with:Exodus for ZUK Z1 5.1.1.MOKEE CM Nightly 5.1.1.Cyanogen OS OTAs thanks to @EagleEyedTom
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards and so on. YOU are choosing to make these modifications.
* Bug reports or confirmation of working things are welcome.
*/
Click to expand...
Click to collapse
DO NOT USE ON AN ENCRYPTED FILE SYSTEM
For some reason I can't get my image to decrypt encrypted file systems. I lost all my data to this issue and at the moment I do not know of a fix. If you need to update or modify and encrypted partition you will have to back up EVERYTHING in your data partition and then do a complete wipe. Sorry.
This image has been recompiled with device checking disabled thank you to @TheCrazyLex for making the new .prop for the international variant.
Please note this image was compiled for the chinese variant of the ZUK Z1 it should work with the international version but zip flashing might not work properly due to device IDs. To flash zips with device specific build.props comment out all the device checks
There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.
Q: Does this work for ZUI devices? A: No, I don't think so. You're welcome to test it and report back but so far I have only tested it with Cyanogen OS
Q: What can I get with this I can't with Cyanogen OS Recovery? A: You can flash unsigned ZIPs such as SuperSU or Xposed (Although I don't recommend doing this as I put my phone into a bootloop installing Xposed)
First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.
Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.
If Windows is giving you an error claiming the best driver is already installed right click Z1 or whatever it is named in Device Manager and click Update Driver.
Then click "Browse my computer for driver software" then click "Have disk" once you have done this browse to the extracted USB driver and open the .inf file it will show you three options select ADB device (Top one). Click yes to any warning and it should be mounted!
Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type
Code:
adb devices
It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.
Code:
adb devices
You will also need to download the TWRP image from the spoiler below.
DON'T DOWNLOAD THESE IMAGES FROM ANYWHERE OTHER THAN ANDROID FILE HOST FROM ME WITH MATCHING MD5 SUMS. I AM AWARE SOMEONE HAS RE-UPLOADED MY IMAGES
Android File Host for Z1 TWRP V2.1 - DOWNLOAD LINK
Android File Host MD5 for Z1 TWRP V2.1 - d5fa8f50144316647b35af4a92a61ab9 - Has all currently reported bugs fixed!
Android File Host for Z1 TWRP V2.0 - DOWNLOAD LINK
Android File Host MD5 for V2.0 = 6226173f5cb17bc7b4ab67ac55efdbbb - Now uses Chroma Kernel to run, reduces heat output, fixes audio bug issues, fixes battery drain, and fixes brightness inside TWRP. Added new splash screen.
Android File Host for Z1 TWRP V1.3 - DOWNLOAD LINK
Android File Host MD5 for V1.3 = eaf29b2653a53d120146d1cedcb1e372p - Added support for both ZUK Z1 variants, international and Chinese.
Android File Host for Z1 TWRP V1.2 - DOWNLOAD LINK
Android File Host MD5 for V1.2 = 3b6fa140737b769f838169e997f58975 - Retired due to limited device compatability
Android File Host for Z1 TWRP V1.1 - DOWNLOAD LINK
Android File Host MD5 for V1.1 = 596816b87a45d78bed4063ac62fac137 - Compiling issue, uploaded without thorough test.
Android File Host for Z1 TWRP V1.0 - DOWNLOAD LINK
Android File Host MD5 for V1.0 = 62b72d5129591d6759bb1917868594f4 - Outdated, filled with bugs.
If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!
Type:
Code:
adb reboot bootloader
You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with
Code:
-i 0x2b4c
.
Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.
To check type:
Code:
fastboot -i 0x2b4c oem get-device-info
If it returns:
(bootloader) Device unlocked: true
Click to expand...
Click to collapse
Then you are ready to begin the flashing process.
Move the downloaded file to your platform tools folder and type:
Code:
fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE1.img
If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.
Special thanks to Anas Khan who made these awesome titles!
XDA:DevDB Information
Un-Official Breadcrust's TWRP 2.8.7.0 Recovery for ZUK Z1, ROM for the Lenovo Zuk Z1
Contributors
Breadcrust, TheCrazyLex
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: ZUK Z1
Based On: TWRP
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2015-11-09
Created 2015-11-11
Last Updated 2016-01-17
https://youtu.be/z5U5QIEbWtI
Version 2.0: TWRP image is now running with the Chroma Kernel as it's kernel. Reduces heat output and battery consumption of the device, added a new splashscreen too.
Version 1.3: Fixed zips not flashing on the international variant due to mismatched .prop files.
Version 1.2: Fixed version 1.1's compilation error causing it not to flash to recovery partition properly, could only be used tethered to PC.
Version 1.1: Fixed E: A render request has failed which was caused by a miss-written UI XML
Version 1.0: First working version of TWRP for Z1
Please be aware if you are running the official Cyanogen OS image OTAs will not apply automatically, you will need to install the incremental ZIPs posted by Titokhan in the "How to root ZUK Z1" thread in the Help and Troubleshooting forum. They will be on your device if you have downloaded the system update but I am yet to find this directory. If anyone finds the download location please post below and test if they will apply.
I am very aware you can't install OTA updates due to the device ID mismatching. I just posted a solution in the Android Development thread HERE credit to Radii for helping me out while working on this with him. Drop us a thanks for our hard work? Means a lot to use you know Each one counts!
Mad props for this!
Gesendet von meinem Redmi Note 2 mit Tapatalk
Hi Breadcrust, thanks for your wonderful work.
One doubt regarding Android 6.0 update, i saw a post on Internet about ZUK Z1 getting Marshmallow update and many users confirming it.
here is the link to this post explaining about updating procedure...http://apkmod4dl.com/howt-to/lenovo-zuk-z1.html
Can you confirm that it is working ? is Android 6.0 available for ZUK that soon ?
My ZUK is on my way, i am super excited to try new update with your recovery... Pls confirm it. Thanks in advance.
plikmuny said:
Hi Breadcrust, thanks for your wonderful work.
One doubt regarding Android 6.0 update, i saw a post on Internet about ZUK Z1 getting Marshmallow update and many users confirming it.
here is the link to this post explaining about updating procedure...http://apkmod4dl.com/howt-to/lenovo-zuk-z1.html
Can you confirm that it is working ? is Android 6.0 available for ZUK that soon ?
My ZUK is on my way, i am super excited to try new update with your recovery... Pls confirm it. Thanks in advance.
Click to expand...
Click to collapse
I'll be honest that post looks like a load of bollocks. The Android 6.0 source hasn't been released yet. Wait for Cyanogen 13 don't jump the gun and brick your phone.
Sent from my Z1 using Tapatalk
This recovery is useless
Cannot flash ZIP with CyanogenMod:
cm-12.1-YOG4PAS2WM-ham-signed.zip
Error appears.
LethalOne said:
This recovery is useless
Cannot flash ZIP with CyanogenMod:
cm-12.1-YOG4PAS2WM-ham-signed.zip
Error appears.
Click to expand...
Click to collapse
Worked for everyone else mate. You can't flash incremental OTAs over ZUI ROMs
It would also help if you told me the error instead of just saying it doesn't work. Especially considering other people have no issues.
Sent from my Z1 using Tapatalk
Ah. Thanks for info.
But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.
LethalOne said:
Ah. Thanks for info.
But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.
Click to expand...
Click to collapse
It will flash any ZIP just like any other TWRP it has not been modified in any way. If it will not flash I think there is an error with the ZIP or its user error
LethalOne said:
Ah. Thanks for info.
But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.
Click to expand...
Click to collapse
Sent from my Z1 using Tapatalk
Android 6.0 source code is released 2 days back already. source: cnx/software.com
i think it takes more time for CM 13 Rom for ZUK Z1...
I found that out off my Dad when I got home, looks dodgy though.
It is dodgy and might be just a themed CM. We have to wait for the kernel source to come up first and then we can think about porting an AOSP. We must wait for an official CM though.
Thanks a lot for your work!!
.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c flash recovery temp\z1.twrp.2.8.7.0.By.Breadcrust-UPDATE2.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY [ 0.268s]
writing 'recovery'...
FAILED (remote: Invalid data)
finished. total time: 0.385s
Click to expand...
Click to collapse
.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c boot temp\z1.twrp.2.8.7.0.By.Breadcrust-UPDATE2.img
downloading 'boot.img'...
OKAY [ 0.309s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.313s
Click to expand...
Click to collapse
Both failed... in bootloader mode (penguin logo). Any idea?
Maybe it's because I've updated to ZUI 1.0.062. with OTA...
mk1129 said:
Thanks a lot for your work!!
Both failed... in bootloader mode (penguin logo). Any idea?
Maybe it's because I've updated to ZUI 1.0.062. with OTA...
Click to expand...
Click to collapse
Most likely an issue to do with ZUI I was working through some installation issues with someone the other night and when we got it working it was through booting the image instead of flashing due to the broken boot loader switch in CM. So I'd bet its the OS stopping you.
Sent from my Z1 using Tapatalk
Breadcrust said:
There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.
FAQ
Q: Does this work for ZUI devices? A: No, I don't think so. You're welcome to test it and report back but so far I have only tested it with Cyanogen OS
Q: What can I get with this I can't with Cyanogen OS Recovery? A: You can flash unsigned ZIPs such as SuperSU or Xposed (Although I don't recommend doing this as I put my phone into a bootloop installing Xposed)
What will I need?
First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.
Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.
If Windows is giving you an error claiming the best driver is already installed right click Z1 or whatever it is named in Device Manager and click Update Driver.
Then click "Browse my computer for driver software" then click "Have disk" once you have done this browse to the extracted USB driver and open the .inf file it will show you three options select ADB device (Top one). Click yes to any warning and it should be mounted!
Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type
Code:
adb devices
It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.
Code:
adb devices
You will also need to download the TWRP image from the spoiler below.
Download
Android File Host for Z1 TWRP V1.2 - DOWNLOAD LINK
Android File Host MD5 for V1.2 = 3b6fa140737b769f838169e997f58975
Android File Host for Z1 TWRP V1.1 - DOWNLOAD LINK
Android File Host MD5 for V1.1 = 596816b87a45d78bed4063ac62fac137 - Compiling issue, uploaded without thorough test.
Android File Host for Z1 TWRP V1.0 - DOWNLOAD LINK
Android File Host MD5 for V1.0 = 62b72d5129591d6759bb1917868594f4 - Outdated, filled with bugs.
If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!
Guide
Type:
Code:
adb reboot bootloader
You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with
Code:
-i 0x2b4c
.
Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.
To check type:
Code:
fastboot -i 0x2b4c oem get-device-info
If it returns:
Then you are ready to begin the flashing process.
Move the downloaded file to your platform tools folder and type:
Code:
fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE1.img
If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.
Click to expand...
Click to collapse
Not working for me. Mine struck at infinite when I type get bootlock info..... I have to reboot my phone.
Mine came with CM 12.1. When I skip this step and go straight away to flash custom recovery, it says flashing failed, device locked!!!
But I have already enabled OEM bootloader unlock option and I am sure that bootloader already unlocked and enabled for tweaking. What should I do now?
I have all the drivers installed and I reinstalled twice just incase... But no help.
Anyone guide me on how to successfully flash custom recovery and root my device?
Thanks in advance
plikmuny said:
Not working for me. Mine struck at infinite when I type get bootlock info..... I have to reboot my phone.
Mine came with CM 12.1. When I skip this step and go straight away to flash custom recovery, it says flashing failed, device locked!!!
But I have already enabled OEM bootloader unlock option and I am sure that bootloader already unlocked and enabled for tweaking. What should I do now?
I have all the drivers installed and I reinstalled twice just incase... But no help.
Anyone guide me on how to successfully flash custom recovery and root my device?
Thanks in advance
Click to expand...
Click to collapse
Any fastboot errors are caused by the device as fastboot will never stop you flashing an image even if it's not supposed to be flashed like flashing recovery to system. Open a thread and appeal there I unfortunately can't help on that front. People do seem to be having issues with the international device I am starting to think it's different in someway for the Chinese one. Maybe the USB id is different.
Sent from my Z1 using Tapatalk
Breadcrust said:
Any fastboot errors are caused by the device as fastboot will never stop you flashing an image even if it's not supposed to be flashed like flashing recovery to system. Open a thread and appeal there I unfortunately can't help on that front. People do seem to be having issues with the international device I am starting to think it's different in someway for the Chinese one. Maybe the USB id is different.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Thanks for your Kind reply. How do i find out what my Device ID is ? I mean, how did you come to know that the device ID of Chinese ZUK Z1 is 0x2b4c ?
Sorry for being noob.
plikmuny said:
Thanks for your Kind reply. How do i find out what my Device ID is ? I mean, how did you come to know that the device ID of Chinese ZUK Z1 is 0x2b4c ?
Sorry for being noob.
Click to expand...
Click to collapse
Paul O'Brien at MoDaCo found it
Sent from my Z1 using Tapatalk
Breadcrust said:
Paul O'Brien at MoDaCo found it
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Can you tell me what it shows when you type adb devices ?
i am curious... that might help me with my Problem.
Thanks in advance.
plikmuny said:
Can you tell me what it shows when you type adb devices ?
i am curious... that might help me with my Problem.
Thanks in advance.
Click to expand...
Click to collapse
D:\AndroidSDK\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
c783ecb7 device
Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Credits
@social-design-concepts for his great work and exploit for Intel Tab Devices
@vampirefo for CWM binary for Intel devices + Linux scripts
@vache for the full Repacked CWM image
Devices Compatible
A1-840FHD
A1-840 (HD)
A1-830
B1-810
A1-850
A1-860
B1-820
A3-A30
Requirement
Install the official Generic Google USB Drivers on your Desktop (http://developer.android.com/sdk/win-usb.html) - Also available in the TOOLKIT Package
Enable USB Debug on your Device
Guide 1 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.042_AV0K1_RV0MRC02_WW_GEN1 and older)
A1-830
Download
myKIT_BATCHv1.1.2.7z available at http://forum.xda-developers.com/showthread.php?t=2681783
myKIT_BATCHv1.1.2d_PATCHKIT.7z at http://forum.xda-developers.com/showthread.php?t=2681783
INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z at http://forum.xda-developers.com/showpost.php?p=51090059&postcount=3
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip myKIT_BATCHv1.1.2.7z and move myKIT_BATCHv1.1.2d_PATCHKIT.7z & INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z in the mykit-downloads directory
Start run-me.bat and type ACCEPT, press Enter. The toolkit is upgraded to 1.1.2d.
Close it, plug your Tab with USB Cable and start run-me.bat again
Type ACCEPT, press enter, type "2", press enter,
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
On your deskop, the script should auto detect the Tab like this :
{
"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"
}
Type A2, press enter, type 1 for INTEL_TRIAL_TETHERED_CWM_PKGKIT and press enter
Type ACCEPT, press enter
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 2 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.057_AV0K1_RV0TRC01_WW_GEN1 or more recent)
A1-840 (HD)
B1-810 [confirmed by @alexys77]
A1-850 [confirmed by @Darrian]
A1-860 [confirmed by @edotcom]
Download
IntelAndroid-FBRL.7z available at http://forum.xda-developers.com/showpost.php?p=57505512&postcount=2375 thx to @social-design-concepts
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip IntelAndroid-FBRL.7z
Plug your Tab with USB Cable and start launcher.bat
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
Type ACCEPT ont the cmd screen, press enter
On your deskop, the script should auto detect the Tab like this (device status online + color blue) :
Type "T3", press enter
Note: if the T3 exploit doesn't work on your device, you can try T2 or T1
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
/!\ Please note that the tethered CWM has just boot, it has not be flashed, we can't flash a custom recovery while our bootloader are locked. /!\
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 3 - Boot Tethered CWM or TWRP
Compatible with
B1-820 (LP 5.0)
A3-A30 (LP 5.0.2) confirmed by @paugustin
Procedure
Follow all steps described by @social-design-concepts on his updated thread :
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Advice/FAQ for Acer Tab Device : :
You should use the CWM recovery and the T4 exploit
TWRP boots, but no touch available
CWM runs fine, but cannot mount internal storage or /data, you MUST use an external SDCard
Flashing SuperSU and Installing Xposed Framework for LP is working great on B1-820 !
Guide 4 - Flash CWM Recovery (permanent)
vache said:
CWM for A1-840 FHD (only) based on Dell Venue 8 one. (http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925)
Tested successfully.
ADB_Fastboot.zip for Intel Devices (use this to flash)
CWM-v6.0.3.7_A1-840FHD.img.zip
stock_recovery.zip
To flash it :
Code:
fastboot flash recovery CWM-v6.0.3.7_A1-840FHD.img
Then use droidboot menu to reboot in recovery.
Click to expand...
Click to collapse
Thx @vache & @vampirefo
Firmwares
Flashable via (stock) Recovery
A1-830
SDs_Acer_AV0K0_A1-830_1.007.00_WW_GEN1.zip
SDs Acer_AV0K0_A1-830_RV01RC02_WW_GEN1.zip
SDs_Acer_AV0K0_A1-830_RV01RC05_WW_GEN1.zip
A1-840
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0ERC02_WW_GEN1
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0LRC01_GC_GEN1
SDs_Acer_AV0K1_A1-840_RV0XRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840_RV0ZRC03_WW_GEN1.zip
A1-840FHD
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0BRC01_WW_GEN1.zip
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0MRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840FHD_RV0TRC01_WW_GEN1.zip
B1-810
SDs Acer_AV0K0_B1-810_RV02RC03_WW_GEN1.zip
SDs_Acer_AV0K0_B1-810_RV02RC04_WW_GEN1.zip
A1-850
SDs Acer_AV0K0_A1-850_RV00RC01_WW_GEN1.zip
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
stari_alca said:
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
Click to expand...
Click to collapse
We can't flash it for now
This exploit only can boot it
We need to unlock the tab to be able to flash something
Envoyé de mon A1-840FHD en utilisant Tapatalk
Great Guide!
Unfortunately it doesn't work with the very similar A1-840HD:
http://forum.xda-developers.com/showpost.php?p=56580827&postcount=2158
Hi there,
How did you guys manage to install the MTP device drivers (the one that pops up in Device Manager when you enable the USB debbugging)? I´m on a Windows 7 (32 bits) and the folder we are instructed to download and unzip apparently does not contain the required files/driver.
Any help is appreciated as I can´t manage to pass that initial point.
Thanks in advance,
Mix
EDIT: I eventually got it to install correctly by using the USB Driver package from Acer:
http://global-download.acer.com/GDF...ep3=A1-840FHD&OS=ALL&LC=en&BC=ACER&SC=EMEA_27
I used the option in the toolkit which installs the drivers. If I remember correctly once you run the .bat file and ACCEPT you are given this option. I used 32 bit version of Win 7 as well.
Sent from my A1-840FHD using XDA Free mobile app
Works on A1 830
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
retroben said:
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
Click to expand...
Click to collapse
Did you try this guide?
I'm not sure I understand your post and what you want to do.
My product and safety information booklet says FHD on it despite mine only having 1GB of RAM.
Is there a root method working on the A1-840HD?
I may try Kingo since they still get updates and just added an exploit for Nexus Android 4.4.4 as well.
I hope it has support for this device.
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
borisgregoris said:
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
Click to expand...
Click to collapse
Well... I don`t have this tablet but think of buying one and I think that this could be done.
CWM has backup feature so I think that you could try backup current ROM and after you did that then root your device and if the problem pops you load CWM again and then restore original state.
If you already rooted then I think that someone that hasn`t rooted the device could make backup of ROM and upload it somewhere on the Internet.
Here is a full UPDATE zip ROM for A1-840 only (not compatible with A1-840FHD), flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
borisgregoris said:
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
Click to expand...
Click to collapse
It means that my image is older than yours (which make sense, it's not the latest firmware)
But I think you can get some file from it and make your tab working fine again.
If it doesn't work, you can try to full flash the update zip to "downgrade" to a stable version (and then, you should get some OTA updates to get back to the latest version)
Here is some OTA manual download if needed :
Code:
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0TRC01 227,47MB http://global-download.acer.com/GDFiles/Application/OTA/635537141647405935_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0RRC02 227,33MB http://global-download.acer.com/GDFiles/Application/OTA/635526789434977662_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0BRC01_AV0K1_RV0MRC02 45,86MB http://global-download.acer.com/GDFiles/Application/OTA/635490499381942196_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV09RC01_AV0K1_RV0MRC02 49,69MB http://global-download.acer.com/GDFiles/Application/OTA/635469761667577586_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0JRC02_AV0K1_RV0MRC02 42,13MB http://global-download.acer.com/GDFiles/Application/OTA/635469757626803549_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV08RC01_AV0K1_RV09RC01 37,53MB http://global-download.acer.com/GDFiles/Application/OTA/635402969903280635_OTA_Acer_1.0_AV0K1_A.zip
Enjoy
Hi, thanks for the image. Custom recovery fails for me:
assert failed: getprop("ro.product.model") == "A1-840"
Error in /cache/sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
stari_alca said:
Hi, thanks for the image. Custom recovery fails for me:
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Click to expand...
Click to collapse
Hi, same error here.
After flashing in stock recovery give me the assert failed error.
Its secure to flash the OTA files? I'm curious if they send me the same error that the update.zip. I'm afraid to brick the tab .
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Shreps said:
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Click to expand...
Click to collapse
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
borisgregoris said:
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
Click to expand...
Click to collapse
You should also set the right permissions and owner to the files like other file in the same directory.
Envoyé de mon One+
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.
I've tried again on Chrome,IE and Firefox but still get Decrypt message.
Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit
Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.
fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp
Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.
People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.
MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.
jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.
Hello, this works fine very thx, but you have recent/new mix version?
{
"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"
}
System Image: https://drive.google.com/file/d/1cAcgP55upO6UuX-gecPIXA_xnO0IXvUO/view?usp=sharing
Flash System Image:
- Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
- Connect your Razer Phone to your computer over USB.
- Start the Phone in Download Mode with one of the following methods:
- Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
- Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
- If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
- Open a terminal on your computer and navigate to the unzipped system image directory.
- Execute the flash_all script. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
- Once the script finishes, your Phone will reboot.
- You should now lock the bootloader for security.
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
LSS4181 said:
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
Click to expand...
Click to collapse
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
JDBarlow said:
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
Click to expand...
Click to collapse
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
LSS4181 said:
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
Click to expand...
Click to collapse
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
JDBarlow said:
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
Click to expand...
Click to collapse
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
LSS4181 said:
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
Click to expand...
Click to collapse
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
JDBarlow said:
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
Click to expand...
Click to collapse
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
LSS4181 said:
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
Click to expand...
Click to collapse
/HavocOS/Ten/20200402-vanilla/Havoc-OS-v3.3-20200402-arm64-ab-vanilla-nosu.img.xz
If anyone can get havoc 3.3 to work on Verizon without the sim card issue please let me know. No gsi rom will work on Verizon. Its frustrating. Thanks.
Finally got the MR3 update extracted
I worked all night extracting/converting the stock img and got beat by minutes posting Lol... anyway I also have the stock ota for global variant of MR3 if anyone needs it. You can easily patch the boot img with magisk and fastboot flash boot_a with the patched boot img and you have root again on MR3 Update. Works flawless
i Take a copy Thank You
Flashed some stuffs from MR3: modem (both), bluetooth (both), dsp (both), vendor (both), boot (inactive B slot only), system (inactive B slot only). These seem to work.
However, when flashing system and vendor I saw it mentioned something about "invalid sparse file format at header magic", but the flashed stuffs (at least vendor) looks fine.
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Havoc 3.3 GSI works fine here (the SELinux fix may still be needed for it to boot). However, for some reasons (either due to recent Magisk canary update, or something else), I lost access to VoLTE and that after updating to the new GSI version, all my app's permissions were lost and I need to reassign them (maybe it's time I back things up and start over again, as the permission reset issue can indeed happen when dirty-flashing newer GSI versions).
LSS4181 said:
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Click to expand...
Click to collapse
Running Manjaro Linux here too and experience the same behaviour.
Peace.
Can you dirty flash the mentioned images? Don't really feel like reinstalling all my apps and data.
is there a new root method
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Those usb drivers didn't work for me. What did work however was the samsung usb drivers so I downloaded them and installed, however that wasn't enough. While in fastboot mode under device manager, I can't recall how I installed it but I forced the driver either from android device in list or added new legacy hardware and installed samsung android adb interface. After that when I typed fastboot devices in console from tools folder it reported back for me. I hope this helps.
Click to expand...
Click to collapse
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
Click to expand...
Click to collapse
I u forgot something....
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Xinfuzemodz said:
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
Click to expand...
Click to collapse
Are you serious? The link of the OP is the link to MR3. If you click the flash_all.bat file it will wipe your phone and you get a fresh copy of MR3 installed so yes it can be installed on other builds
[CONFIRMED] ( WORKING ON XIAOMI MI 10T/PRO )
|-Full tutorial for everything-|
/**
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
**/
---Unlocking bootloader---
This is one of the easiest parts of this tutorial.
-Please keep in mind that this process will reset your device-
You will need:
Xiaomi Mi 10T/PRO device
USB cable
Computer
MiFlash tool (official by Xiaomi for unlocking bootloader) [LINK]
168 hours already spent on your Xiaomi device (It is a security feature that you cannot bypass)
USB drivers for your device [LINK]
Created Xiaomi Account (Used to log in to the MiFlash tool --> so you could unlock your specific device that has the same account on it) [LINK]
ADB, Fastboot tools on Windows [LINK]
-And that should everything needed for unlocking your bootloader-Process:
Open Settings --> About Phone --> TAP on your MIUI version till you see (You are now a developer)
{
"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"
}
Go to Additional Settings --> Developer Options --> OEM Unlock + Mi Unlock Status + USB Debugging
Go to Mi Unlock Status --> Add your Account (If you have not already) and device (Do what you see on the screen)
Enable USB Debugging + Change Default USB Configuration (saves us some time)
Plug your Xiaomi Mi 10T/Pro into the computer and choose on your mobile File Transfer. If anytime it asks you to prompt USB debugging from your computer --> Allow it and set it always to allow this computer.
You will now run Command prompt as ADMIN. Go to your ADB, Fastboot tools path with $ cd C:\YOUR\PATH\TO\PLATFORM\TOOLS (now your adb and fastboot commands will work)
Check if your device is connected to the computer --> $ adb devices Now go to fastboot $ adb reboot bootloader
Open the MiFlash tool and log in to your Xiaomi Account --> Hit refresh and you should see your Xiaomi Mi 10T/Pro device (It will have a different name in the program --> fastboot name) Now hit UNLOCK, and that is all, your device is now Unlocked.
OPTIONAL: If your device has not appeared in the MiFlash tool, open up Driver Booster and check for Drivers, update any MISSING DRIVERS and try again (The program works 100%, but sometimes it does not show the device because of NONE USB drivers in Fastboot mode or BAD USB drivers --> if you fix this you can easily Unlock it like in step 7.)
Now your DEVICE will reset and show you a little icon of an unlocked lock on the top of the screen, which means your bootloader is unlocked.
DONE
---Flashing TWRP and ROOT---
You will need:
Xiaomi Mi 10T/PRO device
USB cable
Computer
TWRP image (should be renamed to recovery.img) [LINK]
Vbmeta - This is used to flash to vbmeta, so No-verity-opt-encrypt could work (the file is inside vbmeta.zip called vbmeta.img) [LINK]
No-verity-opt-encrypt - this is used so we could decrypt our phone storage (in short --> so we could WIPE everything --> very useful when flashing custom ROMS) [LINK]
MAGISK for ROOT (rename .apk to .zip) [LINK] (could be outdated in the future, search for Magisk GitHub and download the latest .apk version)
Process:
Plug your Xiaomi Mi 10T/Pro into the computer and choose on your mobile File Transfer. If anytime it asks you to prompt USB debugging from your computer --> Allow it and set it always to allow this computer.
You will now run Command prompt as ADMIN. Go to your ADB, Fastboot tools path with $ cd C:\YOUR\PATH\TO\PLATFORM\TOOLS (now your adb and fastboot commands will work)
Check if your device is connected to the computer --> $ adb devices Now go to fastboot $ adb reboot bootloader
Your downloaded files should be in your ADB, Fastboot folder so you can flash them (TWRP, vbmeta)
Now type $ fastboot flash recovery recovery.img
After that is done, we will go to the recovery. Type $ fastboot boot recovery.img this will boot us into the recovery.
Now you should be in TWRP recovery.
Now we can flash MAGISK. Firstly we need to send it to our mobile phone. $ adb push Magisk.zip /sdcard (name of the magisk will be different)
Go to the Install section on your phone and select Magisk --> now, swipe. Now you should have Magisk successfully flashed into your device.
Exit from recovery to system. --> Reboot section --> choose System (on the top)
If everything goes right, you can now run MAGISK apk, and it will ask you for additional things, etc.; etc., click OK, and your phone will reboot after 5 seconds. Congratulations, you have successfully installed TWRP recovery, and you have ROOT too.
Now let's go back to fastboot mode. This time we will use MAGISK. On the top right side should be a "reload button," click it and select REBOOT TO BOOTLOADER.
On your computer, now flash vbmeta with this command. $ fastboot flash vbmeta vbmeta.img.
Next type $ fastboot boot recovery.img to go back to recovery, we need to flash now the no-verity-opt-encrypt. When you are there, push that file to your mobile like this. $ adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /sdcard (name of the file could be different). Once that is done, go to the install section, click on the no-verity-opt-encrypt, and swipe to flash it.
Now you can reboot to System and download the Official TWRP app [LINK] (might be outdated, search for TWRP Official app apkmirror, and download the latest version)
This app is handy for flashing other versions of TWRP without the need for a computer. GUIDE: Open the app --> TWRP Flash --> It will ask you to prompt SuperUser rights, click allow. --> You will see two buttons (Select a device and Select a file to flash) --> The Select Device option is left empty (No device selected) and now click on the Select a file to flash and choose your .img file of TWRP. Now you tap, FLASH TO RECOVERY, and you are done.
DONE
---Flashing custom ROMS---You will need:
Xiaomi Mi 10T/PRO device
USB cable
Computer
Your custom ROM .zip file
Everything else mentioned in this tutorial (TWRP, MAGISK, etc...)
Process:
Go to the recovery using Magisk or whatever you like.
This time, we will go to the WIPE section. Do a regular SWIPE --> then FORMAT DATA (type YES) --> then Advanced WIPE (select everything EXCEPT for USB OTG)
Now, if you did everything right, there should not be many errors (It should always show SUCCESSFUL on the top of the screen when operating)
Now we can push our custom ROM .zip file to our Xiaomi Mi 10T/Pro device. The command should look like this $ adb push Evolution_X.zip /sdcard (the name of the custom ROM can be different)
Go to the Install section, select your custom ROM and install it. Now, pray that nothing goes wrong. I have done it right with THIS EXACT TUTORIAL (made by my friend and me). If anything bad happens, ask me for help if you need it. Reboot to the System and ENJOY your new ROM.
DONE
I hope that this helped you. I had to find pretty much all of this on my own. Enjoy.
There are more Custom ROMS for Xiaomi Mi 10T/Pro:
(not on xda, but a Telegram group)
Project 404
CrDroid
Fluid
ArrowOS [FIRMWARE]
Pixel Experience
Evolution X
NusantaraProject
ShapeShiftOS - I don't recommend it
Xiaomi.eu BETA 12.5
TELEGRAM GROUPS:
MOD EDIT: Telegram link removed, please read the STICKY!
PitchBlackRecoveryProject (might not work for everyone)
[LINK]
Thanks for guide, might help someone.
StatDam said:
For this device there only exist two custom ROMS for now, Evolution X and Lineage OS
Click to expand...
Click to collapse
That is not correct. Those two are the ones you will find ond XDA but on Telegram there is more roms.
Lineage has not been updated since December but there is a unofficial 18.1 made by someone on Telegram, seems it is for testing only and not released yet.
There is these roms besides Evo X and Lineage:
Project 404
HentaiOS
CrDroid
Fluid
AncientOS
Pixel Experience - To be released soon.
There is more roms but they are not updated and is not worth mentioning here.
HentaiOS...lol. wheres can i find this telegram group
After flashing disable dm-verity, can I now reboot to twrp and install via usb otg/internal?
fishy_500 said:
After flashing disable dm-verity, can I now reboot to twrp and install via usb otg/internal?
Click to expand...
Click to collapse
Hello. Could you give me more information? What do you want to install? Because if you've flashed dm-verity it's already installed. If it worked, you can try rebooting to recovery (if you have System still) and it will ask you for your password from your phone. It's used for decryption of your Internal Storage.
d3smond said:
That is not correct. Those two are the ones you will find ond XDA but on Telegram there is more roms.
Lineage has not been updated since December but there is a unofficial 18.1 made by someone on Telegram, seems it is for testing only and not released yet.
Click to expand...
Click to collapse
Thank you for moving my post and not deleting. You're a great mod.
StatDam said:
Hello. Could you give me more information? What do you want to install? Because if you've flashed dm-verity it's already installed. If it worked, you can try rebooting to recovery (if you have System still) and it will ask you for your password from your phone. It's used for decryption of your Internal Storage.
Click to expand...
Click to collapse
Apologies for not replying instantly, I have decrypted my device by adding a pattern into it. I can now flash directly via internal storage and otg. Thanks
fishy_500 said:
Apologies for not replying instantly, I have decrypt my device by adding a pattern into it. I can now flash directly via internal storage and otg. Thanks
Click to expand...
Click to collapse
Glad I could help, somehow...
StatDam said:
Glad I could help, somehow...
Click to expand...
Click to collapse
Well, this guide you have created helped me in rooting my device.
This is quite a helpful thread!
I'm struggling to find CrDroid and Fluid ROMs tho but managed to find Project 404, HentaiOs, and AnicentOS...
Thanks!
Sub8 said:
This is quite a helpful thread!
I'm struggling to find CrDroid and Fluid ROMs tho but managed to find Project 404, HentaiOs, and AnicentOS...
Thanks!
Click to expand...
Click to collapse
Glad I could help
If you need help, I'm here for you anytime. I will be updating my tutorial overtime.
Is there a way to fix Fastboot driver either with or without an "actual" tool? I detest that Crapbooster or any adware in paticular. Which exact driver(s) are missing?
Kat Jillianne said:
Is there a way to fix Fastboot driver either with or without an "actual" tool? I detest that Crapbooster or any adware in paticular. Which exact driver(s) are missing?
Click to expand...
Click to collapse
Google legacy drivers. You need something like that. Install them and then repair them with DriverBooster. This worked for me. I haven't found any official drivers. If you find something new or better, please let me know.
StatDam said:
Google legacy drivers. You need something like that. Install them and then repair them with DriverBooster. This worked for me. I haven't found any official drivers. If you find something new or better, please let me know.
Click to expand...
Click to collapse
I already have Google Legacy driver installed for ages, but I did a reinstall just to be sure if there's something amiss by following your guide, problem remain unsolved...
Kat Jillianne said:
I already have Google Legacy driver installed for ages, but I did a reinstall just to be sure if there's something amiss by following your guide, problem remain unsolved...
Click to expand...
Click to collapse
This is the trickiest part. Unfortunately this part wasn't made by me, but my friend. Let me ask him. Brb
StatDam said:
This is the trickiest part. Unfortunately this part wasn't made by me, but my friend. Let me ask him. Brb
Click to expand...
Click to collapse
Fixed it. Uninstall existing driver then reinstall it using bootloader unlock tool.
Thanks for making a detailed guide.
MOD EDIT: QUOTE REMOVED
BTW you should add to your guide that with latest (unofficial) TWRP MTP works, so adb sideloading won't be the only way to transfer files anymore. Or perhaps it works because I did a full driver reinstall, not sure on this one. Just tested.
Kat Jillianne said:
BTW you should add to your guide that with latest (unofficial) TWRP MTP works, so adb sideloading won't be the only way to transfer files anymore. Just tested.
Click to expand...
Click to collapse
Wait. MTP works? I tried a few days ago and still no MTP support. So I gave it the adb push. I thought that more convenient.
StatDam said:
Wait. MTP works? I tried a few days ago and still no MTP support. So I gave it the adb push. I thought that more convenient.
Click to expand...
Click to collapse
Yep just flashed a custom rom on my phone, every zips transferred using MTP. Doesn't hurt if it turns out not working for you or anyone.
Notice this will VOID YOUR WARRANTY.
I am not to blame for BRICKED DEVICE.
Do this at YOUR OWN RISK.
Things you need :
1: OnePlus Nord N100 - Oxygen OS 11.0.5.BE83BA
2: Computer with Adb and Fastboot Installed - check google for adb and fastboot
3: Unlocked Bootloader - https://source.android.com/devices/bootloader/locking_unlocking
4: Adb Enabled in developer options aka USB debugging
5: The Boot.img - below
6: Magisk.apk - https://magiskmanager.com/
Guide :
Step 1: Patch Boot.img with Magisk
Open the magisk app and select Install>Select And Patch a File>Boot.img>Let's go
And then wait for :
Output file is written to
/storage/emulated/0/Download/magisk...img
- All done!
Press the arrow at the top and close Magisk for now
Step 2: Connect to the Computer with adb and fastboot installed
On Phone :
Allow the computer to browse files
On Computer :
Go in the file explorer to your phones downloads( This Computer\BE2013\Internal shared storage\Download ) folder and find the magisk...img
Copy the magisk...img to your desktop or any other folder if you can find it in Command Prompt(Windows)
Then Open Command Prompt(Windows)/Terminal(Linux)
Cd to your work folder(Desktop) or the "any other folder"
cd Desktop(Windows)
Step 3: Boot the device into bootloader
Do a check if the device is connected with:
adb devices
On phone :
Allow USB debugging
If nothing shows up on the phone or it says the phone is unauthorized reconnect the phone and try again.
On Computer :
Next we reboot the phone to bootloader with :
adb reboot bootloader
The phone will restart and you shall see a big START
Step 4: The Final Step Test & Install Root
Testing if everything works as expected eg Wifi, Bluetooth, Hotspot, Other stuff because these things broke for me once because I used the wrong version of boot.img.
Id still test them.
On Computer :
fastboot devices
If there is the same device as in Step 3 adb devices command all should be working expected.
Optional :
fastboot boot magisk...img Tip Use TAB to autocomplete in Command Prompt(Windows)
Next up test if all of the wireless stuff is working eg Wifi, Bluetooth, Hotspot, Other stuff
You can also open magisk to see if the device is Rooted.
Going back to bootloader is important for the next sub step("Flashing").
adb reboot bootloader
Flashing :
Did you boot the magisk...img?
If yes did everything work?
If not do not do this part!
fastboot flash boot magisk...img
fastboot reboot
Done!
Sorry for any typing mistakes if there is any.
If you have any questions ill be slow to respond if I even respond.
Sincerely Maxi
Where did you get this boot image?
I am getting the same behavior I get when trying to patch the global boot image - will not boot this TM model phone.
bouyakasha said:
Where did you get this boot image?
I am getting the same behavior I get when trying to patch the global boot image - will not boot this TM model phone.
Click to expand...
Click to collapse
I extracted the boot image from OTA update.
What do you mean with TM model phone? This is for the BE83BA.
hello someone does not have a rom 11.0.1be83ba I formatted the whole system unfortunately
Grilmama said:
hello someone does not have a rom 11.0.1be83ba I formatted the whole system unfortunately
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
https://otafsg-cost-az.coloros.com/OnePlusN100_EEA/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/patch/amazone2/GLO/OnePlusN100Oxygen/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/OnePlusN100Oxygen_14.E.25_OTA_0250_all_2203311235_0a17ce328283d7.zip
Hi. Anyone can you extract Oxygen OS 11.0.5. BE83BA boot.img for me? Thank you! Can't access PC.
VPH20 said:
https://otafsg-cost-az.coloros.com/OnePlusN100_EEA/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/patch/amazone2/GLO/OnePlusN100Oxygen/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/OnePlusN100Oxygen_14.E.25_OTA_0250_all_2203311235_0a17ce328283d7.zip
Hi. Anyone can you extract Oxygen OS 11.0.5. BE83BA boot.img for me? Thank you! Can't access PC.
Click to expand...
Click to collapse
The post has been updated. It includes the updated boot.img.
Ma_x11 said:
The post has been updated. It includes the updated boot.img.
Click to expand...
Click to collapse
Thank you very much!