Related
Stock zImage
Add features:
busybox auto-injection (/system/xbin)
init.d support - automatically creates init.d in (/system/etc)
twrp-sony-recovery-boot-script based (Thanks @nilezon /jackfagner github script)
TWRP recovery 3.0.2-0 Modified (vol up or down when Violet LED)
Removed SuperSU in TWRP recovery to root because this method will not work
Systemless root support
SElinux permissive
RIC disabled
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Fix swappiness (100 to 60) - as 3.4 kernel source - Improved memory management (23.5.A.1.291 not modified yet)
* Required Bootloader Unlocked!
* Installation:
Downloads:
Advanced_Stock_Kernel_Z2_MM_6.0.1_23.5.A.0.570
Advanced_Stock_Kernel_Z2_MM_6.0.1_23.5.A.1.291
-Flash via recovery or unpack and flash boot.img via fastboot
Code:
fastboot flash boot boot.img
* Root:
-Flash a Systemless SU: SuperSU-v2.76
Note:
- The first boot may take some time, and give the impression that you are in a bootloop. Just wait and it will boot up normally eventually.
* Restore DRM:
-Flash Restore DRM - SONY DRM FUNCTION RESTORATION FOR UB DEVICE
* Please, do not mirror!
Also give a special thank you to @shoey63 in which helped make this possible
Enjoy and press the Thanks button if you like! :good:
.
I'm gonna try it tonight when i plan to swap to MM
thx you.bro.
Gustavo RD78 said:
-Flash Restore DRM - SONY DRM FUNCTION RESTORATION FOR UB DEVICE
.
Click to expand...
Click to collapse
has anybody tried if this actually still works on MM?
Gustavo RD78 said:
Add features:
twrp-sony-recovery-boot-script based (Thanks @nilezon /jackfagner github script)
TWRP recovery 3.0.0-0 Modified (vol up or down when Violet LED)
Removed SuperSU in TWRP recovery to root because this method will not work
Systemless root support
SElinux permissive
RIC disabled
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Fix swappiness (100 to 60) - as 3.4 kernel source - Improved memory management
* Required Bootloader Unlocked!
* Installation:
Download:
Advanced_Stock_Kernel_Z2_MM_Beta_23.5.A.0.486_twrp _3.0.0-0
-Flash via recovery or unpack and flash boot.img via fastboot
Click to expand...
Click to collapse
:good: Thank you, it works for Z2
Works perfectly, thangs
Sent from my D6503 using Tapatalk
Will this give me recovery access without wiping everything on my phone? I have MM beta right now without recovery
edzilla said:
Will this give me recovery access without wiping everything on my phone? I have MM beta right now without recovery
Click to expand...
Click to collapse
Yes he will go
Please add Qc- 2.0 HACK in your Kernel )
pseudoheld said:
has anybody tried if this actually still works on MM?
Click to expand...
Click to collapse
Yes. I installed it . it works
Gustavo RD78 said:
Stock zImage
Add features:
twrp-sony-recovery-boot-script based (Thanks @nilezon /jackfagner github script)
TWRP recovery 3.0.0-0 Modified (vol up or down when Violet LED)
Removed SuperSU in TWRP recovery to root because this method will not work
Systemless root support
SElinux permissive
RIC disabled
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Fix swappiness (100 to 60) - as 3.4 kernel source - Improved memory management
* Required Bootloader Unlocked!
* Installation:
Download:
Advanced_Stock_Kernel_Z2_MM_Beta_23.5.A.0.486_twrp _3.0.0-0
-Flash via recovery or unpack and flash boot.img via fastboot
Code:
fastboot flash boot boot.img
* Root:
-Flash a Systemless SU: BETA-SuperSU-v2.68-20160228150503.zip
Note:
- The first boot may take some time, and give the impression that you are in a bootloop. Just wait and it will boot up normally eventually.
* Restore DRM:
-Flash Restore DRM - SONY DRM FUNCTION RESTORATION FOR UB DEVICE
* Please, do not mirror!
Also give a special thank you to @shoey63 in which helped make this possible
Enjoy and press the Thanks button if you like! :good:
.
Click to expand...
Click to collapse
Great. Thanks. Is this kernel with Kexec Hardboot Support for multirom Secondary too ?
Thanks (Pressed). Its work perfectly on Z2 MM. Great Man!!!
can anyone help?
everytime i download the systemless root SuperSU zip ,and i test it with winrar it says : ! C:\Users\xx\Desktop\mm\BETA-SuperSU-v2.68-20160228150503.zip: The file "common\file_contexts_image" header is corrupt
Thank you, you're a great man! Everything works well ....
WORKING FLAWLESSLY
You're epic...good job
v2 - busybox auto-injection (/system/xbin)
v2 - init.d support - automatically creates init.d in (/system/etc)
Note: when installing v2 flash again SuperSU
It works like charm.
Thanks @Gustavo RD78 for your great work ??
akshay2shah said:
Hey I m not able to flash this kernal.
I have unlocked bootloader.
I m on mm 6.0.1.
I don't have root.
Help me please.
Sent from my D6503 using XDA-Developers mobile app
Click to expand...
Click to collapse
unpack .zip and flash boot.img via fastboot
Code:
fastboot flash boot boot.img
Gustavo RD78 said:
unpack .zip and flash boot.img via fastboot
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Deleted.
akshay2shah said:
I did this already !!
I shows 'failed'
What to do now ?
Sent from my D6503 using XDA-Developers mobile app
Click to expand...
Click to collapse
both versions 1 and 2 you face this problem?
He tried to FlashTool?
Code:
/*
* Your (probably expired) 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.
*/
LineageOS 16.0 for Samsung Note N7000
Beware, you are about to enter a dangerous zone!
ABOUT
This is an unofficial Pie build for the Galaxy Note (N7000) based on LineageOS 16.0.
Read the sections below carefully to understand the status of this ROM and how to prepare your device for installation.
CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.
INSTALLATION FROM STOCK
Follow these steps if you are coming from stock. You will need access to a PC.
1. Prepare Odin, Samsung USB Drivers, PhilZ CWM Odin Flashable, and your phone with a stable USB connection.
2. Install the Samsung USB Drivers and fire up Odin.
3. Select AP and choose the PhilZ CWM Odin Flashable package.
4. Proceed to flash. Once done, reboot your device into recovery.
5. You should be in CWM recovery now. Flash this zip to get TWRP IsoRec: 20210209-boot_n7000-twrp_i9100_3311.zip
6. Reboot recovery. You should now enter TWRP IsoRec recovery. Proceed to the installation steps below, except for step 2.
INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration:
- Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip - Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card (only in Android 7).This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired, or boot_magisk.img if you need Magisk support.
8. Prepare a coffee or tea and sit back on your couch. Click to reboot system, BUT DO NOT SWIPE TO INSTALL TWRP APP or you will end up in a bootloop!
9. Remember to install Magisk Manager if you need Magisk support.
DOWNLOAD
Google Drive
SOURCE
GitHub - leewp14/local_manifests at lineage-16.0
Contribute to leewp14/local_manifests development by creating an account on GitHub.
github.com
GitHub - hikuii/android_kernel_samsung_smdk4412: Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000)
Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000) - GitHub - hikuii/android_kernel_samsung_smdk4412: Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000)
github.com
LineageOS 16.0
LATEST BUILD
lineage-16.0-20210211-UNOFFICIAL-n7000
kernel-e604934cd028ba34c8a52d6898658a2e6053ad8e (hikuii597)
magisk-v21.4
NOT WORKING/UNTESTED
- GPS/AGPS: untested, A-GPS not working
- DRM: untested
- IPv6: no connectivity
- Bluetooth: in-call audio not working
- WiFi: extremely reluctant to auto-connect
- Kernel: app requires restart to use storage after granting storage permission
- Kernel: random reboot freeze at offline charging
- Kernel: requires toggle MagiskHide on each reboot to enable MagiskHide
BUILD-SPECIFIC NOTES
- PowerHAL has been removed to provide flexibility in adjusting CPU governor.
INSTALLATION NOTES
- When prompted in TWRP, do not install TWRP Updater app as it will cause softbrick.
- To pass SafetyNet, you must use boot_magisk.img and toggle MagiskHide on every boot.
- Do not update Magisk! Always stick to the version that the build provides.
Changelog
20210211
- general: upstream updates, ASB 2021-02
- kernel: enable RPFILTER (fixes tethering)
- kernel: switch back to PegasusQ governor with hotplug enabled
- kernel: restore mali400 to stock configuration (166/266MHz)
OLD CHANGELOG
minors 20200809
- device: revert lineage-17.1 configuration changes
- device/kernel: enable zram at 384MB with dual stream compression
- kernel: revert lineage-17.1 binder changes
20200928
- general: upstream updates, ASB 2020-09
- frameworks/base: upstream updates
- kernel: revert lineage-17.1 changes, enabled swap (thanks to @goodwu for notifying)
20200809
- general: upstream updates, ASB 2020-08-05
- frameworks/base: ColorFade fix for exynos mali- device-related: merge lineage-17.1 changes from @rINanDO
20200614
- general: upstream updates, ASB 2020-06-05
- device: merge lineage-17.1 changes- device: remove PowerHAL- hardware: default video buffer size to 1080p- kernel: mali400 reconfiguration, use 133Mhz, 160MHz, 266MHz.- kernel: lock mali to 160MHz during 1080p playback- kernel: disable CPU hotplug- kernel: use interactive CPU governor- kernel: use 500MHz as base CPU frequency- kernel: reconfigure thermal throttling, refer commit- kernel: add TriangleAway support, refer commit- kernel: remove a whole big bunch of logging that your grandpa never check on it
20200417
- galaxys2-common: bring back PowerHAL
- kernel/galaxys2-common: added Lineage Trust USB Restrict support (untested)- kernel: cherry-picked Syncthing-Fork "NAT transversal" fix (credits to @TheNatureOne)- kernel: switch to autosuspend (full credits to @rINanDO and @ChronoMonochrome)
20200407
- n7000: update GPS configuration
- n7000: update build fingerprint- n7000/kernel: add TriangleAway support- galaxys2-common: reconfigure wifi configuration- galaxys2-common: user configurable SWAP- galaxys2-common: actually fix in-call audio control- galaxys2-common: kernel modules to system- galaxys2-common: add Magisk build support (credits to @rINanDO)- galaxys2-common/kernel: bring over LOS 17.1 commits (credits to @rINanDO)- kernel: implement charge current control (credits to @TALUAtXDA)- kernel: prevent LCD lock busfreq- kernel: reconfigure ASV/DVFS for BUS/GPU- kernel: remove inbuilt recovery- kernel: bring back PegasusQ, adapted from Perseus-S3 (credits to @AndreiLux)- kernel: raised safefreq to 1.4GHz- kernel: bluetooth stack update (credits to @TALUAtXDA)
20200205
- kernel: cherry-pick mali400-r3p2-rel4 (don't expect anything from this!)
- kernel: disable modules support, KSM, LZ4 ZRAM and many other unnecessary stuffs- kernel: added GCC optimization flags, build kernel with -Ofast- kernel: a whole lot bunch of changes which is too much to be listed here- kernel: default CPU governor to OnDemand- kernel: modify CPU frequency steps back to 6steps- kernel: modify GPU (mali400) to 2steps, 190MHz and 267MHz- kernel: increase lowest busfreq from 160MHz to 190MHz- kernel: increase display frequency from 57Hz to 59.94Hz- kernel: decrease video engine clock from 267MHz to 190MHz- kernel: decrease shared GPU memory from 512MB to 256MB, increase GPU low-level memory to 24MB- kernel: slightly-slightly tune throttling configs, first throttle to 1200MHz, second throttle to 1000MHz- kernel: bring back FB_BLANK- kernel: adjust CONFIG_HZ to 300- kernel: add/enable exFAT, NTFS support- galaxys2-common: remove PowerHAL- galaxys2-common: revert use low-end video codecs- galaxys2-common: update whole bunch of framework configs- galaxys2-common: disable wifi adapter debug- galaxys2-common: more platform specific gcc optimization flags- galaxys2-common: fix USB info configuration- galaxys2-common: build libsecril-client- galaxys2-common: decrease ZRAM to 128MB- galaxys2-common: enable AOD (Always-On Display)- galaxys2-common: actually make macloader works- galaxys2-common: modify healthd to blank screen first before power off or reboot attempt in offline charging mode- n7000: rework GPS configuration (don't expect anything from this!)- vendor/samsung: add prebuilt si4709 FM driver- general: upstream source updates, security patch 2020-02-05
20191009
- kernel: panel brightness optimization from i9300
- kernel: adjust unified memory allocation size- kernel: disable logging- kernel: disable pegasusq core lock- kernel: switch to ZEN I/O scheduler- kernel: fix tuning table for Q1 (credits to rINanDO)- kernel: misc source updates from rINanDO, ChronoMonochrome, ComicoTeam- galaxys2-common: remove SamsungDoze- galaxys2-common: use low-end video codecs (credits to ChronoMonochrome)- galaxys2-common: make sure burn-in protection is enabled- galaxys2-common: wifi hotspot channel 1-11 instead of 1,6,11 only- galaxys2-common: platform specific gcc optimization flags- galaxys2-common: lower haptic feedback intensity- galaxys2-common: dual-speaker output implementation (back speaker + earpice speaker)- galaxys2-common: fix RIL PIN unlock (credits to rINanDO)- galaxys2-common: misc source updates from rINanDO- n7000: increase minimum adjustable brightness threshold- n7000: fake vendor security patch level- n7000: conditionally reset max17041 fuel gauge on boot- hardware/samsung: added missing OUI mapping [SEMCO - 50:cc:f8] (credits to J..J)- general: upstream source updates, security patch 2019-09-05
20190522
- Removed LTE network option in Settings
- Fixed GPS and RIL functionality- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)- New cursor icon for stylus (thanks to ComicoTeam)- Added xt_hl support in kernel
20190505
- Initial build
- Exclude RIL and GPS blobs due to non-working RIL and GPS
Hello,
We will have Android Pie on N7000 !!!!
Great and thank you !!!
I will buy a new battery for my Note I think.
Oh my god!
Got my N7000 out of the closet and charging it right now! Gonna flash this right away!
Thank you, @lee.wp14
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
[email protected] said:
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
Click to expand...
Click to collapse
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
lee.wp14 said:
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
Click to expand...
Click to collapse
I see, thank you for this information.
I will try repartitioning in the next build.
Right now, the ROM is working great!
GREAT! I am eager to try it as soon the RIL works! (still using this ancient phone as a backup)
Release 20190522
CHANGELOG
20190522
- Removed unused LTE network option in Settings
- Fixed GPS and RIL functionality
- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)
- New cursor icon for stylus (thanks to ComicoTeam)
- Added xt_hl support in kernel
Notes:
- Be patient when the phone is booting up, if you have a sim lock, wait a while before entering the PIN because telephony stuffs might still be loading. You will get SIM unlock failed error if the telephony stuffs are not loaded finish yet. We are using a 2018/2019 Android on a 2011 phone, be patient
- GPS is tested OK personally by me prior to this release. If you can't get a fix or detect any satellites, make sure your GPS antenna connection is ok.
- Due to upstream changes, we are currently using Autosleep driver to let the phone enter a suspend state (doze). A shorter standby time should be expected.
- Builds are not SafetyNet OK and also not pre-rooted. If you want root, you may flash the addonsu package from LineageOS's website.
- Builds have signature spoofing enabled by default (thanks to rINanDO), you may take advantage of this to replace GAPPS with MicroG.
- This build is tested OK with GAPPS (pico ARM 9.0), please expect a longer boot time if GAPPS is installed.
- I'm not sure why, but earlier before this after I made some changes in the sources, the USB dialog won't show in Notifications panel anymore. To change USB operating mode, go to Settings > Connected Devices > USB
Quote:
1. Make sure you have at least a working TWRP 3.x IsoRec on your device. If no, proceed to bauner's LOS13.0 thread for installation steps.
2. Flash this recovery by rINanDO: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip (under directory n7000/misc/recovery)
Unquote
That means I need to flash TWRP twice from stock recovery?
John Moore said:
That means I need to flash TWRP twice from stock recovery?
Click to expand...
Click to collapse
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:
> If you are from stock ROM
1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
> If you are from Custom ROM
1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
lee.wp14 said:
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:
> If you are from stock ROM
1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
> If you are from Custom ROM
1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
Click to expand...
Click to collapse
Thanks very much, Lee.
I Can't boot to twrp 3.1.0 EMU Migtation
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp
Stuck and reboot again in logo
Please help me
Zin Bo said:
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp
Stuck and reboot again in logo
Please help me
Click to expand...
Click to collapse
Can you reconfirm the situation and possibly list out your procedures?
lee.wp14 said:
Can you reconfirm the situation and possibly list out your procedures?
Click to expand...
Click to collapse
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery
Then flash twrp 3.1.0-isorec.zip and reboot into recovery
And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)
So i start doing step-2( that you tell for n7000 pie rom installation )
I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)
So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.
Can't go to Twrp
Thank for your reply.
Zin Bo said:
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery
Then flash twrp 3.1.0-isorec.zip and reboot into recovery
And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)
So i start doing step-2( that you tell for n7000 pie rom installation )
I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)
So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.
Can't go to Twrp
Thank for your reply.
Click to expand...
Click to collapse
Can you flash back to stock to make sure everything is still OK and repeat the procedures again and stop before the step of flashing the twrp emu isorec.
Instead, extract the boot.img from the rom zip and copy to phone (you can do it using TWRP usb mtp) or sdcard, inside TWRP choose inage flash mode, and flash the boot.img to Boot partition.
Next restart to TWRP again. If you can go into twrp then you may try flashing the twrp emu isorec. See if it works this time.
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^
dclou said:
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^
Click to expand...
Click to collapse
Galaxys2/n7000 won't support magisk as our kernel 3.0.101 does not support namespace, which is required for magisk to operate.
Is this ROM Treble based?
Hi..
Here i share some GSIs manual fixes for hi6250 (emui8) devices as many of them they missed huawei patches or ignored them.
To be honest most credits of the fixes go to our hi6250's active devs Haky , DarkJoker360 , Dil3mm4 & of course Phh.
The fixes made after many comparisons between stock, DSSIs & different GSIs builds & versions.
Gsi Installation:
1 - Wipe system data cache & dalvik
2 - Flash system_arm64_aonly.img in system image partition , boot up & look for bugs
3 - Flash the fix
Fixes could fixe bootloop , sdcards bug ( not detected ) , camera/torch toggle , offline charging , Real battery capacity ( 3000mah ) , GPS and automatic APN detect .
*More posts will be added as updates if any fix successfully tested
Well done, bro!
Keep it up :highfive:
Omar Champ said:
Well done, bro!
Keep it up :highfive:
Click to expand...
Click to collapse
Thanks :highfive:
Update : ( only dssi builds )
Possible fast charge fix for p10 lite users who are using dssi PRA ROMs by Haky or by DarkJoker360 following this way :
Using a root explorer go to /etc/init/init.6250.rc and edit values of tow lines :
From 2750 to 4500
write /sys/class/hw_power/charger/direct_charger/iin_thermal 2750
From 1000 to 2000 :
write /sys/class/hw_power/charger/charge_data/iin_thermal 1000
Save/exit/reboot
*Try lower values if fast charge speed seems faster than stock ( use ampere app to compare )
Thank you for sharing these awesome fixes.
I tested some of those on my p10 lite (South Korean single sim variant rebranded to Eurupean dual sim variant).
PixelExperienceP unofficial GSI was bootable after flashing your fix file and also get back offline charging by your fix.
As official PE Pie GSI is expected to be roll out after august, I hope those fixes would also work on that.
Recommend to try!
Update :
Fix vendor mismatch message every time when booting some dssi/gsi roms like Bootleggers and other roms .
Also this guide fixes CtsProfile=false ( magisk safetynet check ) .
GUIDE :
From magisk download section :
-Flash MagiskHide Props config module
-Flash BusyBox magisk module
-Reboot
Tape in termux ( or any terminal emulator )
Su
Props
According to the menus enter :
1 then f then 7 then 7 then y & y & reboot .
Hami_Do said:
Update :
For P8lite/P10lite and should work for other hi6250 devices .
Fix vendor mismatch message every time when booting some dssi/gsi roms like Bootleggers and other roms .
Also this guide fixes CtsProfile=false ( magisk safetynet check ) .
GUIDE :
From magisk download section :
-Flash MagiskHide Props config module
-Flash BusyBox magisk module
-Reboot
Tape in termux ( or any terminal emulator )
Su
Props
Then according to the menus enter :
1 then f then 7 then 7 then y & y & reboot .
Click to expand...
Click to collapse
In my case it ends up with phone locking like it's been restarted (I can't unlock it with fingerprint, have to enter PIN) after about 2 minutes of using. In my case universal SafetyPatch by hackintosh5 works flawless. Phone shows vendor missmatch warining anyway, but for example I was able to activate phone contactless paymants in my bank app.
Update :
HWComposer & blur Fix for GSIs.
So at the moment it's working only on GSI roms.
Here's how to fix blur and hwc:
-Flash the fix and reboot to Android.
-Disable, re-enable and disable again the HW Overlays ( in developer options ), boom blur gone.
Credits: - haky86
- Me for making it flashable & for testing
Update :
- Pie -
Fix NFC on GSIs :
- Go to system/app/NfcNci/ and delete the whole folder
- Flash NFC4PRA-GSI-TWRP.zip
Reboot
Good news !
Finally camera and flashlight fixed for quack gsi build ( android 10 ) :
- Flash the patch through twrp
- Reboot
Any plans or progress in fixing GPS for "quack" gsi?
MIcHiJK said:
Any plans or progress in fixing GPS for "quack" gsi?
Click to expand...
Click to collapse
Idk but it seems working as it should on v203
Hami_Do said:
Idk but it seems working as it should on v203
Click to expand...
Click to collapse
Oh I was on v202 and had problems. Google maps was just finding my location when WiFi was on. I want to use "Here we go" in offline mode but it wasn't working. There is nothing about GPS in changelog. From what EMUI 8 version are you coming. I flash treble ROMs from the February build.
MIcHiJK said:
Oh I was on v202 and had problems. Google maps was just finding my location when WiFi was on. I want to use "Here we go" in offline mode but it wasn't working. There is nothing about GPS in changelog. From what EMUI 8 version are you coming. I flash treble ROMs from the February build.
Click to expand...
Click to collapse
I'm on emui of October 2018
Discussions opened here @hi6250group
Update Q fixes:
How to fix safetynet issues on phh's Q + msg on booting "there is problem in your device ..." :
-Download UnSu.zip
-Download Termux (or use adb)
-Download magisk phh build ( tested with magisk.phh.v19.3 )
#####
-Place unSu.zip on SD card
-Flash magisk phh build
-In termux, enter:
su
(Grant permission on window)
for termux:
phh-su 0 /system/bin/phh-securize.sh
(Add adb shell if using adb)
-Reboot to twrp, mount /system.
-Go to advanced -> File manager : delete /system/app/bin/phh-su
-Factory reset with twrp.
-Flash magisk phh build, reboot.
#####
For now BasicIntegrity should be fixed (true) + android's msg on booting should gone
#####
-In magisk repository (download section), install magisk hide props and BusyBox
-Reboot
-Install termux (or use adb), and run:
su
props
1
f
7
7
y
Reboot.
#######
CtsProfile should be fixed (true)
#######
Enjoy !
Credits :
@PHHtreble @hi6250group's members
Anyway to get a functional NFC patch for PRA-LX1 on android Q GSI ?
cethiel said:
Anyway to get a functional NFC patch for PRA-LX1 on android Q GSI ?
Click to expand...
Click to collapse
Not tried yet , I will look later if I can fix it.
How to fix io schedy missing "none"
Hi.. How to fix this error?
It's show "none" inside scheduler tab selection
itsm03 said:
Hi.. How to fix this error?
It's show "none" inside scheduler tab selection
Click to expand...
Click to collapse
Sorry I don't know
Update Q fixes :
It seems media broken on all v204 based ROMs I have tested such as LOS 17 , MSM Extended Q ( no sound , no video )
I managed to fix it using the patch bellow , and if media not fixed just open terminal and tap :
su
setprop debug.stagefright.ccodec 0
Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01
Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!
Reserved
Great work.
Sent from my Mi A1 using Tapatalk
Thanks ??
Nice. Bro you carried legacy ?
nice work waiting for shrp version of this ??
Noice :good:
Sent from my Mi A1 using XDA Labs
This is an update of TWRP Comic Dan?
manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Great job dude ?
Awesome work!
Thank you so much for this.
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.
Where is the survival checkbox??
What is this "inject twrp" does ?
oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option
Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?
**ATTENTION**
I'm not responsible for any bricked device.How to Install
1. Unlock your bootloader
2. Boot to Odin mode
3. Check AP box and select TWRP tar file
4. Hit start
5. Reboot to TWRP and flash multi disabler if you want (check this before flashing it)
6. Have fun
CHANGELOG
-Upstream Twrp Version variant a11
-Updated Kernel from a12
-Fixed System,Vendor Mount Issue
BUGS
-MTP
DOWNLOAD
TWRP-3.6.2_M51
THANKS TO
OKADA - For building it
thanks for this twrp. Please confirm if DATA backup and restore works?
I tried flashing this TWRP file and it does not work. Had to reinstall and downgrade to A10 again.