Related
This is something I built for my own use. Portions of the files (adbd, etc...) come from chainfire's original boot-to-root image.
This boot image has been modified to pass safetynet with an unlocked bootloader.
This image is NOT rooted in normal boot mode.
Stock recovery boots with adb enabled, and adb shell is rooted in recovery.
/data is accessible from recovery, but userdata is left encrypted.
Be careful if you modify /system/ dm-verity is still enabled.
Usage:
Code:
fastboot flash boot PixelXL_OPP4_PassSafetyNet_RecoveryRootedShell.img
Have fun: PixelXL_OPP4_PassSafetyNet_RecoveryRootedShell.img
You can boot twrp with this or is stock only.
caballon said:
You can boot twrp with this or is stock only.
Click to expand...
Click to collapse
It's the stock recovery binary renamed to recovery_org. recovery is replaced with a script that auto mounts system (ro) onto system_root, and userdata onto /data, and then launches the renamed stock recovery binary.
You can do just about anything you want from a root ADB shell provided you have the know-how.
Fenny said:
It's the stock recovery binary renamed to recovery_org. recovery is replaced with a script that auto mounts system (ro) onto system_root, and userdata onto /data, and then launches the renamed stock recovery binary.
You can do just about anything you want from a root ADB shell provided you have the know-how.
Click to expand...
Click to collapse
Thanks buddy.
Fenny said:
This is something I built for my own use. Portions of the files (adbd, etc...) come from chainfire's original boot-to-root image.
This boot image has been modified to pass safetynet with an unlocked bootloader.
This image is NOT rooted in normal boot mode.
Stock recovery boots with adb enabled, and adb shell is rooted in recovery.
/data is accessible from recovery, but userdata is left encrypted.
Be careful if you modify /system/ dm-verity is still enabled.
Usage:
Have fun: PixelXL_OPP4_PassSafetyNet_RecoveryRootedShell.img
Click to expand...
Click to collapse
I have to root again after flash this Right?
caballon said:
I have to root again after flash this Right?
Click to expand...
Click to collapse
Yes, but be aware that SuperSU fails safteynet on its own.
Fenny said:
This is something I built for my own use. Portions of the files (adbd, etc...) come from chainfire's original boot-to-root image.
This boot image has been modified to pass safetynet with an unlocked bootloader.
This image is NOT rooted in normal boot mode.
Stock recovery boots with adb enabled, and adb shell is rooted in recovery.
/data is accessible from recovery, but userdata is left encrypted.
Be careful if you modify /system/ dm-verity is still enabled.
Usage:
Code:
fastboot flash boot PixelXL_OPP4_PassSafetyNet_RecoveryRootedShell.img
Have fun: PixelXL_OPP4_PassSafetyNet_RecoveryRootedShell.img
Click to expand...
Click to collapse
I just tried flashing this and when flashing OPP4 followed by this kernel I cannot get past the white Google Bootloader screen. It just doesnt seem to work. Is there any special procedure that needs to be followed?
uodii said:
This is something I built for my own use. Portions of the files (adbd, etc...) come from chainfire's original boot-to-root image.
This boot image has been modified to pass safetynet with an unlocked bootloader.
This image is NOT rooted in normal boot mode.
Stock recovery boots with adb enabled, and adb shell is rooted in recovery.
/data is accessible from recovery, but userdata is left encrypted.
Be careful if you modify /system/ dm-verity is still enabled.
Usage:
I just tried flashing this and when flashing OPP4 followed by this kernel I cannot get past the white Google Bootloader screen. It just doesnt seem to work. Is there any special procedure that needs to be followed?
Click to expand...
Click to collapse
Nothing special required. In my experience it worked great as long as you don't root or attempt to flash TWRP. It is possible you will need to let OPP4 boot once in order for sdcardfs to be applied.
To pass SN with root, you can use the latest suhide, you don't need this kernel unless you DON'T want root in normal mode, and still want to pass SN with an unlocked bootloader.
Fenny said:
Nothing special required. In my experience it worked great as long as you don't root or attempt to flash TWRP. It is possible you will need to let OPP4 boot once in order for sdcardfs to be applied.
To pass SN with root, you can use the latest suhide, you don't need this kernel unless you DON'T want root in normal mode, and still want to pass SN with an unlocked bootloader.
Click to expand...
Click to collapse
Some when I tried this I:
- flashed OPP4
- flashed your kernel
- booted into the modded TWRP recovery that supports DP4
- flashed supersu
- reboot
---- This resulted in an endless loop on the G screen with a loading bar (waited about 15 minutes to no avail)
I also tried the above except I booted into the rom before flashing your kernel and proceeding with the process and got the same result.
I also tried the above omitting the installation of supersu altogether and the seemed to result in the worst behavior because it would reboot maybe 1 second after hitting the white google bootloader screen.
So currently i'm on OPP4 with supersu installed and everything is running fine, except as you state, I'm obviously not able to pass safetynet because of this. Any other suggestion as to what I may be doing wrong? Also point of note that I dont believe should make a difference, but I'm running this on Sailfish (Pixel) is there any reason why this kernel would not support it?
Lastly, was it difficult to modify this? Did you build this from source or unpack and modify the image itself?
Thanks for this! I was missing my Android Pay!
uodii said:
Some when I tried this I:
- flashed OPP4
- flashed your kernel
- booted into the modded TWRP recovery that supports DP4
- flashed supersu
- reboot
---- This resulted in an endless loop on the G screen with a loading bar (waited about 15 minutes to no avail)
I also tried the above except I booted into the rom before flashing your kernel and proceeding with the process and got the same result.
I also tried the above omitting the installation of supersu altogether and the seemed to result in the worst behavior because it would reboot maybe 1 second after hitting the white google bootloader screen.
So currently i'm on OPP4 with supersu installed and everything is running fine, except as you state, I'm obviously not able to pass safetynet because of this. Any other suggestion as to what I may be doing wrong? Also point of note that I dont believe should make a difference, but I'm running this on Sailfish (Pixel) is there any reason why this kernel would not support it?
Lastly, was it difficult to modify this? Did you build this from source or unpack and modify the image itself?
Click to expand...
Click to collapse
The safteynet sauce is in the kernel cmdline. Not hard to reproduce, and trivial to detect. This probably won't work for long if the method gets popular.
And, yeah, this is an unpacked Marlin image. That is likely why your Sailfish is a no-go. It is not built from source.
Fenny said:
The safteynet sauce is in the kernel cmdline. Not hard to reproduce, and trivial to detect. This probably won't work for long if the method gets popular.
And, yeah, this is an unpacked Marlin image. That is likely why your Sailfish is a no-go. It is not built from source.
Click to expand...
Click to collapse
Yeaaaa work on final android o!!!!!
Booted twrp on Oreo and installed SuperSU and SU-Hide. Working and passing safetynet
Working fine here on the official release version (Oreo). Thanks!
Fenny said:
The safteynet sauce is in the kernel cmdline. Not hard to reproduce, and trivial to detect. This probably won't work for long if the method gets popular.
And, yeah, this is an unpacked Marlin image. That is likely why your Sailfish is a no-go. It is not built from source.
Click to expand...
Click to collapse
Any instructional guide that you followed on accomplishing this task? Would definitely love to do this for Sailfish
Booting in linux resulted in: FAILED (remote: dtb not found)
rockingondrums said:
Booting in linux resulted in: FAILED (remote: dtb not found)
Click to expand...
Click to collapse
Yeah, it won't fastboot boot. Just fastboot flash.
uodii said:
Any instructional guide that you followed on accomplishing this task? Would definitely love to do this for Sailfish
Click to expand...
Click to collapse
I could probably whip something up for the rooted adb part, but not all of this will be best practice, I think.
The kernel_cmdline patch is easy: Unpack boot image, edit the kernel_cmdline, repack.
If I find time I will do a write-up, I just have a suspicion it will get patched as soon as I do. xD
So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
I'm on 8.0 October Security Patch. My main aim isn't to remove Magisk, but I guess I have to to update to the Nov patch, and then reinstall it
brpqzme said:
So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
Click to expand...
Click to collapse
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work download the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.
I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Homeboy76 said:
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work down the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.
Click to expand...
Click to collapse
brpqzme said:
I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Click to expand...
Click to collapse
I don't know, but I don't think it would hurt to disable the modules.
Just don't lock the bootloader.
So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks
brpqzme said:
So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks
Click to expand...
Click to collapse
Please go to the link below and post the information about the problem Magisk-uninstaller-20171123.zip caused:
[2017.11.23] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Why? So, topjohnwu can fix it or tell you why it didn't work. The link above is where I got the 'Latest Uninstaller (Support v1+)' from.
Also it would help if you add the make and model of your phone, Magisk- version you were trying to uninstall.
Flashed OTA as per the link you gave with flashall
Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.
AlPoo said:
Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.
Click to expand...
Click to collapse
When you go to settings System Updates can you update?
If not Download the appropriate (October 2017) Factory Image for your phone.
Go to Android 8/Oreo and do #5 to SAVE data or #4 to WIPE data.
This will remove root and you should get the OTA.
After using this phone for a while I decided to root it.
I unlocked bootloader, installed TWRP and flashed Magisk, but all I get is bootloop or stuck on bootlogo (your device has been unlocked.....)
SOLUTION
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
Applicable also for moto Z2 Play, just with appropriate recovery, of course
Please note the updates to the first post. It may be necessary to do the procedure twice.
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Klen2 said:
I tried these TWRPs:
3.2.3.0
64bit 3.2.1
and TWRP and modified magisk from https://forum.xda-developers.com/z2-play/how-to/guide-twrp-root-t3667769
I tried all TWRPs with both modified magisk and official v18.
I have XT1710-09 with Oreo and October security patch
Is there a way to root this lastest firmware?
Thanks
Click to expand...
Click to collapse
I did 3.2.3-0 TWRP method (by Junior Passos) on my XT1710-06 device with 8.0 on August 1 security patch (purposefully neglected updating any further cause method was tested exactly up to August patch according to Passos) and everything seems working pretty fine for a month now. Think I've installed no Magisk modules other than Xposed systemless yet and I've no interest in SafetyNet as well, so not deeply tested either. Don't know for sure, but I guess there's a good chance for such method to work on October patch too. Just be sure to perform every step as it is now in the 3.2.3-0 OP. One word of advice: after performing TWRP backup, look for it in /system/media and move it to both external and internal SDcards just in case something goes wrong (usually because of a missed step, I can say)... Also: I recommend to install Magisk v17.1 first time; then, if you want, update to v18 but right from the installer...
Sent from my Moto Z2 Play using XDA Labs
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Have these steps worked for me...
1.)Flash TWRP using Fastboot
2.)Go to TWRP/Settings and open Terminal.
3.)Run both of following commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
Click to expand...
Click to collapse
4.)Flash Magisk-v17.1.zip
5.)Repeat step 2 and 3 dont wipe.
6.)Start
NOTE: before Reinstall stock or uninstall Magisk.
I did the Junior Passos method of doing the backup, and everything is working like a charm.
Cupcake 1.5 said:
Strange, I have zero magisk problems when using the latest stock rom. Flash in twrp, done, no issues. However, it could be because I first back up boot and system and then restore them with twrp before rooting(this removes encryption).
Click to expand...
Click to collapse
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
OldUncle said:
Hi, Could you please, tell me which stock ROM you are using and where is possible to get it?
First time I am having problem with Magisk, never had on other phones.
Problem = Bootlop
Click to expand...
Click to collapse
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Perfect!
Thank you very much!
The only solution which worked!
Finally I got full control on my Z2 Play.
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
Regarding backup, this is done through the stock ROM correct (Settings --> System --> Backup to Google Drive).
Thanks,
smithmal
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
This worked perfectly on my Moto Z2 XT1710-06 with Oreo 8.0 when no other options worked.
Flash or Boot into TWRP
Backup System and Boot partitions in TWRP
Restore System and Boot Partitions in TWRP (note I had to enable R/W access in TWRP to restore the system partition)
Flash Magisk-v19.3.zip
Reboot
That is it. Now Rooted and passes all SafteyNet test. No more restricted apps. Even Google Pay now works.
Thank You.
sick
Cupcake 1.5 said:
It's not what rom but, how you do it. When on stock ROM, it is encrypted so you must first back up system and boot and then immediately restore them, this remove encryption. Now flash magisk and it will work.
Click to expand...
Click to collapse
your method worked like charm, thanks alot man
T-Mobile V30 H932 20P Stock Collection
Based on OEM 20P KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
Latest Magisk Zip (if performing clean flash)
no-verity-opt-encrypt
rctd remover
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
Bootloader: 20p Stock Bootloader ONLY
FullStock: Full 20p Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
FullStock w/Magisk: Full 20p Stock Firmware + Magisk Root - Instructions in Section B
Debloated w/Magisk: Boot+Debloated System + Magisk Root (force enc & dm-verity removed) - Instructions in Section C
StockLAF: Individual LAF image for returning to stock DL mode
Global Instructions
Always make a backup first
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
If coming from Nougat, Clean Flash is Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo versions, Dirty Flash works fine. OS and Apps are updated.
Copy All Zips to SDCard
Flash h932_FullStock.zip
Flash Magisk
Flash no-verity-opt-encrypt
Flash rctd remover
Reboot to system and install Magisk Manager (if not installed)
B - FullStock with Magisk
This zip just cuts out the step of flashing magisk manually.
This zip should be dirty flashed on a system that already has magisk. or Magisk may not flash successfully
If this zip is clean flashed, pay close attention to flash logs. If magisk fails to repack the boot image during flash, flash Magisk again.
Flash h932_FullStock_Magisk.zip
Flash no-verity-opt-encrypt
Flash rctd remover
Wipe Dalvik+Cache
Reboot
C - Debloated with Magisk
Be aware
This ROM does NOT flash LAF, recovery, bootloader or modem firmware directly.
If you are coming from an older version of android, this rom does not include the complete device firmware, which you may want.
For those included above, you should flash FullStock before flashing this to make sure all of your device firmware is up to date.
Boot image has been patched to remove force encryption and dm-verity
This ROM has had several pre-loaded and system apps removed. If someone wants to send me a list of any additional apps that can be safely removed, i can update the rom to include them.
system/app/CloudPrint
system/app/Drive
system/app/Duo
system/app/EditorsDocs
system/app/EditorsSheets
system/app/Gmail2
system/app/GooglePay
system/app/LGAccount
system/app/LGAirDrive
system/app/LGAmazonAssistant
system/app/LGAmazonAttribution
system/app/Maps
system/app/Music2
system/app/Photos
system/app/YouTube
system/priv-app/CloudHub
system/priv-app/CollageWallpapers
system/priv-app/facebook-installer
system/priv-app/LG360VideoWallpaper
system/priv-app/LG360Wallpaper
system/priv-app/LGEasyHome
system/priv-app/LGEmail
system/priv-app/LGExchange
system/priv-app/LGQHelpService
system/priv-app/LGVVM
system/priv-app/NameID
system/priv-app/TMO_MyAccount
system/priv-app/xtra_t_app
system/vendor/app/facebook-appmanager
system/vendor/overlay/com.lge.easyhome
system/vendor/overlay/com.lge.email
system/vendor/overlay/com.lge.exchange
system/vendor/overlay/com.lge.lgworld
system/vendor/overlay/com.lge.qhelp
system/vendor/overlay/com.lge.qhelp.application
system/vendor/overlay/com.lge.qmemoplus
For best results a clean flash is recommended for this package
Format data, and remove any apps installed to external sd. Then wipe system, dalvik, cache, data, internal storage
This will ensure no lingering apps are left behind.
If coming from Nougat, Clean Flash is Highly Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo Versions
Wipe Dalvik, Cache, and System, and optionally data and internal storage
If you do not perform a clean flash, you may need to manually remove the apps left behind after flashing
Flash h932_Debloated_Magisk.zip
Reboot
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge
Bootloader - md5:45d8897c317b2e2e7b02d0766a93556c
FullStock ROM - md5:092585a169b54f067cec27d57b0c041c
FullStock w/Magisk - md5:6854a34ed956e9b30fb8e59c34de6b39
Debloated w/Magisk - md5:5a11334c8e42dfe55f2a71bbb0820612
StockLAF - md5:9090ee8645f2018c6bd88c9169c52c1b
*************************************************************************************************************
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
Packages have been successfully tested VIA the methods outlined above.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h93220p, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/20p/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: 20p KDZ
Version Information
Status: Stable
Created 2018-12-20
Last Updated 2018-12-28
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Verify that you did download "h93220p_fullStock_wMagisk.zip". It worked fine for me, and I can confirm it has magisk as I was on 17.3 on 20o and magisk manager says I'm on 18.
Also, were you coming from 20o?
[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
Yes, I can make a debloated ROM. Gimme a day or two and I'll try to add one to the OP.
Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Sorry M8, but i tested this zip and verified that it flashes all partitions and then flashes magisk all in one go. I think maybe you downloaded the package without magisk by mistake.
This zip does not flash LAF, so if you had TWRP on LAF before flashing this, you should be able to just boot to download mode using the usb cable and reflash TWRP to recovery.
Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed
Click to expand...
Click to collapse
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP
weakNPCdotCom said:
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP
Click to expand...
Click to collapse
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.
Andi32790 said:
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.
Click to expand...
Click to collapse
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.
weakNPCdotCom said:
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.
Click to expand...
Click to collapse
No worries man I still have a phone plus thats why you all add the disclaimer. Idk just looking for a fix at this point.
[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM
Thanks weakNPCdotCom. I dirty flashed over 20o and it's working great.
weakNPCdotCom said:
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM
Click to expand...
Click to collapse
No worries take your time. Appreciate the work your doing
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
I just did it and didn't loose TWRP.
It worked thank you.
SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
Just pay attention to the flash logs and make sure everything flashes properly
[Cruzer] said:
No worries take your time. Appreciate the work your doing
Click to expand...
Click to collapse
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues
weakNPCdotCom said:
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues
Click to expand...
Click to collapse
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work
[Cruzer] said:
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work
Click to expand...
Click to collapse
I did remove chrome in the ROM so ill keep that in mind when I try again tonight. I don't think I'm going to deodex it either unless I get a smooth running build.. I'm not sure the advantage in oreo anyway since it's vdex now. but ill give it another go
I have to tell you :This is the first working TWRP I've found. This os not my work. Just sharing it in Redmi7 Recovery section.
It contains English and Chinese only.
Download link: https://mega.nz/#!TpojlSIA!ymMSB9wBHiza9kSAzqO-8idkuv5mRsvMXQ5rno4Z-so
Redmi 7 special edition TWRP Chinese and English modified optimization version
build date: 2019.4.20
modell: red rice 7, redmi 7
developer: wzsx150
team name: LR.Team
Installation:
Unlocked bootloader required
Working ADB and FASTBOOT connection required
The usually way: with fastboot flash recovery redmi7.img command
after successfully process do not restart the device
type fastboot reboot (do not press enter)
press and hold the volume up button
now press enter
press and hold the volume up button until the fresh TWRP starts
Quote from the Chinese website:
pre-brush into the third-party rec, must unlock the phone! ! Again, the brush machine is risky, please be cautious!
1. This rec supports data partition automatic decryption , encrypted data can be used normally under rec. The official system defaults to encrypting data partitions.
2. This rec supports the official full-page card swipe, but it may cover twrp; when upgrading automatically, you can remove the checkbox of the setting > auto-restart option for easy operation.
3. The bootloader must be unlocked to be able to brush into a third-party rec.
4. Built-in advanced > root system / clear root function.
5. Built-in advanced > remove dm checksum and cancel the forced encryption function, through certain operations, you can remove the official data forced encryption (understand people naturally understand how to operate, because avb2.0 exists, this function may not be normal).
6. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc. (some functions may cause the system to fail to enter, carefully operate).
刷入第三方rec前，必须解锁手机！！再次提醒，刷机有风险，操作请谨慎！
1.本rec支持data分区自动解密，加密的data不用格式化也能在rec下正常使用。官方系统默认是加密data分区。
2.本rec支持刷入官方原版全量卡刷包，但可能会覆盖twrp；自动升级时，可以去掉设置>自动重启选项的勾选，方便操作。
3.必须解锁bootloader才能刷入第三方rec。
4.内置高级>root系统/清除root功能。
5.内置高级>去除dm校验和取消强制加密功能，通过一定操作，可以去掉官方的data强制加密（懂的人自然懂怎么操作，因为avb2.0的存在，该功能可能不正常）。
6.防止被官方rec覆盖的功能：root系统、签名boot、去除dm校验、取消强制加密等（部分功能可能导致进不去系统，慎重操作）
Source: http://www.miui.com/thread-23429227-1-1.html
Do not forget! And be aware of it! No one has commanded you to change your phone!
No one has forced you to do this. So, you take every step at your own risk! Full responsibility lies with you!
Awesome! Thank you so much! You Rock!
I installed and works!
MalyMikrus said:
I installed and works!
Click to expand...
Click to collapse
Of course it works. If it wasn't working, I wouldn't have shared it.
JulianJenner said:
Of course it works. If it wasn't working, I wouldn't have shared it.
Click to expand...
Click to collapse
have u try rooting the phone with this twrp?
Yepp. My MIUI Stable is rooted now.
But, after Magisk19.zip you need a DmVerityForcedEncrypt.zip too!
https://mega.nz/#!6xpgQazL!RZALbnhhR8xEiri_7ljivVBZd2RhZYbQSmWd-tTgwtc
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Thanks !, I have to wait 15 days to unlock the bootloader, and try the twrp with miui eu, do you know if any developer is working in any kernel or rom? Regards!
JulianJenner said:
Yepp. My MIUI Stable is rooted now.
But, after Magisk19.zip you need a DmVerityForcedEncrypt.zip too!
https://mega.nz/#!6xpgQazL!RZALbnhhR8xEiri_7ljivVBZd2RhZYbQSmWd-tTgwtc
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Click to expand...
Click to collapse
This wasn't needed for me.
I just fastboot flashed the twrp.img file, rebooted into recovery mode (aka TWRP), and then flashed the Magisk v19 zip file.
rebooted and magisk was installed properly, twrp is installed properly
Okay. That is good!
I think zip is needing if you flash stock miui rom, with this twrp...
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Can you post the dt and source please?
Dev.Team is the chinese LR.Team.They never give out information. Neither device tree nor other...they never share it.
I've mentioned source, where I found it (on first thread).
This is not my work, I just shared.
This is Recovery section of Redmi7. ...and this is a Recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
JulianJenner said:
Dev.Team is the chinese LR.Team.They never give out information. Neither device tree nor other...they never share it.
I've mentioned source, where I found it (on first thread).
This is not my work, I just shared.
This is Recovery section of Redmi7. ...and this is a Recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Click to expand...
Click to collapse
yea, but to publish a thread in this 'development' section, you need to follow XDA rules, which means the source code has to be published as well
Ok.
I thought this recovery is an important thing for Redmi7 users...
If not...okay...delete this thread...or move to an indifferent section. No problemo...
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
how can I flash stock recovery?? Where i can find stock recovery?
IczYn said:
how can I flash stock recovery?? Where i can find stock recovery?
Click to expand...
Click to collapse
On every stock ROM zip and on every stock TGZ file...
JulianJenner said:
On every stock ROM zip and on every stock TGZ file...
Click to expand...
Click to collapse
OK but why when i try download stock rom i cant do this?
Thread closed on OP's request.
LTT