Official Nougat (7.0) for lenovo K6 Note TWRP Flashable.
#Disclaimer!
I am not responsible for bricked devices!!!
Features.
* Based on official Nougat S218 Release
* Pre Rooted-Root installed during flashing( no need to root after modifying boot.img)
* Modified boot.img
* Busybox Installed
* Should Works both for (K6 Note) ( K53a48) and K6 Plus K53b36 (K6 Plus not tested)
* Build Prop Tweaks
* Can be flashed on top on 6.0 and also if want to install as fresh ROM after factory reset.
Requirements:
* Lenovo K6 Note (K53a48)
* Installed Custom Recovery TWRP.
* Time and patience
Instructions
* Download the zip and put it on internal or external sd card( if you have one)
* Boot into TWRP Recovery
* Create Backup of your ROM.
* Select Install zip.
* Choose the zip you downloaded, and wait till the flashing finishes.
* After installtion the device will boot and reboot, this is normal.
* Finish the setup and enjoy the phone.
https://mega.nz/#!6JND2Q4J!bkZ1jC17q1XHGKRejKqPSk8FI7S-iNUAhnaor9JIcDY
Bugs:
Change Region not working if flashed after factory reset.( will be fixed soon)
Dont Forget to say thanks
Screenshots
{
"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"
}
Reserved
Can it be flashed on already nougat version s218 ?
Thanks!!
I installed it but
Thwre is no root
Hi!
First of all thank you for this awesome effort that you put into this.
I've installed the rom today and it's been working fine so far. Except Snapchat. The app opens fine, but when I try to send a snap, the app crashes. Sometimes I can send one, sometimes not.
Also, after installing the rom I've noticed that the Pixel Launcher and the Samsung browser were missing. That might have been a bug on my behalf, but I was just saying.
I would greatly appreciate if you could help me with this troublesome Snapchat. Hell, maybe even other apps might start misbehaving.
All the best
Lazariche said:
Hi!
First of all thank you for this awesome effort that you put into this.
I've installed the rom today and it's been working fine so far. Except Snapchat. The app opens fine, but when I try to send a snap, the app crashes. Sometimes I can send one, sometimes not.
Also, after installing the rom I've noticed that the Pixel Launcher and the Samsung browser were missing. That might have been a bug on my behalf, but I was just saying.
I would greatly appreciate if you could help me with this troublesome Snapchat. Hell, maybe even other apps might start misbehaving.
All the best
Click to expand...
Click to collapse
I have installed the rom again, on top of 6.0, Both PIxel launcher AND Samsung internet are available, regarding snapchat i cannot test that, i am not able to login.
i would advice to uninstall n reinstall the app to check if that works.
mido1122 said:
Can it be flashed on already nougat version s218 ?
Click to expand...
Click to collapse
Yes can be flashed on top
mido1122 said:
I installed it but
Thwre is no root
Click to expand...
Click to collapse
root working here.
adilrenzu said:
I have installed the rom again, on top of 6.0, Both PIxel launcher AND Samsung internet are available, regarding snapchat i cannot test that, i am not able to login.
i would advice to uninstall n reinstall the app to check if that works.
Click to expand...
Click to collapse
After rooting I couldn't log in either. I used the full unroot option from within the SuperSU app, reinstalled Snapchat, logged in successfully, and I flashed again the SuperSU v2.82 zip with TWRP. Then I noticed that Snap isn't working.
If I were to flash your Android 7.0 installer zip with TWRP again now, would it brick or something? Maybe that'll work.
mido1122 said:
Can it be flashed on already nougat version s218 ?
Click to expand...
Click to collapse
mido1122 said:
I installed it but
Thwre is no root
Click to expand...
Click to collapse
Lazariche said:
After rooting I couldn't log in either. I used the full unroot option from within the SuperSU app, reinstalled Snapchat, logged in successfully, and I flashed again the SuperSU v2.82 zip with TWRP. Then I noticed that Snap isn't working.
If I were to flash your Android 7.0 installer zip with TWRP again now, would it brick or something? Maybe that'll work.
Click to expand...
Click to collapse
flashing again the zip would not brick the phone.
regarding snapchat, the issue seems to be root, if snapchat detects root, it does not work.
Probable solution is here
https://forum.xda-developers.com/general/general/snapchat-rooted-devices-xposed-nougat-t3483001
Or install Magisk, i have tried and tested it.
adilrenzu said:
flashing again the zip would not brick the phone.
regarding snapchat, the issue seems to be root, if snapchat detects root, it does not work.
Probable solution is here
https://forum.xda-developers.com/general/general/snapchat-rooted-devices-xposed-nougat-t3483001
Or install Magisk, i have tried and tested it.
Click to expand...
Click to collapse
Well, I unrooted and Snapchat KEEPS CRASHING. It's so annoying. I'm going to perform a factory reset and then reflash the zip. If that doesn't work, I am going to revert to Marshmallow, but I don't know how to do it. In case I will need to revert, I'd appreciate it if you told me how to revert.
Magisk doesn't install. It asks for a stock boot image.
Lazariche said:
Well, I unrooted and Snapchat KEEPS CRASHING. It's so annoying. I'm going to perform a factory reset and then reflash the zip. If that doesn't work, I am going to revert to Marshmallow, but I don't know how to do it. In case I will need to revert, I'd appreciate it if you told me how to revert.
Magisk doesn't install. It asks for a stock boot image.
Click to expand...
Click to collapse
i Dont know what you are doing wrong. Do the following
1. Install the zip again
2. then follow the youtube tutorial.
https://www.youtube.com/watch?v=zKqOzFSASQU
adilrenzu said:
i Dont know what you are doing wrong. Do the following
1. Install the zip again
2. then follow the youtube tutorial.
https://www.youtube.com/watch?v=zKqOzFSASQU
Click to expand...
Click to collapse
Installed the zip again, and successfully installed Magisk. I was able to login, but it still crashed a few seconds later.
By the way, when flashing the zip I got this:
After it said "Formatting system" : "mount: failed to mount /dev/block/platform/soc/7824900.sdhci/by-name/userdata at /data: Device or resource busy"
And at the end, after "Done!" : "unmount of /data failed (-1): Device or resource busy".
What might that be?
Also, Pixel launcher and Samsung internet aren't here.
I'd rather revert now )
Lazariche said:
Well, I unrooted and Snapchat KEEPS CRASHING. It's so annoying. I'm going to perform a factory reset and then reflash the zip. If that doesn't work, I am going to revert to Marshmallow, but I don't know how to do it. In case I will need to revert, I'd appreciate it if you told me how to revert.
Magisk doesn't install. It asks for a stock boot image.
Click to expand...
Click to collapse
The error has nothing to do with it.
Anyways here is the guide by @mehmet6ok to revert back to 6.0
https://forum.xda-developers.com/ge...ide-restore-stock-recovery-rom-6-0-1-t3599360
adilrenzu said:
The error has nothing to do with it.
Anyways here is the guide by @firemax13 to revert back to 6.0
https://forum.xda-developers.com/ge...ide-restore-stock-recovery-rom-6-0-1-t3599360
Click to expand...
Click to collapse
Not my work @adilrenzu its @mehmet6ok work
i installed it many time but there is no root
i flashed the boot.img again super su again there is no root
please tell me what to do
adilrenzu said:
Official Nougat (7.0) for lenovo K6 Note TWRP Flashable.
#Disclaimer!
I am not responsible for bricked devices!!!Features.
* Based on official Nougat S218 Release
* Pre Rooted-Root installed during flashing( no need to root after modifying boot.img)
* Modified boot.img
* Busybox Installed
* Removed Lenovo bloat (lenovo companion,Lenovo Logger Etc)
* Removed google Bloat (Chrome, Hangout,Drive etc.)
* Samsung Internet Browser
* Replaced Google Music with MIUI Music
* Google Pixel Launcher as well as Lenovo Launcher
* Should Works both for (K6 Note) ( K53a48) and K6 Plus K53b36 (K6 Plus not tested)
* Replaced default wallpaper and lockscreen wallpaper
* Replaced Bootanimation.
* Build Prop Tweaks
* Can be flashed on top on 6.0 and also if want to install as fresh ROM after factory reset.
Requirements:
* Lenovo K6 Note (K53a48)
* Installed Custom Recovery TWRP.
* Time and patience
Instructions
* Download the zip and put it on internal or external sd card( if you have one)
* Boot into TWRP Recovery
* Create Backup of your ROM.
* Select Install zip.
* Choose the zip you downloaded, and wait till the flashing finishes.
* After installtion the device will boot and reboot, this is normal.
* Finish the setup and enjoy the phone.
Bugs:
Change Region not working if flashed after factory reset.( will be fixed soon)
Dont Forget to say thanks
LINK: https://mega.nz/#!qBcj2BTD!3JD0f1hoslRuN0uGzQAnirsrY5zxTFrE4dyDWL9P7WM
Screenshots
Click to expand...
Click to collapse
Thanks for it ,
But if I FLASH ON MY S116 ,will it work?????
sagar4sforce said:
Thanks for it ,
But if I FLASH ON MY S116 ,will it work?????
Click to expand...
Click to collapse
Yes it should work.
adilrenzu said:
Yes it should work.
Click to expand...
Click to collapse
Ty, it worked
---------- Post added at 03:44 AM ---------- Previous post was at 03:42 AM ----------
adilrenzu said:
Official Nougat (7.0) for lenovo K6 Note TWRP Flashable.
#Disclaimer!
I am not responsible for bricked devices!!!Features.
* Based on official Nougat S218 Release
* Pre Rooted-Root installed during flashing( no need to root after modifying boot.img)
* Modified boot.img
* Busybox Installed
* Removed Lenovo bloat (lenovo companion,Lenovo Logger Etc)
* Removed google Bloat (Chrome, Hangout,Drive etc.)
* Samsung Internet Browser
* Replaced Google Music with MIUI Music
* Google Pixel Launcher as well as Lenovo Launcher
* Should Works both for (K6 Note) ( K53a48) and K6 Plus K53b36 (K6 Plus not tested)
* Replaced default wallpaper and lockscreen wallpaper
* Replaced Bootanimation.
* Build Prop Tweaks
* Can be flashed on top on 6.0 and also if want to install as fresh ROM after factory reset.
Requirements:
* Lenovo K6 Note (K53a48)
* Installed Custom Recovery TWRP.
* Time and patience
Instructions
* Download the zip and put it on internal or external sd card( if you have one)
* Boot into TWRP Recovery
* Create Backup of your ROM.
* Select Install zip.
* Choose the zip you downloaded, and wait till the flashing finishes.
* After installtion the device will boot and reboot, this is normal.
* Finish the setup and enjoy the phone.
Bugs:
Change Region not working if flashed after factory reset.( will be fixed soon)
Dont Forget to say thanks
LINK: https://mega.nz/#!qBcj2BTD!3JD0f1hoslRuN0uGzQAnirsrY5zxTFrE4dyDWL9P7WM
Screenshots
Click to expand...
Click to collapse
Ty it worked ,
But for now xposed gone
Can i flash uninstall supersu zip to unroot and get back warranty
can i flash it on Lenovo k6 power will it work?
sagar4sforce said:
Ty, it worked
---------- Post added at 03:44 AM ---------- Previous post was at 03:42 AM ----------
Ty it worked ,
But for now xposed gone
Can i flash uninstall supersu zip to unroot and get back warranty
Click to expand...
Click to collapse
You need to flash xposed again, for warranty you need to look the bootloader again. Search google how to do that.
sudhadown said:
can i flash it on Lenovo k6 power will it work?
Click to expand...
Click to collapse
No this is only for k6 note/plus not for k6 power
Related
CyanogenMod 12.1 for the Memopad FHD 10 4G - ME302KL
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
-----------------------------------------------------------------------------------------------------------------------------------------------------------
What Works:
Touch
Display
Brightness (auto and manual)
4G Network
WIFI
GPS
Bluetooth
Accelerometer
USB Charging
USB OTG
USB Pendrive
Ext SDcard
Deep Sleep
Front and Back Camera
and other things...
Bugs
-----
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Installation
You have to unlock tablet with asus app.
You have to use SevenMaxs TWRP RECOVERY for Me302kl
1. Download the ROM and the BOOT.IMG from the link below
2. Download GAPPS
3. Transfer the zip files to your SD card
4. Reboot to recovery mode
Note: You Must use TWRP recovery
5. Optional: Do nandroid backup
6. Wipe data / Factory Reset
7. Install CM zip
8. THIS STEP IS EXTREMELY NEEDED: Make a backup of system partition
9. THIS STEP IS EXTREMELY NEEDED: Advanced wipe - Wipe only system partition
10. THIS STEP IS EXTREMELY NEEDED: restore system backup
11. Flash Open GApps zip - (do not flash pico gapps. It has a AOSP keyboard FC BUG - I flashed Stock)
12. Install Boot.img zip
13. Reboot to system
Enjoy LOLLIPOP!
The steps from 8 to 10 are needed because the new system installer make a copy by block, not by files. So the system partition will be large as the system image file. After flashed the system, we make a backup and format the partition. Now the size of system partition will be correct so we can restore the rom.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Download: http://d-h.st/57LS This is only the ROM (system) without Boot.img - DONT'FLASH WITHOUT BOOT.IMG
Download Link for Boot.img http://d-h.st/nTaM
Download link for Boot.img with FastCharge [ http://www107.zippyshare.com/v/mrjjcDYf/file.html] thanks to SevenMaxs source.
Download Link for Framework-res.apk patched for Ext SD : http://www61.zippyshare.com/v/wONtvgZ4/file.html
Download TWRP Recovery by SevenMaxs : http://d-h.st/M3ep
To install recovery exstract frm the zip the file recovery.img and put it on the sdcard.
Then connect to the tablet with adb:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p25
Reboot into recovery VOL+ AND POWER
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Source
Check out the KERNEL Source available on https://github.com/yatto/ME-302-KL
The rom is the Nexus 7 Official CM12.1 without some libs : system/lib/keystore.msm8960.so and power.msm8960.so and with the /system/vendor/lib/files from Me302kl 4.2.2 ROM
Feel free to submit any fixes, Just remember to give proper credits when using other people's source.
Credits
Cyanogenmod team
SevenMaxs for his recovery TWRP
If i missed someone contact me!
-----------------------------------------------------------------------------------------------------------------------------------------------------------
XDAevDB Information
CyanogenMod 12.1 for Me302kl, ROM for the Asus Memopad FDH 10 4G
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod for Nexus7 2013
Version Information
Status: Beta1, Stable
All OK
Thank you!
The main camera is working, but I have not found how to switch on the front?
And It seemed to me too big image on the screen, I was a little turned down the dpi settings.
AlexXx70 said:
Thank you!
The main camera is working, but I have not found how to switch on the front?
And It seemed to me too big image on the screen, I was a little turned down the dpi settings.
Click to expand...
Click to collapse
The cameras are hard to fix. They are used in different way by nexus7 and me302kl... I'm working hard on it...
In next release i'll fix the external SD. In my test it works ! Nexus 7 does not have an external_sd so i had to modify kernel, initrd and framework to make sd working...
Have a nice day...
cool
Thanks for this will be giving it a try this weekend.
Boot Img Updated ! link at 1st post.
Fix Cameras
Fix Sdcard
You have to replace framework-res.apk to make extSD working.
1) Download framework-res.apk from the link at 1st post
2) Copy it on sdcard (internal)
3) open a terminal emulator or ADB shell ant type :
Code:
[B]su
mount -o rw,remount /system
cd /system/framework
rm framework-res.apk
cp /sdcard/framework-res.apk ./
chmod 644 framework-res.apk
reboot[/B]
Enjoy LOLLIPOP
I think I need some help.
Currently I have CM 11 installed and I'm trying to install CM 12.1.
I follow instruction step by step, but all I get is endless reboot into black screen right after asus logo.
I still can access TWRP recovery by holding vol+ so I restored CM 11 for now.
What can possibly cause this issue? I can provide TWRP log if this may help, but I'm not sure how to attach file here.
Thank you for all your hard work and sorry for bothering and being such a noob.
redunka said:
I think I need some help.
Currently I have CM 11 installed and I'm trying to install CM 12.1.
I follow instruction step by step, but all I get is endless reboot into black screen right after asus logo.
I still can access TWRP recovery by holding vol+ so I restored CM 11 for now.
What can possibly cause this issue? I can provide TWRP log if this may help, but I'm not sure how to attach file here.
Thank you for all your hard work and sorry for bothering and being such a noob.
Click to expand...
Click to collapse
Make sure that you have done all the Wipes (cahe, dalvik cache, data without data/media). Follow the istructions. If you like provide logs. After bootloop, in recovery "/proc/last_kmsg" log will be interesting. Also TWRP log.
yattodettaman said:
Make sure that you have done all the Wipes (cahe, dalvik cache, data without data/media). Follow the istructions. If you like provide logs. After bootloop, in recovery "/proc/last_kmsg" log will be interesting. Also TWRP log.
Click to expand...
Click to collapse
Yeah, I double-checked all steps, did I miss anything?
1. Wipe dalvik cache, cache and data without data/media
2. Install cm-12.1-test.zip
3. Backup system partition
4. Advanced wipe - wipe system partition
5. Restore system backup
6. Flash GApps (Open GApps stock 5.1)
7. Install Boot.img (ME302KL_LP_READY.zip)
Would you mind if I send you logs in private message?
Any feedback?
yattodettaman said:
Any feedback?
Click to expand...
Click to collapse
It's greate. All working fine.
Root
How to get ROOT now?
Which G-apps do you think is better for the ME302KL tablet?
I'd use "Open GApps arm 5.1 Stock" (arm 32).
Do you think that's good?
feedback
Followed all steps.
Booting took long long time with the ASUS logo flashing up time to time.
After some minutes lollipop robot came out, after a long while more appear the sign "Android starting - Applications....." and after 5 min. the tablet was ready.
Did the patch for external SD card and rebooted.
Took (again) very long time in rebooting but in the end everything seemed to work correctly.
The only problem is that the app "Premium Play" doesn't work because it see the devices as rooted. But it isn't.... or is it?( rooted, I mean)
The other thing is the time for booting but I think we can stand it.
Thank you very very much for your work, we all appreciate it very much.
---------- Post added at 02:02 PM ---------- Previous post was at 01:08 PM ----------
Display start flashing when you type something.
Tried different keyboards, than the default google one, the problem remain.
bye
hi¡¡ can i use this rom on fhd 10 without lte and 4g?
bepigreen said:
Followed all steps.
Booting took long long time with the ASUS logo flashing up time to time.
After some minutes lollipop robot came out, after a long while more appear the sign "Android starting - Applications....." and after 5 min. the tablet was ready.
Did the patch for external SD card and rebooted.
Took (again) very long time in rebooting but in the end everything seemed to work correctly.
The only problem is that the app "Premium Play" doesn't work because it see the devices as rooted. But it isn't.... or is it?( rooted, I mean)
The other thing is the time for booting but I think we can stand it.
Thank you very very much for your work, we all appreciate it very much.
---------- Post added at 02:02 PM ---------- Previous post was at 01:08 PM ----------
Display start flashing when you type something.
Tried different keyboards, than the default google one, the problem remain.
bye
Click to expand...
Click to collapse
Sorry I can't go on testing because an old problem of my tablet jump out again : touchscreen stop working.
I tried everything but nothing really worked the only thing that keep the problem more stable is the kernel inside the sevenmaxs patch :ME302KL_Boot-jb-14.09.25-Perun_by_SevenMaxs.zip.
So I have to go back to it.
Good luck for your fabulous work
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
shindya228 said:
How to get ROOT now?
Click to expand...
Click to collapse
Actually CyanogenMod is a native rooted firmware.
Go in setting and find "root"
Everything is working - both cameras and extsdcard!
Many thanks for your job!!! :good::good::good:
But framework-res change through Root explorer.
Guys, don't forget activated superuser in settings of CM before mounting exsdcard.
First post updated with the link [http://www107.zippyshare.com/v/mrjjcDYf/file.htmlmg]
It is the boot.img with FastCharge.
yattodettaman said:
Any feedback?
Click to expand...
Click to collapse
Booting time (first installation and simple restart) take long time: the ASUS logo appears and than go away (blank screen) and then re-appears.. 3/4 times.
I have no tried the sdcard fix.
I have the problem of the Display flashing blue when typing something.
Problably wifi is a bit slow (i was comparing it with phone in downloading apps from play store ).
i tried it and it's an awesome rom
But the update didn't work with me
My device kept booting over and over again but nothing happened
Please help me to fix it and use sd card at my device
carlo.bar said:
Booting time (first installation and simple restart) take long time: the ASUS logo appears and than go away (blank screen) and then re-appears.. 3/4 times.
I have no tried the sdcard fix.
I have the problem of the Display flashing blue when typing something.
Problably wifi is a bit slow (i was comparing it with phone in downloading apps from play store ).
Click to expand...
Click to collapse
For the blue flashing try this: go on settings, display and lights, then enable .e xtended display.
For the First boot... It is not normal.
{
"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 is only for Huawei P9 (EVA)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-eva.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.1-1/twrp-3.1.1-1-eva.img"][U]download twrp-3.1.1-1-eva.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-01
Last Updated 2017-06-11
Changelog
Code:
[B]TWRP 3.1.1-0[/B]
* bump up TWRP version to 3.1.1
* fix backup of /version
* use device specific and updated prebuilts (+kernel)
* remove the ability to flash images to ext4 mounted partitions
[B]TWRP 3.1.0-3[/B]
* kernel updated for proper loop support
* magisk can now be installed and is supported by every rom running b380+ kernel (tested on b383)
* native_package.xml has been changed to device specific version
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD cards or OTG drives
* Enabled direct image flashing to special partitions
(be careful when using it - one wrong klick means brick in a second!)
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
[B]TWRP 3.1.0-1[/B]
* proper handling of decryption (improves booting time by ~10 seconds)
* do not wipe /data/hw_init during /data wipe or factory reset to prevent system errors
* cleanup ramdisk, reduced image size by 10mb
[B]TWRP 3.1.0-0[/B]
* add the ability to format oem specific partitions
* add back f2fs support so we can format /data as f2fs
* bump up twrp version to 3.1.0
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
frenzissi said:
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
Click to expand...
Click to collapse
Yes, should be fine
Atarii said:
Yes, should be fine
Click to expand...
Click to collapse
I can confirm this works fine
Thanks
<<<by scaniathe>>>
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
LE: I flashed @Atarii B378 img and now I am rooted. AdAway is working as expected. Thank you!
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
OldDroid said:
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
Click to expand...
Click to collapse
The one from here https://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947. Dont waste your time. Its working if B378 img from Atarii is flashed.
Atarii said:
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
Click to expand...
Click to collapse
L09 B378 img is ok for now. Still need to test if system apps uninstall. But I am happy Adaway is working!
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Perfect!
Thanks
cbgti said:
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Click to expand...
Click to collapse
Encryption/decryption support is related to the /data partition (where your user files are stored). The encryption scheme changed for Nougat, so this is the first TWRP that supports being able to read/write to that encrypted /data partition.
Read-only system mode (aka systemless mode) - some people do not touch the system partition, so they can later apply OTAs easier (as they perform a diff on system files)
good job OpenKirin team, thx a lot
So supersu from chainfire isn't working even on this, right?
@Atarii : Thanks!
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
maliniaka said:
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
Click to expand...
Click to collapse
Propably the script wont work on huawei, but we work on it.
will this TWRP work for the Honor 6x Nougat Beta too?
sassmann said:
will this TWRP work for the Honor 6x Nougat Beta too?
Click to expand...
Click to collapse
what does the title say, whats the name of the forum where this has been posted?
Hope this answers everything!
PS: Its comming soon for H6X.
{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21
Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...
Reserved
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Woks awesome, thank you dev
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!
LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please
asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat
Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help
BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.
{
"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"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04
OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
NIce, thank you
hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation
Can this ROM be installed on top of LineageOS 16 without wape?
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse
@NeoArian Any chance for a screen recording of how it runs?
JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: excalibur
Maintainer/Authors build: @TheMalachite
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/TheMalachite/android_device_xiaomi_excalibur
Kernel: Prebuilt kernel from MIUI V11.0.2.0.QJXINXM
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Device Changelog
Code:
2020-07-30
- Initial unofficial release
PBRP Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/file/d/18MzNCTExOWLiu9ZUD3A7SXlD4QY2grrZ/view?usp=drivesdk
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Redmi Note 9 Pro Max
Contributors
TheMalachite, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2020-07-30
Created 2020-07-30
Last Updated 2020-07-30
Bugs: You tell me
Reserved #2
thank you sir..... for providing this recovery and opportunity to test your initial relese
Good but when other custom rom for redmi note 9 pro max
[email protected]@ said:
Good but when other custom rom for redmi note 9 pro max
Click to expand...
Click to collapse
When their will be dev who wanna build custom rom for it
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.
kannss said:
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.
Click to expand...
Click to collapse
Ok. Never go back to 'Mi Unlock Status' under Developer Options to add ur device again...
I did that mistake and my wait time got reset to give me new wait time.
Also don't log out of Mi account or play with 'Find Device' settings.
U may know already. But im just saying..
If u face any driver related issues, then in the Mi Unlock Tool itself, they have provided a way to install it, if u check their settings...
Good Luck
Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
Enable DM VERITY
MaheshTechnicals said:
Enable DM VERITY
Click to expand...
Click to collapse
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.
I'm currently using SD Maid app (Pro version) to remove all unnecessary bloatwares. Works like a charm.
And IMO, also works better than Termux or any other debloater. Although debloating is just one of the function of termux, but if u r using it just to debloat, then better go for SD Maid ?
UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)
coolvipcandy said:
UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)
Click to expand...
Click to collapse
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??
Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
Vijo123 said:
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??
Click to expand...
Click to collapse
i did as mentioned in first post,, as i was already root, i first flashed recovery.img and then from recovery, flashed the whole zip archive. thats all.
then.booted to system,, again booted manually to recovery and it was there,, and checked twice again, recovery was there.
---------- Post added at 05:25 AM ---------- Previous post was at 05:24 AM ----------
i didnt mess with dm verity,,
Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.
how to wipe "system" partition, there's no option for that ??
wipe > Advance > ???
Format data option
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Do not install inbuilt magisk from this recovery. It gives bootloop, download from github or xda and flash zip manually
Stuck on fastboot mode
PLEASE HELP
i installed twrp recovery in my redmi note 9 pro max and install magisk , now my device is stuck on fastboot.
---------- Post added at 05:22 AM ---------- Previous post was at 05:18 AM ----------
kannss said:
Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.
Click to expand...
Click to collapse
bro when i installed i got stuck in fastboot
what should i do now ...? should i install custom rom or not