Hi guys
if anyone is interested in testing out this boot image i created for my c636b172
removes all encrypt, perfect mounting options for all partitions (this took a while to figure since some caused bootloops)
also reduced voltages for wifi module (may be unstable, if anyone has problems let me know i can try and adjust, otherwise if im not getting problems ill just keep decreasing it)
how to install
1. make sure twp is installed
2. in data/dalvik-cache delete arm and arm64 folders.
3. boot into twrp > wipe cache and dalvik
4. flash the boot image in twrp (flash image select image flash to boot)
5. if you had su installed, flash the zip again
6. go to wipe cache and dalvik again (just in case)
7. reboot and enjoy, theoretically should be slightly faster, and less overhead.
Download
https://www.dropbox.com/s/msda9a3smy9lqb4/modBootv2.img?dl=0
if anyone has a request for their specific boot image let me know and ill add the same values.
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
audioralf said:
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
Click to expand...
Click to collapse
i think DT2W is disabled, no flags of it in the boot image, you can try this guide.
https://forum.xda-developers.com/mate-9/how-to/enable-double-tap-to-wake-mate-9-t3580764
the boot image is for the c636, im not sure if you can flash it on another base you can try just have a stock boot.img handy
or to be safe you can send me your boot.img and ill edit it the same.
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
audioralf said:
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
Click to expand...
Click to collapse
no, twrp 3022 doesnt have MTP access right now.
Thank you for the info.
Which advantage is on daily usage. I guess I would have to install supersu again, for it modifies the boot.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
ante0 said:
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
Click to expand...
Click to collapse
ill try this
always thought it didnt work since it worked fine in 303
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
xjeepnsk said:
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
Click to expand...
Click to collapse
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
ante0 said:
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
Click to expand...
Click to collapse
Hi ante0,
I succeeded, Thank you so much
Hello sir,
My mate 9 stuck in boot loop....
And I can't access to recovery too
Can u make scatter file for mate 9 to fix boot loop
Related
Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
I also included the recovery for the SDMerge and also a linux script. Sorry, but the archive is too big to post it here on xda so i had to upload it on 4shared.
Requirements:
1) Rooted phone (obviously!!)
Instuctions Windows:
1) Download the package from 4shared
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
Instructions Ubuntu/Debian/Mint:
1) Download the package from 4shared
2) Extract it
3) Make sure you have the sdk properly installed with adb (if not check here: http://forum.xda-developers.com/showthread.php?t=2100673 )
4) Run the script by typing
Code:
./CWM-Installer.sh
5) Enjoy the new recovery
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /data/local/recovery.img
or if you want the recovery for the SDMerge just replace:
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
with this:
Code:
Files\adb push Files\SDmergerecovery.img /data/local/recovery.img
And then run the script again.
Feel free to post comments!!
Download here:
http://www.4shared.com/archive/8HmnogYQ/CWM-Installer-E400tar.html
wow, long time no see...
keep it up buddy
yayakuya said:
wow, long time no see...
keep it up buddy
Click to expand...
Click to collapse
Thanks yaya, I was busy with work and home and I haven't internet at home so I can't download the huge GBs of a repo.
Works like said great job keep it up buddy!
Cobmaster said:
Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
Requirements:
1) Rooted phone (obviously!!)
Instuctions:
1) Download the attachment
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
IT DOESN'T WORK WITH SDMerge MOD!!!
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /mnt/extra-sd/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /mnt/extra-sd/recovery.img
And then run the script again.
Feel free to post comments!!
Click to expand...
Click to collapse
i created a flashable zip for the recovery her it is please thank me.:good:
jeffreyvh said:
i created a flashable zip for the recovery her it is please thank me.:good:
Click to expand...
Click to collapse
I used the script written a long time ago for who has only the device rooted but hasn't the recovery installed... Btw good job!
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
andwie said:
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
Click to expand...
Click to collapse
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Cobmaster said:
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Click to expand...
Click to collapse
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
andwie said:
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
Click to expand...
Click to collapse
Here it is, to flash it use my script replacing the recovery.img with the one attached and report if it works or not.
Btw, are you sure that the "/data" partition is ext4? Because if it's wrong the recovery doesn't mount it.
Very sorry for the very late reply, I just had the time to test your new recovery (I had to create flashable zip for it since the script didn't work) and it work perfectly.
Now we have alternative to increase data partition without having to edit apps like gellmar's StockMergE400, means it will be compatible with all stock-based rom :victory:
Thanks again @Cobmaster :good:
Don't worry about it. It's very pleasing to see that it works.
hi!
@Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
dricoarmani said:
hi!
@Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
Click to expand...
Click to collapse
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Cobmaster said:
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Click to expand...
Click to collapse
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Axims said:
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Click to expand...
Click to collapse
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Cobmaster said:
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Click to expand...
Click to collapse
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
lomax84 said:
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
Click to expand...
Click to collapse
only use gellmar recovery, because it is fixed for sdmerge
kien_vip said:
only use gellmar recovery, because it is fixed for sdmerge
Click to expand...
Click to collapse
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
lomax84 said:
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
Click to expand...
Click to collapse
it contain in step 2 or you can see it on some sdmerge rom
Has anyone been able to get adaway to work on N with su2. 70? It loads, gets root, tries to copy host files.. Then says "host files cannot be copied".. Select target directory. What is the target directory for N?
I'm on su2.69 and it worked just fine
chapelfreak said:
I'm on su2.69 and it worked just fine
Click to expand...
Click to collapse
I flashed this to get on N.. http://forum.xda-developers.com/nexus-6/general/android-n-preview-npc56p-twrp-recovery-t3332599 is this what you used?
Same error here - with latest TWRP, SuperSU 2.70, and elementalX kernel 4.01... :/
There is a flashable zip for usage with systemless root in the adaway Thread, flash that one too and everything is fine.
Edit: this file https://www.androidfilehost.com/?fid=24438995911977059
Gesendet von meinem Nexus 6 mit Tapatalk
It needs Busybox for mine to work.
kwdan said:
I flashed this to get on N.. http://forum.xda-developers.com/nexus-6/general/android-n-preview-npc56p-twrp-recovery-t3332599 is this what you used?
Click to expand...
Click to collapse
I took the ota pushed to me from marshmallow.
Same thing here Adaway doesn't work.
I installed android N with the beta enrollment OTA.
I Used the SuperSU 2.70 AutoRoot, then install Adaway and then busybox; not working :/
bluetigger68 said:
There is a flashable zip for usage with systemless root in the adaway Thread, flash that one too and everything is fine.
Edit: this file https://www.androidfilehost.com/?fid=24438995911977059
Gesendet von meinem Nexus 6 mit Tapatalk
Click to expand...
Click to collapse
Thank you... Working perfectly now. I never knew how many ads were on this phone.
Dreadk said:
Same thing here Adaway doesn't work.
I installed android N with the beta enrollment OTA.
I Used the SuperSU 2.70 AutoRoot, then install Adaway and then busybox; not working :/
Click to expand...
Click to collapse
same steps here.
tried with the zip to prep the OS and still no work
Work around for ad blocking on Android Preview 5 (latest NPD90G)
#Windows PC download the following:
'SuperSU' ("UPDATE-SuperSU-v2.76-20160630161323.zip") https://download.chainfire.eu/969/SuperSU/
MoaAB_ADBlocking_06082016_R1.zip http://forum.xda-developers.com/showthread.php?t=1916098
TWRP 3.0.0-1 from https://dl.twrp.me/angler/
Install Android N 7.0 NPD90G on Nexus 6P
reboot into bootloader (Power Button and Vol Down)
fastboot flash recovery twrp-3.0.0-1-angler.img <------ Download from TWRP (3.0.2 seems to always get stuck on TWRP splash screen)
#Boot to recovery
#if TWRP asks for a password to decrypt you will need to format userdata (THIS WILL FACTORY RESET YOUR PHONE!!!)
#ONLY do the following if you can not get directly into TWRP and are asked for a decrypt password
Reboot into bootloader
fastboot format userdata
fastboot format cache
#boot into TWRP recovery
Manually add the files you downloaded via Windows PC to Nexus 6P while in TWRP (put them in the / or /sdcard/Download directory *or a directory of your choice)
#Windows PC unzip MoaAB_ADBlocking_06082016_R1.zip and go MoaAB_ADBlocking_06082016_R1 > system > etc >
# There should be 2 files here hosts, and hosts.defaults
TWRP > Advanced > Terminal
cat /system/etc/hosts
#note that stock only the following should be displayed.
127.0.0.1 localhost
::1 ip6-localhost
# The following will copy the hosts file you got from MoaAB zip to /system/etc
cp /sdcard/Download/hosts /system/etc/
^ This is the 'hosts' file you downloaded from MoaAB previously
cat /system/etc/hosts
#output should be rather large now...
Reboot phone and test ad blocking on apps 'speedtest' is a good app to test on... No ad after speedtest ad blocking is working....
#profit
bluetigger68 said:
There is a flashable zip for usage with systemless root in the adaway Thread, flash that one too and everything is fine.
Edit: this file https://www.androidfilehost.com/?fid=24438995911977059
Gesendet von meinem Nexus 6 mit Tapatalk
Click to expand...
Click to collapse
Yes it work! perfect!!!
kwdan said:
Has anyone been able to get adaway to work on N with su2. 70? It loads, gets root, tries to copy host files.. Then says "host files cannot be copied".. Select target directory. What is the target directory for N?
Click to expand...
Click to collapse
Flash this in Recovery, Reboot Handy, Start Adaway: https://www.androidfilehost.com/?fid=24438995911977059
To get Adaway working in Android N, All you need to do is...
1. Install the Adaway apk
2. Flash this zip in TWRP, https://www.androidfilehost.com/?fid=24438995911977059
And that's it!!!
Don't **** around with updating SuperSU, or installing busybox, or any other suggestions made here.
CLOSE THREAD!
pr0ndigy said:
To get Adaway working in Android N, All you need to do is...
1. Install the Adaway apk
2. Flash this zip in TWRP, https://www.androidfilehost.com/?fid=24438995911977059
And that's it!!!
Don't **** around with updating SuperSU, or installing busybox, or any other suggestions made here.
CLOSE THREAD!
Click to expand...
Click to collapse
No mirrors found for that file on filehost.. Can you provide an alternative location please?
Edit: Link eventually worked after refreshing the page a few times..
I'm Just bumping this up so I don't have to make a new thread. The latest update seems to have broken this. The hosts file gets replaced automatically on reboot. Anyone else have this problem?
You're just genius! Works perfectly on Nexus 5X (NBD90W) without even formatting userdata (twrp 3.0.2-2)
Found another way. Mount system r/w in terminal or use root explorer after that adaway should work normally till next reboot.
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
Use mount-magisk.zip found in collection of modules thread and delete the folder via twrp in /magisk
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
zdimension said:
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Start reading the thread from the beginning and you'll find it.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Install "Uninstaller Mod Magisk" from TWRP. Then go in the TWRP terminal and type uninmod_magisk and follow the instructions.
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
nodio said:
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
Not working for me!
I will uninstall "Audio Compatibility Patch" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
dewois said:
Not working for me!
I will uninstall "Audio Compatibility Pach" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
tobi14 said:
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
Click to expand...
Click to collapse
If you have a current version of Magisk installed, yes you do. Enable viewing hidden files and folders in your file explorer. The dot at the beginning of the folder name means it's hidden...
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
mklee11224 said:
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
Click to expand...
Click to collapse
Thanks mate ! it worked like a charm !
just use "ls" command on step 3 after changing directory to mktmp , to show installed modules.:silly:
My Phone Specification : Moto X Play ------ 7.1.1 Stock Firmware -------- Squid kernel --------- rooted using Magisk ------ systemless xposed module "xposed_25" installed using magisk module(Uninstalled by this method !) .:victory:
Tanks a lot!
Crossbreeder lite made my phone unusable. Working fine again!
magisk.img not found in /data
This works like charm, if you can't find the magisk.img in `/data` check `/data/adb` ... I hope this work .
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
Own domain huh? Business growing? Hehehe I only came for the uninstall zip, hey quick question, I'm on a micro sd-less phone (big news), still a flashaholic, kinda, but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go? Thank you sir, you almost get more thanks than posts! Talk about reputation!
culiacanazo said:
Own domain huh?
Click to expand...
Click to collapse
I keep a few of them around. It was nice to finally find a good use for that one...
but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go?
Click to expand...
Click to collapse
Do you have to completely wipe the device? Or can you keep internal storage intact? If not, it sounds like you're out of luck.
Nice thread hijack, by the way... :laugh:
Didgeridoohan said:
Do you have to completely wipe the device?
Click to expand...
Click to collapse
Well i do a factory reset, flash system img and reboot, let it loop because it will, and then do a data format before it will boot, so system, caches, and data go... (Huawei, see)
Didgeridoohan said:
Nice thread hijack, by the way... :laugh:
Click to expand...
Click to collapse
I kinda stayed on topic didn't i? :crying:
You linked to your help guide which i read the beginning of that by the way has nothing to do with the help you offered to the op and reminded me of my struggles with a totally different device and problem!!
It's like how I'm related to my grandma's cousin's wife's sister's doctor's neighbor's son's friend, ain't it?
Sent from my Huawei Mate 10 Pro using XDA Labs
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Apply .disable_magisk
saturday_night said:
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Click to expand...
Click to collapse
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:41 PM ----------
neromanello said:
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
Click to expand...
Click to collapse
I need to know how to locate the mount point of my /cache partition at the stock recovery ADB Sideload. Then, to mount it, transfer the blank file to it, and then unmount /cache. I think it's an easy labor. So here my incomplete updater-script:
ui_print("Trying to make an script with ADB Sideload..."); CRLF
ui_print("Creating file to disable Magisk Modules..."); CRLF
I NEED THE MOUNT POINT HERE CRLF
ifelse package_extract_file(".disable_magisk", "/cache/.disable_magisk") == "t", ui_print("OK!"), ui_print("Failed!"); CRLF
UNMOUNT COMMAND HERE. CRLF
--last blank line--
So, I need to complete that, BUT things gets difficult when I need the update-binary for my Nougat 7.0 version, and to sign the whole .zip file in order my stock recovery recognizes it. I think this last thing could be made by this Thread. But really I don't know. Please help.
Thanks!.
TWRP 3.2.3-0 for Moto Z2 Play (albus)
Latest TWRP changelog :
3.2.3-0 full changelog
Working/Bugs :
I have just basically tested and all seems to be working (including decryption of /data and mount External SDCard).
Installation Guide :
Make sure you have unlocked bootloader.
Reboot to bootloader and install.
Use command: fastboot flash recovery twrp-3.2.3-0-albus.img to install.
Download Link :
twrp-3.2.3-0-albus.img
How to use TWRP for first time:
1- Unlock Bootloader (search in Google how to do);
2- Flash TWRP via CMD and reboot recovery;
3- Boot in TWRP and allow permission to modify system (internal storage don't be accessible);
4- Go to Wipe > Format Data > type YES and swipe (you will see an error formatting data);
5- Back to TWRP Menu, go to Reboot and Recovery;
6- In TWRP, go to Wipe > Format Data > type YES and swipe again (TWRP will decrypt internal storage);
7- Reboot to TWRP one more time and internal storage will be accessible;
8- DONE!!!
How to Root Stock Oreo:
1- Boot in TWRP;
2- Go to Backup > mark Boot and System partition > Swipe to backup (don't needed system_image);
3- After this, go to Restore > select Boot and System > Swipe to restore;
4- After finished, install zip Magisk (17.1 or 17.3);
5- Reboot and DONE!!!
You don't need flash F2FS zip and too don't need any command in the terminal.
You don't need to do anything else!
Click to expand...
Click to collapse
Credits :
@Junior Passos
Thanks so much to @Dees_Troy, @Santhosh M and @vache.
:highfive:
Thanks for this Junior. I've installed it and works. Over wrote the previous ver so didn't have to format data. Finally able to make a backup straight to the sdcard.
Thanks,i had temporarily boot TWRP 3.2.0.I'm now able to mount internal and external sd-card.New TWRP successfully decrypt my data partition.I have installed magisk and it works now.Many many thank
I cannot backup any partition on micro sd card, it's only saying "updating partition details..."
Borchuck said:
I cannot backup any partition on micro sd card, it's only saying "updating partition details..."
Click to expand...
Click to collapse
SD Card in TWRP works without no problem.
i try to boot & try to flash in xt1710-06 but just say
fastboot boot twrp-3.2.0-0-albus.img
downloading 'boot.img' ...
and the device just get freeze... i need to press all buttons to restart....
and i try with twrp_3.1.1-0_albus.img
and is not possible get in twrp
Junior Passos said:
SD Card in TWRP works without no problem.
Click to expand...
Click to collapse
For me it shows nothing under the "Progress:" and I've tried two different sd cards.
Borchuck said:
For me it shows nothing under the "Progress:" and I've tried two different sd cards.
Click to expand...
Click to collapse
Hi,
Have you flashed TWRP or temporarily boot into TWRP ?
I have temporarily boot into TWRP,and the Backup stucks too
Gesendet von meinem Moto Z2 Play mit Tapatalk
Archerous said:
Hi,
Have you flashed TWRP or temporarily boot into TWRP ?
I have temporarily boot into TWRP,and the Backup stucks too
Gesendet von meinem Moto Z2 Play mit Tapatalk
Click to expand...
Click to collapse
Yes, I have temporarily boot. Are you suggesting I should flash it? Anyway, thanks for help!
Borchuck said:
Yes, I have temporarily boot. Are you suggesting I should flash it? Anyway, thanks for help!
Click to expand...
Click to collapse
Dont flash it,if you not have the original recovery.img.Without original recovery,you cant update your phone via OTA
Gesendet von meinem Moto Z2 Play mit Tapatalk
Archerous said:
Dont flash it,if you not have the original recovery.img.Without original recovery,you cant update your phone via OTA
Gesendet von meinem Moto Z2 Play mit Tapatalk
Click to expand...
Click to collapse
Well, in fact, first what I've done after purchasing the phone was disable Updater.apk and unlocked bootloader -I don't care about OTA. I only want to know is this TWRP working well and could be used as a daily driver. If yes I would gladly flash it. All in all I could make recovery backup, right?
Borchuck said:
Well, in fact, first what I've done after purchasing the phone was disable Updater.apk and unlocked bootloader -I don't care about OTA. I only want to know is this TWRP working well and could be used as a daily driver. If yes I would gladly flash it. All in all I could make recovery backup, right?
Click to expand...
Click to collapse
Ok,then you can flash it.Or ask the OP with a pn
Gesendet von meinem Moto Z2 Play mit Tapatalk
Archerous said:
Ok,then you can flash it.Or ask the OP with a pn
Gesendet von meinem Moto Z2 Play mit Tapatalk
Click to expand...
Click to collapse
I've flashed it and it work absolutely great! Thank you so much.
One more question: can you tell me what is "System image" backup? I thought I have full system partition backup when I choose just "System" and "Data" if I want to store my settings and apps...
Borchuck said:
I've flashed it and it work absolutely great! Thank you so much.
One more question: can you tell me what is "System image" backup? I thought I have full system partition backup when I choose just "System" and "Data" if I want to store my settings and apps...
Click to expand...
Click to collapse
You don't have to backup the system image since stock images are available.
Please keep in mind that TWRP does not backup the extremely important /data/media folder. See also https://twrp.me/faq/backupexclusions.html. So I usually do the following: Via TWRP's terminal I move media to media2 and then backup the data partition. When the backup is finished I move media2 back to media (you also have to do that when you restore your backup obviously).
Borchuck said:
Yes, I have temporarily boot. Are you suggesting I should flash it? Anyway, thanks for help!
Click to expand...
Click to collapse
Temporary boot don't have successfull permissions to create system backup. For this, use permanent flash.
bear263 said:
Thanks for this Junior. I've installed it and works. Over wrote the previous ver so didn't have to format data. Finally able to make a backup straight to the sdcard.
Click to expand...
Click to collapse
Borchuck said:
I've flashed it and it work absolutely great! Thank you so much.
One more question: can you tell me what is "System image" backup? I thought I have full system partition backup when I choose just "System" and "Data" if I want to store my settings and apps...
Click to expand...
Click to collapse
I have the alternate TWRP installed.
Can I just flash this in fastboot and overwrite the other with no other steps needed?
pizza_pablo said:
I have the alternate TWRP installed.
Can I just flash this in fastboot and overwrite the other with no other steps needed?
Click to expand...
Click to collapse
Yes, it should overwrite previous one.
Borchuck said:
Yes, it should overwrite previous one.
Click to expand...
Click to collapse
Great, so I won't have to wipe anything, just carry on with a new version of TWRP?
pizza_pablo said:
Great, so I won't have to wipe anything, just carry on with a new version of TWRP?
Click to expand...
Click to collapse
If you've wiped in previous version then it's already done. You can start using this.
Borchuck said:
If you've wiped in previous version then it's already done. You can start using this.
Click to expand...
Click to collapse
Piece of mind is priceless!
Thanks, again!
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled.
Prerequisites:
Oneplus 8 Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <filename>
(with <filename> being the name of the recovery in the format of "recovery.img" you wish to flash)
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Step-by-step this would be:
Code:
cd /data/adb/modules
to change to the Magisk modules directory
Code:
ls
to list the content of this directory, each module has its own directory, usually with a well-recognizable name
Code:
rm -r <directory>
to delete the directory in question. Tip: in console TAB-autocomplete works
Downloads:
10.5.4 BA Recovery
Modified 10.5.4 BA recovery from GDrive
Original 10.5.4 BA recovery from Gdrive
10.5.5 BA Recovery
Modified 10.5.5 BA recovery from GDrive
Original 10.5.5 BA recovery from Gdrive
10.5.6 BA Recovery
Modified 10.5.6 BA recovery from GDrive
Original 10.5.6 BA recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Description of method to modify recovery by yourself:
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Thanks for this...
On fastboot we have to flash the modified recovery img?
EDIT : Nevermind haven't read the whole OP
I have a noob question: this won't affect data or magisk right?
To remove a module , command should not be :
( rm -rf < directory> ) ?...
cultofluna said:
To remove a module , command should not be :
( rm -rf < directory> ) ?...
Click to expand...
Click to collapse
Thanks for your comment, but technically no
The - f flag is used to omit prompts before each removal, which may or may not be helpful - depending in how sure the user is on what he does
I chose the safer variety in my example, confident that users with more knowledge can always look at the "rm" man page to decide what command they want to use...
But again thanks, I do appreciate your help!
HottieLinus said:
I have a noob question: this won't affect data or magisk right?
Click to expand...
Click to collapse
Correct, the recovery resides in a separate partition and flashing it doesn't do anything anywhere else.
In fact the recovery looks and behaves the same when booting into it, the change only becomes apparent by being able to use adb in recovery.
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
cultofluna said:
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
Click to expand...
Click to collapse
It should be possible as the recovery gives you full access to your file system and so, given you know what to remove/change, it should also be possible to recover from issues as you mentioned.
My problem: I have no idea where themes or substratum additions are installed directory-location wise, will need to research a bit. Or maybe someone else can chime in on this, then I could update OP with info on that as well...
Ok one more question..
Can we flash zips through the recovery?...
Via ADB sideload?.. maybe..
cultofluna said:
..Can we flash zips through the recovery?...Via ADB sideload?..
Click to expand...
Click to collapse
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Ok...
Because on pixel4 XL you can reboot to stock recovery and choose the the option ADB sideload...
And from there you can flash a custom ROM...etc..
Updated OP with 10.5.5 recovery..
s3axel said:
Updated OP with 10.5.5 recovery..
Click to expand...
Click to collapse
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Click to expand...
Click to collapse
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
cultofluna said:
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
Click to expand...
Click to collapse
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Burt Squirtz said:
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Click to expand...
Click to collapse
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
pyry666 said:
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
Click to expand...
Click to collapse
What an incredibly helpful response. Sorry but if there's something that'll decrypt and allow me to backup and recover, of course I'm going to try and find it. And I suspect most other people here would too.
Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
Click to expand...
Click to collapse
I don't know presently, usually I compare recoveries or I (or other users) add recoveries for other regions which they made by themselves. When recoveries are the same of course they can be used
RIght now I cannot download the 10.5.5 AA firmware (download aborts after some time), I'll add the recovery once this is working... EDIT: seems OP pulled the downloads, so no luck at the moment...
If there is a working twrp in China then perhaps it's worth making contact with them to see if either:
A) they can let you have it
B) they can help you fix this one?
It's presume the former would make the most sense, with permission I see no problem in obtaining it or linking it, certainly not taking about it. Makes no sense to just avoid an obvious assist whilst we all struggle without twrp.