Related
can someone please upload the stock "install-recovery.sh"?
It's located in /system/etc.
I forgot to backup it, while rooting the device.
I need it for the OTA updates.
thanks
@vel_tins
Do not flash the ota if you are rooted, you might get bootloop. Full unroot your device before attempting to update. Anyhow, the ota will most likely fail since you already modified your system partition. Your best option is to unroot your device and capture the ota link, modify the ota updater-script and remove the lines that are showing "unexpected contents" errors. The original "install-recovery.sh" is still there, supersu renamed it to something like "/system/etc/install-recovery_original.sh". Keep in mind, you might loose your custom recovery if you renamed it back to "install-recovery.sh".
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
^^
??
vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
If you still have the original OTA zip, can you please post it for future reference?
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
pawitp said:
If you still have the original OTA zip, can you please post it for future reference?
Click to expand...
Click to collapse
No problem
pawitp said:
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
Click to expand...
Click to collapse
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
vel_tins said:
No problem
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
Click to expand...
Click to collapse
On TWRP, try running "find /dev/block/platform" and see if anything is created there.
The directory should have been populated by init. See https://android.googlesource.com/pl...0ab94b7d5a888f0b6920b156e5c6a075fa0741a^!/#F0.
That code should also be in TWRP, but something might have prevented it from working properly on this device. You might find some clues in dmesg or TWRP's logs.
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
vel_tins said:
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
Click to expand...
Click to collapse
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Personally, I prefer the "by-name" mapping rather than the "/dev/block/mmcblk0p" because it is harder to make mistakes if you use a name. With numbers, if a wrong number is typed, then you might end up flashing the wrong partition and bricking the device.
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
Hi sir ,
Please share to us , how you do this , because I have status 7. Install-recovery.sh problem
I have stock recovery , and I'm only make a root for my device by kingroot .
Please share update.zip file and tel me how to make ota update
pawitp said:
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Click to expand...
Click to collapse
Exactly this is the point...
pawitp said:
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
Click to expand...
Click to collapse
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
So how you made this ota update after all ?
theeteempire said:
So how you made this ota update after all ?
Click to expand...
Click to collapse
OTA doesn't work with rooted devices.
Do a full un-root and try again.
vel_tins said:
OTA doesn't work with rooted devices.
Do a full un-root and try again.
Click to expand...
Click to collapse
I did it , full unroot , I couldn't update even that with full-unroot , I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device !!!
can you help me please !!!!!
theeteempire said:
....I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device...
Click to expand...
Click to collapse
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
vel_tins said:
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
Click to expand...
Click to collapse
So I need the stock install-recovery. Sh ,.
Are you have it ?
vel_tins said:
Exactly this is the point...
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
Click to expand...
Click to collapse
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
If you know C, you might want to try mucking around in system/core/init/devices.c and see why it's behaving that way.
pawitp said:
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
.....
Click to expand...
Click to collapse
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
vel_tins said:
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
Click to expand...
Click to collapse
From my experience, you can't rely too much on Google for ROM development. I've found the flag by reading the source file I've previously mentioned.
Sent from my Nexus 4 using XDA Free mobile app
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
same here. anyone please help us
quiks11ver said:
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
Click to expand...
Click to collapse
delete unneeded system apps from /system/app/ then reboot and try again
simms22 said:
delete unneeded system apps from /system/app/ then reboot and try again
Click to expand...
Click to collapse
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
quiks11ver said:
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
Click to expand...
Click to collapse
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
simms22 said:
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
Click to expand...
Click to collapse
Hi, jus a simple question..will my phone be wiped?
quiks11ver said:
Hi, jus a simple question..will my phone be wiped?
Click to expand...
Click to collapse
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
simms22 said:
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
Click to expand...
Click to collapse
Ty simms22, i just realise my phone has no supersu, but quite odd, kernel auditor works haha...using elite kernel, i may flash later and try
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
quiks11ver said:
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
Click to expand...
Click to collapse
2.46 is very old now, you want 2.65 or above. google SuperSU 2.65, and you'll get it.
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
quiks11ver said:
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
Click to expand...
Click to collapse
wtf? lol! you can try to start over and reroot. thats what i would recommend, and its probably the right thing to do as well.
How to reroot? I oledi reflash but still cant
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
quiks11ver said:
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
Click to expand...
Click to collapse
what kernel are you trying? try elementalx.
---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------
oh, BTW, reroot = flash factory image via fastboot, flash twrp via fastbpot as well. then flash SuperSU 2.65 and boot up.
i'm using elite kernel, what is factory image?? i'm kind of a newbie just unlocking and rooting watching youtube videos. please help me!!
where can i find factory image??
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
quiks11ver said:
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
Click to expand...
Click to collapse
factory images https://developers.google.com/android/nexus/images?csw=1#yakju
you have a nexus 6, so you need a factory image for shamu
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
x-530 said:
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
Click to expand...
Click to collapse
delete whatever system apps you don't need from /system/app/ then reboot. it will clear up enough space. google did that on purpose, made it read that its full, this will clear up the space.
After flashing Marshmallow update, I'm cannot mount /system while in recovery mode (I have tried TWRP 3.0 and also 2.8.6.1 with no luck).
The main dissapointment with this is I can't flash any ZIP while in recovery.
I have tried to reflash Marshmallow update with no luck.
Any help will be appreciated!
bartito said:
After flashing Marshmallow update, I'm cannot mount /system while in recovery mode (I have tried TWRP 3.0 and also 2.8.6.1 with no luck).
The main dissapointment with this is I can't flash any ZIP while in recovery.
I have tried to reflash Marshmallow update with no luck.
Any help will be appreciated!
Click to expand...
Click to collapse
reinstall twrp
suljo94 said:
reinstall twrp
Click to expand...
Click to collapse
Reinstalled from fastboot but no luck.
When I click Mount -> System from TWRP recovery (2.8.6.1 / 3.0.0) nothing happens.
I have also connected using adb to the watch in recovery and tried to manually mount /system but a error is triggered
Code:
mount: no se puede encontrar /system en /etc/fstab o /etc/mtab
Appreciate if you are in Android 6 and you can reboot bootloader then try to mount /system
bartito said:
Reinstalled from fastboot but no luck.
When I click Mount -> System from TWRP recovery (2.8.6.1 / 3.0.0) nothing happens.
I have also connected using adb to the watch in recovery and tried to manually mount /system but a error is triggered
Code:
mount: no se puede encontrar /system en /etc/fstab o /etc/mtab
Appreciate if you are in Android 6 and you can reboot bootloader then try to mount /system
Click to expand...
Click to collapse
okee did you boot the watch in mm
suljo94 said:
okee did you boot the watch in mm
Click to expand...
Click to collapse
Yes
Device boots up, but I can't root it...
bartito said:
Yes
Device boots up, but I can't root it...
Click to expand...
Click to collapse
try systemless root from chainfire I think they changed permissions
suljo94 said:
try systemless root from chainfire I think they changed permissions
Click to expand...
Click to collapse
Also doesn't works.
I think this is due to the /system FS is now formated on squashfs 8-/
bartito said:
Also doesn't works.
I think this is due to the /system FS is now formated on squashfs 8-/
Click to expand...
Click to collapse
That's exactly it. Twrp fstab will have to be updated to support both ext4 and squashfs for system.
bartito said:
Also doesn't works.
I think this is due to the /system FS is now formated on squashfs 8-/
Click to expand...
Click to collapse
when you are correct you are correct it seems twrp cant handle it but it still seems weird because other deevices don't have the error
@Dees_Troy
suljo94 said:
when you are correct you are correct it seems twrp cant handle it but it still seems weird because other deevices don't have the error
@Dees_Troy
Click to expand...
Click to collapse
yes, yes, due to that I appreciate if some people that has installed the update can't try to mount /system in recovery.
Thanks!
bartito said:
yes, yes, due to that I appreciate if some people that has installed the update can't try to mount /system in recovery.
Thanks!
Click to expand...
Click to collapse
could you drop the recovery log my boss is starring at me weird I hava a watch constantly rebooting and is vibrating so I cant flash ir boot recovery anymore (keeps going away)
I'm not quite sure the syntax twrp is expecting to be able to handle partitions of multiple types. My watch is supposed to get here on Saturday. So if no one has released a patched version by then, I'll take a look at trying to figure out how to make it work.
---------- Post added at 07:45 PM ---------- Previous post was at 06:56 PM ----------
@bartito
So I don't have a watch yet, but I hacked up this twrp image. Not sure if it works though...
http://www.mediafire.com/download/zkn0wwh454x037f/twrp-3.0.0-0-bass+squashfs.img
That twrp image works, but the current supersu (nor the current beta for MM) seems to be working. The systemless root (new beta from chainfire) at least installs supersu in the app list, but it crashes on execution.
heffe2001 said:
That twrp image works, but the current supersu (nor the current beta for MM) seems to be working. The systemless root (new beta from chainfire) at least installs supersu in the app list, but it crashes on execution.
Click to expand...
Click to collapse
The only difference between the regular supersu and the "wear" supersu is the apk is deleted. So using the latest stable, 2.65, and just deleting /data/SuperSU.apk afterwards, it should work.
rbox said:
I'm not quite sure the syntax twrp is expecting to be able to handle partitions of multiple types. My watch is supposed to get here on Saturday. So if no one has released a patched version by then, I'll take a look at trying to figure out how to make it work.
---------- Post added at 07:45 PM ---------- Previous post was at 06:56 PM ----------
@bartito
So I don't have a watch yet, but I hacked up this twrp image. Not sure if it works though...
http://www.mediafire.com/download/zkn0wwh454x037f/twrp-3.0.0-0-bass+squashfs.img
Click to expand...
Click to collapse
Can you do one for lenok please? Were facing the same issues...
miffymiffy said:
Can you do one for lenok please? Were facing the same issues...
Click to expand...
Click to collapse
Done. Posted in the lenok thread.
rbox said:
Done. Posted in the lenok thread.
Click to expand...
Click to collapse
where is the lenok thread? THx
bartito said:
where is the lenok thread? THx
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-w...recovery-twrp-2-8-4-0-touch-recovery-t3001890
rbox said:
The only difference between the regular supersu and the "wear" supersu is the apk is deleted. So using the latest stable, 2.65, and just deleting /data/SuperSU.apk afterwards, it should work.
Click to expand...
Click to collapse
Hello,
Tried your modified TWRP (thanks in advance).
It is mounting system image (but only in readonly mode).
Supersu is installing, but even if I delete the supersu.apk after the first boot, isn't working at all and the "su" command is blocked.
bartito said:
Hello,
Tried your modified TWRP (thanks in advance).
It is mounting system image (but only in readonly mode).
Supersu is installing, but even if I delete the supersu.apk after the first boot, isn't working at all and the "su" command is blocked.
Click to expand...
Click to collapse
Well it looks like my watch is on track to arrive on Saturday, so unless someone else looks at it before then, I'll hopefully figure something out this weekend. system will always be readonly because they switched to squashfs, which is a readonly filesystem.
(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!.
My Magisk does not mount the system in RW, when the system changes, the smartphone hangs. Smartphone BQ Aquaris X Android 7.1.1
Xtriel said:
My Magisk does not mount the system in RW, when the system changes, the smartphone hangs. Smartphone BQ Aquaris X Android 7.1.1
Click to expand...
Click to collapse
It's systemless. Make /system changes in recovery. You can use twrp file manager to edit things in /system or /oem
madbat99 said:
It's systemless. Make /system changes in recovery. You can use twrp file manager to edit things in /system or /oem
Click to expand...
Click to collapse
So it's not a bug?
And yes i use TWRP File manager
I have the some problem. I mount system rw in esexplore and when i change some file i have info system is ro, or systemui crash.
koko115 said:
I have the some problem. I mount system rw in esexplore and when i change some file i have info system is ro, or systemui crash.
Click to expand...
Click to collapse
Well that is kinda strange. You should be able to change things since you have root, but some devices do tend to lock up changing certain files while the system is running. Depending on the file of course.
For instance,y moto e4 locks up if I modify anything in /oem. So I have to do it in recovery.
I also have this problem on my Lenovo TAB 4.
When I remount /system to rw, android hangs/freezes and only thing that unfreeze my device is power button reboot.
Can someone help me with that?