[SIZE=+3]Lenovo P2[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE][SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, or create your own thread in the Q&A forum. Do not use this as a general help thread.[/SIZE]
Basic Device Information
Released in November 2016, the Lenovo Vibe P2 is a 5.5" smartphone with mid-range specifications and a budget-friendly price. It is the successor to the Lenovo Vibe P1, offering an even higher battery capacity fitted inside a thinner and lighter body.
There are two variants of the Lenovo P2; the international (or global variant) and the Chinese variant. Therefore, it is very important to know which one you have or which one you should buy. If you bought your device from retailers in India/UK/Europe, it is very likely that you bought the international version. The international version has the code name P2a42, whereas the Chinese version is labelled P2c72. The easiest way to distinguish between the two is to check the storage size. Only the Chinese variant (P2c72) of the P2 comes with a 64GB storage. Hence, if your P2 has only 32GB of internal storage, your P2 is the international variant (P2a42).
Aside from differences in storage, the two P2 variants differ in the bands they support. Courtesy of user @911-Future_Maker, the differences are highlighted in red.
P2a42
GSM: GSM850/ GSM900/ GSM1800/ GSM1900
3G: UMTS2100 (B1)/ UMTS1900 (B2)/ UMTS850 (B5)/ UMTS900 (B8)
4G: LTE2100 (B1)/ LTE1800 (B3)/ LTE1700/2100 (B4)/ LTE850 (B5)/ LTE2600 (B7)/ LTE900 (B8)/ LTE800 (B20)/ LTE700 (B28)/ TD-LTE2600 (B38)/ TD-LTE2300 (B40)
P2c72
GSM: GSM850/ GSM900/ GSM1800/ GSM1900
3G: UMTS2100 (B1)/ UMTS900 (B8)/ CDMA800 (BC0)/ TD-SCDMA2000/ TD-SCDMA1900
4G: LTE2100 (B1)/ LTE1800 (B3)/ TD-LTE2600 (B38)/ TD-LTE1900 (B39)/ TD-LTE2300 (B40)/ TD-LTE2500 (B41)
Despite the differences in the internal storage and radio bands, both variants share common partitions, aside from the data partition, of course. As a result, many global Chinese shops, such as bangggod and gearbest, sell the P2c72 preflashed with the P2a42 firmware; the reason being that the P2a42 firmware supports more languages, whereas the P2c72 firmware supports only English and Chinese, among other reasons. Even though the P2c72 can run the P2a42 firmware, the bands that it supports remain those of the P2c72.
NOTE : Do not flash your device with files that are intended for the other variant. You will very likely end up with either a bricked phone or a phone that does not recognize the sim or your carrier's network. You have been warned!
Official Stock Firmware
You should only flash the full firmware when it is the method of last resort. The choice of which firmware version to use should be based on the variant you own and the version of Android installed. It has been reported that if you flash the full firmware intended for Android 6 on the P2 that is already on Android 7, then you will have modem issues. Be warned.
P2a42 Firmware
Downloads (Thanks to @abhayruparel. Password: lenovo-forums.ru)
P2a42_S048_161111_ROW_fastboot.7z
P2a42_S062_170117_ROW_fastboot.7z
P2a42_S232_170320_ROW_fastboot.7z
P2a42_S233_170404_ROW_fastboot.7z
P2a42_S244_170725_ROW_fastboot.7z
P2c72 Firmware
Downloads (The files below are hosted on baidu servers; download speed is very slow.)
联想VIBE P2 P2c72_USR_ST1637_官方原厂固件ROM线刷包下载 首发
联想P2 P2c72_VIBEUI_V3.5_1652_5.1342.1官方固件ROM线刷包下载
联想P2c72官方线刷固件VIBEUI_V3.5_1706_5.1599.1_ST安卓7.0首发
Official Stock Updates
Upon receiving the P2, it will most likely still have Android 6 installed. You can either update your device automatically to Android 7.0 via OTA updates or manually by downloading the files below and flashing them one after the other. Please note that these files are intended only for owners of the P2a42 or the P2c72 with the P2a42 firmware.
Downloads
From S048 to S062 (Android 6 minor update)
From S062 to S232 (Android 6 to Android 7.0 update)
From S232 to S233 (Android 7.0 minor update)
From S233 to S244 (Android 7.0 minor update)
In order to manually upgrade, you must have a sdcard. The upgrading process has to be done in the numerical order in which the files are listed above. For example, you download the first file, move it to the root of your sdcard, rename it to update.zip, reboot into recovery, upgrade, restart the phone, and repeat the same process for the second file and so on.
To manually install updates:
Shut down the phone.
Hold Vol Up + Vol Down + Power Button to boot into the recovery menu. Release the buttons when the screen turns on.
In the recovery menu, Select Install Update Package > Yes.
After the last upgrade is installed, it is advisable to do a factory reset. Enter the recovery menu. Choose Wipe User Data. First do Fuse Wipe Data, then Fuse Format Data, and finally Wipe Cache, all the while selecting Yes when asked.
USB Drivers, Root, Custom Recoveries + Stock Recoveries
USB Drivers
Lenovo USB driver 1.1.34
Qualcomm USB driver 2.2.0.0
Unlocking the Bootloader
The bootloader must be unlocked before any modding can be done on the P2. Please be aware that unlocking the bootloader voids your warranty and formats your data partition (don't forget to backup important files). Unlocking the bootloader on the P2a42 or the P2c72 running the P2a42 firmware is a simple process.
Go to Settings > About phone > Tap 7 times on Build number > Go back > Enter Developer options > Enable OEM unlocking
Accept the terms that you understand that you're voiding your warranty by choosing to unlock your bootloader
Login with your Lenovo account (if you already have one) or create a new one
Wait for 14 days. A countdown timer will begin that is specifically associated with your device.
After the waiting period, go back to OEM unlocking so that the Lenovo servers can toggle the bootloader unlock switch.
At this point you must have installed the Lenovo USB drivers and Minimal ADB Fastboot on your Windows computer.
Shut down the phone. Enter into fastboot mode by holding Vol Down + Power Button until the screen turns on.
Connect the P2 to your computer and open Minimal ADB Fastboot.
Type: fastboot oem unlock
Recoveries
TWRP 3.2.1-0 (latest custom recovery)
Stock Recovery for Android 6
Stock Recovery for Android 7
If you're going to be installing custom ROMs, it is better to replace the stock recovery with TWRP. Check this page for more information or the latest updates. The procedure below works for both the P2a42 and the P2c72 running the P2a42 firmware.
Rename the TWRP file to twrp.img and move it to both the root of the internal storage of your P2 and the folder where Minimal ADB Fastboot is installed (usually C:\Program Files (x86)\Minimal ADB and Fastboot).
Boot the P2 into fastboot mode.
Open Minimal ADB Fastboot and type : fastboot boot twrp.img
Inside TWRP, choose Install > Install Image > Look for twrp.img > Select recovery > Slide to install.
TWRP will now be installed over the stock recovery. At this point, it makes sense to do a full backup of your partitions. Backup everything except System Image and Cache. In the event you want to return to stock recovery, either restore only the recovery from the Restore menu in TWRP, if you had saved a backup, or flash it as in step 4 above. You should download the stock recovery for the Android version installed on your P2.
Rooting
Files for Magisk method
Files for SuperSU method
The methods described here are only applicable for the P2 running on stock Android 7. Check this post for more details or instructions on how to root the P2 on stock Android 6.
There are basically two methods that can give you super user privileges on the P2. If you have apps that won't allow you to use them if your device is rooted (such as Android Pay), then the Magisk method is for you. This method roots your device without modifying Android's system partition at all. This means that fewer of Android's built-in security measures need to be bypassed in order to gain root access. At the moment, for the Magisk method to work, you need to format the data partition to EXT4. This will obviously erase all your files; so, backup important files before going ahead with it. Download the latest version of Magisk from the link above and move the zip file to the P2's internal storage.
Shut down. Boot into TWRP.
In TWRP, select Wipe > Advanced Wipe > Select Data > Repair or Change File System > Change File System > Select EXT4
Go back to the main menu: Select Install > Look for Magisk-vx.y.zip > Slide to install.
There's also another method you can root the P2 with, but this method is deprecated; it is advisable to use Magisk to provide root privileges as described above. Rooting via the SuperSU method is only presented here for the sake of reference.
You will find two files in the "Files for SuperSU method" linked above.
Install the me.phh.superuser.apk file.
Move the superuser-r259.zip file to the root of the P2's the internal storage.
Shut down. Boot into TWRP.
Select Install > Look for superuser-r259.zip > Slide to install.
Reserved
MODS, GUIDES, and Misc
Decryption the internal storage
The only reason I could think of why someone would want to decrypt the internal storage is to be able to multiboot as one of the requirements of DualBootPatcher is for the internal storage, or more specifically the data partition, to be unencrypted. It's important that you understand that decrypting the internal storage makes it very easy for anyone with access to your phone to access all your data. You're warned: your phone is the most personal and most portable device you have, don't be reckless with your data.
It is very likely your P2 is already encrypted. You can easily verify that by going to settings > security. If you see "Encrypted" under "Encryption", the internal storage is encrypted. If you had not set the phone to require a pin/password to boot, the phone would be encrypted using the default password. If TWRP doesn't prompt you for authentication, it may be because it tries the default password at first and succeeds with that. So, getting access to your internal storage in TWRP does not necessary mean the internal storage is not encrypted.
You need to format data (under TWRP) to remove the encryption. This obviously deletes everything on your phone; so, backup your important stuff first. Reboot the phone back into recovery after formatting data. If TWRP doesn't detect the the partitions of your internal storage, boot/flash the stock recovery. The stock recovery will properly format the partitions. Boot/Flash TWRP one more time and you will see all the partitions again. At this point, you should change the format of the data partition to ext4 and install Magisk. Installing Magisk will modify the boot partition and will prevent the phone will automatically re-encryp itself.
Getting back to Stock Firmware
In the event you can no longer boot into the phone, or your phone is bricked, you may want to reinstall the stock firmware. After downloading and extracting the zip file, you will find a file called flashall.bat inside the SW folder. All what is required then is putting the phone in fastboot mode and executing this file. However, if you've already unlocked your bootloader, running flashall.bat will fail. What you need to do is to flash the partitions manually.
In the extracted zip file, you will find files labelled systemchunkx.img (probably around 15 of them), boot.img, and recovery.img. Put your phone in fastboot mode, open Minimal ADB Fastboot and do the following:
Flash the boot image: fastboot flash boot boot.img
Flash the recovery image: fastboot flash recovery recovery.img
Flash the system chunks one after the other, starting with the first one until the last one. For example, to flash the first system chunk: fastboot flash system systemchunk1.img
medwatt said:
Official Stock Firmware
You should only flash the full firmware when it is the method of last resort. The choice of which firmware version to use should be based on the variant you own and the version of Android installed. It has been reported that if you flash the full firmware intended for Android 6 on the P2 that is already on Android 7, then you will have modem issues. Be warned.
P2a42 Firmware
Downloads (Thanks to @abhayruparel)
P2a42_S048_161111_ROW_fastboot.7z
P2a42_S062_170117_ROW_fastboot.7z
P2a42_S232_170320_ROW_fastboot.7z
P2a42_S233_170404_ROW_fastboot.7z
P2a42_S244_170725_ROW_fastboot.7z
P2a72 Firmware
Downloads (The files below are hosted on baidu servers; download speed is very slow.)
联想VIBE P2 P2c72_USR_ST1637_官方原厂固件ROM线刷包下载 首发
联想P2 P2c72_VIBEUI_V3.5_1652_5.1342.1官方固件ROM线刷包下载
联想P2c72官方线刷固件VIBEUI_V3.5_1706_5.1599.1_ST安卓7.0首发
Click to expand...
Click to collapse
P2c72 * in firmware
Add blankflash tool also to recover from hardbrick
Sent from my Lenovo P2a42 using Tapatalk
Add advice as to how to safely flash TWRP and root a P2c72 hardware device running P2a42 firmware.
Add twrp installation and root method on nougat
Im a new owner of P2, recently i upgraded my firmware to the latest(S244) and doing so upgrade ended up with something wrong i mean process/recovery didn't gave any error and even phone booted up normal but process wasn't 100% phone rebooted from like 88%, so after bootup from recovery i wiped all data and did a factory reset and used it like normal, everything was working perfect but after a week i facing random issues like battery drain, signal not sticking to 4g network, low wifi reception etc, i tried factory resetting again from recovery but that didnt solved my problem so i want flash factory firmware(android 7 S244) given above.my device is P2a42, locked bootloader, so can anyone tell me how should i flash those images, because i dont want to end up messing with modem files
After the waiting period, go back to OEM unlocking so that the Lenovo servers can toggle the bootloader unlock switch.
Click to expand...
Click to collapse
I am at this step. When press "Next" nothing happen. What do I do? Latest update, pa42 version
Found, I needed internet access.
Nice work! Helpful for new users!
Also include QCN backup method.
Sent from my Lenovo P2 using Tapatalk
Hi @medwatt,
Is there an official link to those official OTA updates please?
Bump
I rooted with super su I want to unroot and try magisk
How do I unroot?
Hello I have a P2 p2c72 with rom p2a42 bought at gearbest.
I just want to root it to use titanium backup (root access), should I use twrp recovery or can I stay with the original recovery and flash magisk after unlock bootloader ?
I don't want custom rom.
Thank you.
[EDIT] Thanks for the guide, it's good for me, twrp ok and root with magisk !
Just want to say great work on this thread!
The information for the P2 has become convoluted in the past 12 months and a summarization and write up such as this is helpful for everyone to benefit from!
Big Thanks.
Related
(Rooting guide at post #5 http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5)
(Stock ROMS at post #7 http://forum.xda-developers.com/showpost.php?p=63939728&postcount=7)
Hi,
The new flagship from Wiko, the Wiko Fever, it's a great device. :good:
Here my research with it:
- MT6753 with 16GB ROM and 3G RAM
- Bootloader LOCKED (you can unlock it using one option in the developers hidden menu (you know how to enable it!) and then after reboot in the bootloader execute "fastboot oem unlock" (note, that selecting OK you will erase your data!).
:good:
- You can download an EXPERIMENTAL (=ALPHA) custom Recovery (CWM-Carliv) from here (you need to flash it to use it):
***removed***
- Also you can download the original DUMP of the boot.img and recovery.img from here:
http://www.sendspace.com/file/zy9q6g
:silly:
You can pack/unpack the recovery/boot using the CarlivImageKitchen selecting "normal" (not MTK) version!
..
Hi,
This device (Wiko Fever) is the same as Micromax Canvas 5 E481:
http://www.micromaxinfo.com/mobiles/smartphones/canvas/canvas-5-e481
Also, is identical to Blue Life ONE X:
http://www.bluproducts.com/index.php/life-one-x-2016
Follow the thread (with custom Kernels) at:
http://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428
Then the same firmware and rooting procedure will be shareable between both!
Here a great guide for Wiko Fever & Clones:
http://forum.xda-developers.com/android/general/guide-clones-t3421539
Hi,
Here the scatter file for Wiko Fever Lollipop 5.1.
Two versions: a) extracted from stock update (scatter_stok); b) made by hand (scatter3).
Rooting GUIDE
Hi,
Good news: Rooting is done! :victory:
Here is the guide for rooting your Wiko Fever:
Warning (for newbies): First copy all indicated files to your SD card using your phone in normal state. Or use a PC and a SD reader for copy them when indicated.
1) Unlock bootloader:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Install custom Recovery:
2.1) Download from here the BETA 1 of CWM BETA 2 of CWM BETA 3 of CWM: http://www.sendspace.com/file/4g87bj
OR Download TWRP Beta 1 for Lollipop 5.1 from Hanuma: http://www.sendspace.com/file/y4jel8
(Original post: http://forum.xda-developers.com/showpost.php?p=64543542&postcount=45)
OR Download TWRP 3.0.2.0 for Marshmallow from Hanuma: https://www.sendspace.com/file/9ms9zz
(Original post: http://forum.xda-developers.com/showpost.php?p=67531723&postcount=217)
2.2) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Then execute command “fastboot flash recovery recovery-custom-wiko-fever.img”; and then “fastboot reboot”.
3) Rooting:
3.1) Copy last beta of SuperSU v2.52 to your SD Card (file BETA-SuperSU-v2.52.zip).
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3.2) Boot in the CWM with “Vol+” and “Power” buttons.
3.3) Install ZIP from external-sd card.
3.4) Reboot and don’t select “fix root”, only “Yes”.
3.5) After boot, start SuperSU and configure it. Root done!
4) Xposed install:
4.1) Copy last release of Xposed Installer to your SD Card. Use files from here:
http://forum.xda-developers.com/showthread.php?t=3034811
* xposed-v78-sdk22-arm64.zip
* XposedInstaller_3.0_alpha4.apk
* xposed-uninstaller-20150831-arm64.zip (in case of errors).
4.2) Boot in the Recovery, and install the framework (file xposed-v78-sdk22-arm64.zip).
4.3) After reboot, install the Xposed APK (file XposedInstaller_3.0_alpha4.apk).
4.4) Reboot. The Xposed framework is running.
Enjoy!
Notes: Before starting to root your device I recommend to do a full DUMP of the firmware using the SP Flash Tool. Use my handmade scatter file. :angel:
Thank you to all developers & supporters! :highfive:
ChangeLog:
- Beta 3: Fixed ADB shell with root uid.
- Beta 2: Fixed SELinux context support in ext4 filesystem. Full woking for rooting!
Note: If you like to use adb shell in recovery but an error like "exec '/system/bin/sh' failed: No such file or directory" then first mount /system partition.
- Beta 1: Don't use this version, has a bug with SELinux contexts!
- Alpha(1,2,3): Pre-releases.
List of stock ROMs (for flashing with SPFlashTools) for Fever V8 (16GB/3GB) only:
- Lollipop v39 (last version until 5/2016): http://world.wikomobile.com/scripts/telecharger.php?id=140&type=MAJ
- Lollipop v22 (update 02.12.2015): http://fr.wikomobile.com/scripts/telecharger.php?id=105&type=MAJ
- Lollipop v18 (update 10.11.2015): http://fr.wikomobile.com/update-918-FEVER-4G
In case you need it!
List of stock OTA ROMs (for flashing with CWM/TWRP Custom Recovery):
If you have rooted your device, you can upgrade using these ROMs...
- Lollipop v39 (pre-rooted, with Xposed and ViPER Audio):
part 1: http://www.sendspace.com/file/d0js30 md5: e8706e0f5860e907fb8169856fc5e3b9
part 2: https://www.sendspace.com/file/iv4mnb md5: dd76926221ef40c872e4548a9b9e1f19
part 3: https://www.sendspace.com/file/6lfd18 md5: 838e6e608983a296611a284831fffd47
WARNING: At time this is untested! Give feedback with a post in the thread!
Decompress it using 7zip in your PC, copy files to your SD Card TWRP/Backup folder, and restore this backup with TWRP
Probably you want to use these versions!
Hi,
God news! I de-bricked my device... ****ing erroneous selinux context attributes in /system/lib64/ and /system/bin/ are the reason!
So, I don't futher need the stock SYSTEM partition. I'll continue with the rooting process... soon I'll publish it.
this device can support cm12-cm13?
djsolidsnake86 said:
this device can support cm12-cm13?
Click to expand...
Click to collapse
I hope!
Maybe will be easy for some developer to port one CM13 firmware for MT6753 to this device.
The opensource package for this device isn't at time available. Sorry!
Verify that the bootloader is unlocked
Hi manos78, first of all thanks for this guide and all the efforts you are putting into this.
manos78 said:
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.
1.2) Power on the device in the BOOTLOADER mode. Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
Click to expand...
Click to collapse
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Thanks again!
hi guys, i followed the guide and all worked also with the last update
cippaciong said:
I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?
Click to expand...
Click to collapse
After the command "fastboot oem unlock" If you see the Warning message and the device is rebooted and formating the data partition, then you have for sure unlocked the bootloader.
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
manos78 said:
But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.
Click to expand...
Click to collapse
Unlocked
You have been really helpful, thank you!
oile said:
Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?
Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/
Click to expand...
Click to collapse
Hi,
I try to boot the custom recovery image with fastboot without flash and it fails. So for rooting, at time, the only way is: unlock->flash custom recovery->install superSU. But after that, you can try to: flash stock recovery->re-lock, if you like (not tested by me! Be carefull!). However, with the custom recovery you can do full backups, so I recomend it. The side effect is that you can't upgrade with OTAs.
Another option is use the original stock firmware and readback/flash the SYSTEM partition and modify it using an external computer (modify the IMG). But, this solution is quite complex.
Finally, related to the SD-CARD. The "internal memory" is only for "media", not for Apps. I use one 64GB SD on my Fever and I store in it: photos, music & ISO/IMG images. Any other data is in the internal storage (emulated sdcard). Also, I "installed" (=moved) some huge games (>100MB) to the sdcard (the real SD); and I store my Google Kiosk and Music files on the sdcard (also the real SD). Please, don't care about the sd storage, is working right on the stock firmware.
:good:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
oile said:
About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)
Click to expand...
Click to collapse
In stock Fever ROM:
/sdcard --> the REAL SD Card (the Sygic data, Google Music & Kiosk, etc. are in the REAL SD Card)
/storage/sdcard1 --> the EMULATED SD (internal memory)
Then you can use the SD as real one with Apps, and use alternative (emulated) when you like. The "media" Apps can use sdcard0 (real) or sdcard1 (emulated).
Related to this sentence: "hese apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)"
Please, remember: both, external memory and internal memory, have LIMITED life (write operations). Then, what you prefer: write more on the internal and not interchangable memory, or in a removable and inexpensive memory?
Please, think well! :angel:
Also, FYI, in my current Wiko Fever I use a 64GB SDXC UHS-II, far away than a simple class 10 (x15 reads/x30 writes).
oile said:
Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.
Click to expand...
Click to collapse
I'm quite accustomed to filesystems and partitions since I've been using Linux for many years but I've got almost zero experience with Android internals, so please help me to understand if I got this right.
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
I'm sorry if my questions might sound dumb to you but I'd like to start tinkering with Android a bit more but having a hard time finding a good starting point.
cippaciong said:
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
Click to expand...
Click to collapse
Hi,
Unlock bootloader is for booting NON-SIGNED kernels (the boot or the recovery), not for partitions.
When you unlock the bootloader you can install (or boot) a CUSTOM recovery. In the custom recovery you can mount and modify the SYSTEM partition (where is included the root).
For "flash" or "dump" the internal memory of the device, if it's using a MTK cpu (like the Fever) then you can use SP FLASH TOOL. You have the scatter file in this thread!
We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Perhaps useful for you: I've managed to extract the stock rom of a brand new TB3-710F
http://forum.xda-developers.com/android/help/lenovo-tab-3-7-essential-tb3-710f-mt8127-t3416397
This also includes the "recovery.img" so you could try to change this image and simply flashing it. If it does not work you'll have a stock rom to restore it.
gogetrd said:
We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Click to expand...
Click to collapse
Did u manage to get TWRP or CWM for TB3-710F ?
zwirc said:
Did u manage to get TWRP or CWM for TB3-710F ?
Click to expand...
Click to collapse
Yes, I built it for them. Download here
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
You can configure 1 tablet, then extract the ROM and flash it with the "download mode". You don't even need to boot the tablet!
If you want more info let me know, back from holiday in a few days
@lacostej You can certainly automate some steps, and you do not always need root. (And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...)
There are three ways to install another firmware:
The MediaTek SmartPhone Flash Tool (SPFT). This is a PC program (Windows and Linux) that allows reading and writing of the entire internal storage (on a partition granularity). Via USB, while the device is powered down. Only for devices based on MediaTek chips, of course (this tablet is MediaTek-based).
Fastboot. This is a little USB protocol implemented by the bootloader. A Fastboot client on PC can communicate with the bootloader via USB and execute certain commands, e.g. "fastboot flash" for flashing partitions. However, there are a few drawbacks with this:
First, you need to boot the device into fastboot mode. Some devices have a boot menu that allows you to do this, but this device doesn't. Starting the tablet via power+volumeUP takes you directly to the recovery instead of a boot menu. But in the recovery, whether stock or TWRP, there's a reboot to bootloader option. Using ADB (adb reboot bootloader) should also take you there.
Second, the "fastboot flash" command is restricted on this tablet. If you were to use "fastboot flash recovery <recoveryfilename_here>", for example, it would abort with an error message. I have patched the bootloader to allow the flash command, but you'd first need to install this patched version on your tablet(s), of course, via SPFT or other means.
Third, the "fastboot flash" command has a size limit - the bootloader needs to buffer the USB data in RAM before it can be written, and since the tablet has only 1 GB of RAM, you obviously can't flash a 1 GB system image this way. The buffer is actually a lot smaller: just 128 MiB. Meaning whatever file you send to the tablet via "fastboot flash", it cannot be larger than 128 MiB. So, how do you flash the system or userdata partition then, which are much, much larger? By splitting their image file into many smaller "sparse" image files, each of which is below the size limit. There's probably a tool for doing this, but I don't know any details.
TWRP, or another custom recovery. They allow you to create and restore backups. TWRP has some automation support via OpenRecoveryScript.
So, if you have 700 tablets to configure, you can configure just one, then save its state via SPFT or TWRP, then restore that on each other tablet.
What is its "state"? Well, the system, cache, and data partitions. The system partition is normally read-only and won't change, therefore you do not need to clone it. Unless you install root and modify stuff on the system partition, of course. The cache partition is quite irrelevant. It is the data partition that has all the app settings.
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
You can at least avoid cloning the MAC addresses by deleting the entire directory /data/nvram/ before you create your backup. MediaTek devices have a dedicated NVRAM partition that contains the MAC addresses and some other stuff, and this data gets unpacked to /data/nvram/ when Android boots. Unless the files there already exist. So, by deleting /data/nvram/ before you clone, you force each tablet to extract its unique MAC addresses again at the next boot...
Thanks a lot for the feedback. Really appreciated.
Tzul said:
@lacostej And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...
Click to expand...
Click to collapse
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
.
Click to expand...
Click to collapse
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
lacostej said:
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
Click to expand...
Click to collapse
SuperSU is just like any other root manager. It provides the actual "su" (superuser) binary that other programs rely on to obtain root privileges, plus an Android app for managing permissions and settings. The su binary needs to be installed on the system partition (at least traditionally), but in order to get write access there, you need root privileges. Therefore, this is a chicken and egg problem: SuperSU provides root, but it also needs root in order to be installed. Other root manager are no different - except that some try to exploit security flaws in Android in order to temporarily obtain root and install their su binary.
Anyway, the classic solution to this conundrum is the (custom) recovery: it basically has root built-in. It can write to the system partition by default, after all one of its jobs is to install firmware updates.
TWRP includes a SuperSU stub. If you leave TWRP via the Reboot menu, it checks whether or not the su binary is installed (at least in Android 4 and 5), and if it isn't, it asks if you'd like to install the SuperSU stub. Which you can then use in Android to update to the latest SuperSU via Play Store. But you can also install SuperSU's latest "update zip" in TWRP to immediately install the full version.
lacostej said:
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
Click to expand...
Click to collapse
Yeah, it is annoying. MediaTek apparently wisened up a bit. Newer platforms they produce do not unpack the NVRAM partition to the data partition anymore. Instead, they use a dedicated "nvdata" partition for that purpose. That way, if you clone the data partition, you at least won't include the unpacked NVRAM data (MAC addresses and IMEI). But still, some other IDs such as the Android ID, references to the serial number, etc. will very likely be referenced by some other files on the data partition.
I created a little "update zip" that can be "installed" via TWRP, which is just a shell script that tries to delete all the files on the data partition that contain unique or sensitive info. I use it to "clean" a data partition before publishing it. But it's not perfect yet...
@Tzul Your modified rom is great. But I have one problem with it.
When you connect your turned off device to the power supply there is a clock and charging animation. The clock is several hours ahead of the system clock. System clock and clock during the charging are connected (when I change the system time the 2nd clock also changes the hour).
I was trying to use hwclock but without success.
Is there some kind of file where I can set the correct time zone for the 2nd clock?
Sorry for my English.
@Yozen I didn't modify the ROM. I extracted and packaged it.
When the tablet is turned off and then connected to a power supply, it will usually start "off-mode charging" (can be disabled, so that Android will boot up instead). This is handled by the bootloader (LK, lk.bin), which also displays the battery animation and the clock that you see. Apparently the bootloader on this device doesn't handle time zones, because the clock shown uses China Standard Time (CST, UTC+08:00). This is the first MediaTek-based device I've seen which shows a clock in the off-mode charging screen at all. I guess they normally don't because they have no simple way to figure out the user's correct time zone at that stage.
Will this method and these files work for TB3-730F?
Sir, is there a custom ROM available for Lenovo tab3-710f ?
lacostej said:
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
Click to expand...
Click to collapse
How did you do it in the end? I'm trying to do something similar here and am very curious!
.acy said:
How did you do it in the end? I'm trying to do something similar here and am very curious!
Click to expand...
Click to collapse
For us it is this "simple".
1. Manually configure a single device
2. Readback the ROM (get the ROM from the device and store it on your PC) using SP Flash Tool
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
4. (clear cache partition & remove stuff like serial number)
5. Load your ROM in SP Flash Tool
6. Click start
7. DO NOT START your new tablet
8. Connect it to USB
9. Wait (assuming you already have the preloader drivers installed)
10. Done, new ROM is flashed to your tab!
edit:
Oh and with 700 tablets it might be nice to look into compressing the file as the full 8gb dump we flash (and we don't do a lot these days) will take ~30-40 minutes
mattiemvs said:
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
Click to expand...
Click to collapse
That's unnecessary, because the SP Flash Tool can already read back partitions into separate files.
Also, you don't need to clone some partitions like cache, and you really should not clone nvram and parts of data, otherwise you'll end up with tablets sharing unique IDs such as MAC addresses, which will cause problems.
Tzul, you are absolutely right! I typed the items from my mind as it has been quite some time since I've created the ROM
tb3-710f s000028
Tzul said:
Yes, I built it for them.
Click to expand...
Click to collapse
Hello tzul,
Thanks for your jobs.
I want to install Lenovo_TB3-710F_S000027_TO_S000028_Patched_Tzul.zip
But i don't know how i do this when i try with SPFT i choose teh scatter-file and i have an error :
sp flash toll error : 5417
The load scatter file is invalid !
hint :
please check the scatter file and select again
Can you help me ? please
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Tzul said:
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Click to expand...
Click to collapse
Thanks for your answer.
I go to test it.
I want to root this kernel 000028 and i have difficult to do it ?
Do you have a easy solution ?
Thanks a lot for your help.
I'd like to create a new thread on installing TWRP and rooting Android Nougat (7.x) on version B360 of the Honor 8. All the threads I see are people frantically trying to restore their phone to their previous glory. To keep people from asking "will this work on yada yada model, *I* have a FRD-L04 which is the 32gb unlocked SINGLE SIM variant sold locally at Best Buy here in the states and I'm pretty sure the FRD-L09 is the international DUAL SIM version with 64GB and I believe firmware for both of these are different? If not, please correct me. The process should be the same for all variants, but the files used will be different.
I want to update this OP and keep it as up to date as possible. If we can get 3 or more people to confirm a certain process works in this thread, I will update it with the proper links to all tools/files/versions of TWRP and SuperSU as well as firmware that's needed. I think I currently count eleven different threads all over the place on this and would be nice to have it centralized. Let's help out and get this phone going with a working root on Nougat!!!
Here are the questions I propose:
1. What is the actual steps to root the Honor 8 running a FULL STOCK version of B360 (Android 7.x)?
A. Unlock Bootloader (This process should be the same as always)
B. Flash TWRP (Which version?) This should be a simple flash with fastboot
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
If I can have answered the questions above, I will clean it up and move it over to the guide section. As it stands now we have no guide. We just need clarification on what works, what doesn't and the process.
Also, PLEASE be kind to those who don't speak English as their primary language. The Honor 8 is an international phone and I see many people getting angry because they don't understand or don't follow instructions correctly because the OP didn't clearly state what they did. Let's help each other out!
Here's an example step by step for unlocking the bootloader below. This is what I'd like to do for each of the questions above.
A: Unlocking the bootloader (UNDERSTAND THAT BY UNLOCKING THE BOOTLOADER ALL YOUR DATA ON THE PHONE WILL BE ERASED AS IF YOU'RE PULLING IT OUT OF THE BOX FOR THE FIRST TIME)
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/HiSuite_en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio/releases/platform-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
B. Flash TWRP (Which version?) This should be a simple flash with fastboot. This is already discussed in another post, but I will put here for reference.
1. Grab a working copy of TWRP for the Honor 8 here: https://forum.xda-developers.com/showpost.php?p=70893767&postcount=408
2. Download TWRP into the same folder you used in step A above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP. This is a crazy process because of the encryption on the Data partition. Below is the exact steps I can confirm works from the help of others on here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Once here, you can download root checker and it will verify you have root access - BUT.. see section D below!
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
Some applications like Root Checker will verify that you have root. Other applications will even prompt you (like any of the basic quick reboot apps that easily let you back into recovery) but other major apps like BusyBox and Viper4Audio (when asking to load the driver) will simply fail upon installation. I'm not sure why, since you have R/W access to both the system and the newly unencrypted data partition. I'm really hoping someone can help with this one!
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
I know and have done A, B, and C, but as for the rest I'm not too sure about those.
Maybe in the wrong section but thank you.
joesee said:
14. It will format data using make_ext4fs..
Click to expand...
Click to collapse
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
joesee said:
15. When finished, tap Reboot System
Click to expand...
Click to collapse
When I wipe then reboot I get stuck in the bootup screen
EDIT； Nevermind I just didn't wait long enough for my phone to boot up
KevinN206 said:
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
Click to expand...
Click to collapse
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
faizalotai said:
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
Click to expand...
Click to collapse
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
KevinN206 said:
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
Click to expand...
Click to collapse
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
faizalotai said:
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
Click to expand...
Click to collapse
I am afraid of running into this issue from a fellow xda. The person still doesn't have a solution. https://forum.xda-developers.com/mate-8/help/encrypted-data-mount-t3537645
I'm running into issues with Bluetooth activation, and previously NFC, which i fixed by reflashing the hw_update package, but still no Bluetooth.
I've followed each and every single step on this guide, and BT was working perfectly before.
Any ideas where this may be coming from ?
Still, thanks or the guide
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Hello. Im coming from general topic on Honor 8 rooting but my issue is related to Android MM.
So i had stock EMUI 4.1 (Android 6.0) which i unlocked, flashed TWRP and SuperSU.
Today EMUI 5 (Android 7 ) update came by air so i installed it. After update - no TWPR neither SuperSU.
I enabled Developer options and saw "Enable OEM unlock" switch in OFF state and grayed out (impossible to switch ON).
So now i cannot flash TWPR as fastboot gives error "Command not allowed".
During boot phone says that it is unlocked, FRP lock. Otherwise it boots and works fine but no root.
Any solution possible?
Thank you.
Telperion said:
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Click to expand...
Click to collapse
can u please tell more or make a step by step tutorial on rooting? I'm stuck in rooting, when I format data and boot agai into recovery and flash su It still ends with error 1, dnt know which error it is..
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Is there any way to do this without rooting?
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
ajmdrh said:
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Click to expand...
Click to collapse
Update to latest TWRP and try again
Shehzaan said:
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
Click to expand...
Click to collapse
Indian version?? Frd-l02?
venugopalu007 said:
Indian version?? Frd-l02?
Click to expand...
Click to collapse
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Shehzaan said:
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Click to expand...
Click to collapse
Yes, it is middle east variant
PalakMi said:
Yes, it is middle east variant
Click to expand...
Click to collapse
Do you have any idea how can I get EMUI 5.0 without rooting?
Welcome!
This Megathread is to help bring the different threads together for the Xiaomi Black Shark (SKR-A0 or SKR-H0) since the xiaomi-black-shark tag is broken (at least for me it is). This will also serve as a one-stop shop for people who need general black shark support!
Disclaimer: You (the user) assume the risk for any bootloader unlocking, rooting, or any other modifying of your device. These can lead to phone's being bricked or boot-looped. We aren't to blame if the directions aren't followed to the T!
Tips before modding your phone
1. Stay organized! Make a folder for any files you download or data your backup so you don't lose anything important
2. Backup your user data onto your computer. It is guaranteed 100% of the time that your phone's data will be wiped when installing of uninstalling ANY of the modifications listed below. Unless you have been rooting and unlocking bootloaders for years, you don't want to skip this step.
Common ADB and Fastboot Commands
These are some commands you'll need to get to know:
adb devices: this shows what devices are currently connected to your computer
adb pull: this pulls a file from your phone and saves it to a location on your computer. You will need to specify the location of the file and the save location of the file
adb reboot bootloader: this reboots the phone into fastboot mode to use fastboot commands
fastboot devices: this shows what devices are connected to your computer in fastboot mode
fastboot boot filename.img: this boots the phone with using a image file of your choice
fastboot flash disk_partiton filename.img: this will flash an image file over the disk partition you want.
Example:
fastboot system system.img flashes a new system_a.img over the system parition of your phone's storage. This is where the main operating system is held on the phone.fastboot reboot: reboots the phone
fastboot continue: boots the phone straight from fastboot into the system, not restarting the phone.
Unlock/Relock your Bootloader
WARNING: This WILL wipe your internal data
On Android, the phone must have an unlocked bootloader to enable some of the common modding features. These steps will unlock your bootloader.
Pre-requisites:
1. You will need the SDK Platform Tools downloaded onto your computer. This has the necessary adb and fastboot programs you will need in order to unlock your bootloader.
2. Enable Developer Options on the Phone
-Go to Settings -> About phone and tap the Build Number 7 times to enable Developer Options
3. Enable OEM unlocking
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
4. Enable USB Debugging. This lets you use ADB (Android Debugging Bridge) to send commands from your computer to the phone.
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable USB debugging.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable USB debugging.
5. Boot into fastboot mode.
-Booting from the Phone:
Turn the Phone off
Press and hold the Volume Down Button
Turn the phone on while holding the volume down button
-Booting from the PC:
Connect your phone to your computer.
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: adb devices
A pop up should show up on your phone. Click the checkmark next to "Always allow from this computer" and click ok. Your computer is now allowed to send commands to the phone.
Now run the command: adb reboot bootloader
You should now be in fastboot mode!
To check if you're in fastboot mode:
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: fastboot devices
If your device shows up then you're in fastboot mode! You should also see a line of text that says something like:
"Bootloader Locked"
"Bootloader Unlocked"
Unlocking your Bootloader:
1. If your phone says bootloader is locked:
While connected to your PC run the following commands:
-For SKR-A0
fastboot oem unlock
-For SKR-H0
fastboot flashing unlock
If there is a warning click to proceed with the unlock. THIS WILL WIPE YOUR DATA AT THIS TIME.
If your phone says bootloader is unlocked:
Skip this step!
Your Bootloader is now Unlocked!!
Relocking your Bootloader:[/size]
1. Boot into fastboot mode
2. Connect your phone to your computer
3. Run the Bootloader Lock command
3a. For Both Versions
fastboot flashing lock
WARNING: THIS WILL WIPE YOUR DATA.
Your bootloader is now Locked!
Rooting Using TWRP
Unlocked Bootloader Required!
Required files:
The latest Magisk Zip and APK files...it can be found here
A Computer with the latest SDK Platform tools
TWRP image file found at this thread
Do NOT download the installer.
1. Boot into fastboot mode and connect to your computer
2. Run the command: fastboot boot Name_of_twrp_file_.img
Replace Name_of_twrp_file.img with the name of the twrp image file you've downloaded for the blackshark
Tips:
If your screen is upside down, that's ok! Your touches will be in the same spot, the image is the only thing that's upside down.
On first boot, if TWRP is asking for a decryption password, you will need to wipe your data before going forward.
3. Move the Magisk Zip file to your phone's storage
4. On TWRP:
Click install -> Magisk.Zip file -> Swipe to confirm flash
5. After the install is complete: Swipe to reboot the phone
DO NOT INSTALL TWRP APP IF IT ASKS YOU TO
6. After the phone reboots, install the Magisk apk file
7. If you start the magisk app and it says Magisk is not installed, try rebooting your phone.
8. If you start the magisk app, and it asks to download extra resources, click ok.
You're now rooted!
Install GApps
Installing GApps should only be for the CN version!
You can find the directions and required files in this thread here
Factory Images
For the CN version (SKR-A0)
The factory images can be found on Google Drive here
For the Global version (SKR-H0)
[Guide] Restoring Black Shark 1 Global to Stock OTA bug fixed!
Using Project Treble (GSI) System Images!
What is Project Treble and GSI?
The Generic System Image (GSI) was added into Android 8.0 devices to enable OEM partners and developers to help with updating devices. Using an dual system approach (slot a and slot b) android phones can be updated seamlessly (without rebooting) and recover devices from a bad update.
Project Treble is an extension of this feature to enable developers to update their OS easier to new versions of Android! This includes *drum roll* the ROM commmunity!! So if your phone supports project treble and gsi (which the Black Shark does) we already have ROMs available to us!
The Downside to Project Treble Roms
Our Vendor File isn't compatible with Treble ROMs and we can't use other vendor files (as what I have seen so far) so these bugs will exist for now:
The S logo doesn't turn off. Stays Green lit.
You may not be able to increase screen brightness.
Fingerprint may not work on the Treble ROM.
Installing a Project Treble Rom
YOU WILL LOSE YOUR USERDATA. THERE IS NO GETTING AROUND THIS AS OF NOW.
Prerequisites:
Unlocked Bootloader on your phone and adb, fastboot, TWRP image and the most recent Magisk Zip on your computer.
For CN variants (SKR-A0) you may need to use the Global (SKR-H0) vendor and boot images. These steps were tested on using the Global Images
1. Choose your rom over here
2. Download the ARM64 A/B version of your rom of choice. The Black Shark supports Seamless Updates and it's based on the 64bit architecture (as are most modern phones).
3. Factory Reset your phone. You can do this either through the recovery or through the system settings.
4. Boot into bootloader mode on the phone and connect the phone to the PC.
5. Erase the system partition: fastboot erase system
6. Flash the new system OS: fastboot -u flash system system_image_file.img
7. Boot into TWRP from fastboot: fastboot boot twrp_file.img
8. Tap the DO NOT ALLOW SYSTEM MODIFICATIONS
9. Move the Magisk Zip file to your phone.
10. Click Install -> Magisk Zip -> Swipe to Install
11. Reboot the Phone
That's it! Your screen will be upside down during the media locking process (using a Disable Force Encryption file has not worked for me). Once your get to the setup page you may have to set it up with the screen upside down. THIS IS THE SAME AS HOW TWRP IS UPSIDE DOWN BUT THE TAPS ARE IN THE NORMAL SPOTS. If a warning comes up that's normal.
Android 9.0 Pie News!!!
https://forum.xda-developers.com/android/development/news-black-shark-2-features-coming-to-t3924703
How to Get CN Rom's Shark Space and MI Market onto Global ROM:
https://forum.xda-developers.com/an...-cn-shark-space-mi-market-blackshark-t3927854
Credits:
TWRP by @mauronofrio
Offical XDA Magisk Thread
@gilbert32 for factory global images
Placeholder
---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
gilbert32 said:
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Click to expand...
Click to collapse
No problem!
The CN version gets messed up on the OTA if your active boot is on B. It seems the OTA updates only work with active boot A. It also gets messed up obviously if the backup boot is not the same version. I had to make sure both system_a and system_b were on CN before updating system_a with the OTA.
Hope this helps.. obviously I'm a CN user, but you never know! :good:
gilbert32 said:
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
Click to expand...
Click to collapse
I already have a linux environment in the works...
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
gilbert32 said:
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
Click to expand...
Click to collapse
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
JengaMasterG said:
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
Click to expand...
Click to collapse
AFAIK, it's gonna be pretty hard to build without having the kernel sources. Unless they release them soon, building for the device directly is gonna be a long shot.
However, checkout the treble device forums. You can download and flash roms from that section, and they will probably boot, but you'll have problems with auto brightness, random reboots, etc.
I still can't get the auto brightness and device specific stuff to work.
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
a8530516 said:
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
Click to expand...
Click to collapse
can you share how you did it here?
JengaMasterG said:
The Model version is set by the vbmeta.img files. You should be able to find those here under the factory image files section.
If you want any future support, ask for it in in the megathread so we can keep all the support in one thread :good:
Click to expand...
Click to collapse
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
khususgw said:
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
Click to expand...
Click to collapse
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
JengaMasterG said:
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
Click to expand...
Click to collapse
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
khususgw said:
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
Click to expand...
Click to collapse
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Reply:
Xiaomi Black Shark support are the thing which people need to know now a days world is evolving and things are changing rapidly.
JengaMasterG said:
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Click to expand...
Click to collapse
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
khususgw said:
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
Click to expand...
Click to collapse
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
JengaMasterG said:
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
Click to expand...
Click to collapse
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
khususgw said:
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
Click to expand...
Click to collapse
Yeah you can do it that way!
JengaMasterG said:
Yeah you can do it that way!
Click to expand...
Click to collapse
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
khususgw said:
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
Click to expand...
Click to collapse
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
JengaMasterG said:
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
Click to expand...
Click to collapse
after i try flash from scratch
and using old vendor b
still i cant do the OTA update
If you've recently purchased a Xiaomi Poco X3 Pro, but were on the fence about using it until an AOSP ROM became available then you're in luck. Kudos to @kubersharma for his contribution by providing us the first official AOSP release, ArrowOS v11.0 [vayu].
Now, throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. These are fully detailed instructions to make it easier for newbs.
I've spent the better part of my day figuring all of this stuff out so hopefully you won't go through the trouble I did. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW, THANKS. NOW LET'S BEGIN!!!
UNLOCK BOOTLOADER
1. Unlock the bootloader with Xiaomi Unlocker tool.
a. Be aware this process will factory reset the device before proceeding.
b. Download the Mi Unlock app onto your PC. Extract the contents within the zip file into an empty folder then run the app.
c. Register for Xiaomi account and sign in with your Mi Account.
d. Your Mi Account must be added to your Mi Settings
Sign into your Mi Account on the device.
Go to Settings –> About Phone –> tap on MIUI version (For POCO) until it says Developer options is enabled.
Back out of About Phone, Additional Settings –> Developer options –> Mi Unlock status.
Agree, then "Add account and device".
e. Shut down your phone manually, and hold Vol down + Power button to enter Fastboot mode.
Download and install the latest Xiaomi USB Drivers or here (or Google's latest USB drivers for Windows if all else fails) for your PC.
Connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface" (in Device Manager), and click "Unlock" in the Unlock app.
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
f. After your first initial unlock attempt, you MUST wait 168 hours before unlock process can fully complete.
Wiping the device or removing the Mi account from the device could result in the timer being reset.
g. After the waiting period expires, click "Unlock" in the Unlock app. You will notice the phone will restart followed by subsequent different screens during the phone's boot sequence including the "POCO" screen which now displays an "open lock icon" at the top, indicating your bootloader unlock attempt and will eventually end up on a "This device is locked" screen where you have to confirm you are the device owner by entering your Mi Account password to "activate this device"; connect to your WiFi prior to doing so if the device lacks an active sim card.
FLASH CUSTOM RECOVERY, DECRYPTION DISABLER, & ROM THEN ROOT
2. Download the Official ArrowOS v11.0-vayu fastboot ROM for POCO X3 Pro [direct link here].
a. NOTE: ArrowOS requires MIUI V12.0.4.0 firmware so it recommended to downgrade to this version before flashing ArrowOS otherwise the ROM may not boot.
b. Choose the GApps build type which "includes Play services and now some AOSP apps have been replaced with GApps... All GApps packages and other[sic] files [were] extracted from original firmware images for Pixel4XL (coral)."
3. [OPTIONAL] Download the latest version of Encryption Disabler then copy it along with the fastboot ROM into a folder named 'TWRP' on the root of your microSD.
4. Ensure USB Debugging is already enabled on your device (in Settings –> Additional Settings –> Developer options).
5. Remove any screen unlock (i.e., fingerprint, PIN, pattern or password) in MIUI.
6. Power off device and put it in Fastboot mode (Vol down + Power button).
7. Download the latest SDK Platform Tools from Google for adb compatibility and create a folder called "adb" in the root of the "C:\" drive.
a. Extract the files adb, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot into the folder.
b. Ensure the latest USB drivers are installed for your PC, connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface".
c. Launch "Command Prompt" on your PC and run the command:
cd C:/adb
To show a list of devices (including your phone) connected to your PC, enter the command:
fastboot devices
8. Download the unofficial Pbrb (test3) recovery file (PitchBlack Recovery Project 3.1.0 unofficial) by Alex Besida and copy it into the ADB install folder and rename it to "recovery.img".
9. Flash custom recovery file in CMD, run commands:
fastboot flash recovery "recovery.img"
fastboot boot recovery.img
10. Your device should automatically boot into custom recovery. At this point, the microSD will become accessible from recovery or the PC, but the device's internal storage will not be which makes using a microSD card much more imperative for this process since the recovery is in early access development.
a. Go to Wipe –> Format Data, type "yes" to perform data wipe; Back out to the main menu.
b. Go to Install –> Navigate to the TWRP folder on the microSD (via "external_sd").
Select "Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip" and flash the ROM, but do not change any of the checkboxes that show up before doing so.
Format data (not wipe) before rebooting into the new ROM.
NOTE: At most it takes around 1 minute to boot back up.
11. [OPTIONAL] Power off the device and boot back into recovery.
a. Go to Install –> Navigate to the TWRP folder on the microSD.
Select " Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" and flash it, but do not change any of the checkboxes that show up before doing so.
NOTE: This will disable forced encryption of data partition for better performance and internal SD + Data mounting in TWRP. It's not needed for the ROM to work, but due to disabling encryption it compromises security.
Reboot into the new ROM.
12. After going through the phone's boot sequence, you'll be presented with the initial phone setup process onscreen where you can begin recovering your data.
13. Go to Settings –> About phone –>tap on Build number until it says Developer options is enabled.
a. Back out to Settings –> System –> to access Developer options –> Enable USB Debugging.
14. Installing Magisk via custom recovery will fail in the background, resulting in an unresponsive "POCO" screen which is caused by installer scripts not being able to properly detect the correct device info or the recovery environment does not meet its expectation. In this case, you will need to use the Patch Image method as it is guaranteed to work 100% of the time. Installing Magisk through custom recoveries on modern devices is no longer recommended due to this reason.
a. Pull down the Notification Bar from the top of the screen and change "Charging this device via USB" to "File Transfer".
b. Open " Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip " and copy "boot.img" to the phone's internal storage.
c. Download the latest version of Magisk (Magisk v22.1) and copy it to the phone's internal storage and use the native "Files" app to install the apk.
NOTE: Magisk binaries (ZIP) are now included within Magisk Manager APK file. Now you don’t have to download it separately. You can install the .apk file or rename its extension to .zip then flash it through custom recovery / TWRP.
d. Launch Magisk from the app drawer and go to "Install" under Magisk –> "Select and Patch a File," select the "boot.img" you copied internally –> "LET'S GO".
e. Copy the generated patched file to the ADB folder and flash it via fastboot by running the following commands:
cd C:/adb
fastboot flash boot boot.img
f. Reboot into the new ROM and voila!
fastboot reboot
g. Use an app such as Root Checker or BusyBox Checker (from the Play Store) to confirm root status.
h. To bypass/restore SafetyNet validation, open the Magisk app, go to Settings (cogwheel icon) and enable MagiskHide.
SIDENOTES:
These are either my comments or other user's comments that may be considered helpful as it relates to ArrowOS
Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro (Credits to @pl1992aw)
Using TWRP to install OTA Updates
Installing OTA updates
Stability of 'PitchBlack Recovery Project' Recovery
How to verify SafetyNet status
Feel feel to let me know of other threads or comments that are also related to installing ArrowOS.
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
kamild_ said:
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
Click to expand...
Click to collapse
Fair enough, thanks for the suggestions. I can add them in.
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Aulig said:
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Click to expand...
Click to collapse
Yes, you have to update to MIUI 12.0.4.0 before flashing.
How stable is the PBRP Beta? Great Guide btw
DeblaGaming said:
How stable is the PBRP Beta? Great Guide btw
Click to expand...
Click to collapse
More stable than other unofficial custom recoveries such as OrangeFox, especially when it comes to functionality. Based on my experience using OrangeFox, it failed to flash anything that was already present on my microSD, but PBRP worked OOB w/ no issues first time, and allowed me to copy over files onto the microSD while the device was in recovery while simultaneously being connected to my PC. Thanks btw.
AusVGM said:
Yes, you have to update to MIUI 12.0.4.0 before flashing.
Click to expand...
Click to collapse
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Aulig said:
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Click to expand...
Click to collapse
Thanks for the compliment... I didn't feel the need to include how someone could check their device's SafetyNet status, but the app I use is called SafetyNet Helper Sample in the Play Store.
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
bla.tiga said:
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
Click to expand...
Click to collapse
Thanks for the compliment. To answer your questions:
1) Any version of MIUI V12.0.4.0 will do.
2) To flash future OTA updates (ROMs), it will require flashing the "compatible recovery" (vayu ArrowOS Recovery) in fastboot mode, rebooting the device then followed by installing the OTA update once it becomes available and letting it flash automatically.
hello all,
I have flashed vanilla version of ArrowOS, and magisk...
could somebody help me with installing microG for VANILLA build ROM? I'm new to microG stuff, so I don't really know from where should I install, what version etc.
some apps are not running as they require Google play services
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
Best that your question be taken up w/ the devs.
as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
So I have some breaking news:
I can confirm that the latest unofficial alpha version of TWRP (TWRP-3.5.1-vayu-Nebrassy-1) is capable of decrypting and reading internal storage. Due to this advancement, I can also confirm that ArrowOS OTA updates will officially work using TWRP. There is NO NEED TO USE ANY OTHER CUSTOM RECOVERY BESIDES TWRP.
Hi everyone, i have one dubt in unlock bootloader process...
When phone wipe /data partition???, after or before wait the time to unlock???
Let's remain on topic and avoid bickering.
My bootloader unlocks in 4 days and I am planning to change the room using your guide. I have a doubt, I am a beginner. can I do step 8 with TWRP instead of Pbrb (test3)? Would the steps be the same with the change?
@newbrn of course. Pitch Black is literally a dark themed TWRP with some tweaks.