Database Develop

[FlashPatch] IncDoes flash-patch [v0.2] Nov-12th

BETA~
"Before you download please read 2nd post"
This is the first stage of flash-patch development, this will be used to get AOSP/Vanilla builds onto our INC's in an easy suitable way that fits us all. No more rebuilding or packing a whole new zip
I will be updating the patch as we get more fixes. v0.1 is released and you can grab them below.
Download AOSP FlashPatch v0.2:
http://ziggy471.com/incredibledoes/AOSP-FP-v0.2-signed.zip
Click to expand...
Click to collapse
What the patch does:
- flashes INC's necessary system files
- flashes INC's boot.img
What to come:
- Sense ROM support
Click to expand...
Click to collapse
How to install:
- download flash-patch (posted above)
- download an AOSP/Vanilla rom
- full wipe required
- flash the AOSP/Vanilla ROM but DO NOT REBOOT after install
- flash the patch over the AOSP/Vanilla ROM
- now reboot
That's pretty much it for now, later I will clean up the install and add more fixes to it... Please report back the ROM tested and/or if it failed.
ID
Click to expand...
Click to collapse

OKAY, this is a beta form flash-patch. This Patch will flash over any AOSP/Vanilla build "IF" the update/r-script is not asked to read the board of your device...?!
EXAMPLE:
- CyanogenMod builds have a getprop in the script which will not let you flash. If the script has something like this:
Code:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
then the installation will fail because the board does not match.. you can simply edit these your selves by editing the update/r-script...
BEFORE:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
AFTER:
assert(getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc" || getprop("ro.product.board") == "inc");
Click to expand...
Click to collapse
You can test out AOSP/Vanilla ROMS from any device like Droid, Desire, EVO, Nexus etc... as long as the script does not require the 'getprop' then you should be fine.
PLEASE NOTE: No telling on which roms are supported, only way to find out is to look around the forums and give it a flash... If tested and worked please post ROM/Developer so I can update OP.
"HOW TO EDIT update/r-script" 2 different ways~
NOTE: There is 2 different scripts "update-script" and "updater-script" you will see that I write "update/r-script" because there of the two different scripts. Updater-script comes with an "updater-binary" I never edit the binary so you can leave it alone... just edit the update or updater-script.
Click to expand...
Click to collapse
1- unzip the downloaded ROM
2- open folder META-INF >> com >> google >> android >> update/r-script
3- Open the update/r-script using an xml reader (For WINDOWS use notepad++) (For LINUX use gedit) or something similar...
4- Change the getprop "<device>" to getprop "inc"
5- save and replace the old update/r-script with the one you just saved
6- sign .zip and flash (If I remember correctly Clockwork recovery does not need a signed update.zip so signing the .zip is not required)
Click to expand...
Click to collapse
1 easy step:
This is the easiest way to edit the update/r-script... Completely remove the "assert getprop"
~EXAMPLE from CyanogenMod for N1~
Before:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
assert(getprop("ro.bootloader") == "0.33.2012" ||
getprop("ro.bootloader") == "0.33.0012" ||
getprop("ro.bootloader") == "0.35.2017" ||
getprop("ro.bootloader") == "0.35.0017");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
After:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you want to learn how to sign .zips follow this thread>>> http://forum.xda-developers.com/showthread.php?t=537937

0.2:
- fixed data
- cleaned install
- audio fixed
- build.prop edits
- tethering now works
0.1:
- initial release

you know, I just started using ShadowROM and am loving it! I finally found a great AOSP rom that works wonderfully for me exactly how I want it. I really thought that I was going to stop flashing roms every day finally because I found an AOSP that I love! And then BAM, I read this thread and my choices of roms to try and test just grew 10 times larger....Thank You ID, really...Thanks >0.
Haha, no just kidding. This patch is awesome, I can't wait to start finding and testing out ROMS for other devices. Way to go ID!

Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP

khanam said:
Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP
Click to expand...
Click to collapse
clockworkmod recovery.img Im pretty sure it does not need a signed.zip but if you use amon_ra then you need to sign the .zip
Q2: Nandroid will restore as normal, no need to re-apply the patch.

well, i thought i edited my getprop stuff but cyanogen 6.1 from nexusone failed due to getprop bootloader =0.33.2012 and a few others...

you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu

Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.

touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
dx has that ninjablur BS
this is only for aosp roms.

touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
Apparently I have stayed in the Inc area too much as I was just wondering if there are kitchens like their used to be for WinMo...

es0tericcha0s said:
dx has that ninjablur BS
this is only for aosp roms.
Click to expand...
Click to collapse
Ok, I'll just add the files needed to port it then. Thanks!

es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
Thanks!
So, obviously, Cyanogenmod for the Nexus works. Just removed the assert from the update/r script for both the bootloader and the device. Once that was fixed
1. install rom
2. run Inc's zip
3. ziggy kernel
4. Gapps
rebooted and running.
Not sure why, but wifi isn't working with it and I've tried the Kernels recommended in the Inc Cyanogen thread.

I got lithium mod to work using patch. Thank you.
Sent from my ADR6300 using XDA App

es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
oh wow! thanks man!

I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App

papi92 said:
I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Just leave the binary alone...
ID

I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App

updated 2nd post with two ways to edit the script...

papi92 said:
I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
reboot recovery

[Q] Can't flash apps from CWM

So, i'm having this issue with flashing apps such as superuser and cerberus on my Optimus 2x.
At first i just thought it might be an issue with the update itself (Only tried superuser at first) but now i wanted to check out cerberus, and it exhibits the same behaviour.
Basically it just says something like opening and installing update, then it goes "Error in <path to file> (Status: 0) installation failed" or something like that, and that is basically all there is to it.
CWM is version 4.4.0.7
CWM Recovery is version 5.0.2.0
And yes, i know i can just manually put it in /system/app if i want to, just really would want the convenience of automatically updating su and perhaps Cerberus, if i stick with that, everytime i flash a new nightly.

Let me guess, you're using a stock based ROM and ROM Manager to install them?
If so, then you'll want to either change your recovery to an 'internal' one, or boot to recovery and install them yourself.

Rusty! said:
Let me guess, you're using a stock based ROM and ROM Manager to install them?
If so, then you'll want to either change your recovery to an 'internal' one, or boot to recovery and install them yourself.
Click to expand...
Click to collapse
Thanks for your help, if by stock you mean LG-based rom, then no, i use CM7 currently on Nightly 148. Edit: Additionally i'm using VorkKernel (the one from the 21st) if that has any bearing on the issue.
It doesn't matter if i install from ROM Manager og Recovery, the result is the same, i'm not sure what you mean with an internal recovery, i just installed the one that CWM installed for me.

Also tried the new update for CWM that were supposed to fix 10% of install issues or something like that, still no luck though

If you're on CM7 then you don't want an internal recovery, unless you don't have an external SD card.

Rusty! said:
If you're on CM7 then you don't want an internal recovery, unless you don't have an external SD card.
Click to expand...
Click to collapse
I tried installing your recovery for external sd cards, still the same error, and yeah i do have an external sd card.

When did it start happening? It must have worked at some point as you have CM installed.

Rusty! said:
When did it start happening? It must have worked at some point as you have CM installed.
Click to expand...
Click to collapse
It only happens for apps (For example Superuser and Cerberus) CM flashes just fine, so does my kernel.

Well that's just bizarre then, if one thing works, they all should
If you go to advanced in recovery you get an options to display the log, might be worth doing that after it's failed at installing.

Rusty! said:
Well that's just bizarre then, if one thing works, they all should
If you go to advanced in recovery you get an options to display the log, might be worth doing that after it's failed at installing.
Click to expand...
Click to collapse
Well it starts up saying "Checking for extendedcommand" then "Skipping execution of extendedcommand. file not found"
Then it goes back to just showing the same log from the installation saying that there is an error in the file (status 0)
And nothing else.

Error status 0, I missed that, it means a problem with the updater-script.
Now, how old are these .zips? If they're not too new, they could use Amend scripts (instead of Edify that you need on CWM v3+), and you'll get that error. You can ignore the extended command bit, that's OK.

Rusty! said:
Error status 0, I missed that, it means a problem with the updater-script.
Now, how old are these .zips? If they're not too new, they could use Amend scripts (instead of Edify that you need on CWM v3+), and you'll get that error. You can ignore the extended command bit, that's OK.
Click to expand...
Click to collapse
The zips were downloaded today, superuser 3.0 can't be more than a few days old, don't know about cerberus though, the archive timestamp indicates 2008, but that doesn't make sense.

Rusty! said:
Error status 0, I missed that, it means a problem with the updater-script.
Now, how old are these .zips? If they're not too new, they could use Amend scripts (instead of Edify that you need on CWM v3+), and you'll get that error. You can ignore the extended command bit, that's OK.
Click to expand...
Click to collapse
Edit: Oops was meant to be an edit.
If it makes any difference here are their update scripts:
Cerberus:
Code:
show_progress(1.000000, 0);
ui_print("Mounting /system");
run_program("/sbin/busybox", "mount", "/system");
set_progress(0.125000);
ui_print("Mounting /data");
run_program("/sbin/busybox", "mount", "/data");
set_progress(0.250000);
ui_print("Deleting old APK from /system");
delete("/system/app/Cerberus.apk");
set_progress(0.375000);
ui_print("Deleting old APK from /data");
delete("/data/app/com.lsdroid.cerberus.apk");
delete("/data/app/com.lsdroid.cerberus-1.apk");
delete("/data/app/com.lsdroid.cerberus-2.apk");
set_progress(0.500000);
ui_print("Extracting files to /system");
package_extract_dir("system", "/system");
set_progress(0.625000);
ui_print("Unmounting /data");
unmount("/data");
set_progress(0.750000);
ui_print("Unmounting /system");
unmount("/system");
set_progress(0.875000);
ui_print("Installation complete!");
set_progress(1.000000);
Superuser:
Code:
ui_print("***********************************************");
ui_print(" Superuser 3.0 for Android 2.0-3.2");
ui_print("***********************************************");
show_progress(1.000000, 0);
ui_print(" Mounting SYSTEM...");
run_program("/sbin/busybox", "mount", "/system");
set_progress(0.100000);
ui_print(" Deleting SYSTEM:bin/su...");
delete("/system/bin/su");
set_progress(0.200000);
ui_print(" Deleting SYSTEM:xbin/su...");
delete("/system/xbin/su");
set_progress(0.300000);
ui_print(" Extracting files to SYSTEM...");
package_extract_dir("system", "/system");
set_progress(0.400000);
ui_print(" Setting SYSTEM:bin/su permissions to 6755...");
set_perm(0, 0, 6755, "/system/bin/su");
set_progress(0.500000);
ui_print(" Creating SYSTEM:xbin/su symbolic link...");
symlink("/system/bin/su", "/system/xbin/su");
set_progress(0.600000);
ui_print(" Unmounting SYSTEM...");
unmount("/system");
set_progress(0.900000);
ui_print("Install complete. Enjoy!");
set_progress(1.000000);

They're Edify scripts, so nothing wrong there. That's confusing.

Anyone else dares enter the fray?

Same issue here for cerberus, although on a different device (galaxy note, notecore v10.2, cleanote v4).
Has anyone found a solution for this?

Extract the updater-binary from your rom and replace the ones in the app zips.
Sent from my LG-P990 using xda app-developers app

Try disabling the Toggle Signature to disabled in CWM...
Sent from my LG-P999 using Tapatalk 2

[Q] problems in building rom

hey i m trying to learn to build a custom rom.
i m using dxida's kitchen for dat purpose
on building d rom n flashing it using cwm i get an error "error:status 7 mount() requires 4 args"
i found this in updater-script
Code:
mount("MTD", "system", "/system");
so i tried to updater scripts from another roms from development section
Code:
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
but den my phone gets into bootloop
wat shld be d issue??
thanks in adv

Then You probably soft-bricked it

Yeah ...you've soft bricked it

andy_android said:
hey i m trying to learn to build a custom rom.
i m using dxida's kitchen for dat purpose
on building d rom n flashing it using cwm i get an error "error:status 7 mount() requires 4 args"
i found this in updater-script
Code:
mount("MTD", "system", "/system");
so i tried to updater scripts from another roms from development section
Code:
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
but den my phone gets into bootloop
wat shld be d issue??
thanks in adv
Click to expand...
Click to collapse
Try to reflash the Firmware, altrough you will Lost everything

yeah i got dat one
but wat i want to knw is how to get d error??
logcat???

toterkeks said:
Try to reflash the Firmware, altrough you will Lost everything
Click to expand...
Click to collapse
what do u mean by lost everything???
i was able to revert back to stock

andy_android said:
hey i m trying to learn to build a custom rom.
i m using dxida's kitchen for dat purpose
on building d rom n flashing it using cwm i get an error "error:status 7 mount() requires 4 args"
i found this in updater-script
Code:
mount("MTD", "system", "/system");
Click to expand...
Click to collapse
Here the binary is telling you it needs 4 arguments (args) and you are only giving it 3 (1. "MTD", 2. "system" and 3. "/system") which is why you were getting the error. If it had of worked, I'm not sure what it would have done because MTD is the wrong partition type for our phone. You have to be a bit careful here because there is the possibility of hard-bricking your phone doing things like that. I think the kitchen does tell you somewhere that you need to edit the script if your phone doesn't have a YAFFS based filesystem.
andy_android said:
so i tried to updater scripts from another roms from development section
Code:
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
but den my phone gets into bootloop
wat shld be d issue??
thanks in adv
Click to expand...
Click to collapse
This second one that you have used is correct so I can only assume it's another part of the script that's causing the problem. To be 100% sure you can also remove the mount command altogether and just use the menu options in CWM to make sure /system is mounted before flashing the ROM.
Also did you wipe data/cache before flashing the ROM?

Xposed Installer destroyed my Toshiba AT300SE rooted

I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.

Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk

kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.

Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk

GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.

rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.

Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse

GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.

Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.

Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?

Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.

GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse

Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).

rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.

Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS

[ROM[[GPE][4.4.4][m7spr][m7wls] Pixel Perfect GPE Beta 1

Hey guys!
So, I got sick of not having a simple, stock, GPE ROM comparable with my device!
I knew a little about porting roms from the UL to the Sprint variant of the HTC One, as per the almost complete port of the L Preview from it's current state to our radio (Thanks @manups4e !!! You probably helped me directly the most, although I can't count out @sykopompos @ANDR01DN00B ( hate typing that username) or @tiny4579)
As for actual work on this, I want to thank @artur0588 for the TWRP-ready version of GPE!
Features:
Code:
De-odexed
Zipaligned
Pre-rooted
Busybox
Sprint kernel tweaks
Sprint proprietary binaries (From http://forum.xda-developers.com/showthread.php?t=2371960)
Otherwise TOTALLY STOCK GOOGLE PLAY EDDITION
Kernel from http://forum.xda-developers.com/showthread.php?t=2371960
XDA:DevDB Information
[ROM[[GPE][4.4.4][m7spr][m7wls] Pixel Perfect GPE Beta 1, ROM for the Sprint HTC One
Contributors
ajbiz11, artur0588, manups4e
ROM OS Version: 4.4.x KitKat
Based On: Google Play Edition
Version Information
Status: Testing
Created 2014-10-11
Last Updated 2014-10-11

Downloads:
REMINDER: I POST THESE RIGHT BEFORE I TEST THEM! AS OF THE MOMENT THEY'RE POSTED, THEY'RE UNTESTED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Beta 1 - Build 1: https://mega.co.nz/#!tZ9mjJYY!mbdARE_2Gw4E6RRESM7PTRQ50HW4ur37s1nC63gIWuc THIS HAS A BROKEN UPDATER SCRIPT! I NEED TO FIGURE OUT WHAT I BROKE, BUT THE SYSTEM AND KERNEL SHOULD WORK
Beta 1 - Build 2 https://mega.co.nz/#!5E000YQa!2z2j8vwXTr9GNMxOkveaJw4s-nPo76RGHOIQM0wdwQg - I think I fixed the issues with the updater-script and update-binary Edit: NOPE

Reserved

Last one! I swear!~

Well, there appears to be an issue with the updater binary, so I'll have to sort that out

Can't wait to try this once you get the update binary and script sorted out!
Sent from my HTCONE using Tapatalk

My username is the most unique out of all XDA!!! Good luck with this project, but unfortunately I don't have a Sprint/Verizon variant, so I cannot test and I am not of any help to you.
Cheers.

Are you using the right binary and have it set up right in meta-inf?
Sent from my LG-D851

sykopompos said:
Are you using the right binary and have it set up right in meta-inf?
Sent from my LG-D851
Click to expand...
Click to collapse
Well, I used my kitchen to rebuild my edify script, so perhaps it broke everything

ajbiz11 said:
Well, I used my kitchen to rebuild my edify script, so perhaps it broke everything
Click to expand...
Click to collapse
I'll download it and fox your updater script for you in a bit
Sent from my LG-D851

Try replacing the updater-binary with the one from one of my L builds and then pull the recovery log if it doesn't go. It looks like it is using the newer style binary
Sent from my LG-D851

sykopompos said:
Try replacing the updater-binary with the one from one of my L builds and then pull the recovery log if it doesn't go. It looks like it is using the newer style binary
Sent from my LG-D851
Click to expand...
Click to collapse
Will do

sykopompos said:
Try replacing the updater-binary with the one from one of my L builds and then pull the recovery log if it doesn't go. It looks like it is using the newer style binary
Sent from my LG-D851
Click to expand...
Click to collapse
Well
Here's the error with the new bianary (same as old iirc)
Code:
Installing '/sdcard/gpe/gpe.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
line 4 col 28: syntax error, unexpected STRING, expecting $end
1 parse errors
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/gpe/gpe.zip'
Setting performance mode OFF.
Error flashing zip '/sdcard/gpe/gpe.zip'
Updating partition details...

ajbiz11 said:
Well
Here's the error with the new bianary (same as old iirc)
Code:
Installing '/sdcard/gpe/gpe.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
line 4 col 28: syntax error, unexpected STRING, expecting $end
1 parse errors
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/gpe/gpe.zip'
Setting performance mode OFF.
Error flashing zip '/sdcard/gpe/gpe.zip'
Updating partition details...
Click to expand...
Click to collapse
Well that is much more informative. You need a file_contexts file (it is in the boot IMG) then fix the syntax error on line 4
Sent from my LG-D851

sykopompos said:
Well that is much more informative. You need a file_contexts file (it is in the boot IMG) then fix the syntax error on line 4
Sent from my LG-D851
Click to expand...
Click to collapse
Oh how did I miss the file_contexts

The funny part is the syntax error wasn't on line 4
it was line 3 making line 4 look wrong
Code:
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p37");
mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system"); "0 /system/
package_extract_dir("system", "/system");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
I imagine it should look more like this, no @sykopompos?
Code:
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p37");
mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system");
package_extract_dir("system", "/system");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");

The "0" marks it mounted as root, it looks like the syntax might be missing quotes though
Sent from my LG-D851

sykopompos said:
The "0" marks it mounted as root, it looks like the syntax might be missing quotes though
Sent from my LG-D851
Click to expand...
Click to collapse
Well, if you get a chance to look, https://mega.co.nz/#!VEM3gZhR!Fjv8YIbvsozo_QeCxl7oji4uPdxOynXewnDwYS9McQA here is the script (before the removal I made)
Or the zip is in the 2nd post

ajbiz11 said:
Well, if you get a chance to look, https://mega.co.nz/#!VEM3gZhR!Fjv8YIbvsozo_QeCxl7oji4uPdxOynXewnDwYS9McQA here is the script (before the removal I made)
Or the zip is in the 2nd post
Click to expand...
Click to collapse
I had already downloaded it but I can't test it because I don't have the device
Sent from my LG-D851

sykopompos said:
I had already downloaded it but I can't test it because I don't have the device
Sent from my LG-D851
Click to expand...
Click to collapse
I was referring more to if you saw syntax errors
I'll take another crack at it tomorrow