Hi All,
***MIUI 8 is now operational on our TCL_S960!
I managed to get it running on TCL S960 (IDOL X+),
Here's my work... (I am not a developer but I followed some instructions online and was able to make it at least for me...)
Probably there will be bugs - so let me know
I'll try to fix what I know...
If you want to use my work elsewhere, you must request in advance and make sure that credits goes to the correct people....
Supported Languages:
All languages that are supported by Xiaomi.EU roms.
Credits:
Xiaomi.eu - for the translations and guides.
Latest version Download links:
Android File Host: (WIP)...
30/Jul/2016 -
Older Versions (Miui8)
24/Jul/2016 (fixes to 14/7/2016) - https://www.androidfilehost.com/?fid=24651429356503158
14/Jul/2016 - https://www.androidfilehost.com/?fid=24591000424947416
7/7/2016 - https://www.androidfilehost.com/?fid=24591020540823614
30/6/2016 - https://www.androidfilehost.com/?fid=24591020540823614
Older Versions (MIUI7):
26/5/2016 - https://www.androidfilehost.com/?fid=24566454284190288
19/5/2016 - https://www.androidfilehost.com/?fid=24533103863143479
12/05/2016 - https://www.androidfilehost.com/?fid=24533103863139453
05/05/2016 - https://www.androidfilehost.com/?fid=24533103863137243
28/4/2016 - https://www.androidfilehost.com/?fid=4996500813288309006
14/4/2016 - https://www.androidfilehost.com/?fid=24499762636000772
7/4/2016 - https://www.androidfilehost.com/?fid=24459283995317117
31/3/2016 - https://www.androidfilehost.com/?fid=24459283995310311
17/3/2016 - https://www.androidfilehost.com/?fid=24459283995303903
XdaDevDB:
Installations:
Important:
Prior to any install make sure to backup your existing ROM. (TWRP backup?) if you wish to backup your SMS/Contacts there are a bunch of apps that can do it... (MobilePro is an example)
Backup your IMEI just in case... (Use MobileUncle or similar)
If you chose to install - your warranty is void.
I am not responsible for any damage that may be caused by this ROM.
Did you make a backup? - Save your backup on a PC...
First time transition to MIUI8 requires re-partition of the phone to increase system size.
you will need a different recovery to finalise the process.
1. Copy the Repartition zip file to phone.
2. Copy the Philz recovery to your phone.
3. Install Philz recovery.
4. Reboot into recovery
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
8. Restore your backup.
9. Boot the phone.
10. Copy the MIUI8 install file to phone.
11. Click on the 3 dots
12. Chose select update file --> select your copied file.
13. Phone will Reboot and install.
If the above version does not work, you will need to use SP-Flash tools to install the EBR1, EBR2 files in the zip.
Then continue from step 6 (Format partitions)
if coming from another rom/ Fresh install
as ususal... - I recomend a total wipe, but it is not a must....
Wipe Cache, Dalvik, Data, System, custpack.
Install Rom from internal memory
reboot.
Wait patiently - it will take 3-4 minutes on the 1st boot.
To update (existing Miui Rom):
Copy rom to SD Card
Open updater app.
Click on the 3 dots
Chose select update file --> select your copied file.
Reboot
*** Make sure to disable Automated OTA... as it is based on Redmi Note 3G MTK, and I can't promise to keep this forever...
Recovery:
I used TWRP 2.8.7.0 for TCL S960
Other recoveries:
CWM - Link
TWRP 2.6.3 - Link
If you like my work feel free to buy me beer Donation link
Known Issues:
Default theme - some icons are missing - Use another theme icon set...
When making full wipe - unable to login to MiAccount - Install 6.1.28 version --> login, then update to latest.
TouchAssistant APK exceeds the space of System partition - I removed it, you can install it manually after the rom installs. - Link solved after repartition.
31/3/16 - Additional settings FC - Fixed.
12/05/2016 - Fixed wallpaper carousel FC when unlocking device
Some screenshots:
Miui8:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Miui7:
XDA:DevDB Information
TCL S960/Alcatel (IdolX+), ROM for the Android General
Contributors
hellfreezover, Xiaomi.eu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: MIUI
Version Information
Status: Beta
Current Beta Version: 26-05-2016
Beta Release Date: 2016-07-15
Created 2016-01-22
Last Updated 2016-07-30
Reserved
Changelog: (Latest Version)
24/7/2016 - still based on 6.7.14
Fixed Settings menus.
Enabled "Button mode"
Enabled additional settings to split the menu bar.
Fixed MIUI version to 8...
System seems to be running faster...
Older versions:
14/7/2016
System
Fix - Fingerprint issues (07-12)
Fix - Fingerprint scanner made the device freeze and reboot (07-12)
Lockscreen, Status Bar, Notification Bar
Optimization - Clickable arrow for Wi-Fi (07-12)
Optimization - A prompt about entering password and activating fingerprint after rebooting the device (07-13)
Fix - Customized carrier name isn't shown in Second space (07-12)
Home screen
Optimization - Landscape mode for Task manager (07-08)
Optimization - Task Manager stability (07-13)
Fix - Issues with wallpaper when switching to Second space (07-13)
Delete - Home screen Music widget (07-13)
Gallery
New - Delete directly from the screenshot preview page (07-12)
Optimization - Adjusted size for the button which creates new albums (07-12)
Optimization - "Show original" option appears only on cloud or optimized items (07-12)
Optimization - Double tap to zoom in, swipe up without entering sharing mode (07-12)
Optimization - When auto-rotate is off in Gallery, it won't influence the rest of the system (07-13)
Fix - Scrolling screenshot issues in Notes and Mail (07-12)
Fix - Couldn't go back to the original photo after making a screenshot or finishing editing/sharing it (07-12)
Fix - Couldn't pick up calls while making Scrolling screenshots (07-13)
Fix - Enter system app while editing a scrolling screenshot in the OOB flow (07-13)
Delete - Removed Edit option for GIF images (07-12)
Weather
Fix - Issues with curves in forecasts (07-13)
Optimization - Set C/F in settings (07-13)
7/7/2016
Highlights
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
Lock Screen, Status Bar, Notification Bar
New - Animation of WiFi connection (07-07)
Optimization - separate "Ringtone and Vibration" permission in Notification （07-07）
Fix - Switching notification bar style in landscape view issues (07-07)
Fix - In Second Space, enter Mi Home in lock Screen issue (07-07)
Desktop
Optimization - Restore app uninstallation sound effect (07-07)
Fix - Recent app tray, long press to enter wrong app info page issue (07-07)
Fix - Recent app tray, switching view mode issues (07-07)
Settings
New - Saved and available Wi-Fi networks appear first in the list (07-05)
Clock / Calculator
Optimization - "Shutdown alarm", "Set default alarm sound" moved up In Clock settings. (07-01).
30/6/2016 - Miui 8.
26/5/2016 -
Gallery
New - Deleting synced photos from internal storage without deleting from Mi Cloud (05-25)
Cleaner
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
19/05/2016 -
System
Optimization - Background CPU processes caused performance issues (05-16)
Optimization - Delayed response for charger's notifications (05-19)
Fix - Wireless display caused reboots (05-19)
Fix - Read mode appeared more red than it should be (05-19)
Fix - Draining battery while using GPS in some cases (05-19)
Fix - Bluetooth turned on automatically with the device (05-19)
Settings
New - Introducing Shortcut menu. Check out the new MIUI 8 feature early. You can turn it on in Additional settings. (05-17)
TouchAssistant must be installed post rom.
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
12/05/2016 -
System
Optimization - System storage UI (05-05)
Optimization - Background processes kept CPU busy and lead to performance issues (05-09)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Backup
New - Optimizing transferring rate in File Transfer (05-09)
05/05/2016 -
System
Optimization - System storage UI (05-05)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Security
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
28/4/2016 -
System
Optimisation - Improved speed and performance for devices which have been used for a long time (04-27)
Weather
New - New white design (04-27)
Cleaner
New - New design for Cleaner (04-27)
Gallery
New - Progress list for syncing with Mi Cloud (04-27)
Optimization - Added a prompt notifying about Mi Cloud trash bin when deleting photos for the first time (04-27)
Optimization - Improved sharpness for big photos (04-27)
Security
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
14/4/2016 -
System
Optimization - Improved algorithms for Silent and DND modes to be used at the same time. (04-13)
Fix - Storage leaks lead to performance problems (04-08)
Fix - Security Center FC in Hebrew Language
7/4/2016 -
Lockscreen, Status Bar, Notification Bar
Optimization - Improved order of switches in notification shade (04-06)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Settings
Optimization - Improved algorithms for international roaming (04-06)
Mi Account
New - Added more items to personal info (04-06)
Cleaner
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Mi Cloud
Fix - Couldn't find device or sign in to Mi Account due to wrong system time (04-06)
Fix - Fixed issues with incorrect time in backup lists (04-06)
Bug fixes by Xiaomi.
Fixed Additional settings FC.
31/3/2016 general bug fixes by Xiaomi.
24/3/2016
System
Optimization - Apps open faster, system animations work smoother (03-17)
Optimization - Increased image processing speed for image decryption database (03-22)
Fix - Problems with performance after switching from mobile data to Wi-Fi (03-18)
Backup
In some cases Mi Mover stopped working after the connection was established (03-18)
Clock / Calculator
New - Option for deleting an alarm automatically after it was used if it had been set to go off only once (03-23)
thank you
thank you for this awesome Rom. but the sound setting under audio force closes im on viper4android
Did you try sound settings without viper?
For me it works... but I did had to do a clean install...
Sent from my ASUS_Z00XS using XDA Free mobile app
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
santhosh5639 said:
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
Click to expand...
Click to collapse
Try using an older version like 6.1.28, then log in to miui, then update without full wipe.
I have reported this to miui, it is under discussion...
Sent from my ASUS_Z00XS using XDA Free mobile app
Updated OP with the link to 6.1.28 version
Sent from my ASUS_Z00XS using XDA Free mobile app
Updated OP with MIUI 8 for TCL.
Sent from my ASUS_Z00XS using XDA Free mobile app
Bricking my phone
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
I am not at home now,
I have the files...
You can get searching TCL multi language rom 70 languages and download it through SP flash tools, then, repartition and finally the rest....
Sent from my ASUS_Z00XS using XDA Free mobile app
Olympos.81 said:
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
Click to expand...
Click to collapse
Check your PM - I sent you a link with all files needed...
Updating problem
hellfreezover said:
Check your PM - I sent you a link with all files needed...
Click to expand...
Click to collapse
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Olympos.81 said:
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Click to expand...
Click to collapse
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
hellfreezover said:
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
Click to expand...
Click to collapse
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
Click to expand...
Click to collapse
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Click to expand...
Click to collapse
you can change the mount location in Philz recovery...
6.a. - check to see where the SDCARD data directory is mounted(\data or \data\0), if it is the \data\0 - change it back to \data in the philz recovery, otherwise - upgrades will not work in TWRP.
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Olympos.81 said:
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Click to expand...
Click to collapse
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Somebody could install this rom as Hellfreezover described?
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
hellfreezover said:
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Click to expand...
Click to collapse
Dear Hellfreezover!
I am sure, that you are advanced or professional developer and you have more experience about mobiles and ROMS, but now, I think what you have written in instructions is different as you have done it in real life.
...or someting is wrong with ROMs.
So...
I tried to follow your instruction several times and when I have reached that point that there were no error message at the beginning of installation of ROM, finally, it was also unsucessfull:
- begining: http://kepfeltoltes.hu/160717/IMG_1592_www.kepfeltoltes.hu_.jpg
- ending: http://kepfeltoltes.hu/160717/IMG_1593_www.kepfeltoltes.hu_.jpg
(See, there is no error message as before like "unmount /data" or somthing else...)
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
hellfreezover said:
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
Click to expand...
Click to collapse
Now I tried again and again, I followed again your every intsructions and I tried the following ROMs with TWRP 2.6.3.0:
- xiaomi.eu_multi_TCL_S960_6.7.14_v8-4.4 (latest) - Failed
- xiaomi.eu_multi_TCL_S960_6.6.30_v8-4.4 (previous) - Failed
- xiaomi.eu_multi_TCL_S960_6.3.10_v7-4.4 - Success!
Now, the MIUI 7 is running.
I am trying to upgrade to latest MIUI 7 and after to MIUI 8....
...but I am afraid: this will be again failed.
Related
All-In-One Toolkit
It is an easy to use tool (especially for noobs) with On-Screen instructions step-by-step to do what the following main menu screen says .. Read detailed information below.
!!! Open to suggestions and ideas !!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This toolkit runs under Windows. Installation Instructions:
Download the package from these links: Mirror1 Mirror2
Run the downloaded package and select a folder to extract the files (your user account must have write permissions in this folder). You can now extract it over a previous version because any un-needed previous files will be removed automatically.
SU660 Users: Download Both P990 & SU660-AddOn packages. Run & extract the P990 first and then extract in the same folder the SU660-AddOn. AIO-Toolkit will be converted to support SU660 device. Short & useful description for these options
1 - Backup/Restore Options.
A) Backup/Restore your internal SD Card (via USB Mass-Storage) which is taken with 7z open source tool. Auto-Detects the SD-card’s drive letter (by searching for external_sd or _ExteralSD folder). It just makes a compressed file (7z) of all the files in SD-card as backup action, and extracts this file in SD-card as restore action.
B) Backup/Restore ROM and/or Data partition with nvflash. Backup saves images under Bachup\OldLayout or Backup\NewLayout folder. Restore checks the sizes of current partitions and the backed up images and aborts restore if a partition is smaller than its image or warns if larger. It is needed because anyone now can resize the partitions easily with option 9. Note!! Smaller images can be restored to larger partitions but the final usable size will be the image’s one.2 - Change your Recovery Image.
Easily change the recovery. It supports two methods: via ADB or NVFlash. It detects the current partition layout and lists the suitable recovery images available for you to choose.
A) Change Recovery via ADB (rooted devices only). It is done with adb tool and dd command.
This works on both normal operation and recovery mode.
On normal operation the device must be rooted and USB debugging must be enabled.
Note: LG Driver package (or at least ADB drivers) must be installed at your PC for these to work.
B) Change Recovery with NVFlash. The recovery is flashed by NVFlash tool.
All latest available recovery images are located in ToolKitFiles\P990-imgs folder to be used by toolkit in any option needed. (or ToolKitFiles\SU660-imgs if SU660-AddOn package is installed).
1) The latest versions of cwm v5, v6 and twrp v2.6, for old BooLoader based ROMS prefixed as oldbl-
2) The modified cwm ones v5, v6 and twrp v2.6 for new BooLoader based ROMS prefixed as newbl-
Any procedure in toolkit, if needed, automatically detects the current partition layout, old or new and lists the suitable recoveries from imgs folder for you to choose.
Tip: You can add/remove/modify the recovery images yourself by copying/deleting/renaming them, in ToolKitFiles\<device>-imgs folder and just prefixing them as oldbl- or newbl- The toolkit will include them automatically. 3 - Root a Stock ROM (with NVFlash method).
Roots a stock ROM with the method of NVFlashing a recovery of your choice and then installing SuperUser or SuperSU within recovery mode. This method always worked when other tools failed. 4 - Repartition your device with preferred layout and bootloader:
ATTENTION!! This operation totally wipes your device's internal memory including internal SD-Card. Make sure you have a backup of your critical files, contacts, sms, etc.
It wipes internal memory, recreates partitions, and flashes the right bootloader and recovery image of your choice. You'll be able to boot in recovery mode only to install a new ROM or restore a previous nandroid-backup. It can be used for:
Quick switching to different partition layouts and bootloaders
Repairing a bricked device
It also offers a choice between pre-sized partition tables (for the selected layout and BL) to flash:
Stock [512MB System, 1536MB Data]
Double-Sized System [1024MB System, 2048MB Data] DualBoot Ready
Your own custom one (if you created one with option 9).
After repartition is finished you are prompted to:
a) Fix internal SD-Card automatically, because it is un-mountable after repartitioning.
b) Enable Dual-Boot (only if a DualBoot Ready partition table is selected).
For controling/maintaining Dual-Boot please refer to the DualBoot-Manual.pdf.
Note: LG Driver package (or at least ADB drivers) must be installed at your PC for these to work.
Safety keys: If any of the “SD-Card fix” or “Enable Dual-Boot” step fails go to ToolkitFiles\tools folder and run the IntSD-MountFix.cmd or DualBoot-Enable.cmd accordingly.
Attention: Both scripts are designed to run as standalone scripts also. The IntSD-MountFix.cmd is harmless but DualBoot-Enable.cmd always leaves system switched to ROM1 at the end, so use it ONLY if needed and ONLY on full-wiped data & boot partition e.g. after repartitioning.5 - Extract LG KDZ and/or AP.bin file.
Use this to extract a downloaded kdz file to get the baseband (fls file) and/or the ROM (bin file) to flash with SmartFlash.
Additionally you may need to extract the bin file to separate the included partition images like chefs need to cook their new ROM. 6 - LG Update Tool (Off-Line mode) to flash any KDZ ROM file.
It helps you flash any KDZ file, since the LG Update Tool does not allow a flash if the device is not in the current version LG expects. So we make our PC to serve LG update tool locally (offline).
The script automatically:
Adds 127.0.0.1 csmg.lgmobile.com entry (temporarily) in hosts file,
Sets the mini mongoose web server on the PC listening to port 9002 which serves the requests of the LG flash utility and run from wherever this package is extracted),
Installs MSXML needed for the tools to run
Runs all the utilities automatically for you (you only have to set to ON the windows enabler)
Opens in your web browser the instructions to follow and flash the ROM.
Finally it reverts back your hosts file, after closing the utility (R&D Test Tool), removing the above entry and stops http server and windows enabler.
7 - SmartFlash a Stock ROM and/or BaseBand.
It flashes a full Stock ROM (bin file) AND/OR Baseband (fls file) as I mention before in option 5.
For BaseBands information and downloads visit the detailed and helpful Complete Baseband overview thread by tonyp.
For official Stock ROMs (KDZ files) visit this site8 - Replace Stock (locked) ICS BootLoader with the New un-locked one.
ONLY for devices already partitioned to ICS layout.
It detects the current partition layout and does not proceed if OLD layout found.
Needed for those who:
Installed Stock ICS with SmartFlash or LGUpdate
Flashed a ready-rooted system.img only and trying to flash a recovery image after
Have a P990 device but are still on the bootloader logoed with a white padlock, which does not enter SmartFlash mode.
9 - Create your own custom-sized partition table to flash with option 4.
It launches the Partitions Customizer GUI tool I created (see attached picture), to help you easily create your own custom-sized partition table to flash with option 4.
Attention!! DO NOT use it if you don’t know what and why you are doing it.A – Get useful logs.
This option gets 4 different useful logs (Normal Logcat, Radio Logcat, Kernel and Last_kmsg) as very nicely described in this useful TonyP’s thread. All four commands are integrated in AIO-Toolkit for quick use without having to remember the commands. Thanks to TonyP.I - Install APX (NVFlash Recovery) Drivers if not already installed.
It starts the windows device driver wizard to help you install the drivers needed for NVFlash. It detects your system OS and gives additional on-screen instructions needed if your PC is running Windows 8.
FYI: The drivers are located under ToolKitFiles\nvflash\driver folder.Spanish Translation here by elxufas (Thank you)Change Log
V6.0: Date 10 November 2013:
Evolved DualBoot-Control.zip v6.0:
It now supports two different sized system parts for ROM1 & ROM2 (not only two half) depending on total system size. You can also have a standard 512MB for one ROM and the rest for the other.
One zip for both P990 & SU660 devices (no more different zips for the two devices)
An option is added to re-join the previously split /system partition after enabling DualBoot.
Some bug fixes
New icons and short descriptions for each option added.
DualBoot-Enable.cmd (under ToolKitFiles\tools) is also updated to support different sized system parts too. This is called by Option 4 after repartitioning to enable Dual-Boot, when a DualBoot Ready layout is selected.
Small HTTP server (http.exe) which was used by option 6 for off-line LG update, has been substituted by mini web server mongoose, cause http.exe was considered infected by most Anti-Virus SW.
Prefixes ICS- and GB- of files and recovery images changed to newbl- and oldbl- accordingly, as these are commonly used at all XDA threads to declare the bootloader and partition layout. (SU660-AddOn package also updated to v6.0 with prefix changes).
New Update mechanism: When extracting toolkit-package into existing toolkit-folder, any previous manually added recovery image(s) will be kept and properly prefixed automatically (SU660 recoveries too). Recovery images are now reside under new folder named ToolKitFiles\<device>-imgs where <device> is P990 (or SU660 if SU660-AddOn package is installed).
You can now add more than 9 recovery images per layout. No more limits of nine (9) recovery images per layout. (That’s only because I don’t like limits, not because more than 9 recoveries exist )
TWRP Recovery images updated with TonyP’s latest v2.6.0.0 versions. Thanks TonyP
SuperSU install zip updated to latest version 1.65 (SU\SuperSU-v1.65.zip)
Some warning msgs added about adb drivers when they are gonna be needed.
Of course updated manuals to reflect new changes.
A HowTo.. Steps Guide (pdf) is included, to help (mostly new) users.
Older versions' changes:
V5.6: Date 03 June 2013:
SDCard can now be fixed if TWRP recovery is selected.
a typo corrected that caused the toolkit to close without any explanation after option 4 was completed.
V5.5: Date 07 May 2013:
New and more efficient DualBoot-Control.zip v5.5:
Dual-Boot is NO MORE dependent on the specific re-sized layout DualBoot-Control.zip auto-detects the system partition’s total size and splits it into two parts when enabling dual-boot. Note: If you create your own custom partition table (Option 9), the minimum system’s total size for enabling Dual-Boot is 1024MB.
It is noob-proof because it detects the current system part (ROM1 or ROM2) and gives only the appropriate options for maintaining Dual-Boot.
An additional option is added in its aroma menu, to switch ROMs within recovery (not only through SystemChangerX app in normal operation).
Improved and more detailed aroma GUI and more..
Same zip for both P900 & SU660 devices. (Till now a different file was included in SU660 add-on pack)
Option 4 renamed to: Repartition your device with preferred layout and bootloader
Optimized and updated to support Dual-Boot. Besides layout and bl you can now choose between a) stock, b) dual-boot ready partition table and c) your own created with option 9 (if you created one)
It fixes automatically the Internal SD-Card after repartitioning (if you select so when prompted). Necessary for devices with no external sdcard available. No more need to install the IntSD-MountFix.zip.
Simplified and clearer display messages to eliminate newbies’ confusion.
It also enables dual-boot (if you accept when prompted), if a dual-boot partition table is flashed and save you some steps and reboots from installation instructions.
Option A – Prepare device for Real Dual-Boot is removed. The existing Dual-Boot ready re-sized layouts are now available in Option 4.
Option 8 renamed to:Replace Stock (locked) ICS BootLoader with the New un-locked one to eliminate newbies’ confusion about its use.
TWRP Recovery images updated with TonyP’s latest v2.5.0.0. Thanks TonyP
New Option: A – Get useful Logs is now added in toolkit as requested by some of you. All commands described very nicely in TonyP’s thread are integrated in toolkit for quick use. Thank you TonyP.
Minor fix in backup/restore sd-card: When canceling it didn’t return correctly.
ADB tool updated to latest 1.0.31
V5.0: Date 08 Feb 2013:
Toolkit is now modular: It can support theoretically more LG devices with AddOn packages. An AddOn package for SU660 is already implemented.
Option: A – Prepare device for Dual-Boot is added to repartition the device for Dual-Boot support. Attention: DualBoot uses a spesific partition table, so if you are on dual-boot you cannot resize partitions because it will mess-up the device.
Changing recovery via adb now also works when device is into recovery (not only on normal operation) and gives the option to boot into the newly flashed recovery right after.
In option 8 is now clearly mentioned that it is not needed if option 4 has been used, It is needed only if the device is still on Stock locked bootloader. A lot of people still think that they have to use option 8 every time they change to ICS partition layout. Option 4 had always been flashing the un-locked ICS bootloader when changing to ICS partition.
After repartitioning the device enters recovery automatically when powered on. No need to keep pressing Vol- & Pwr.
For OLD BL only the extended (512MB system) partition table is included, to support up-coming new ROMs. If someone wants the stock 350MB he can always make one with PartitionResizer.
Only one of the latest v5, v6 & twrp v2.4 recovery versions is now included for each bootloader to reduce the package size. It will not remove the existing recoveries if extracted into the same folder. Remember that any other recovery image wanted can be added manually as always. (Thanks to Tonyp for his modified twrp v2.4 for the new bl)
Fixed: Extracting kdz under WinXP not working. It was due to different behavior of Microsoft expand.exe on WinXP than on Win7,8 (it doesn't accept wildcards as input file).
Toolkit now checks its write permissions in the folder extracted and gives a warning.
Updated IntSD-MountFix.zip & System-ReFormat-ext4.zip to work on both P990 and SU660 devices independently of the partition layout and bootloader.
SuperSU install zip updated to install latest v1.04 version.
V4.0: Date 05 Jan 2013:
Includes the fix for the options 1 & 5 not starting under certain circumstances.
Off-Line LG-Update Instructions now converted to html and will be opened on your default browser. (NO doc file, NO need to be associated to some application like office to open). It also has an info page of its own too.
More checking and error handling. Now checks (where possible) prerequisites and errors and gives possible reasons and solutions. It is important at least to prevent showing that an operation finished successfully while it didn't. I had to use other mechanisms to do that since some tools don’t return error codes.
KDZ extractor will stop if file is corrupted
BIN extractor will also check if images extracted successfully.
Off-Line LG Update will check if http.exe is not blocked by AV S/W and if the hosts file is modified successfully.
NVFlash Restore checks the sizes of current partitions and the backed up images and aborts restore if a partition is smaller than its image or warns if larger. It is needed because anyone now can resize the partitions easily with option 9. Note!! Smaller images can be restored to larger partitions but the final usable size will be the image’s one.
Completed instructions for flashing a recovery image via ADB successfully on CM10 ROMs too.
Minor changes in displayed messages.
V3.6: Date 01 Jan 2013:
Fixes the nvflash configuration file error: file not found In option 4, which happens if error occurs and user presses any key to retry.
V3.5: Date 30 Dec 2012
Option 1 changed to Backup/Restore options and now (additionally to SDCard backup/restore) includes NVFlash Backup/Restore of full ROM (boot, system, data), ROM only or Data only.
Option 2 changed to Change your Recovery Image and have two options (to select the method)
1 - Change Recovery via ADB (rooted devices only). It now works in CM ROMs too
2 - Change Recovery with NVFlash
The new versions of intSD-MountFix.zip and System-ReFormat-ext4.zip (already attached in OP) now included in toolkit
IntSD-MountFix.zip now works on both layouts and fixes SD only if needed to avoid formatting wrong partition when flashed by mistake.
System-ReFormat-ext4.zip now works on both layouts too.
More detailed information On-Screen for newbies by just pressing H when prompted.
ics-partitions.cfg file for nvflash has the ext3 FS-fix for the MSC partition (thanks pengus77 for your advice).
New ICS recovery 6.0.2.5 by pengus77 is now included. (Thanks pengus77).
Install APX Drivers now as new option (I) in main menu with on-screen instructions for win8 users. (In gray color cause it's an one time action and needed only if drivers are not already installed).
The AIO-Toolkit now zipped as self-extracted exe. It can be extracted over a previous version also, because now any un-needed previous files will be removed automatically. Also creates a shortcut in your desktop for quick access.
V3.0: Date 23 Dec 2012
A new tool “PartitionCustomizer.exe”added with option 9 to help you easily create a re-sized partition table to flash with option 4.
Windows 8 users won’t be asked anymore to install MS .Net Framework 3.5.
Toolkit now checks your windows version and uses system’s choice.exe in Vista,Win7& Win8. In WinXP systems it will use the alternate Choice.exe (under ToolKitFiles\tools, renamed to Choice4XP.exe.
CMxx_IntSD-Mount-Fix_AfterRepartitioning.zip added in CWM folder. Install this in recovery mode after repartitioning and installing a CMxx based ROM.
Install-APX-Drivers.cmd script is added in ToolKitFiles\nvflash\driver. It installs APX drivers without having to plug the phone first (in nvflash mode pressing vol- & vol+)
All instructions and help of OP now Included in pack as a pdf document for quick help. I will keep working on it to make it a full manual and guide.
V2.0: Date 16 Dec 2012
Two more options added.
SmartFlash a Stock ROM and/or Baseband (Completing this way the toolkit’s name “All-In-One”)
Flash New Un-Locked ICS Bootloader.
Added more safeties (like automatic detection of partition layout) and warnings to prevent wrong choices.
Added a cwm-flashable SuperSU-v0.99.zip inSU folder also for those who prefer it instead of SuperUser. Every zip can be flashed over an already installed SU or SuperSU. Removes previous occurrences of these.
Added two flashable zips in CWM folder for re-formating system partition in ext4 in case nandroid restore fails after repartioning.
Simplified/shorter instructions for the automatic off-line LG Update Tool
2nd minor fix in BIN extractor occurring sometimes when drag/drop a folder or file. Thanks to SuperSkill for discovering the bug.
Bugfix of not backing-up files with no extension from internal SD-card.
DPInst32.exe& DPInst64.exe files have been added under ToolKitFiles\nvflash\driver. Run one depending on your windows platform (x86, x64) to install APX drivers easier if needed.
An extra Addon pack available for fixing the not mounting interal sd-card bug in CMxx ROMs.
V1.1: Date 2 Dec 2012 Fixes a weird bug in BIN Extractor, when the full pathname of the BIN file contains parenthesis ( ) either in a parent folder or the name itself.
V1.0: Date 29 Nov 2012 First version uploaded.
Credits
rmein & Stefan for the idea and parts of their scripts I integrate
wkpark for the modified cwm v5.0.2.8e the BIN extractor and of course for Unlocking the ICS Bootloader, Big thanks to him. Without him we would have no ICS development.
Tonyp For: baseband instructions, his modified twrp recovery for new BL and adb commands for getting logs.
pengus77 for his custom v6.0.2.5 cwm image
Rusty! for cwm 5.0.2.8 (internal – external)
Stefan again for modified v6.0.1.5 cwm image
homero2 for part of his script in bin extractor.
unknown_world for his original instructions how to officially update in off-line mode.
ProgMaq: For his Full Brick Repair tool that helped with CMxx mount bug.
jes0411 for his original script for P970 to extract KDZ files.
navossoc and XDA team for creating LGExtract tool
thomas_polaert for his colorizing echo (cecho.exe)General Info: How to install unsigned drivers in Windows 8.
For APX Drivers needed for NVFlash operations, use Option I.
For any other unsigned drivers needed, this is the way to install them:
Move your mouse to Right down Corner.
Click Settings (gear icon)
Click Change PC Settings
Click General (On right panel of the screen) under Advanced startup
Click Restart now
OR
Easiest way for the above: Hit WinKey + R, type in the following command and hit enter:
shutdown -o -r -t 0
--------------------
Wait for next menu..
Click Troubleshoot.
Click Advanced Options
Click Startup Settings
Click Restart.
Wait to reboot. It will come back with boot menu with many options
Press the number of the Disable driver signature enforcement
Windows will boot normally.Now install the drivers you want.
Note:After your next reboot the enforcement gets enabled again.
thanks for sharing
Oh nice. thats hell lot of options. will try sometimes this weekend. Thanks a lot for your work. P990 is unbrickable phone and many nvflash builds available, so not afraid of trying anything these days. lolz.
Thank You! This toolkit is very useful! From new ics layout back to GB layout smartflashing 28G baseband was easy!
Thanks...
Looks to be very promising, Thanks, will try it.
Nice work indeed!
I love the fact that there's still fresh development on this old phone
But I don't think I should appear in the credits for providing CWM 6.0.1.5 touch.
I just dowloaded the official build from here: http://www.clockworkmod.com/rommanager
For removing me you could highlight wkpark a little more, especially for cracking the new bootloader.
Without him there wouldn't be any CWM with the new bootloader.
What was the data size? 1.5GB? Can u make a size of 744 for the system? Tks alots....
tonyp said:
Nice work indeed!
I love the fact that there's still fresh development on this old phone
But I don't think I should appear in the credits for providing CWM 6.0.1.5 touch.
I just dowloaded the official build from here: http://www.clockworkmod.com/rommanager
For removing me you could highlight wkpark a little more, especially for cracking the new bootloader.
Without him there wouldn't be any CWM with the new bootloader.
Click to expand...
Click to collapse
Thank you,
You are right about wkpark and the bootloader I forgot the new bootloader completely.
I will correct it.
@wkpark sorry,
cmahendra said:
Oh nice. thats hell lot of options. will try sometimes this weekend. Thanks a lot for your work. P990 is unbrickable phone and many nvflash builds available, so not afraid of trying anything these days. lolz.
Click to expand...
Click to collapse
Glad you found this to be true in your case Been struggling with a bricked P990 for a few days now that errs out when nvflash tries to flash a new bootloader. Will definitely try this tool when I get home tonight and see what I find. Crossing my fingers here
[EDIT] No dice. Still bricked. Happy for any input here; I'm clueless at this point. Seems I've tried everything the internet can suggest. Can't even read the partition table from my phone; can't download bootloader; always errors. Full info at http://forum.xda-developers.com/showpost.php?p=34754117&postcount=38 [/EDIT]
orbital_71 said:
What was the data size? 1.5GB? Can u make a size of 744 for the system? Tks alots....
Click to expand...
Click to collapse
Noted.
Maybe in next version I will include different system sizes for the user to select.
But for now you can always edit the .cfg file (gb-large.cfg or ics-partitions.cfg) under ToolKitFiles\nvflash folder.
Search for the partition named APP and change its size to 780140544 (744*1024*1024).
Note: This is enough for old layout (gb-large.cfg). For ICS one (ICS-partition.cfg) since all partitions are sized (in contrary with OLD layout that UDB partition is set to 0xFFFFFFFFFFFFFFFF which means all the rest) you have to reduce UDB size (internal SD) by the additional size you added in APP partition.
So for this example you have to reduce UDB by (744-512)*1024*1024 = 243269632.
Have in mind that you are not gonna have this system size available if you flash one of the current ICS NVFlash ROMs because their system.img is 512MB.
The whole 744 size will be avalable only with ROMS that are flashed with CWM zips, which don't have a system.img inside but a system folder.
OR
After you flash an nvflash ROM make a nandroid backup, resize the partitions and restore the backup (I haven't tried it but it should work)
can you add the bootloader install?! old and ne, may be useful after flash ics via smart flash ie
solrakk6 said:
can you add the bootloader install?! old and ne, may be useful after flash ics via smart flash ie
Click to expand...
Click to collapse
I am not sure I understood.
Which new and old? You mean the GB and the ICS one or the ICS locked and unlocked one?
The new unlocked one is usefull in case you want to be able to boot in a cwm recovery and it is flashed in rooting option along with the recovery of your choice.
What would be the reason to flash only the bootloader.
Great tool, but is it only me who can't extract the bin file? Thanks
Sent from the new smoothly LGP990
I just uploaded an update v.1.1
It fixes a weird bug in BIN Extractor that it's not working, when the full pathname of the BIN file contains parenthesis ( ) either in a parent folder or the name itself.
If you already have downloaded the v1.0 just download the updated-script attached in post.
EDIT: It is a batch scripting bug.
I had used conditional “IF something DO (….) ELSE (….)” in BIN extracting script, to extract all partitions or just one. A BIN file’s pathname with parenthesis breaked the IF ELSE condition. Batch just s***ks
spyrosk said:
I just uploaded an update v.1.1
It fixes a weird bug in BIN Extractor that it's not working, when the full pathname of the BIN file contains parenthesis ( ) either in a parent folder or the name itself.
If you already have downloaded the v1.0 just download the updated-script attached in post.
Click to expand...
Click to collapse
I got it working last night, so this is my reply, I got another output on the bin file
Thanks for updating
Sent from the new smoothly LGP990
Internal SD
Hey, I really like your ToolKit. I've been messing around with it, but I have one problem (not sure whether it lies in your ToolKit or me being stupid). After I flashed to a rooted ICS leak a few days ago, I wanted to revert back to CM10 (to check out the in-call-bug fix). Now, it seemed to me that your toolkit would come in handy to revert back to the old bootloader and partition layout. At first i was messing around with CWM: I couldn't mount my SD to flash a CM.zip. It seems that only the older CWM version (1st option in your menu) lets me mount the SD. Ok, so I was able to mount my micro-SD again and I flashed the rom, gapps and the fix. After booting, my phone didnt recognize my internal nor external SD; after connecting to USB, my computer only showed my micro-SD, but when I entered it, it seemed empty. The internal storage isn't recognized by my computer at all. I tried some other tools to flash a few different roms but I ended up reverting back to the ICS-leak I was using in the first place: then both the internal and external storage were recognized again (with no loss of data on the micro-sd).
Well, I'm no developer at all but I read some things about formatting the internal storage; could it be that, after repartitioning, your tool doesn't format my internal storage partition and that this causes mounting problems? I tried formatting it manually through ADB, but it didn't work (probably because my ADB/linux s*ck).
Maybe you have any idea to help me out here Thanks in advance
Thank you for this great tool!
ValentineCrow said:
Hey, I really like your ToolKit. I've been messing around with it, but I have one problem (not sure whether it lies in your ToolKit or me being stupid). After I flashed to a rooted ICS leak a few days ago, I wanted to revert back to CM10 (to check out the in-call-bug fix). Now, it seemed to me that your toolkit would come in handy to revert back to the old bootloader and partition layout. At first i was messing around with CWM: I couldn't mount my SD to flash a CM.zip. It seems that only the older CWM version (1st option in your menu) lets me mount the SD. Ok, so I was able to mount my micro-SD again and I flashed the rom, gapps and the fix. After booting, my phone didnt recognize my internal nor external SD; after connecting to USB, my computer only showed my micro-SD, but when I entered it, it seemed empty. The internal storage isn't recognized by my computer at all. I tried some other tools to flash a few different roms but I ended up reverting back to the ICS-leak I was using in the first place: then both the internal and external storage were recognized again (with no loss of data on the micro-sd).
Well, I'm no developer at all but I read some things about formatting the internal storage; could it be that, after repartitioning, your tool doesn't format my internal storage partition and that this causes mounting problems? I tried formatting it manually through ADB, but it didn't work (probably because my ADB/linux s*ck).
Maybe you have any idea to help me out here Thanks in advance
Click to expand...
Click to collapse
your tool doesn't format my internal storage partition and that this causes mounting problems?
Click to expand...
Click to collapse
Repartitoning uses nvflash to recreate all partitions again and nvflash wipes all partitions including internal SD for sure.
At first i was messing around with CWM: I couldn't mount my SD to flash a CM.zip. It seems that only the older CWM version (1st option in your menu) lets me mount the SD
Click to expand...
Click to collapse
where your CM.zip was? In external or Internal SD? 1st option should be the cwm-5.0.2.8-ext.img. That recovery mounts the external SD by default.
Could you give me more details of what exactly you did step by step? Somewhere I lost you.
1) you repartioned to old layout
2) which cwm did you choose?
3) Your CM.zip should be in your external SD because internal would be wiped.
I would also suggest that if you have a nandroid backup of a previous CM ROM try to restore it first, make sure that everything is working as it should and then flash the newer CM you want. Maybe the problem with SD cards is in the ROM you are trying to flash.
Please let me know
can i root the 30A with the root toolkit option??!
---------- Post added at 08:45 PM ---------- Previous post was at 08:28 PM ----------
spyrosk said:
I am not sure I understood.
Which new and old? You mean the GB and the ICS one or the ICS locked and unlocked one?
The new unlocked one is usefull in case you want to be able to boot in a cwm recovery and it is flashed in rooting option along with the recovery of your choice.
What would be the reason to flash only the bootloader.
Click to expand...
Click to collapse
exactly
solrakk6 said:
can i root the 30A with the root toolkit option??!
---------- Post added at 08:45 PM ---------- Previous post was at 08:28 PM ----------
exactly
Click to expand...
Click to collapse
I tested it with V28G and it worked. It should work with 30A also
Hello guys, just sharing my first porting work to u all
Please read this post from first to the end of this post
"Please respect to my work,
I'm doing this fix all alone by
giving up my rest time, quota (since i didnt have wifi), etc..
so dont complain if u find any bugs, or
a lil bit hassle to install it.
if u find any, just report it to me
if it's possible to fix,
i will try to make a patch / troubleshoot updates."
Click to expand...
Click to collapse
NOTE : DO THIS AT YOUR OWN RISK
Changelogs :
ROM :
#> BETA 2 - 20151213
- Fixed META-INF problem, can flash using any recovery now except stock
- Fixed Completely selinux problem
- Fixed Camera and screen issues on other A1 devices (ex Mito Impact a10)
- Fixed Flashlight
- Fixed Bootloop at first time install (dont need to wipe dalvik again)
- Fixed Offline charging
- New kernel and ramdisk
- some other patches and minor fix
#> BETA 1 - 20151211
- Fixed RIL (only single sim for now)
- Fixed Launcher icons
- Fixed Dialer and Contacts FC
- Fixed Change wallpaper FC
- Fixed some layout
- Fixed MTP
- Fixed Themes FC
- some minor fix and patches
#> DevBuild 1 (Tester Only)
- Initial Release
- All Devices standard features working except (for now) :
RIL (SIM Network/Data Cellular)
- Some of apps fc
Click to expand...
Click to collapse
PATCH :
#> Patch for BETA 2 - 20151220
Fix LED notification
New sqlite_jni [test] : tell if u got any huge sqlite problem in the {logcat} than before patch
Fix weather app
#> Patch for BETA 1 - 20151211
Patched services.jar to disable apps verify
DownloadProvider fix
Click to expand...
Click to collapse
Bugs :
- DUALSIM
- Launcher 4x5 layout bug (use another launcher if u want)
- Google play services sometimes fc. Due to unexpected sqlite problem sometime
- Media stopped working after 5-10 seconds gplay services fc so cant take screenshot and gallery become empty, and in some cases taking screenshot while opening screenshot folder using miuigallery (u need to reboot the phone or wait approx 10-30min)
- Font changing in theme app only works for miui's default browser
- tell me other
Click to expand...
Click to collapse
Download links :
ROMs :
MIUI6_20151213_BETA 2
MIUI6_20151211_BETA 1
GApps :
GApps_miui6_optimized_edition
Patchs :
BETA 2 :
miui6_patch_beta2_20151220
BETA 1 :
miui6_patch_20151211
BOOTLOOP PATCH : miui6_patch_after_flash
BOOTLOOP PATCH : miui6_patch_after_boot
Installation Procedure :
1. Go to recovery
2. Wipe data, cache, system
3. Flash the rom
4. Flash miui gapps
5. Flash the patch (if any)
6. Reboot.
If u are updating from BETA 1 to BETA 2, i recommend to do a wipe data or clean flash to avoid some unexpected issues
BETA 1 Notes :
For you who gettings bootloop at last time, try this :
1. Download these two bootloop patch
2. Rewipe your phone (data,cache,system)
3. Flash the rom, then flash gapps, after that reboot to recovery mode
4. Flash the miui6_patch_after_flash
5. Reboot. Wait till its booting to homescreen (approx 6-10mins)
6. After finishing the setupwizard, go back to recovery
7. Flash the miui6_patch_after_boot
8. Reboot. And ur done
After booting and finishing the setup wizard (and done flashing the bootloop patch if u got bootloop), set selinux to permissive, set using kernel adiutor (go to plugins, download selinux plugin, set to permissive), enable apply on boot
After booting to homescreen u can reput your 2nd card now. but remember its will still didnt detect your 2nd card
Troubleshoot :
1. How to enable root access?
- Open security app, choose permissions, root access .. there u go (make sure ur root apps already asked for root first to show it on there)
2. How to disable warn when want to install app?
- Open Privacy, choose device administration, change in unknown sources from ask to allow
3. How to make my phone mtp detected?
- Unplug ur usb, open miui default file explorer, select phone, wait till its complete loading, then connect ur usb
4. Google apps or keyboard is force closing how to fix?
- Use my miui6_gapps
5. Titaniumbackup is restarting after grant root access, how to fix?
- Update your current tb to version 7.2.1.2 or latest
6. Cant install apps from PS, says no free storage, how to fix?
- Flash the download provider fix
7. Cant install apps from my sdcard, says no free storage, then after i try it its says install failed
- Set your phone selinux to permissive, then use root ex delete the package folder in data/data .. ex Im failed to install bbm, delete the com.bbm folder
8. Cant import theme from sdcard, what to do?
- The new MIUI at default doesnt allow you to apply theme which not from their store, but try other theme, theres some of theme still can be imported
9. Issues with downloading, how to fix?
- Turn off the xunlei download engine at download - settings, also set the limit to unlimited
10. Navbar is too small, how to fix?
- If u want alternative, use MiPop 2.0 .. im reduced its size due to fix some of layout bugs. To remove the navbar add "qemu.hw.mainkeys=1" without " in the bottom of the build.prop then push Mipop.apk to system/priv-app
11. How to show messenger chat heads?
- Download app-ops app from playstore, install then reboot, after that search for messenger permission, enable the draw over blabla permission : thanks to Kishan Kumar for the guide
How to Install Video Review, thanks to Sounak Pal :
Here
To appreciate my hard works, you can consider giving me some donations by :
Giving some steam wallets : nteztaz
or if u at Indonesian country, u can send me some credit balance to buy quota,
msg me for my call number
Credits :
[email protected] for the rom base
Yusuf Maulana for the idea of porting from 'based cm11'
Sounak Pal for the video review
All my Tester
All Android One users
Me (TezTaz Si Rama)
A huge thanks for this Rom was waiting for different ui.
It would be great if u will provide some screen shots
Screenshots
I havent found any fc
Hoping that the sim bug will be fixed soon
I dont mind using the Single SIM as I use it for single sim most of the time. Thank you for sharing it here. I'm downloading it now.
an awesome rom
This is the best rom I have ever used on my Sparkle V. Very smooth ,
but I found a bug - while backing up data on local storage the phone hangs and reboots itself in a minute, but that's not a major issue.:good:
guys, I tried flashing, but failed. ,
- first I tried wipe everything, and then flash. But flash or rom failed, giving sole softlink issue. I tried multiple times, but failed. Finally, fixed issue by having another 4.4.4 rom installed first and then flashing this rom without wiping system
- once flash was successful, I rebooted device, but it keeps looping wihout booting up. OP suggested multiple iterations of (battery remove, goto recovery, wipe dalvik, boot) , but I am in my 7th attempt and device not booting still.
How many times you guys had to wipe dalvik? Very much anxious to test this MIUI rom !
Flash why philz
Do not flash gapps it was bootlooping
yadavdharmendar said:
Flash why philz
Do not flash gapps it was bootlooping
Click to expand...
Click to collapse
thanks @yadavdharmendar, I am installing from philz, and I avoided installing gaps as well. Still not luck. I get Simlink error.
I am coming from FIUI rom. Not sure if that matters (as anyway I am wiping everything before starting rom flashing).
I was on Fiui too
Then i flash cm11 ,then miui
yadavdharmendar said:
I was on Fiui too
Then i flash cm11 ,then miui
Click to expand...
Click to collapse
thanks! But why you installed CM11 first before installing Miui. OP didn't asked for it. Just curious to know!
And where you got CM11 from? From Cyanogenmod download page for "sprout"?
mobilepgk said:
guys, I tried flashing, but failed. ,
- first I tried wipe everything, and then flash. But flash or rom failed, giving sole softlink issue. I tried multiple times, but failed. Finally, fixed issue by having another 4.4.4 rom installed first and then flashing this rom without wiping system
- once flash was successful, I rebooted device, but it keeps looping wihout booting up. OP suggested multiple iterations of (battery remove, goto recovery, wipe dalvik, boot) , but I am in my 7th attempt and device not booting still.
How many times you guys had to wipe dalvik? Very much anxious to test this MIUI rom !
Click to expand...
Click to collapse
Its not davlick issue it's just meta inf folder bug
Just open ROM zip and delete meta inf folder and replace it from any downloaded sprout ROM zip just copy meta inf folder frm there and paste it in miui ROM n u r done just do a clean install n w8 for 5 mins
teztaz--v3 said:
Hello guys, just sharing my porting work to u all
"Please respect to my work,
I'm doing this fix all alone,
so dont complain if u find any bugs,
if u find any, just report it to me
if it's possible to fix,
i will make a patch updates."
Changelogs :
Bugs :
Download links :
ROMs :
Here
MIUI GAPPS :
soon
Patchs for Download Provider :
Here
Installation Procedure :
1. Remove your 2nd sim card, then go to philz recovery or LATEST (2.8.7.x) TWRP recovery (darkplay)
2. Wipe data, cache, system (or just use the 'clean to install rom' function)
3. Flash the rom
4. Flash miui gapps
5. Flash patch
6. Reboot, wait till 6 mins, pull your phone battery, then goto recovery and wipe dalvik cache, then reboot*
7. After booting and finishing the setup wizard, set selinux to permissive, set using kernel adiutor, enable apply on boot
*do it again until the progress bar bottom of the screen showing
Troubleshoot :
1. How to enable root access?
- Open security app, choose permissions, root access .. there u go (make sure ur root apps already asked for root first to show it on there)
2. How to disable warn when want to install app?
- Open Privacy, choose device administration, change in unknown sources from ask to allow
3. How to make my phone mtp detected?
- Unplug ur usb, open miui default file explorer, select phone, wait till its complete loading, then connect ur usb
4. Google apps or keyboard is force closing how to fix?
- Change your gapps, use pico/nano gapps for now
5. Titaniumbackup is restarting after grant root access, how to fix?
- Update your current tb to version 7.2.1.2 or latest
6. Cant install apps from PS, says no free storage, how to fix?
- Flash the download provider fix
7. Cant install apps from my sdcard, says no free storage
- Wipe data your phone, reflash again, after boot set selinux to permissive
Credits :
[email protected] for the rom base
Yusuf Maulana for the idea of porting from 'based cm11'
All my Tester
All Android One users
Me (TezTaz Si Rama)
Click to expand...
Click to collapse
not downloading rgt now....will instead wait for another a bit stable build...a salute to your work...hope ur working on fixes...already pressed thanx button...keep going boy...
Thanks all. Installed cm11, then installed ROM with the patch, and avoided flashing any gapps. It worked! Just one bootloop, which went away after wiping dalvik.
Thanked OP!!
BTW, any ways to make the navigation buttons look big. And possibly increase bar height?
about 2nd sim
bro plz plz get 2nd sim working.
thanks for your work and you are awesome.
@teztaz--v3
how to make navigation bar transparent ?
and a big thanks for your beautiful awesome work
no FCs seen so far!! Looks perfectly usable as daily rom.
Just one problem seen :
Can not install Google maps. Says insufficient space, which is strange. Also failed to install Link2SD. Tried even installing from ADB, gave error INSTALL_FAILED_UID_CHANGED. Hope Miui is not blocking it.
Every thing is fine bro its super rom but I can't move apps to SD card
Thanks bro! gr8 work! bt can u make e single zip with all fixes? people will get confused with so many patches
nsytechno96 said:
bro plz plz get 2nd sim working.
thanks for your work and you are awesome.
Click to expand...
Click to collapse
B'coz this ROM is based on CM11, it's impossible to get multi sim working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huawei P8 Custom ROM
* MagicArrow *
Version Two
Magisk Edition and Classic Edition
Teamwork by Tecalote and KangV
Based on the European firmware b398 - only installable, if you are already on Marshmallow Firmware (Android 6)
Developed on GRA-L09 C432 - but it should run on all GRA-xxx models and regions due to my modification
Thread for German Users: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8.2257/huawei-p8-rom-6-0-emui-4-0-3-magicarrow-v2-by-tecalote.819399.html
Well, you've been waiting long enough I am pleased to present you the new version of Arrow under the extended name "MagicArrow"
1) Difference between Magisk and Classic Edition:
The Magisk Edition was made to have a safteynet capable device that still offers much more features than Stock Firmware ... It has the same features like Classic Edition, with one difference: Outward It looks as if you had not unlocked the bootloader .... Apps like Pokemon Go, various banking apps - which does not work anymore on rooted devices should work in this Rom
However, you can not install Xposed Framework in the Magisk Edition without losing the green safetynet! There is the systemless Xposed Framework by topjohnwu, the developer of Magisk and it works, can be easily downloaded and installed in the Magisk Manager via modules (SDK 23) - but - there is currently no way to pass safetynet with a modified custom Rom together with Xposed Framework! For this reason, the installation pool in K-Settings for Xposed is removed from its function.
Attention: Update the preinstalled Magisk with newer Version 15.3 flashable zip made for this ROM: https://forum.xda-developers.com/showpost.php?p=75178940&postcount=871
Then look in the Thread for new posts about future Updates.
The Classic Editon is rooted with SuperSU and has same features, but you cannot bypass safteynet check. However, who does not run apps depending on this "questionable" service will have the same joy with this Rom. The advantage of the Classic Edition is: You can install from K-Settings Wanams Xposed Framework 87.1 and use a lot of Xposed modules ...
2) Requirements and information for this Rom:
If you want to have the best of this Rom, then it would be necessary to start completely clean - means from Custom Rom back to Stock Firmware b398 - With the exception of devices for which there is no more recent firmware than b370. An EMUI Custom Rom is as good as the before installed Firmware in the background. In principle, only system, cust and kernel will be flashed with the Rom zip. The original Firmware update a lot more, like modem etc. Therefore, the Custom Rom works best if you start from latest firmware for your device on which the Rom is based.
If you have already latest official Huawei Stock Firmware installed, it is less work...
I really dont recommend to flash dirty this Rom directly from Arrow v1 or if you stay on older Firmware. System and Apps will be wiped with the installation script. So you cannot keep your previous apps and data, you have to install them new.
You need the latest TWRP:https://dl.twrp.me/grace/twrp-3.1.1-0-grace.img Do not use older ones!
The bootloader must be unlocked. Pick up the Huawei unlock code, because it is always valid for the same device. If you do not have an unlock code from Huawei and have problems to get it from Huawei Website, recently you can call regional Huawei service hotline and get the code by mail during 24 hours.
3) Installation guide for the MagicArrow:
1) Backup your apps and data from your current Firmware or Rom - but only User-Apps and not System-Apps. You can use Huawei Backup as well as TitaniumBackup. (Dont restore any System-Apps from previous system in the new Rom - example: if you use Huawei Backup dont backup Phonemanager, but you can backup desktop layout, sms, calendar, User-Apps etc.) Dont backup and restore Chat-Apps like WhatsApp, Viber, WeChat, Facebook and so on - use their inbuilt Backup Function like Google Drive Backup (its different, some Apps are storing everything on their server like Telegram) You must install and register Chat-Apps new on your new Rom. If you dont do that, Push-Notifications cannot work.
2) Make a backup of important folders and files from your internal storage (DCIM, WhatsApp folder, Downloads....)
3) Download Firmware update.zip - depending on the device model - and unzipp it on your PC - you receive META-INF and UPDATE.APP
GRA-L09C432B398: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v88316/f1/full/update.zip
GRA-L09 with other Cust: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=GRA-L09&firmware_page=0
Other GRA models: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=GRA&firmware_page=0
4) Copy UPDATE.APP and META-INF into a folder on the root directory of your external SD which must have the name: dload
5) If you are on Stock Firmware, not rooted you can directly update your Firmware. But go to step 6
A) If you are on Stock Firmware, but rooted, with TWRP installed and Xposed Framework installed, uninstall first Xposed Framework, reboot to system, after unroot your device, restore original boot.img and flash the original Huawei Stock Recovery.
B) Arrow Editions: If you have Xposed Framework installed, uninstall Xposed Framework, reboot to system (15 min) - after go to step 6
If you are on Arrow v1 Classic Edition without Xposed Framework, flash Huawei Stock Recovery from K-Settings /more settings / flash recovery - flash official recovery. You can reboot directly from here to Stock Recovery.
If you are on Arrow v1 Magisk Edition without Xposed Framework, flash with TWRP Magisk Uninstaller: http://tiny.cc/latestuninstaller and after flash Huawei Stock Recovery b391 (by choosing img): https://www.androidfilehost.com/?fid=529152257862705190
- go to step 6
6) Press Vol+ and Power Button until phone reboot and hold this position until phone boot up to Stock-Recovery. Here you do first "Wipe Cache Partition" and second "Factoryreset" - go to step 7
7) If you start EMUI Update from here, just go to Restart and press Vol+ and Vol- (in the middle down and hold this position), wait until phone reboots and EMUI Software Installing begin (of course, update.app and meta-inf must be already in dload folder)
If you was back in system between you can start update with pressing down Vol+ and Vol- in the middle and at the same time pressing Power Button. Wait until phone reboot and you see Huawei Logo. Now you can release Power button, but you must keep holding all the time the pressing down postion with Vol+ and Vol- until EMUI Software Installing begin. After some time your firmware is updated and restart to system. Dont make an account yet, just make short setup.
8) Open settings /about phone and klick 7 times on build number for enabling developer options. Open developer options and in there enable USB Debugging. After go to settings / (advanced) settings and enable "unknown sources"
9) Connect your device with USB to your PC and let windows install the drivers or install HiSuite (which installs drivers if windows cannot recognice) You need the USB Connection. With Minimal ADB and Fastboot in administrative mode you can flash now the newest TWRP, which I have linked above.
10) Disconnect your device from USB Cable, soon TWRP is succesful flashed
11) With Vol+ and Power Button reboot your device to TWRP - this step is important if you want to keep TWRP
12) Allow system modification and go to ADVANCED WIPE - choose in the first step ONLY internal Storage (nothing else). Do not wipe internal Storage together with the other partitions in step 14! Soon internal storage is wiped, go back to main menu and restart the recovery. You should get the Root Permission request from TWRP "Allow system modification" once again, allow it and open settings to configure (24h clock, language, time zone, etc) If you dont get the Root Permission request from TWRP yet, you will get it after next boot to TWRP.
13) Now copy MagicArrow.zip to your external SD - Attention: If you want the boot sound to be played on the phone - before flashing the Rom, sound must be switched on!
14) Boot to TWRP and go to ADVANCED WIPE - Wipe following partitions:
Dalvik/Art Cache
Cache
Cust
data
system
15) Go back to main menu and flash MagicArrow. After flashing is done, reboot system without wipe of dalvik/cache. As you know, the first boot process can take up to 15 minutes (just like installing the Xposed Framwork)] After boot to system and first setup - you have to make some IMPORTANT STEPS (see next Point) before you restore /installing your apps and adjust your phone.
4) Important information for the Magisk -Edition:
During first setup you may receive a root-rights request, if so, confirm this. After first setup - please do not open the Magisk Manager . Before you do anything else,open settings / about phone and klick 7 times on build number to enable the developer options. Open developer options and in there enable USB debugging! Then go back to Settings - in the b398 there are the extended settings with the short name: Settings. In it, please enable " allow unknown sources "
At this point restart immediately your P8.
Now open the Magisk Manager, the app is looking for updates - to speed this up, drag from first white field (like refresh of a website in Chrome) with the finger pressed down - the manager is up to date. Makes a query of the Safteynet = green.
Then you go in the Magisk-Manager left to the Controll-Pannel to settings. Do not change anything, with one exception: enable systemless hosts! This step is very important. Then immediately the second reboot .
Next open AdAway and activate the hosts file (download files and activate the advertising block) - then the third reboot .
After open AdAway again and see if the hosts file is active, if it is, all well, if not, download the hosts files once again and restart P8. (Sometimes another reboot is necessary at the point) Only when AdAway is green (activated) - then the safetynet is passed by. You can now again check in the Magisk manager safetynet = green - if you do not these steps, you can break the safetynet. In addition, root and apps can be blocked!
As you know, Magisk uses his own superuser, integrated into Magisk Manager
For some reason if you have problems with safetynet with some apps, just download the following module in the Magisk Manager in the Control-Pannel under Download:
Universal Safetynet Fix
Otherwise, please do not download any modules, you do not know if they run and what they do.
Two modules are preinstalled - please leave this, otherwise this Rom does not function properly with K-Settings!
5) Important information for the Classic -Editon:
The Classic edition gets systemless Root during the installation by SuperSU 2.82 SR1 (SR1 has an integrated update for Huawei devices). After Rom is flashed and you restart phone, the first boot process will terminate, the device will restart once again - this is normal because of systemless rooting . Why systemless this time? Because of compatibility with SuperSU. The new versions of SuperSU are rooting always systemless. If there is the next Final version of SuperSU, you need only flash the zip in TWRP and there are no problems with the update.
To enable AdAway , just download the AdAway ad block (hosts file) and reboot the P8 - but after rebooting, please open AdAway again and see if it worked the first time - otherwise just download again and restart the device once more. The second time it fits. AdAway is controlled by the systemless root using an init.d script that mount the hosts file systemlessly and this script is usually only active after the second restart. If you ignore this step, you can block root privileges.
6) Features:
• VoLTE and IP-Calling enabled - disable it, if your mobile provider dont support it!
• Push notifications working - Enable WhatsApp, Telegram... as protected apps and enable Wlan and mobile data during "sleeping mode" as always on
• Most Gapps contained in system debloaded - please dont flash any GApps, just install it with Playstore (Core GApps and settings are present in the Rom)
• System is deodexed
• pre-rooted: Classic Edition by Chainfires SuperSU 2.82 SR1 - Magisk Edition by topjohnwuMagiskSU 13.3
• BusyBox 1.27.1 - Please dont change this BusyBox to any other (not Stericson, not JRummy...)
• Call Recorder - You can enable recording manually, if a call comes through with the memory icon in dialer - or constantly in dialer settings
• Some nice themes, BlackPyramid ...
• K-Settings - as usual with extended restart menu
• MiXplorer (very powerful Root-Explorer) and TitaniumBackup (can store backups without any problem through storage SD instead of document provider)
• Dolby / Atmos for Teamwork with Viper4Android - best experience with BlackPlayer (or similar) but not Huawei Music App
• Security patch level 1 July 2017 - all known Stagefright Security holes are closed
• Multiwindow mode - you can start this mode with long tap on square in navigation bar. Close the Mod in the middle with the turquoise symbol.
• Viper4Android (enable it via K-Settings) can be linked to its settings permanently in notification bar for quick access. - as usual.
• Xposed Framework of Wanam included in K-Settings, Installation start from there, reboots automatically. The Restart needs about 15 minutes.
• VIA Browser instead of Chrome
• AdAway - newest release
• And much more...
7) Phone Manager and the app PMPlus:
Phone Manager does not include the Autostart Manager in European Firmware. The advantage is: you do not have to worry about anything, everything is controlled automatically - and also works. But the battery consumption is slightly more, since all apps wait in the background to be called.
With the app PMPlus, you can activate the Autostart Manager in the Phone Manager. To do this, start the app, go to Installation and as soon as the succesful message comes, close the app (can be uninstalled thereafter). Now, on screen two of the Phone Manager, the entry "App auto-launch" appears!
But NOTICE - through this upgrade will initially set ALL Autostarts to 0 ! You must manually enable the most important apps in App auto-launch - all apps that should receive push notifications - and, most importantly, SuperSU in the Classic Edition and Magisk Manager in the Magisk edition. Otherwise Root permissions do not work!
Advantage: You have control over which apps should not start at system start or in the background (if you need it rarely)
But you must always remember to activate a newly installed app there if necessary. Example: Amazon, E-Bay, PayPal - some of these apps are coupled and not only need the autostart to work , but also the so-called " app activation " (which appears in Autostart Manager when such apps are installed)
Disadvantage: If the apps are not configured correctly in the mask, you have more trouble than good. So, if you're not control freaks, then let's keep your fingers out of it.
But if you want to activate this function, it is recommended to do it at the end, if you have already installed all the apps you are using and not before!
8) Disable Chinese Letters:
The Rom is European, but the K-Settings are from KangV. Thats why the Lunar component is installed in K-Settings (these are the only Chinese letters in this Rom).
To hide these, go to K-Settings:
1) Lockscreen and desktop settings and disable: "Lunar Calendar" and at "Desktop weather lunar"
2) Notification settings - disable: "Show statusbar lunar"
9) Save Battery:
NFC (with Android Pay) ist enabled by default - disable it and enable it only for the time you need it
VoLTE is enabled by default - disable it, if your mobile provider dont support it
Location Settings (menu: scan settings) disable WLan and Bluetooth Search while Wlan and Bluetooth is disabled, Navi Apps are working also without this setting.
Performance is enabled by default - change this in Akku-Manager (part of Phone Manager) to SMART
With "auto app-launch" (if you have installed) you can disable Apps which you use just sometimes.
Bluetooth enable it - if you use it and disable it - if you dont need it at the moment
9) Download MagicArrow:
MagicArrow Classic Edition: https://www.androidfilehost.com/?fid=889764386195920974
MD5: 5ee32443300f10dcbced4808101aff42
MagicArrow Magisk Edition: https://www.androidfilehost.com/?fid=673368273298976764
MD5: 7afa8619778a81a11a60665f27b2289f
Magisk-Update to 15.3 - use only this zip from this post please: https://forum.xda-developers.com/showpost.php?p=75178940&postcount=871
Please check the MD5 after the download! Because if the download / the zip is faulty - then you have problems after the flash!
And please keep to my instructions - then everything is as it should be
Have much fun with this ROM
Many thanks to KangV for his K-Settings Framework
If you like K-Settings - fell free to donate KangV: https://www.paypal.me/KangVIP
If you like MagicArrow, I am happy about some beer: https://www.paypal.me/Tecalote
Many thanks and credits to other great Developers:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@dkionline - Custom Roms for P9
@Blackball - BlackPyramid Theme and Custom Roms for P8 - P9 - P10
Last Thread Update: 03.01.2018
Right settings for Push Notifications and install manual for Stock Firmware Update
Right Settings to make Push-Notification work for Chat-Apps like WhatsApp:
Settings with Phone Manager:
1) Once you have installed with PMPlus the Autostart-Manager called: App auto-launch as a part of Phone Manager- WhatsApp, Viber and all those apps must be activated!
2) Activate these applications also in Protected apps
3) In Notification center activate for these applications - Priority display, Status bar, Banners and Lock screen
4) If these apps are available in Dropzone management - activate them
5) In Phone Manager /open Akku-Manager (Remainning) and in this mask open the settings-symbol above - deactivate Power-intensive prompt and deactivate "Close excessively power-intensive apps" and some lines below:
Activate: Keep Wi-Fi on when sleeping ALWAYS - Keep mobile data on when sleeping
Settings with Permissions and Notifications:
1) Open settings /Apps and search for WhatsApp. In this mask you find Permissions- and Notifications-Settings , go inside of both and set the needed permissions for the app and also "Alllow Notifications" and Priority display
Settings in Developer options:
1) one point after "use legacy DHCP client" - set: Mobile data always active
Additional Settings:
1) Settings /More - Open Mobile network and set: Mobile data - and Enable always-on mobile data
2) Open Settings /Wi-Fi and go to menu in the right corner below "Advanced setting" - set: Keep Wi-Fi on during sleep ALWAYS
3) Open Settings /Notification panel & statusbar - activate: Notification panel "Allow notification panel to be opened from the lockscreen if not password protected
4) Open Settings /Screen lock & passwords - activate "Show detailed notification info" and activate optional "Notification turn on screen"
For most users of ARROW Push-Notification for Chat-Apps are working now as they should (whitout converting them to system-apps like in Gratitude before) -
And for most users battery life is much more better than in Gratitude or in Stock Firmware.
But for some users not!
- Notifications coming not constant or not at all - andBattery life is worse than before - How can that be?
Answer: The complete different initial situation and sometimes also the settings.
Initial Situations (examples):
User A updated Lollipop with Stock Firmware to Marshmallow a long time ago (example: from b200 to b317) - after he was going to Custom Rom "Gratitude" - and from this time he was never back to any Stock Firmware and flashed new versions of Custom Rom always dirty.....
User B was also last on b317, after on "Gratitude" and flashed every new version clean, with Fullwipe.....
User C was last on b321a, after on "Gratitude" and flashed every new version clean, with Fullwipe but Arrow dirty....
User D was on Gratitude 5 and then he go back to Stock Firmware b370 - from there with OTA to b382 and after he flashed TWRP and did a Fullwipe before installing ARROW - this user has the best starting position! And for this user ARROW should work as provided
Why?
Custom Rom can only modifiy on Huawei Devices following partitions: system - cust - vendor (and nothing else!) Modem Updates, Updates for Push-Notifications and other sync services or battery software updates are coming with official Firmware!
The best performance for ARROW is given, if your Marshmallow Firmware and Bootloader and Modem.... is also up-to-date.
There is no need to do following steps, if you have flashed ARROW and everything is fine for you.
I would recommend to go back to Stock Firmware as an step between - before flashing ARROW - for Users which come from Gratitude and for Users which have already ARROW installed and issues with Push-Notifications or too much battery drain!
(STOCK-RECOVERY AND UNROOT IS REQUIRED - AND YOU NEED ALWAYS FULL FIRMWARE FROM CUSTOM TO STOCK) - see install manual below!
The Full-Firmware you download (no OTA Files please) should be minimal b370 (which is available for all models). After this EMUI-Installing with reboot to system you can use in settings the Update-App to receive the next OTA Update and install this also. If the Update-App says after installing "no more Updates available" it is okay!
Normally you can use one Full-Firmware above b370, for GRA-L09 it is b382 - alternatively you can use b391 - but a higher version like b391 seems not work (cause Rom is based on b391)
Complete List of Huawei P8 Firmwares (for all models and cust v.): http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra
GRA-L09:
GRA-L09 Full Firmware b370: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v54178/f1/full/update.zip
GRA-L09 Full Firmware b382: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v69133/f1/full/update.zip
Attention: Bootloader may closed after update with Firmwares above 390 (even if showing in fastboot mode as open - but cannot flashing TWRP "command not allowed" - needs unlock Bootloader again)
GRA-L09 Full Firmware b391: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v71319/f1/full/update.zip
Complete list for GRA-UL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-ul00
Complete list for GRA-TL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-tl00
Complete list for GRA-CL00: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-cl00
Firmware for GRA-CL10: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G985/g104/v73798/f1/full/update.zip
Complete list for GRA-UL10: http://hwmt.ru/oth/HWFF/info/view.php?find_model=gra-ul10
Install manual:
To go back to Stock Firmware you have to do following steps:
1) Backup what you need to backup! Use Huawei Backup and also Titanium Backup. NOTE: But dont restore in the new ARROW then system-apps or data from system-apps from previous system! Restore only USER-APPS. For Chat-Apps like WhatsApp, Viber, Skype use the built-in Backup function - but keep or backup the folder from those apps on internal memory (because you need them on the same place if you reinstall those apps)
Battery must have minimal 80% doing those steps....
2-A) Users of Classic-Edition: Open K-Settings /more settings /flash recovery - Flash official Recovery (grant Root-Permission) - this flashes Stock Recovery in half a second.
2-B) Users of Magisk-Editon: Please go to TWRP and flash Magisk-Uninstaller.zip to unroot your Phone. Users of Gratitude Magisk Edition should also flash unsu.zip (both linked in OP) After reboot make a connection with USB to your PC. With Minimal ADB and Fastboot program (on PC) flash Stock-Recovery. If you dont know how to do, ask me in this Thread. Download: https://www.androidfilehost.com/?fid=529152257862705190
If you have Xposed Framework installed - uninstall it (Magisk Users in Magisk Manager/Modules - Classic Users in K-Settings /Xposed Settings /Install Xposed confirm - Reboot needs about 15min)
3) Download the Full Firmware for your model, unzipp it on your PC (mostly you get update.app and meta.inf)
4) Create a folder on internal memory or external SD and name it: dload
5) Copy only update.app and meta.inf (if meta.inf is present) in this folder. After DISCONNECT USB from Phone!
6) Reboot to Stock Recovery - with Restart menu (also possible with pressing Vol+ and Power-Button at the same time as long until Recovery is displayed)
7) Wipe Cache with Stock Recovery (it uses another engine than TWRP) and do after a Factory Reset. There is no need to restart the phone to system now. Go to:
8) Press Vol- and Vol+ (in the middle) and Power-Button at the same time, until phone reboots and EMUI-Software-Installing is displayed
9) Let the EMUI-Installing finishing - it reboots automatically to system and starts the EMUI-Optimizing - wait until Language-Selection is displayed. Make a short set up (You can skip the most) - but it is important to arrive the homescreen.
10) Go to Settings / About the phone and tap 7x (times) on Build-Number. It activates developer options.
11) Go to Developer options and activate USB DEBUGGING - after open Advanced settings /security and activate "Unknown Sources"
12) Connect Phone with USB to your PC (Accept the Fingerprint query with "always" on your Phone) Look, if Windows installed the right drivers so you have access to phone - if not install HiSuite http://consumer.huawei.com/minisite/HiSuite_en/index.html and make a connection with HiSuite. Allow installing HiSuite on Phone. If you have access now, close HiSuite (also in Background).
13) Copy ARROW-Rom to your Phone.
14) With Minimal ADB and Fastboot flash TWRP: https://www.androidfilehost.com/?fid=529152257862681510 - if you are unsure with the right commands, ask me in the Thread.
15) DISCONNECT USB Cable now from your Phone
16) Press Vol+ and Power-Button at the same Time until phone reboot (at the moment, Huawei Logo comes you can leave Power Button, but keep holding Vol+) Reboot to TWRP takes a while
17) Set up TWRP (allow modification, set language, screen timeout, time zone...)
18) There is no need to wipe internal SD (but if you like to do this, do it at first and restart after TWRP - then you must setup TWRP again)
18) Go to Wipe, Advanced Wipe and wipe: Dalvik&Cache, Cache, data and system
19) Install ARROW Rom
20) Restore User-Apps, but dont restore any System-Apps (or data from it) Chat-Apps install from Playstore, and use the built-in restore function.
ARROW should work now as ist should!
Men like always the best work!! I already intalled the Arrow ROM... At the moment working excellent... Congratulations :highfive:
Hucast_DL said:
Men like always the best work!! I already intalled the Arrow ROM... At the moment working excellent... Congratulations :highfive:
Click to expand...
Click to collapse
Thank you
Hello @Tecalote, at first i wanna thank you for your work! I want to as you, in description you have "Open PMPlus, select "install it" - message "succesful installed" , but not such app is preinstalled in my Rom, clean flashed classic version, any tips?
00471 said:
Hello @Tecalote, at first i wanna thank you for your work! I want to as you, in description you have "Open PMPlus, select "install it" - message "succesful installed" , but not such app is preinstalled in my Rom, clean flashed classic version, any tips?
Click to expand...
Click to collapse
Hi This is interesting - I am at home in two hours and loading up the apk for you.
I flashed both versions of the Rom about 20 times for testing several things and had always the App preinstalled...
I think it is cause of TWRP.
After making a Nandroid Backup before flashing the Rom it has problems to unmount and remount partitions.
If data was not mounted correctly, the App would not be preinstalled - cause it should go to /data/app
That's why I recommend, after making a Backup to Restart TWRP (reboot Recovery) before flashing the Rom...
Tecalote said:
Hi This is interesting - I am at home in two hours and loading up the apk for you.
I flashed both versions of the Rom about 20 times for testing several things and had always the App preinstalled...
I think it is cause of TWRP.
After making a Nandroid Backup before flashing the Rom it has problems to unmount and remount partitions.
If data was not mounted correctly, the App would not be preinstalled - cause it should go to /data/app
That's why I recommend, after making a Backup to Restart TWRP (reboot Recovery) before flashing the Rom...
Click to expand...
Click to collapse
i will try dirty reflash it with mounted data and let you know :good:
EDIT. reflashing fixed it and app appeared, thanks for halp @Tecalote
To say sir, a perfect job, thank you for all your effort and give you the opportunity to have this great ROM. My congratulations and best wishes to you.
Sent from my GRACE using XDA Labs
lespaul79 said:
To say sir, a perfect job, thank you for all your effort and give you the opportunity to have this great ROM. My congratulations and best wishes to you.
Sent from my GRACE using XDA Labs
Click to expand...
Click to collapse
Thanks a lot
Hello, first of all, thank you for this amazing rom. I've installed it about 6 hours ago and its work perfect at the moment. The only thing that I cannot explain is why show me the block screen weather widget in Chinese, can u help me?
enzoade1994 said:
Hello, first of all, thank you for this amazing rom. I've installed it about 6 hours ago and its work perfect at the moment. The only thing that I cannot explain is why show me the block screen weather widget in Chinese, can u help me?
Click to expand...
Click to collapse
Hi
Written in OP
"In ARROW are not included Chinese letters, with the exception of "Lunar" - which comes with K-Settings. Gratitude users know how to get rid of them. For all others:
1) Go to K-Settings, in there to:
2) Notification Settings / Show "statusbar lunar" - deselect.
3) Go to Lockscreen and desktop settings "Lunar calender + desktop wheather lunar" - deselect."
Great work, flashed it on my UL00 3 hours ago after wiping cache and dalvik cache only, everything seems to work alright, I can confirm that this ROM works flawlessly on UL00.
Ammar_ said:
Great work, flashed it on my UL00 3 hours ago after wiping cache and dalvik cache only, everything seems to work alright, I can confirm that this ROM works flawlessly on UL00.
Click to expand...
Click to collapse
Hi Thank you for your feedback!
You have installed the ROM on the Middle Eastern variant UL00C185...
I am glad to hear that it not only works on GRA-L09
This is what I promised, but I wasn't 100% sure - cause I have only L09...
I am interested which build number is displayed in "About the phone"?
Thanks!
Everything is looking good so far. Thank you for your time and effort!
How do I activate automatic call recording? Is there a possibility of adding more regions to this rom? I have region specific software that fails. My digital satellite provider's software checks my region before it can work. I'm in South Africa.
rodlane said:
Everything is looking good so far. Thank you for your time and effort!
How do I activate automatic call recording? Is there a possibility of adding more regions to this rom? I have region specific software that fails. My digital satellite provider's software checks my region before it can work. I'm in South Africa.
Click to expand...
Click to collapse
Hi there Automatic Call Recording can be enabled that way:
Open the Dialer App - below left is a star, below right is the symbol for the settings menu. Open it and there you can enable automatic call recording.
For the other issue: Can you give me a link to an African Marshmallow Huawei Stock Firmware? So I can look at it and perhaps include the Region.
Which Region did you set up right now?
Thanks very much man!
Flashed it last night, after it took me half an eternity to backup all my files (had something messed up so I had to look a bit deeper). Flashing and all was fine, including xposed via magisk.
Been using it the day now, but at 2 Things im not sure if it is caused by the Rom or by the latest whatapp update:
-in widgets i can select WhatsApp - but there is no more this huge 4*2 widget with message-preview, does anybody else have this? (only WhatsApp Chat and WhatsApp camera available there)
-even though i have given WhatsApp all permissions, my Screen won't wake up when i receive a message. It was quite usefull while the phone lay at my table i could see in one glance whether or not it was important and decide to pick it up
....okay i have tried a bit and found out my Screen also won't wake up after receiving sms or email.. where could i look after that? every app has "Show on lockscreen" enabled
There was another thing, which i could't read fast enough, but it was something with kvip Settings and some overlay permissions and a path where to find them or so?
it popped up a couple of times at the beginning (those little messages in the lower middle of the Screen, just like "wifi connected") next time i will try to make a screenshot of that.
edit:
@Tecalote congrats for 500 Posts and 300 likes! :good:
@Tecalote your ROM IS ****ing awesome, congratulations!!!
Enviado desde mi HUAWEI GRA-L09 mediante Tapatalk
@ChavezD For the Wakeup Screen you must open Phonemanager and in there the Notification Manager. Every App like WhatsApp and Gmail, Email... is in the list - open WhatsApp or Email in the list and set up "Showing on Homescreen" and everything.
The other things I must look. Small popup messages should be shown, like "RAM 1.7 GB available, Wifi connected".. I must look later, at the moment I am not at home
Edit:
For enabling the Wakeup on Homescreen - you must go to Settings /Screenlock and Password - and there set up : Notification turn on screen!
Tecalote said:
@ChavezD For the Wakeup Screen you must open Phonemanager and in there the Notification Manager. Every App like WhatsApp and Gmail, Email... is in the list - open WhatsApp or Email in the list and set up "Showing on Homescreen" and everything.
The other things I must look. Small popup messages should be shown, like "RAM 1.7 GB available, Wifi connected".. I must look later, at the moment I am not at home
Click to expand...
Click to collapse
@Tecalote yeah those Settings are all activated, really don't know what went wrong for me again or what i broke..
EDIT: OH god damn it, thank you so much! I hope i didn't actually disable it half sleeping this morning/"night"
Take your time, it wasn't annoying or anything, just wondered what it was. But it's exactly as you described, but not just 4 words but 4 rows or so in the same time period.
Maybe im also gonna reflash and not install every stupid app i've installed once. Is there any Chance to stop Google from automatically downloading all (>100) recently installed apps after reflashing a Rom? [I always Flash clean, so.. no dirty Flash for me^^]
Edit2: I think in those Messages i was talking about it wasn't Overlay - it was Dropzone. But still no clue what i should do there, everthing is allowed that wants to be
ChavezD said:
@Tecalote yeah those Settings are all activated, really don't know what went wrong for me again or what i broke..
EDIT: OH god damn it, thank you so much! I hope i didn't actually disable it half sleeping this morning/"night"
Take your time, it wasn't annoying or anything, just wondered what it was. But it's exactly as you described, but not just 4 words but 4 rows or so in the same time period.
Maybe im also gonna reflash and not install every stupid app i've installed once. Is there any Chance to stop Google from automatically downloading all (>100) recently installed apps after reflashing a Rom? [I always Flash clean, so.. no dirty Flash for me^^]
Click to expand...
Click to collapse
Hi again You can stop Google from downloading the previous installed Apps at the first start. After Google Login you will be asked if you want to restore - just deny.
Don't know yet what you exactly mean with 4 rows in the same time.
Do you mean perhaps Toast Messages? There's for example an Xposed Modul called "Perfect Color Bar" - in this you can enable "Toast" with mixed compatibility. After you get instead of the the small black info messages colored ones with the symbol of the App message. There are also other "bars" on the Repo for customization that messages.
Do you remember which official firmware did you have before using Custom Roms like Gratitude? b317, b321a, or b370? I know, there were some modem updates coming with the official firmwares (which cannot be done with Roms on Huawei Phones)
Maybe you should update to officially Firmware as an step between before reflashing the Rom. For this you would need the Stock Recovery, which can flashed from K-Settings, more Settings. On xda you can find the b391 here:
https://forum.xda-developers.com/huawei-p8/how-to/firmware-huawei-p8-b391-gra-l09c432-gra-t3534020
It would refresh the Rest of your Phone (which cannot be reached by ROM) - and after the ROM can work as it should...
Just an idea
Code:
/*
* Your warranty is not void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* make sure you are aware of any risks associated with using the options in
* the toolkit BEFORE using it! YOU are choosing to use this toolkit, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you want to unlock your bootloader and root? Or switch to another ROM? Are you asking yourself which one of the 100s of guides here on xda should I use? Well no need for any guides! Use this toolkit and be bootloader unlocked and rooted or on a different ROM within MINUTES! Super simple to use, just a couple of clicks and the toolkit does everything else!
COMPATIBILITY
Supports A2017, A2017G, and A2017U (all software builds)
Windows 7 and up
FEATURES
- Automatic file downloads with hash verification
- OTA updates
- ADB and Qualcomm EDL driver Installation
- ADB and Fastboot Test
- Backup apps+data
- Restore apps+data
- Backup system/data/boot partitions
- Restore system/data/boot partitions
- Unlock bootloader on ALL software builds (Marshmallow and Nougat) without voiding your warranty!
- Lock bootloader
- Flash TWRP and disable dm-verity and forced encryption
- Root with SuperSU
- Restore to stock/ Recover from hard bricking with EDL restore packages
- Flash an unlimited amount of ROM, kernel, and other zips at once!
-Magisk root (Coming soon)
-Unroot (Coming soon)
-Remove ZTE bloatware (Coming soon)
DOWNLOAD
You may need to disable your antivirus as the EXE file may get quarantined or removed due to "malware". This is because of the BAT to EXE compiler used and is a false positive. More information available here: [url]https://superuser.com/questions/1117747/why-do-av-software-thinks-that-all-compiled-batch-files-are-viruses[/URL] (read the answer)
CREDITS
ZTE of course for the Axon 7
Google for Android
@Unjustified Dev for being the reason why there is any development in the first place
@Koush for Universal ADB Drivers
@Dees_Troy and @jcadduono for TWRP
Xiaomi for MiFlash
@jcadduono for MiFlash method and A2017U packages
@djkuz for A2017 and A2017G MiFlash packages
@Chainfire for SuperSU
@WugFresh for his awesome Nexus Root Toolkit and inspiring me to make one for the Axon 7
Anyone on Stack Overflow who helped me with batch commands
AFH for hosting setup files
Github for hosting masterlist files
Any one else who I forgot to mention (sorry)
And of course...me!
Please make sure you are aware of any bugs/issues BEFORE trying any of the toolkit options!(4th post)
XDA:DevDB Information
Axon7Toolkit, Tool/Utility for the ZTE Axon 7
Contributors
bkores
Version Information
Status: Stable
Current Stable Version: 1.2.1
Stable Release Date: 2017-09-04
Created 2017-03-14
Last Updated 2017-10-16
FAQs and Troubleshooting
I want to switch to [insert ROM name]How?
1) Use the Install Drivers option
2) Use the ADB+Fastboot test option to test the ADB and fastboot drivers
3) Use the backup apps+data option
4) Use the bootloader unlock option
4) Download the ROM of your choice, along with gapps (such as Opengapps arm64 7.1) and anything else you want to flash. Make sure you download the universal bootloader and modem for your variant as well from the lineage thread otherwise THE ROM WILL NOT FLASH!
5) (optional) Use the Flash TWRP option.
6) Use the flash zips option to flash the ROM along with everything else
7) (optional) Use the root option.
Profit!
The adb restore apps+data option did not work on my device.
Unfortunately, this is a ROM issue as some ROMs have broken backup managers. There is no other way to restore the backup through the adb way, however there is a way to restore a backup on the device. This method requires an unlocked bootloader and root. It also requires a paid app.
1) Download Titanium Backup from the Play Store: [url]https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup[/URL]
2) Download the Pro key. It costs $5.99 US but the app itself is extremely worth it (from my experience) : https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupPro&hl=en
3) Open up the app on your device. You should get a Superuser request popup. Tap `Grant`.
4) Connect your device to your computer with the factory USB-C cable. Open a command window anywhere by holding down shift and then right clicking. Click on 'Open command window here' from the menu options.
5) Execute the following command to push the backup file to your internal storage:
Code:
C:\Axon7Development\Axon7Toolkit\adb push filepath /sdcard/
where filepath is the location and name of your backup such as C:\Axon7Development\Axon7Toolkit\backups\my-backup.ab
6) If there is no menu option in the app execute the following command to emulate a "menu" key press:
Code:
C:\Axon7Development\Axon7Toolkit\adb shell input keyevent 82
This should bring up Titanium Backup's menu options.
7) Scroll down to 'Extract from ADB backup' and select it. This will bring up a list of "Open with" options. Choose any installed file manager on your device, such as the one pre-installed with the stock ROM or a third-party file manager such as ES File Explorer.
8) Navigated to the /storage/emulated/0 directory and find your backup file and select it.
9) Restore the backup on your device.
The partition restore option did not work on my device.
Follow the instructions above but use the 'Extract from Nandroid backup' option instead.
My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
The download of a file keeps failing even though I am definitely connected to the Internet.
-There may be problems with the link or server, usually in the event of high traffic. In this case use the import option. Please let me know if this happening for longer than 24 hours so I can investigate it.
-If you are on versions 1.0.0-1.1.1 the download agent is outdated. Download and run the fix here: [url]https://drive.google.com/open?id=0B2VBJePGznYjdXNUUkY5UzFJTm8[/URL]
Can I access the source code?
No.
Changelog
v1.2.1
-New design
-Added back Driver Installation option
-Added back variant auto-detection
-Added android version auto-detection
-Fixed adb backup save location/name bug
-Remove system apps backup option for better chance of successful adb restore
-Fixed system partition restore bug
-Fixed flash zips option
-Fixed "boot failed" error
-Fixed bootloader lock brick for some users
-Fixed Android Marshmallow compatibility issues
-Other minor enhancements and bug fixes
v1.2.0
-Dropped support for Windows XP and Vista
-All drivers now installed during setup
-New popup design and system
-Revised some popups with more helpful information
-Revised and removed some notifications
-Faster launch (~15 seconds)
-Minimized use of temp files
-Completely new downloader with new UI, integrated hash verification, fixed hash mismatch bug, revised import option, and option to override hash verification
-Downgraded adb version to 1.0.36 to fix toolkit hang bug for some users
-Updated download agent (wget) to latest version
-Completely new updater with automatic installation and logging
-New simplified toolkit: removed Advanced Utilities and Driver Installation/Test
-Added emulator check on startup to prevent conflicts
-Build no longer required, just variant
-Added ADB+Fastboot Test option
-Added Flash TWRP option
-User can now set backup name and location for the backup options, default path is the toolkit's backup folder
-Fixed restore apps+data(ADB) option
-Revised miflash unlock package (it's the A2017G unlock package from the Russian forum)
-New toolkit UI
-Fixed numerous minor bugs
-Minor enhancements
-Updated MiFlash to latest version
-EDL connectivity checking and driver replacing now done by the toolkit
-Implemented more error checking
-Toolkit will launch FileDependencyChecker instead of exiting if file dependency is missing
-Fastboot and aboot images will be reflashed before bootloader lock to guarantee success
-Added A2017G B10 for restore stock option
-Added A2017U B19 for restore stock option
-Fixed bugs with restore stock option
-Fixed wipe system and data loop bug for flash zip option
-Fixed toolkit crashing when choosing file with spaces or special characters in path or name for import
-Zips no longer need to be imported for flash zip option, the toolkit can now use the original path
-Cache and dalvik now wiped automatically for all zip flashing
-Added limit download rate for downloader to settings
-Added view most recent update log to settings
-New uninstaller
v1.1.1
-FULL SUPPORT FOR A2017G! This means if you are on the G variant you can now UNLOCK YOUR BOOTLOADER and (in the future) RESTORE TO STOCK!
-Miscellaneous bug fixes
-Fixed "hashcheck mismatch" bug when importing a file dependency
-Added FAQs & Troubleshooting option
-Option to auto-detect device variant/build on startup
-Minor improvements to UI and options
-NEW ADVANCED OPTION! Bugreport generator
-Added options to filter log output by verbose, debug, info, warning, error, fatal or silent for Logcat generator
-Fixed unable to uninstall toolkit from Settings
-System write protection is now automatically disabled for root option
-Fixed incorrect canceling of download dependencies when inputting cancel option after failed download or hashcheck mismatch
v1.1.0
-Added support for B19_N
-Full support for A2017! This means those of you with the Chinese variant can now unlock your bootloader and restore to stock B13! (Set your build to "Any A2017")
-Option to choose "Any" build for A2017G variants or unsupported builds
-Fixed inability to change theme and build in settings
-THE MIFLASH ISSUE IS COMPLETELY FIXED! THIS MEANS THAT THOSE OF YOU HAVING TROUBLE USING MIFLASH FOR THE BOOTLOADER UNLOCK AND RESTORE TO STOCK OPTIONS THEY WILL NOW WORK!!!
-Option to skip ADB check for bootloader unlock & restore to stock options if your device is already in EDL mode
-Cache and dalvik will now be wiped automatically when flashing zips
-Removed all powershell commands for better compatibility
-Added option to wipe system and data before flashing a Custom ROM zip
-NEW OPTION! Support for twrp adb backups and restore in TWRP 3.1.0
-Changed the "Flash TWRP and/or root" option to just "root". If you want to flash TWRP permanently, use the fastboot flash recovery option in Advanced Utilities
-minor enhancements to UI and options
-B29 added as restore stock option along with B15_N with @jcaudanno's MiFlash package and @DrakenFX's TWRP package for A2017U
-Screenshots and screen recordings are now pulled from device to PC
-Added rotate 90 degrees and verbose logging options for screen record
-Option to backup system and shared storage applications for adb backup
-Downgraded ADB version to 1.0.31 and revised syntax to fix adb backup issues
-completely new ADB check method to prevent false "device connected" for instances when device is not actually connected
-Downloader will now launch the AFH download page of all dependencies instead of the direct download link for failed file dependency
downloads in case the direct download link is no longer working
-Updater will now launch the AFH download page for all toolkit versions if downloading of the update package fails
-List connected devices option now shows device state in addition to serial number for ADB
-NEW ADVANCED OPTION! ADB logcat
v1.0.2
-fixed syntax errors for flash zip option
v1.0.1
-fixed application closing during fastboot check for bootloader unlock option
v1.0.0
-Initial release
Bugs/Issues:
-TWRP gets stuck in loop when wiping system for flash zips option if system is mounted read-only
Thanks man. It's good to see more developers for Axon 7.
Cool, will probably check it out later. You should post up some sceenshots so we can see how it works.
Just one thought, does bootloader lock warn user to have untouched system? Lots of people lock on custom rom/modified stock for some reason.
lafester said:
Cool, will probably check it out later. You should post up some sceenshots so we can see how it works.
Just one thought, does bootloader lock warn user to have untouched system? Lots of people lock on custom rom/modified stock for some reason.
Click to expand...
Click to collapse
Yep. You'll get a popup that says you have to be complete stock to use it otherwise you'll be hard bricked.
I kinda wish we'd scrap all of the unlock and recover methods and just have all of the devs making threads to just resort to a Wugfresh tool like this. Any way to make unlock/locking/restoring/recovering hands off and safe would really help a lot of us out.
We could implement a bunch of backing up, signature verifications, and delays before steps occur so it's more foolproof and not have to rely on timing of key combinations and picking which file to use for whatever.
Here are some screenshots i just took. Thanks for your work on this, bkores.
http://imgur.com/a/qS4Ib
sm.bxsq said:
Here are some screenshots i just took. Thanks for your work on this, bkores.
http://imgur.com/a/qS4Ib
Click to expand...
Click to collapse
Thanks. You beat me to it lol.
Also, since you're using it please let me know of any bugs or improvements. Thanks!
Wow, nifty. Thanks, man.
Thanks for providing this to the community! Good work!
I'm planning to release a new version soon with support for adb backups in TWRP, restore to stock using TWRP, and an option to restore to B29 in edl for those who don't want B15.
Stay tuned
This does not seem to be working for me. When attempting to unlock the bootloader the application puts my phone into fastboot mode, and closes. ZTE Axon 7 factory nougat upgrade (B15). Have downloaded the MiFlash application as requested, but option 4 just places my phone into fastboot mode and then the application just exits.
Phone will now only boot to Team Win asking for a password (I didnt have a password set). Looks like my phone may be dead.
wyrethewolf said:
This does not seem to be working for me. When attempting to unlock the bootloader the application puts my phone into fastboot mode, and closes. ZTE Axon 7 factory nougat upgrade (B15). Have downloaded the MiFlash application as requested, but option 4 just places my phone into fastboot mode and then the application just exits.
Phone will now only boot to Team Win asking for a password (I didnt have a password set). Looks like my phone may be dead.
Click to expand...
Click to collapse
Hold on let me look into this.
@wyrethewolf The issue has been fixed. I'll upload the new version as soon as possible. For the time being if you are in TWRP you should be able to boot to system by pressing cancel on the decryption screen and then going to Reboot<System.
It was a tiny typo in the fastboot check which screwed up the entire script lol.
bkores said:
@wyrethewolf The issue has been fixed. I'll upload the new version as soon as possible. For the time being if you are in TWRP you should be able to boot to system by pressing cancel on the decryption screen and then going to Reboot<System.
It was a tiny typo in the fastboot check which screwed up the entire script lol.
Click to expand...
Click to collapse
Thank you, I will give this a try. Thank you for checking in on this!
New version is up! This should *hopefully* fix the application closing issue with the bootloader unlock option.
If you already have the toolkit, no need to download this one. It'll automatically be downloaded when you launch the toolkit.
Also if you get any errors of failing to close adb.exe during installation just press ignore. I've already fixed this for future releases.
@wyrethewolf tell me if the update fixed the issue. Thanks!
@bkores thanks for all you hard work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring many of the best features in existence today.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Syslog (free, open source, available on Play store and F-droid) is your friend.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0
Notes:
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Thanks dev. This is a great ROM
When you say latest fw, you are talking about OOS Pie or H2OS Q?
firebird11 said:
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
To be defined
First time installing crDroid to your Op6, or coming from another ROM:
- Be on the latest firmware
- Make sure you're running latest TWRP
- Copy GApps and crDroid zip to your internal storage
- Disable your screenlocks
- Boot into Recovery
- Wipe cache,data
- Flash crDroid zip
- Flash TWRP zip
- Reboot to recovery
- Flash GApps zip
- Flash Magisk zip
- Reboot system
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such as Xposed!
- have modified system files
DONATE
crDroid Website
Telegram Oneplus6/6t group
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 6
Contributors
firebird11, neobuddy89, gwolfu
Source Code:https://github.com/crdroidandroid
Source Code Kernel:https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LOS
Version Information
Status: Testing
Created 2019-10-16
Last Updated 2019-10-16
Click to expand...
Click to collapse
Any bugs or something not working?
Will try this weekend.
Thank you dev
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
veronesi.n said:
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
Click to expand...
Click to collapse
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
savinjo22 said:
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
Click to expand...
Click to collapse
Sorry I said not rooted ?... I wanted to say that magisk wasn't installed.
i tryed this rom on my htc m8 and i love it and i will try it again on oneplus 6
Is this also implemented already in android 10? TIA
tiga016 said:
View attachment 4847745
Is this also implemented already in android 10? TIA
Click to expand...
Click to collapse
Yes there's some customization settings.
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
backtrack292 said:
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
Click to expand...
Click to collapse
I assume you used the 'Green Box' link in Sourceforge? That always trips people up. That link is the latest ROM across all crDroid devices. (Currently the OP5 'Cheeseburger') Or next time actually read the file name before flashing.
Ignore that Green Box. Just pretend it doesn't exist. Use the links underneath to get the Enchilada downloads.
a new v6 build is up !
october security and statusbar padding are new
firebird11 said:
a new v6 build is up !
october security and statusbar padding are new
Click to expand...
Click to collapse
does it supports signature spoofing?
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
meistr91 said:
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
Click to expand...
Click to collapse
thank you for the suggestion... gone well beyond the link's status by the time i read this (on oos from local update), so may just wait it out for a working twrp solution - been too long since last used OOS anyway!
new v6 builds are up !
firebird11 said:
new v6 builds are up !
Click to expand...
Click to collapse
Can be flashe with oos 10 base ?