Hello, i wanted to know if anyone can help me. I am trying to include a pre rooted magisk but it gives me an error like this:
Failed to unmount /system: No such volume script aborted (no error message)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Bootleggers Edited.zip'
my code (which i found online) to include magisk is this:
ui_print(" Installing Magisk Root...");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox", "unzip", "/tmp/magisk/Magisk-v18.1.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");
run_program("sbin/busybox", "sh", "tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/Magisk-v18.zip");
unmount("/system");
I personally think it's because of the busybox, i want to fix this. Just to confirm, I am editing the Bootlegger NOT to post online, it is just for me because i have to much spare time haha
Thanks in advance
RyzoModding said:
Hello, i wanted to know if anyone can help me. I am trying to include a pre rooted magisk but it gives me an error like this:
Failed to unmount /system: No such volume script aborted (no error message)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Bootleggers Edited.zip'
my code (which i found online) to include magisk is this:
ui_print(" Installing Magisk Root...");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox", "unzip", "/tmp/magisk/Magisk-v18.1.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");
run_program("sbin/busybox", "sh", "tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/Magisk-v18.zip");
unmount("/system");
I personally think it's because of the busybox, i want to fix this. Just to confirm, I am editing the Bootlegger NOT to post online, it is just for me because i have to much spare time haha
Thanks in advance
Click to expand...
Click to collapse
I fixed the error by now but it doesn't root. So it completed flashing and after launching and installing magisk manager, it said it isn't rooted
RyzoModding said:
I fixed the error by now but it doesn't root. So it completed flashing and after launching and installing magisk manager, it said it isn't rooted
Click to expand...
Click to collapse
Why are you doing this exactly?
Is it not just easier to flash a Magisk zip than going through all this trouble?
Or is this something you are merely interested in trying out because you are interested?
garylawwd said:
Why are you doing this exactly?
Is it not just easier to flash a Magisk zip than going through all this trouble?
Or is this something you are merely interested in trying out because you are interested?
Click to expand...
Click to collapse
Yeah it is indeed because i'm intrested haha i make apps die pc with c# and stuff and wanted tot try this as Well, i always rooted the wat you said forum 3 years, nut i just wanted tot start editing Roms with pre root and edited apps and stuff haha
No idea... Go ahead ?
Related
I have done my fare share of writing updater_scripts. For some reason i can not get twrp or cmw to flash a zip. I get no errors, it prints verything on the screen from th ui_prints and twrp gives me a sucessfull but when i reboot the cnages iv made are not there. i have attached 2 scripts tha i have tried so can someone take a look, but i really dont think my script is the problem. thanks to anyone that can help.
Not sure why... your scripts look fine... but could you try this mount instead...
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/system", "/system");
craigacgomez said:
Not sure why... your scripts look fine... but could you try this mount instead...
Code:
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/system", "/system");
Click to expand...
Click to collapse
thanks for the input! but no such luck on that one either. im at a loss on this one. It has to have something to do with the mounting, because the delete_recursive("/system/app"); is not even working.
So I have the asop 4.2.1 built with make otapackage but every time I try to install it using TWRP I get an error 7
What I did:
- built the ota
- deleted recovery folder
- flashed rom - got an error 7
Any tips on this? Thanks.
up?
try not deleting anything and flash again, there might be something in the install script that relies on it. for anything it tries to do there and wont find it will throw an exception and break the install. after you have your cause you can still worry about the recovery.
vomer said:
So I have the asop 4.2.1 built with make otapackage but every time I try to install it using TWRP I get an error 7
What I did:
- built the ota
- deleted recovery folder
- flashed rom - got an error 7
Any tips on this? Thanks.
Click to expand...
Click to collapse
vomer,
You have to remove these lines from '/META-INF/com/google/android/updater-script' file (in your ota zip).
Code:
package_extract_dir("recovery", "/system");
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
i.e, search 'recovery' in 'updater-script' and remove that line.
Okay so I am working on a custom rom and my first few attempts didn't copy anything into the /system so I decided to add the mount system into my updater-script-
I added the mount to system:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
but after flashing and grabbing a copy of the recovery.log I get the following error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
so I am wondering if something is wrong with the mount command or if something else could be wrong?
Any assistance will be appreciated
XxZombiePikachu said:
Okay so I am working on a custom rom and my first few attempts didn't copy anything into the /system so I decided to add the mount system into my updater-script-
I added the mount to system:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
but after flashing and grabbing a copy of the recovery.log I get the following error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
so I am wondering if something is wrong with the mount command or if something else could be wrong?
Any assistance will be appreciated
Click to expand...
Click to collapse
I'v got the same problem i tried to copy other roms updater scrips put it does not work too
XxZombiePikachu said:
Okay so I am working on a custom rom and my first few attempts didn't copy anything into the /system so I decided to add the mount system into my updater-script-
I added the mount to system:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
but after flashing and grabbing a copy of the recovery.log I get the following error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
so I am wondering if something is wrong with the mount command or if something else could be wrong?
Any assistance will be appreciated
Click to expand...
Click to collapse
These commands are correct actually... But are you following them with:
delete_recursive("/system");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
If you use the updater-script from my stock ATT rom as an example it should boot for you...
Also you need to make sure you have Loki in the script and rom itself...
VECTUS said:
These commands are correct actually... But are you following them with:
delete_recursive("/system");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
If you use the updater-script from my stock ATT rom as an example it should boot for you...
Also you need to make sure you have Loki in the script and rom itself...
Click to expand...
Click to collapse
I definitely have the delete recursive system followed by the extract system/data but I don't have the loki folder/commands for updater-script mainly because I don't know where to get them from/what is the command to run, when I get home I'll take a look at your updater-script and do what needs to be done(I don't want to be using other peoples scripts or files because I know some can get rather overprotective, so far I've been getting help from xdabbeb/bigfau but I don't want to have to ask for every little detail) thanks for the tip I'll update if anything good or bad happens
Sent from my potato d800
XxZombiePikachu said:
I definitely have the delete recursive system followed by the extract system/data but I don't have the loki folder/commands for updater-script mainly because I don't know where to get them from/what is the command to run, when I get home I'll take a look at your updater-script and do what needs to be done(I don't want to be using other peoples scripts or files because I know some can get rather overprotective, so far I've been getting help from xdabbeb/bigfau but I don't want to have to ask for every little detail) thanks for the tip I'll update if anything good or bad happens
Sent from my potato d800
Click to expand...
Click to collapse
Anything you want to use in that stock ROM is free to use. That's why I made it. The ROM includes loki with correct file structure. Loki install commands are at the end of the udater script in the ROM...
Edit. Lol I just remembered I threw in the data folder in the stock ROM as a place holder for apps etc. If you use the data command I'm your updater script you will need a data folder in the ROM but the data folder is not a must have for your ROM because it will be created anyway... The data folder is an old trick to load updated apks or system app Apks can be moved there to create more space for system/apps...
VECTUS said:
Anything you want to use in that stock ROM is free to use. That's why I made it. The ROM includes loki with correct file structure. Loki install commands are at the end of the udater script in the ROM...
Edit. Lol I just remembered I threw in the data folder in the stock ROM as a place holder for apps etc. If you use the data command I'm your updater script you will need a data folder in the ROM but the data folder is not a must have for your ROM because it will be created anyway... The data folder is an old trick to load updated apks or system app Apks can be moved there to create more space for system/apps...
Click to expand...
Click to collapse
The boot.img in your Rom is the 10d boot?
Yea I know about the data folder and I have it in to include some apps/others stuff and remove some of the system apps and use them as normal apps for greenify
Sent from my potato d800
hey @VECTUS after getting loki working(tested with some test splitwindow stuff I'm working on and in case you are wondering one of them force closes and renders the phone unusable while the other works but no apps show up so work in progress), I rebuilt my custom rom with new stuff(loki/kernel) and still get the mount failed in recovery, everything after the mount fails does it stuff extracting data/system, symlink and loki/boot flash(I don't see the recursive system delete in recovery.log), if you would like to take a look at the script/log let me know and i'll share a link for now I am taking a break because everything else I have made works(custom bootanimation/mods/etc) but the rom is a no go, in the last 2 days I've flashed like 15 different test and nothing if you have any insight please let me know
p.s. in your updater script you use the set_metadata/set_metadata_recursive, when I tried it I got a syntax error and changing it to set_perm/set_perm_recursive eliminates the error but then I get the /system is not a valid uid bla, bla, bla any thoughts on this?
XxZombiePikachu said:
hey @VECTUS after getting loki working(tested with some test splitwindow stuff I'm working on and in case you are wondering one of them force closes and renders the phone unusable while the other works but no apps show up so work in progress), I rebuilt my custom rom with new stuff(loki/kernel) and still get the mount failed in recovery, everything after the mount fails does it stuff extracting data/system, symlink and loki/boot flash(I don't see the recursive system delete in recovery.log), if you would like to take a look at the script/log let me know and i'll share a link for now I am taking a break because everything else I have made works(custom bootanimation/mods/etc) but the rom is a no go, in the last 2 days I've flashed like 15 different test and nothing if you have any insight please let me know
p.s. in your updater script you use the set_metadata/set_metadata_recursive, when I tried it I got a syntax error and changing it to set_perm/set_perm_recursive eliminates the error but then I get the /system is not a valid uid bla, bla, bla any thoughts on this?
Click to expand...
Click to collapse
Hey can you send me a link to your ROM? I have tomorrow to look at it... Just pm me...
I'm getting this exact same error with my SafeStrapped, GPE re-ROM'ed AT&T S4 (the one that Asurion had the nerve to replace a shattered first-gen Moto X of mine with) when attempting to take the Lollipop OTA from Joe-Tech's ROM... but then again, that's what you'd expect from a bootloader/recovery-locked device. Even so, it actually passes the verification stage... which is remarkable.
EDIT: I BOUGHT IT, FOR MORE INFO, PICTURES, SYSTEM IMAGES, APPS VISIT: Mod Edit: Link removed
Hi. In Turkey, Nokia Cares are closing. So we can find some interesting devices like this.
When I saw these pictures, I shocked. It is true and has newer firmware. So I wanted to buy this device and dump its firmware for our DS variant of X2. (I will upload all partitions images on here too)
It is about 200 US Dolar and I need donations for buying it. But I dont know how to get donations too.
I have basic skills for development with android. I worked with legendary HTC HD2 and I have developed a lot of things for this device. (You can see my works on androidforum.tytung.com , I am a moderator of this site too) I am a Google Play Developer too. (Named Av. Ali BEYAZ) So, I believe I can do more with this prototype.
I need your donations and waitin your replies. Thanks.
https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2306579
https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2306578
https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2306580
I bought it, thanks for donations. I will upload some photos with my standart nokia x2 soon.
Some pictures of it:
Interface & Menus:
I searched its product code on both Navifirm and Data Package Manager. But didnt find anything.
So I scare a bit for rooting, installing x2 ds's custom recovery.
I know, I should delete PackageVerifier.apk from system apps via adb first.
Anyone help me? Thanks.
symbuzzer said:
I searched its product code on both Navifirm and Data Package Manager. But didnt find anything.
So I scare a bit for rooting, installing x2 ds's custom recovery.
I know, I should delete PackageVerifier.apk from system apps via adb first.
Anyone help me? Thanks.
Click to expand...
Click to collapse
Yes bro...i wanted to tell you that..there is no firmaware availble on the Navifirm For that product code..
As my Exams are going on..i Forgot to tell you..soorry...
Now making changes and Porting will be a big problem as you camt recover....
As you bought it for 200US dollars its too costly..
As my X2 dual cost me..8000INR i.e. 133Us Dollar..
If you can exchange the device with dual sim variant it migjt be grt..
Or else Talk to nokia care for the Flash File..They migjt be able to provide you...
Another thing...You can try flashing the Recovery Of nokia X2...
If it doest work....then you cant only use the recorvery partition...The phone Can work..
This is my assumption....cant gaurantee any thing...
And can you Upload the Launcher.apk of Your variant...??
x2wolf said:
Yes bro...i wanted to tell you that..there is no firmaware availble on the Navifirm For that product code..
As my Exams are going on..i Forgot to tell you..soorry...
Now making changes and Porting will be a big problem as you camt recover....
As you bought it for 200US dollars its too costly..
As my X2 dual cost me..8000INR i.e. 133Us Dollar..
If you can exchange the device with dual sim variant it migjt be grt..
Or else Talk to nokia care for the Flash File..They migjt be able to provide you...
Another thing...You can try flashing the Recovery Of nokia X2...
If it doest work....then you cant only use the recorvery partition...The phone Can work..
This is my assumption....cant gaurantee any thing...
And can you Upload the Launcher.apk of Your variant...??
Click to expand...
Click to collapse
Thanks for your reply.
I tried to extract all system apps (because their versions newer than DS variant) via ADB but no luck without root permission
I have another X2 DS too. I bought this phone for community and research.
I know all risks.
Is there anyway dump recovery partition via fastboot like adb's dd command?
Can anyone upload Nokia X2 DS's original recovery?
Thanks.
You can get the Nokia X2 Ds stock and custom recovery here...
http://forum.xda-developers.com/devdb/project/dl/?id=10292&task=get
And for Rooting You can do it manually also..via adb..
Check this out..http://forum.xda-developers.com/showthread.php?t=2684210
Hope this help you..
Good Luck bro..
Thanks. Will try and post results soon
Can anyone from 4pda.ru forum help me for sign in to forum?
I want to write Nokia X2 DS topic in here: http://4pda.ru/forum/index.php?showtopic=582858&st=8500
I know you will see this message, I need your help. Thanks.
I researched some workarounds for installing custom recovery and root.
This is from original X2 DS recovery installer commands:
Code:
ECHO.
ECHO. Please Wait Installing Nokia X2 Custom Recovery.
ECHO. Device Will Reboot During Installation
Pause
"%~dp0adb\adb" reboot bootloader
"%~dp0adb\fastboot" -i 0x0421 oem unlock
"%~dp0adb\fastboot" -i 0x0421 flash recovery "%~dp0rec\custom.img"
"%~dp0adb\fastboot" -i 0x0421 oem unlock
"%~dp0adb\fastboot" -i 0x0421 reboot
ECHO Done Installing Nokia X2 Custom Recovery.
ECHO.
PAUSE
goto end
So I can flash recovery via same commands via fastboot:
Code:
fastboot -i 0x0421 oem unlock
fastboot -i 0x0421 flash recovery custom.img
fastboot -i 0x0421 oem unlock
After that I will flash flashable SuperSU by Chainfire from http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
But still PackageVerifier.apk installed which will bricks phone when any foreign apk installed to system/app folder. For removing it, I tried on my DS variant to run Aroma File Manager via PhilZ Touch custom recovery. But it couldnt run, gave error.
So I need a special PhilZ Touch flashable which removes system/app/PackageVerifier.apk and system/app/PackageVerifier.dex Can anyone help me for this script?
Note: I tried to run some codes on Philz Touch Recovery from DS variant to remove these files, My PC didnt recognize it like a adb device.
symbuzzer said:
But still PackageVerifier.apk installed which will bricks phone when any foreign apk installed to system/app folder. For removing it, I tried on my DS variant to run Aroma File Manager via PhilZ Touch custom recovery. But it couldnt run, gave error.
So I need a special PhilZ Touch flashable which removes system/app/PackageVerifier.apk and system/app/PackageVerifier.dex Can anyone help me for this script?
Note: I tried to run some codes on Philz Touch Recovery from DS variant to remove these files, My PC didnt recognize it like a adb device.
Click to expand...
Click to collapse
Hi! Try on your DS device delete package verifier.apk and package verifier.odex from system/app with Root Explorer and then install SuperSU. I am not 100% sure, so try on DS device firstly) BTW i posted your story on 4pda but no helpfull replies yet, can't post links so it is on page 425.
Can you try installing the following zip via CWM..
Hope it deletes the Package verify.apk.
Or else you can try using RootExplore..
Is sholuld be able to del the app without root permisson..
Just tell the result..
fenderstrc said:
Hi! Try on your DS device delete package verifier.apk and package verifier.odex from system/app with Root Explorer and then install SuperSU. I am not 100% sure, so try on DS device firstly) BTW i posted your story on 4pda but no helpfull replies yet, can't post links so it is on page 425.
Click to expand...
Click to collapse
Doesnt work without root permission
x2wolf said:
Can you try installing the following zip via CWM..
Hope it deletes the Package verify.apk.
Or else you can try using RootExplore..
Is sholuld be able to del the app without root permisson..
Just tell the result..
Click to expand...
Click to collapse
Code:
ui_print(" ******************* ");
ui_print(" Delete PackageVerifier.apk ");
ui_print(" By X2Wolf ");
ui_print(" ****************** ");
ui_print("Deletingfile files...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
delete("/system/app/PackageVerifier.apk");
delete("/system/app/PackageVerifier.odex");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Uninstall complete!");
Can you try this script? Code seems to work but, PhilZ Recovery a bit buggywith flashables.
symbuzzer said:
Doesnt work without root permission
Code:
ui_print(" ******************* ");
ui_print(" Delete PackageVerifier.apk ");
ui_print(" By X2Wolf ");
ui_print(" ****************** ");
ui_print("Deletingfile files...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
delete("/system/app/PackageVerifier.apk");
delete("/system/app/PackageVerifier.odex");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Uninstall complete!");
Can you try this script? Code seems to work but, PhilZ Recovery a bit buggywith flashables.
Click to expand...
Click to collapse
I dont think PhilZ Recovery Is buggy...
It work fine...it has only one problem that screen goes sometime Off While taking backup...rest is fine..
You can give it a try..for intallong the zip
I installed recovery and root succesfully.
I will upload system and kernel images on Monday
I need a simple deodexer too. Thanks for your help.
Superb Bro..
Will be waiting..
Thankxx Bro..
Video preview: https://www.youtube.com/watch?v=rF-DcEqpdxw
Partition Backup tool didnt work. So I could upload Philz Recovery Backup (system and boot partitions)
http://dosya.co/tl259xchfwsa/rm1014.zip.html
I have a problem in my install script and idk how to fix it to flash integrated kernel image from zip to rom. On my older galaxy mini 2 , this method worked. but now it fail. Maybe samsung has changed something, so please help me to figure out how to solve it. Here is how the flashing lines are looking:
Code:
mount("/dev/block/mmcblk0p16", "/dev/block/mmcblk0p15", "/dev/block/mmcblk0p3", "/system");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p16"),
delete("/tmp/boot.img"));
File gets copied on tmp but recovery log says: assert failed: write_raw_image.... ERROR 7
You're maybe using the wrong update-binary.
Check if you have the right zip for your model.
The right zip? I want to create one. And where to choose that right zip from? Can you link or upload the right updater binary ?
Sent from my SM-J500F using XDA-Developers mobile app