Visual Land 7L stuck in clockworkmod v6.0.1.3 - Android Q&A, Help & Troubleshooting

Tried to get a clockworkmod working on my Visual Land 7L. Found a thread that gave me a clockwork recovery that worked with the Visual Land 7 (NOT 7L) but it still installed normally and even booted into it. Volume rocker didn't interact with the recovery so I rebooted. Took the recovery that same recovery and used CWM's Recovery Builder but added touch support. It finished successfully so I flashed the new recovery, now I can move through the menu but when I restart my phone it always goes into clockworkmod. Any help fixing this would be great. If I could just downgrade the recovery to the one that didn't mess up my tablet I'm sure I'd be fine but I only have a recovery.img and somewhere I read putting it in a zip named update by itself should be fine but installation always fails. The error is "Installation aborted."

Ok so I've made some progress, turns out I can install another recovery (the one that didn't brick my device) but it needs to be a recovery.img inside of a .zip file. On top of that a META-INF file with four or five subdirectories with two files at the end. One of which I think is just initializes the other one. I was able to edit the updater-script because I kept getting status errors. Now it'll start to install the image and show a progress bar but comes up with an error when it has to ask me if it's ok to keep going. The error is now just with Assert. No idea what I need to change. This is what my updater-script looks like when you open it in notepad.
show_progress(1.000000, 0);
ui_print("");
ui_print(" Notion Ink Adam Clockworkmod 3.0.2.8 051311 ");
ui_print("");
ui_print("---------------installing recovery.img----------");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "/system/bin/recovery"), delete("/tmp/recovery.img"));
ui_print("-----------------------------------------------");
ui_print("Installation done! Please reboot");

squirrelthingy said:
Ok so I've made some progress, turns out I can install another recovery (the one that didn't brick my device) but it needs to be a recovery.img inside of a .zip file. On top of that a META-INF file with four or five subdirectories with two files at the end. One of which I think is just initializes the other one. I was able to edit the updater-script because I kept getting status errors. Now it'll start to install the image and show a progress bar but comes up with an error when it has to ask me if it's ok to keep going. The error is now just with Assert. No idea what I need to change. This is what my updater-script looks like when you open it in notepad.
show_progress(1.000000, 0);
ui_print("");
ui_print(" Notion Ink Adam Clockworkmod 3.0.2.8 051311 ");
ui_print("");
ui_print("---------------installing recovery.img----------");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "/system/bin/recovery"), delete("/tmp/recovery.img"));
ui_print("-----------------------------------------------");
ui_print("Installation done! Please reboot");
Click to expand...
Click to collapse
Im in the same boat i cant get out of CWM for nothing it keeps saying cant mount well anything

Related

Anti-theft android system?

Hi there, guys. I don't know if I should ask this here or in the general forum, so... here I go.
I use cerberus in my nexus one since several months ago, and after watching the SassiBoB review of this program, I started to think how could I get it permanently configured into my system, just in case the thief knows how to restore the system configuration of the phone.
She says something about installing it as a system app with... ¿Rom manager?
I can't understand it perfectly, english isn't my mother tongue.
Anyway, I used titanium backup and I was able to get it installed as a system app (I could also add it to the rom zip, but... I know, I'm such a lazy ), so this step is done. Next problem: the configuration. When you do the factory reset, the configuration of the cerberus app is deleted, so it doesn't matter if it's installed or not. It won't work.
Is there any way to keep the configuration in the system, even if you do a system reset?
I know there are several other problems, like the root apps to flash the phone, or even the recovery menu, but I would like to solve all the problems step by step, and I think this is the first one.
Thank you, guys.
Pretty sure this belongs in the question section.
I don't have it cerb but, my friend told me you go to there website https://www.cerberusapp.com/ and there's a flashable zip you download and install with Rom manger.
Yes, you are right. In the cerberus web page there is a zip file which contains the cerberus app, so you can flash it as a rom, and it keeps it installed as a system app, but unfortunately there isn't any difference with the other methods. It keeps the app after a factory reset, but the configuration is deleted, so it's like the app isn't installed. I have already sent an email to them asking if there is a way to keep the configuration, but I haven't received any answer yet (and it's new year, it's weekend...).
OK, step done. They will release another version (2.0) that keeps a copy of the configuration in /etc/system, so if we add the apk and this file to the ROM, it will be safe.
Next step: the app is installed and configured BUT it has to be added to the list of devices administration in the security and privacy option (it has to manage the device). To add it, you must open the app and set the "activate" option, so we have the same problem that we had, so now it's not an app problem, but a ROM problem.
Is there any way to change the apps aded to the devices administrator option? I supose it should be, as the configuration has to be stored somewhere...
A little step more. I think I found the file where the administration params are stored. It's in /data/system/device_policies.xml
New problem: this file is in the installed system, but I can't find it in the ROM.
¿Any idea? Thanks
Another hint: I found this:
http://hi-android.info/src/com/android/server/DevicePolicyManagerService.java.html
It seems this is the class who creates the file. It should be easy to modify it so it adds the required data to the file. New problem: I can't find this class in the ROM file. I'll keep searching...
FOUND!
It's in services.jar, inside the framework directory.
It's necessary to extract the classes.dex, convert it into .jar, extract the DevicePolicyManagerService class and decompile it as java code, and here it is:
Code:
private static JournaledFile makeJournaledFile()
{
File localFile1 = new File("/data/system/device_policies.xml");
File localFile2 = new File("/data/system/device_policies.xml.tmp");
return new JournaledFile(localFile1, localFile2);
}
I think I should be able to modify it. I can't right now, but I'll post it when I try it.
I was trying to change that java file, but it's a real pain in the ass to recompile it and avoid all the errors. Then I realized that I can just modify the update script to copy the file (yes, I'm such an idiot lol).
I was trying to get it done with the update-script in META-INF/com/google/andriod/updater-script, but I can't get it working. A little help would be appreciated
Another update (Were you missing me?). I decided to modify the flasheable zip of the cerberus, so it has all the configuration files. I added the data/system/device_policies.xml and also de etc/cerberus_conf.xml files to this zip. Then, I changed the updater:
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);
--------------ADDED-------------------
ui_print("Extracting files to /data");
package_extract_dir("data", "/data");
set_progress(0.680000);
---------------------------------------
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);
It's a standalone zip file, so you need to flash your ROM and flash this zip file after it. Anyway,
WARNING
This doesn't work. After flashing the second zip file, the ROM won't boot (It keeps booting, with the boot animation in loop). I suppose I break the data directory or something like that. I'll keep trying.
Yep, I tried several things and the problem is with this line:
package_extract_dir("data", "/data");
It seems it breaks the data directory or something like that. The other files are copied perfectly.
OK, problem found with adb. With this command, it deletes completely the /data/system directory, so it keeps only the new file. Time to fix it...
EDIT: my fault. /data/system is empty until we start the system for first time. We must flash the rom, boot it, restart and flash the patch with cerberus. This is starting to be kinda stupid... If we do this, we can select cerberus in the administrators menu, instead of flashing anything...
Last post for the moment with partial conclussions.
When we do a factory reset, it deletes ALL the content of the data directory. So it's impossible to solve this problem just flashing anything after the ROM. Is the ROM who HAS TO COPY the device_priorities.xml into /data/system/. There isn't any other way, it would be erased after a factory reset.
Now, time to find out how to get it done by the ROM. I'll let you know as soon as I get it.
Work!
I did a full wipe (Wipe Data / Factory Reset + Wipe Cache Partition Wipe Dalvik Cache) and installed the official samsung rom (Android 4.1.2). I installed the flashable ZIP from the site on my galaxy s2 and did not have to reconfigure anything. Everything worked as it should. I believe that the application connects to the user's account based on the information of the device recorded previously.
Avast anti-theft has a Function to protect the configuration after a wipe. Just discover how avast achieves this.
(Translated via google translator)
That's the one thing is that even Avast and Cerberus won't escape if /system is formatted, but Avast did make it through a full SBF followed by factory reset on my phone.

[Q] assert failed: getprop("ro.product.device") =="p4wifi" ...

Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
did you try to update script directly into zip file ?
I don't know which OS you are using (maybe windows ?), with linux, you can edit a file directly a zip file (file roller for me). After saving your file, zip is automatically updated.
if you are using winzip, i guess you can drag and drop updated file into your zip.
of course, you need to edit the zip file out of your tab.
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Kokapelly said:
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Click to expand...
Click to collapse
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
BatBat said:
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
Click to expand...
Click to collapse
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Kokapelly said:
Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
Click to expand...
Click to collapse
If you're seeing that, then you should update your CWM. It's not recognizing your tablet device. I'm using CWM 5.5.0.4 and it does recognize the P7510 as "p4wifi".
Kokapelly said:
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
Click to expand...
Click to collapse
If it's easier, edit the file and just insert a "#" before the "assert". That will comment it out. However, I'd recommend updating the recovery instead.
Success Story - you figure out how...
This is a SUCCESS story...
I got by this somehow, not sure what it was but will over communicate so someone else can figure out specifics.
updating my gt-p7510 from android 3.1 to Android 4.1.2 (CM 10 ROM 20121215 nightly)...
My tab was in weird state from a prior rom sequence (I had rooted it long ago.. some programs said it was rooted, but programs trying to get the permission, like titanium backup, would fail)
so I followed the instructions to root again from HERE
up to the point to the point where you load a ROM. ie. I loaded CWM 5.5.0.4 using odin3.
Then I downloaded the latest CM 10 , copied it to root folder on my tab... and tried to use CWM to install it...
got the "assert(getprop("ro.product.device") == "p4wifi" ... Failure...
went wild and tried other programs (ROM Manager, System Updater etc. avail from "Play Store" ... actually I had tried these prior to rooting again...
they failed before (not able to get root permissions) and after (not able to perform the update... assuming they got and hid similar error)
Tried to edit out the assert in the updater-script as in the prior post... but unzipping had a lot of duplicate file overrides (into clean folder) and they were not all exactly the same file (ie some had different sizes)... so gave up that path.
I had been avoiding updating CWM further because of k1mu's success above ... and avoided the "CWM Touch" flash as I thought base CWM would be better.
Went back to try to update CWM (went to www.clockworkmod.com) and was annoyed when I could not download the CWM zips... links returned characters in browser...
Finally went wild again... used ROM Manager Pro to update CWM to the latest "CWM Touch"
Surprisingly this updated CWM easily...
Then used it to Load the latest CM 10 nightly ... again shockingly easy AND successful... (no Assert failure)
ROM Manager did not automatically update the google apps ... so I got my first look at the CWM Touch interface installing gapps...
But it all worked... So LOVE ROM Manager...
(although for grins I also found and tried CM 10 downloader and retried System Updater Pro etc.. .they all work now)
But hats off to ROM Manager's update and to CWM touch for seemingly fixing all my problems.
lightman33 said:
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Click to expand...
Click to collapse
I open in notepad++ and here is the code from updater-script
Code:
assert(!less_than_int(1383478437, getprop("ro.build.date.utc")));
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
So do I need to delete full 1st line or 2nd line?
If I follow your instruction, I have to delete 2nd line...
EDITED:
Line 2 deleted! And done flashing
The answer to all of this: The problem is the recovery, not the update package, or the updater script.
The assert fails because CWM, TWRP, and some other modified recoveries do not include the getprop command in their small, ramdisk linux OS. So, when the assert tries to run getprop to check ANY property for the installed system, it fails.
Apparently CWM Touch has this binary included.
Custom recoveries generally don't think to include it because pretty much the only thing being flashed through them are custom roms, with their own custom installer scripts, and these rarely (have they ever?) include asserts checking for properties.

[Q] New cooked ROM from android kitchen gets status 7 error when flashing

Okay so uh...I'm trying to make my own custom ROM from a stock Galaxy S3 sgh-i747, using dsixda's Kitchen.
My problem is that I am getting a status 7 error when trying to flash it.
Now I know, since I read the FAQ, that it has something to do with the updater-script. The only info I could gather is that you need to go in and change the format/mount code.
I have this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/data");
So I suppose my real question is...what am I supposed to change (it to) so I can make it work? (and what else might I need to change?)
Any help greatly appreciated!
Edit: Oh and um...I'm also wondering.... If I put any new apks in the rom (such as note2 camera, etc.), do I have to put specific code in the script for them? (I'm a bit new to all this--everyone starts somewhere I guess)
same issue with me also .. Any one there to help?
Figure out your mount points if this is your error, also depending on your update-binary youay need to change the format of the arguments
As for the question about adding .apks, yes you need to modify updater-script to reflect this, and it depends on what folder they are in for ROM.zip and what partition you want them stored in.
Can't answer any further without more info but Google is your friend
Sent from my Nexus 4 using Tapatalk 2
Thats why i don't use kitchen, you wont LEARN anything.
and then you have this kind of problems, and you cant fix them.
And the last reply it usefull, check your mount points.
may be the updater-binary making the cause, try updater binary of working rom.
TroubleShooter™ said:
may be the updater-binary making the cause, try updater binary of working rom.
Click to expand...
Click to collapse
Try from the stock rom first (if the stock is running the same Android os version)

[Q] Creating a CWM flashable zip

Can anybody point me out how to create a CWM flashable zip? i did find a lot of topics, but i've noticed that any ZIP package has to be phone specific, at least a glimpse on the updater-script showed me partition names which i am very unfamiliar with.
The simplest method gives you a zip file where all you have to do is put system.img, boot.img and recovery.img on it, and a very basic script (i think):
Code:
ui_print("Starting ...");
ui_print(" ");
ui_print("Boot Partition Writing ...");
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
ui_print("System Partition Writing ... ");
package_extract_file("system.img", "/dev/block/mmcblk0p15");
ui_print("Recovery Partition Writing ... ");
package_extract_file("recovery.img", "/dev/block/mmcblk0p13");
ui_print("Pass");
ui_print("Wipe data & Cache & Dalvik and reboot system ");
however, the code above, i found it on the GT-i9001 threads, so i dont want to risk anything...especially with the partition blocks.
the point of this thread is to convert our odin packages to cwm flshable zips, though the reason behind it is trying to flash a 4.2 rom from a identical device as ours, in fact, it is the same device, for more info check this thread
i think it's already exist now
PlutoDelic said:
Can anybody point me out how to create a CWM flashable zip? i did find a lot of topics, but i've noticed that any ZIP package has to be phone specific, at least a glimpse on the updater-script showed me partition names which i am very unfamiliar with.
The simplest method gives you a zip file where all you have to do is put system.img, boot.img and recovery.img on it, and a very basic script (i think):
Code:
ui_print("Starting ...");
ui_print(" ");
ui_print("Boot Partition Writing ...");
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
ui_print("System Partition Writing ... ");
package_extract_file("system.img", "/dev/block/mmcblk0p15");
ui_print("Recovery Partition Writing ... ");
package_extract_file("recovery.img", "/dev/block/mmcblk0p13");
ui_print("Pass");
ui_print("Wipe data & Cache & Dalvik and reboot system ");
however, the code above, i found it on the GT-i9001 threads, so i dont want to risk anything...especially with the partition blocks.
the point of this thread is to convert our odin packages to cwm flshable zips, though the reason behind it is trying to flash a 4.2 rom from a identical device as ours, in fact, it is the same device, for more info check this thread
Click to expand...
Click to collapse
The below can be used fro CWM. I didn't try it yet, but it was posted in tools and utilities section.
mohamed_fattoh said:
The below can be used fro CWM. I didn't try it yet, but it was posted in tools and utilities section.
Click to expand...
Click to collapse
Oh, you probably misunderstood me. I needed to know how to create a ZIP so i can flash it through CWM. I already have it, exactly what you've pasted , thnx for trying to help btw.
Check this this out. http://pan.baidu.com/s/1qWyNG8O
Might be a flashable i8558 rom. Muamk1
It semms that download links for i8558 custom roms are removed from their sites.
Got that link fromb http://m.romjd.com/Rom/Detail/35720
Another rom here. http://m.romjd.com/Rom/Detail/27609

Error flashing my custom ROM

I'm new in ROMs creating and I've followed a LOT of tutorials to create my own ROM. Only one ROM works in my device, but the problem is this one have their bugs and isn't compactible very well. So I decided begin develop my ROM with the stock. I installed kitchen and made my ROM, deodexed the apps, installed busybox and root support, everything. I did not touched in any apps or other thinks, only in kitchen menu. After everything I builded the ROM with kitchen and tryed to flash it in my device.
In TWRP, when I flash I get the following error:
E:Error executing updater binary in zip 'external_sc/rom_name.zip
Click to expand...
Click to collapse
So, I got the Droidwin v3.1 update-binary (it's the unique ROM which worked in my device). After some errors corrections in the updater-script (and a lot of errors), I decided debugging the script, placing puts commands before every line. Now I stuck in this line (with the same error, "Error executing updater binary", but before commands are runned):
Code:
package_extract_dir("system", "/system");
I don't know what to do now, I don't have other META-INF folder to copy into my ROM.
All my updater-script: http://pastebin.com/eM48k1fu.
That's all, I hope you can help me. Sorry my english.

Categories

Resources