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.
Related
I located the flash archive last night hoping to get a copy of Flash on my HD+ that the Play store would recognize and offer updates for. So far, I haven't got that working.
Over on the Nook forums, a lot of folks from the UK are reporting that Flash is not available via BN, and many in the US are having trouble using the BN shop to install it.
There may be folks who would like to just install the app and not enable unsigned sources? If so, I rewrote one of the CWM flashes that Leapinlar developed to install just Flash.
If you've already enabled unsigned installs on your device, you can get the Flash installer for ICS at
http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html (scroll down a bit for the android versions)
If you don't want to enable that but you've already made one of the clockwork disks for your device, I think this file will let you install flash on either the HD or HD+ -- it has only been tested on the HD+, and I truncated the start of the script so that it's no longer asking about hummingbird versus ovation, as that doesn't seem germane to what I'm doing, copying a file to /data/app.
However, the CWM script should only be used on the BN HD/HD+ platforms as Leapin points out below.
You can download the file at http://www.mediafire.com/?yz0r39nym8ffho0
Copy installflash.zip to your CWM card, boot from it, and install it - it simply copies the Adobe installer into /data/app and your device does the rest.
And if for some reason you haven't enabled installing unsigned apps? Go for it. Tastes great, less filling - but in case you haven't you can certainly use this file.
This is the entirety of the installation, based on leapinlar's scripts:
ui_print("Installing Flash Player fron Adobe Archive...");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata", "/data");
package_extract_dir("data", "/data");
unmount("/data");
ui_print("All done!");
ui_print("Please Remove the SDCard, Reboot, Enjoy!");
Two things, first, this is for stock only. Second, if you make any more zips you should keep that assert statement at the top so in case someone gets a hold of this they can not flash it to their non-Nook HD/HD+ device, since it is hard coded for those. Take the assert statement from one of the other zips marked HD/HDplus that have both hummingbird and ovation asserts in it.
Edit: I'll tell you a story. A user was trying to flash a Nook Tablet ROM to his Nook Color and it understandably failed the assert test. He did not understand what that meant so he did a search and found a post that told him to remove that first statement if he wanted it to flash. So he did and flashed the wrong ROM to his Color. It totally hosed his device since the Tablet partitions are totally different than the Color's. And he could not figure out why it would no longer boot or accept other ROMs.
Since then I always put assert statements in all my zips, just in case.
Sent from my Nook HD+ running CM10 on SD
XT907
rooted
unlocked
TWRP 2.5
Stock ROM 4.1.2 98.15.66
Thinking about taking the 98.18.78 OTA and keeping stock. Had a couple of ideas to keep root and keep TWRP.
Looking in META-INF/com/google/android/updater-script from /cache/Blur_Version.98.15.66.XT907.Verizon.en.US.zip, the problem lines are:
Code:
# This breaks root
2863: set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
Code:
# This breaks TWRP on reboot
2828: assert(package_extract_dir("recovery", "/system"));
So, looks like the options are
1. Edit the OTA .zip by
a. Adding to updater-script
Code:
set_perm(0, 0, 6755, "/system/xbin/su");
b. Include a script to move recovery-from-boot.p to recovery-from-boot.bak (overwriting previous) and calling from updater-script.
c. Re-sign the zip and flash in TWRP.
-or-
2. Flash the OTA in TWRP, then manually edit /system/xbin/su permissions to 6755 and rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak before rebooting.
Questions are: Anyone tried either? After flashing a .zip in TWRP, can you return to the command line to do stuff before rebooting?
Thank you!
That is interesting.
Is there any way to stop the checks for stock apps and install over them?
donslade said:
That is interesting.
Is there any way to stop the checks for stock apps and install over them?
Click to expand...
Click to collapse
Not exactly. Most of the updates in the OTA are in the form of binary patches. These patches contain instructions to modify existing binaries, and only represent the changes to the files. That is why the OTA is only 50 MB, whereas a full copy of all the affected binaries would be much larger, as high as 600 MB.
For the patch to work, it has to affect the exact same binary that Moto/VZW used to generate the patch. This is why the OTA verifies the checksums of the files to be patched before performing the update.
I suppose you could remove some of the check (apply_patch_check) and apply (apply_patch) commands from the updater-script to ignore updates to bloatware.
Disclaimer: I am NOT responsible for any damage you do to your device.
Slate 7 Plus 4200 owners, I have a version of this ROM for you guys as well. You can find it here.
This is JB-SlateROM, a customized and debloated ROM for the HP Slate 7! This was designed for the 2800 but might work on the 4600 as I haven't tested since I don't have a Slate 7.
EDIT: Confirmed working on the 2800!
EDIT: NOT working of the 4600/4601. I'll recook the ROM for you guys when time permits.
Before you can install this ROM you need CWM on your device. Go here to get a build of ClockWorkMod v6.0.3.3.
FEATURES
Bloatware removed! :victory:
If the bloatware is still there, go to Settings, then Apps. Find the app and hit Disable Updates. That will delete the bloatware permanently. If it's still there after that I did not remove it. Tell me what you want removed in that case.
Original launcher has been hidden (saved as an .apk-hide file) in favor of Apex Launcher.
ES File Explorer added.
GravityBox Xposed module added.
App Settings Xposed module added.
Quick Boot added.
Xposed Installer added. (Not activated by default! Go into the installer, hit Framework, then hit Install/Update, then hit Soft Reboot or Reboot!)
Download
Changelog
v2.0 - Coming Soon Complete redo. More bloatware removed and tweaked a few more things... (AKA the "If an android crashes and nobody is around to logcat, can it still be fixed?" Update)
v1.1 - Removed references to ePrint.kpa (UNRELEASED)
v1.0 - Initial release.
Sent from my Sero 7 Pro using Tapatalk
Hi, I just tried to install this ROM (on Slate 7 4601), but in CWM, I get the 'Status 7' error.
before this, I see the line 'set_perm: some changes failed'. If that helps, I don't know?
Thanks.
callidus_ex_de_latebros said:
Hi, I just tried to install this ROM (on Slate 7 4601), but in CWM, I get the 'Status 7' error.
before this, I see the line 'set_perm: some changes failed'. If that helps, I don't know?
Thanks.
Click to expand...
Click to collapse
The ROM must not be compatible with the 460x as I know it works fine with the 280x. I'll do a port of this with the 460x ROM and add it to the OP by next weekend at worst.
Hi. Same Error 7 here on my Slate 7 2800. Formatting all partitions before install doesn't change anything ..
dderek said:
Hi. Same Error 7 here on my Slate 7 2800. Formatting all partitions before install doesn't change anything ..
Click to expand...
Click to collapse
Which country is your Slate from? Status 7 means incompatible with device.
If you're really adventurous do a Nandroid then toggle signature verification then flash the ROM. Theoretically everything will work, but Nandroid just in case
Sent from my Sero 7 Pro using Tapatalk
Thank you for your reply.
My Slate is from Polish distribution channel. It's P/N is E0H92AA.
Signature verification is by default switched off in CWM. Looking at the detailed installation log I can see these lines before the Error 7 is reported:
minizip: Extracted file "/system/xbin/iwpriv"
minizip: Extracted file "/system/xbin/iwspy"
minizip: Extracted file "/system/xbin/su"
set_perm: chown of /system/vendor/app/ePrint.kpa to 0 0 failed: No such file or directory
set_perm: chown of /system/vendor/app/ePrint.kpa to 644 failed: No such file or directory
script aborted: set_perm: some changes failed
E:Error in /external_sd/_/JB-SlateROM.zip
(Status 7)
Installation aborted.
EDIT: adding original file /system/vendor/app/ePrint.kpa to your ROM allowed to install it within CWM 6.0.3.3.
But after reboot the device is now stuck at the HP logo
EDIT2: Suspecting the device incompatibility I have tested that the original firmware (taken from http://forum.xda-developers.com/showthread.php?t=2608181 ) runs without problems
dderek said:
Thank you for your reply.
My Slate is from Polish distribution channel. It's P/N is E0H92AA.
Signature verification is by default switched off in CWM. Looking at the detailed installation log I can see these lines before the Error 7 is reported:
minizip: Extracted file "/system/xbin/iwpriv"
minizip: Extracted file "/system/xbin/iwspy"
minizip: Extracted file "/system/xbin/su"
set_perm: chown of /system/vendor/app/ePrint.kpa to 0 0 failed: No such file or directory
set_perm: chown of /system/vendor/app/ePrint.kpa to 644 failed: No such file or directory
script aborted: set_perm: some changes failed
E:Error in /external_sd/_/JB-SlateROM.zip
(Status 7)
Installation aborted.
EDIT: adding original file /system/vendor/app/ePrint.kpa to your ROM allowed to install it within CWM 6.0.3.3.
But after reboot the device is now stuck at the HP logo
EDIT2: Suspecting the device incompatibility I have tested that the original firmware (taken from http://forum.xda-developers.com/showthread.php?t=2608181 ) runs without problems
Click to expand...
Click to collapse
It's because I removed bloatware and forgot to remove the references in the updater-script. Sorry about that, I'm VERY new to developing.
You should expect a updated ROM very soon. Probably tomorrow worst-case scenario.
Sent from my Sero 7 Pro using Tapatalk
Mmmh I tried to install your ROM but I got the same Error 7.
Then I proceeded to remove any reference into META-INF subfolders about ePrint.apk package and finally CWM installed it without hassle.
Nonetheless I got a stuck boot logo. I left it 5 minutes, but had no success, now I'm going back to my rooted 1.05.14 stock firmware.
I noticed a pair of things that may be useful to report:
- In /recovery folder there's a patch for the recovery. It may be useful to inhibit such patch, I added an exit 0 in /recovery/etc/install-recovery.sh just to be safe
- When you use CWM to do a factory reset (wipe data/factory reset), it doesn't wipe /system partition. You have to manually go in backup/restore -> format /system. Then you should wipe cache, maybe dalvik cache, and finally install the zip package.
blackshard83 said:
Mmmh I tried to install your ROM but I got the same Error 7.
Then I proceeded to remove any reference into META-INF subfolders about ePrint.apk package and finally CWM installed it without hassle.
Nonetheless I got a stuck boot logo. I left it 5 minutes, but had no success, now I'm going back to my rooted 1.05.14 stock firmware.
I noticed a pair of things that may be useful to report:
- In /recovery folder there's a patch for the recovery. It may be useful to inhibit such patch, I added an exit 0 in /recovery/etc/install-recovery.sh just to be safe
- When you use CWM to do a factory reset (wipe data/factory reset), it doesn't wipe /system partition. You have to manually go in backup/restore -> format /system. Then you should wipe cache, maybe dalvik cache, and finally install the zip package.
Click to expand...
Click to collapse
Is this a bootloop or stuck at bootloader?
Sent from my Sero 7 Pro using Tapatalk
how does this rom work on the 2801. Has it been updated?
Thx, vIgGeN!
jerbear294 said:
Is this a bootloop or stuck at bootloader?
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
jerbear294 said:
Is this a bootloop or stuck at bootloader?
Click to expand...
Click to collapse
Just stuck at bootloader. I see the HP logo (still image, not the boot animation) and then nothing happens. I have to push the power button for a long time to power off the device.
I'm redoing the ROM completely and hoping it works. Perhaps my Mediafire upload corrupted?
Sent from my Sero 7 Pro using Tapatalk
jerbear294 said:
I'm redoing the ROM completely and hoping it works. Perhaps my Mediafire upload corrupted?
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
Don't think so, the .zip file unpacked correctly.
Sorry for the hiatus- other devices were taking my attention.
I just need to add some things into the redone ROM then I'll upload it. It could take a couple days though, I'm busy porting PAC-ROM to my tablet. Once that's done I'll continue work on this.
Sent from my Sero 7 Pro using Tapatalk
jerbear294 said:
Sorry for the hiatus- other devices were taking my attention.
I just need to add some things into the redone ROM then I'll upload it. It could take a couple days though, I'm busy porting PAC-ROM to my tablet. Once that's done I'll continue work on this.
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
any idea on an update for this Rom?
keepaf1 said:
any idea on an update for this Rom?
Click to expand...
Click to collapse
Yep. I found the source of the error, and I am fixing it now.
Sent from my Sero 7 Pro using Tapatalk
Hellow, i want to request you to enable usb otg. There are many members on hp forums who are trying to enable it. Otg troubleshooter does not work on stock rom
jerbear294 said:
Yep. I found the source of the error, and I am fixing it now.
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
Looking forward to the new release. just got a slate 7 i repaired and cant wait to flash. thanks for your work on this!!!:good:
If you have the time please
Sorry to be a pain, but any idea when you will have the time to fix this. Its my grandsons tab and I would like to fix it for him. Thanks. I know I could probably learn how to do it myself but the old brain cells are a bit thick these days.
hi, i followed this guide ( https://forum.xda-developers.com/android/software-hacking/guide-port-nougat-roms-snapdragon-t3552897 ) to port validus rom from redmi note 4 (same chipset) but everytime i get error 7 in twrp:
...
patching system image unconditionally...
E1001: failed to update system image.
updater process ended with ERROR: 7
anyone can help me?
the rom is uploading to google drive. tomorrow i put link in this thread
rom link: https://drive.google.com/open?id=0ByWXQMKmKF0-NWplWlM5Z04xQzQ
Edit the updater-script by removing everything before the "ui_print" line.
wang1chung said:
Edit the updater-script by removing everything before the "ui_print" line.
Click to expand...
Click to collapse
i do it but same error, i uploaded my update scritp file below
ExperienceTesla said:
i do it but same error, i uploaded my update scritp file below
Click to expand...
Click to collapse
the script looks good to me, shouldn't be causing you issues as far as I can tell (but what do I know, lol). Are you using the latest version of TWRP?
Anyone try to flash this rom??
wang1chung said:
the script looks good to me, shouldn't be causing you issues as far as I can tell (but what do I know, lol). Are you using the latest version of TWRP?
Click to expand...
Click to collapse
yes: 3.1.0.0. i think the error is the system.new.dat. there is a way to keep system folder in rom zip instead of system.new.dat? like kitkat roms
ExperienceTesla said:
yes: 3.1.0.0. i think the error is the system.new.dat. there is a way to keep system folder in rom zip instead of system.new.dat? like kitkat roms
Click to expand...
Click to collapse
i know there is a command for the updater-script called package_extract_dir("system", "/system"); which should work if you extract system.new.dat to the /system directory of your rom zip, but there's a lot (like 100 lines) of other symlink and metadata commands that I don't understand.
Have you had any luck?
Edit.....think I found something. Try using the first 5 lines of transfer list file from the stock Rom. Maybe more, I'm not sure.
Edit 2: after looking at a breakdown of how the transfer list works, I think this is dangerous.
Edit 3: the "port rom" you uploaded is a lollipop 5.x android Rom, so I'm not sure what you're using as a "base Rom" when porting this as I thought the zf3 only came with 6.x and 7.x?
wang1chung said:
i know there is a command for the updater-script called package_extract_dir("system", "/system"); which should work if you extract system.new.dat to the /system directory of your rom zip, but there's a lot (like 100 lines) of other symlink and metadata commands that I don't understand.
Have you had any luck?
Edit.....think I found something. Try using the first 5 lines of transfer list file from the stock Rom. Maybe more, I'm not sure.
Edit 2: after looking at a breakdown of how the transfer list works, I think this is dangerous.
Edit 3: the "port rom" you uploaded is a lollipop 5.x android Rom, so I'm not sure what you're using as a "base Rom" when porting this as I thought the zf3 only came with 6.x and 7.x?
Click to expand...
Click to collapse
the port rom is Validus-mido-7.1.2.STABLE.15.1-UNOFFICIAL-20171022-2227 from xiaomi redmi note 4 and the stock rom is lineage os. i tried other tutorial with no success. tommorrow i try to port another rom :good:
@ExperiencedTesla
It's weird, because when I extracted the system.new.dat of the stock 7.1 Rom, it showed it was a android 7.1 Rom....but when I extracted your validus rom, it showed 5.0?
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 ?