I've got a Galaxy SGH-1897 "captivate".
I've been running various kernels and ROMs for quite a while now. I'm handy with linux and adb and I can flash things with heimdall.
Whelp, I saw that CM7.1 finally had a version for my captivate, so I installed it last night with Clockwork mod recovery. All went well with the install, but the system seemed buggy, or at least I was having some problems. One was that I couldn't seem to get all my user data restored through Titanium backup like I've been able to after other installs. So, having fun and walking along, I thought, oh, well what I want to do is restore back to 2.2 and my old rom (which was "Torch 2.1 or something"). Anyway, I booted into recovery then told CWM to restore. It errored out and tried to reboot, but couldn't get past the startup screen.
So, I used the volume-up-down plug-in-usb trick to get back into download mode. Then I used heimdall to flash the overstock kernel and CWM (http://cmw.22aaf3.com/aries/sgh-i896/root/) all went well. Now, I have the issue that I can't seem to go ahead and reinstall a new (or old) ROM. If I try to do a "restore", I get the error that I can't mount /system, installation aborts. The error says "file already exists", so I'm trying to figure a way to unmount /system before trying it, but so far no luck (maybe I can flash busybox and get su and get the job done). Alternatively, I've been trying to flash CM7 again, but that installation errors out with "Status 7", and seems to be failing some assert statement.
I'd love any advice. Let me know if you need more detail or if this is in the wrong forum.
---------- Post added at 03:48 PM ---------- Previous post was at 03:19 PM ----------
Just following up with more info here.
It seems like "Status 7" happens when the software one is trying to install is intended for some other hardware. I'm trying to verify this now.
Looking at the output of my error, all of the asserts seem true. getprop("ro.product.device") == "captivate" ...
getprop keeps wanting "captivate" or "captivatemtd" or "SGH-I896" or "SGH-I897" it seems. And that's no surprise, I'm using a captivate. I'm not sure what the "mtd" part is about yet. And I'm pretty sure my device is an I897.
Now I'm trying to isolate which statements are causing assert to fail. I'm using grep and find on the update-cm-7.1.0-RC1-Captivate.signed.zip archive to try to locate some clues. Any ideas?
---------- Post added at 04:30 PM ---------- Previous post was at 03:48 PM ----------
Okay, now I'm thinking that I'm simply barking up the wrong tree with the assert statements and the Status 7 error. From what I can tell, I'm trying to install captivate software on a captivate, so maybe this error message is spurious. Especially considering the fact that other tasks such as "restore" also seem to be failing, but with a more general sort of error.
When I use clockworkmod recovery to go to "recover" then I select my latest backup point, I get to wait abit during md5 checks then:
Code:
E:Can't mount /dev/block/st19 to /system with parameters auto llw,check=no
(File exists)
Error mounting /system/!
Skipping format ...
E:Can't mount /dev/block/st19 to system with parameters auto llw,check=no
(File exists)
Can't mount /system/!
So, 'file exists' seems to mean that the /system directory is mounted when it shouldn't already be, or else the install script should unmount it before it starts but has failed there. In either case, maybe this is a permissions issue. Does the recovery OS need privileges it doesn't have? Is there some way to flash busybox/su using heimdall or adb? Does that seem like my problem?
not permissions, still no progress
Maybe I'm posting in the wrong forum ... ?
Let me know if there's some other group (irc?) which might have ideas?
So, it seems that the problem isn't permissions. At least insofar as I found in the ClockworkMod Recovery settings a selection to install su. So, that seemed to go fine, but afterwards I'm still getting "cannot mount /system/!" when I try to do a restore.
Still stumped. Looking for ideas.
Same error on SGSI
I've got the same error on my Samsung Galaxy S.
But I can't even boot the device, it freezes on the first boot screen, I've installed the cyanogenmod but, when I've tried to install the MIUI this problem appears and know, I can't do nothing.
When I try to install the cyanogenmod or the MIUI I get the following error:
assert(getprop("ro.product.device") == "galaxysb" || getprop("ro.build.product") == "galaxysb" || getprop("ro.product.board") == "galaxysb" ||
getprop("ro.product.device") == "galaxysbmtd" || getprop("ro.build.product") == "galaxysbmtd" || getprop("ro.product.board") == "galaxysbmtd" ||
getprop("ro.product.device") == "GT-I9000B" || getprop("ro.build.product") == "R8GT-I9000B00at" || getprop("ro.product.board") == "GT-I9000B"
Click to expand...
Click to collapse
If I enable the signature verification I get this error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Did you fix your problem?
Someone else have any clue?
Thanks.
I've solved this problem I just changed a file updater-script located at /META-INF/com/google/android/ of the cyanogenmod zip file.
I've simple delete the lines that make a reference to my device.
tic-tac-toe said:
I've solved this problem I just changed a file updater-script located at /META-INF/com/google/android/ of the cyanogenmod zip file.
I've simple delete the lines that make a reference to my device.
Click to expand...
Click to collapse
how did u do that? did you just access the ROM zip file and edited it from there
Related
Just got my captivate today.
I'm a noob at mobile phone dev, but I've been using linux as my primary operating system for years now.
I'm trying to root the phone.
I've attached the file that I used.
I mounted the phone as a mass storage device, it showed up in /media as /media/6F...
I copied the file (attached) to the top level directory of the mounted device and named it update.zip.
I rebooted the phone into recovery mode (using the hold down all three buttons method). I select "reinstall package" and get this error:
"assert failed: getprop("ro.product.device") == "GT-I5800" || getprop("ro.build.device") == "GT-I5800" || ..."
There are several other disjuncts in the statement, it seems to be trying getprop for "ro.product.device" and "ro.build.device" for GT-I5800, GT-I9000, and SGH-T959.
Then I get the error message and exit with status 7, installation aborted.
I'm guessing that I'm having this problem because I've got the wrong file for this phone, since the wiki seems to suggest that the att captivate is actually an SGH i897.
So, questions are:
*should i go get a different file, or edit the one I have?
*if the former, where can i get the file? if the latter, does anyone have instructions about what needs editing?
Thanks to all, I'm really looking forward to learning all about linux on my mobile.
Okay, I guess I'm a hasty poster. I tried again with the update.zip found here http://forum.xda-developers.com/showpost.php?p=7169129&postcount=18 and all is well. I'm su!
Thanks to chaoscentral for posting that file.
Hi all,
Based on the instructions broodplank posted in the Cranium thread (here), I created some scripts to automate the entire process. Not sure whether you find it useful, but here it is.
If you want to do it directly on your device with an cwm-installable zip, please go to this topic:
The making of ... an ODIN installable package with CWM
It will create a zipped version of the md5-tar file of the package compatible with Odin.
Instructions
1. Build your ROM using packages in the forum. Add new apps, change battery, etc., etc. till your satisfied. Make sure not to add sensitive data (user credentials etc)
2. Download a base-ROM like XXKPS and put the following files in the BaseRom folder:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
3. Boot your device
4. Make sure you have BusyBox installed
5. Connect your device with USB, make sure your sdcard is not mounted on the PC
6. Make sure you have enough space on the internal sdcard; at least 1,84 GB:
system.img.ext4 = 532 MB
tar file = 644 MB
base rom = 100 MB
md5 file = 644 MB
(it would be possible to delete tar file, but I perfer to be safe than sorry)
7. Start BuildOdin.cmd
Thanks to broodplank1337 I now also created some scripts to do it through Cygwin. After rethinking this I could have done it easier by invoking the cygwin commands directly, but for now I am doing it through the shell . See attached.
Downloads... see next post
Regards,
Nika.
Downloads
Just the scripts:
http://forum.xda-developers.com/attachment.php?attachmentid=821537&stc=1&d=1324250313
File that includes BaseRom XXKPS (80 MB):
http://www.multiupload.com/FYGRD3LDFG
What it does...
Here's a little more explanation of what the script does:
BuildOdin.cmd allows minor customization:
ROMName = name of the ROM you are creating (CraniumRC5 in my case)
BaseRomFolder = location it takes the BaseRom files from (default = BaseRom)
TempBuildFolder = location on device it will use to build your ROM (default = /sdcard/BuildRom, I guess you can also use your /sdcard/external_sd - haven't tested it)
It will execute the following scripts:
adb-PushBaseromSdcard.cmd - this will push the files from your baserom folder to the build folder on the device
adb-ExtractRom.cmd - will dump your raw ROM data to files
adb-MakeImageShell.cmd - will create a tempfile that contains the shell commands that will be executed for tarring and md5-ing the ROM
adb-GetRom.cmd - will retrieve the ROM and make a zip-file. It retrieves the ROM and renames it to a time/date based file, this may need some customization in some cases as the date/time naming depends on regional settings...
Any questions? Any tips and tricks to make this better? Let me know!
Regards,
Nika.
Wow! Thanks man, very nice! You can create the tar/md5 on your computer by just copying the files from your sdcard to /home/username in cygwin folder then use the same commands
Thank you! Do I have to use Linux or Windows is good?
edit: I've understood by myself , thanks again for your work
broodplank1337 said:
Wow! Thanks man, very nice! You can create the tar/md5 on your computer by just copying the files from your sdcard to /home/username in cygwin folder then use the same commands
Click to expand...
Click to collapse
Thanks, I'll try cygwin. I tried unxutils, but that added an CRLF instead of LF only at the end of the file and rendered the checksum invalid
nikagl said:
Thanks, I'll try cygwin. I tried unxutils, but that added an CRLF instead of LF only at the end of the file and rendered the checksum invalid
Click to expand...
Click to collapse
Maybe if you invoke a dos2unix? Or 'perl -i -p -e 's/\r//' <your .md5 file>?
wintel_mac said:
Maybe if you invoke a dos2unix? Or 'perl -i -p -e 's/\r//' <your .md5 file>?
Click to expand...
Click to collapse
Good thinking, I did try manually changing the file using a hex-editor but that didn't work and wouldn't be a good permanent fix for something automatic.
I'll try soon ...
Thanks to broodplank1337 I now also created some scripts to do it through Cygwin. After rethinking this I could have done it easier by invoking the cygwin commands directly, but for now I am doing it through the shell . See post #1
nikagl said:
Thanks to broodplank1337 I now also created some scripts to do it through Cygwin. After rethinking this I could have done it easier by invoking the cygwin commands directly, but for now I am doing it through the shell . See post #1
Click to expand...
Click to collapse
Very nice addition! I will use the script for sure
This script also helps in making odin flashables, just posting it as a support to ur work
First thanks for this!
After flashing, the recovery starts and tries to install an update.zip but this fails. I think it doesn't influence the whole falshing process in a bad way. But is there a possibility to skip the installation of the update.zip after flashing an own ROM with Odin.
What is this update.zip exactly doing?
crybert said:
First thanks for this!
After flashing, the recovery starts and tries to install an update.zip but this fails. I think it doesn't influence the whole falshing process in a bad way. But is there a possibility to skip the installation of the update.zip after flashing an own ROM with Odin.
What is this update.zip exactly doing?
Click to expand...
Click to collapse
ah... the Android with the exclamation mark, right? Good question! How do the stock ROMs from Samsung do that? We could off course try to install a dummy update.zip, I think they're the same as the other CWM scripts (ie. Edify scripts)?
By the way, I have only followed the instructions of Broodplank who took them from some other location again (I guess from another phone developer section and simply replaced the right mount points in the instructions) - so I have no idea either
Here's broodplank's previous comment about this:
broodplank1337 said:
normally on a stock rom it installs update.zip after the first boot so if you flash the custom recovery.img it gets conflicted somehow
Click to expand...
Click to collapse
So I guess we could also use the recovery.img from the original xxkps but in that case you'd have to add CWM recovery manually after flashing... it all depends on preference One other option could be to use the stuff from the FeaModRecovery_1.2.tar?
Yes it seems it's a forced option. I always get that after every odin flash. so I'm thinking about using that update.zip to install apps after flashing with odin. This "bug" might even become handy!
broodplank1337 said:
Yes it seems it's a forced option. I always get that after every odin flash. so I'm thinking about using that update.zip to install apps after flashing with odin. This "bug" might even become handy!
Click to expand...
Click to collapse
You're right that sounds really good. But where can I find this update.zip in an Odin-Package?
crybert said:
You're right that sounds really good. But where can I find this update.zip in an Odin-Package?
Click to expand...
Click to collapse
Yep.. that's what I wanna know also I think we can test by placing an update.zip in every directory and then make every separate update.zip unpack an unique file like this:
the one in /sdcard extracts /sdcard/1
the one in /system extracts /sdcard/2
the one in /data extracts /sdcard/3
or
the one in /sdcard extracts /sdcard/present
the one in /system extracts /system/present
the one in /data extracts /data/present
I think that's they way we could test it, I don't think there is an other option available where the zip could be, maybe even on external_sdcard, but that doesn't make sense since not everybody has one..
Could it be that this update.zip is the "sec_csc.zip" which is included in cache.img.ext4. This would make sense. Because this is an flashable zip.
Updater-Script Code
Code:
assert(getprop("ro.product.device") == "GT-P1000" ||
getprop("ro.build.product") == "GT-P1000" ||
getprop("ro.product.device") == "GT-I9000" ||
getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "SC-02B" ||
getprop("ro.build.product") == "SC-02B" ||
getprop("ro.product.device") == "GT-I9003" ||
getprop("ro.build.product") == "GT-I9003" ||
getprop("ro.product.device") == "GT-I9001" ||
getprop("ro.build.product") == "GT-I9001"
);
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
# mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
# unmount("/system");
EDIT: In cache.img.ext4 is a folder called recovery.
recovery includes the following files:
command
sec_csc.zip
in command is the following:
Code:
--update_package=CACHE:recovery/sec_csc.zip
--wipe_cache
So I would say there is really a possibilty to flash something with this command and a zip file in this folder.
crybert said:
Could it be that this update.zip is the "sec_csc.zip" which is included in cache.img.ext4. This would make sense. Because this is an flashable zip.
Updater-Script Code
Code:
assert(getprop("ro.product.device") == "GT-P1000" ||
getprop("ro.build.product") == "GT-P1000" ||
getprop("ro.product.device") == "GT-I9000" ||
getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "SC-02B" ||
getprop("ro.build.product") == "SC-02B" ||
getprop("ro.product.device") == "GT-I9003" ||
getprop("ro.build.product") == "GT-I9003" ||
getprop("ro.product.device") == "GT-I9001" ||
getprop("ro.build.product") == "GT-I9001"
);
show_progress(0.100000, 0);
show_progress(0.500000, 0);
# format("MTD", "system");
# mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
# unmount("/system");
Click to expand...
Click to collapse
Awesome find!!! Gonna try this soon!
I noticed that too, but as the cache file contains the correct script and csc zip I doubt it's that file. Plus, that cache image is also in the stock rom...Last but not least, be careful modifying stuff in csc as that could kill your phone afaik
I have also unpacked the recovery.img from the xxkps and cranium rom (the latter one has the android too after installing my odin package ) but neither contain an update.zip. The big question is what the Odin installers of a stock rom does differently compared to the combination of stock and custom rom the way we make the odin packages. It has to be something in system.img.ext4, recovery.img or boot.img as those are the ones we "custom created" compared to the stock rom...
I'll unpack boot.img too to see what is in there
Regards,
Nika.
Hi,
just to put info at the right place.
A510 root is yet available, thanks to Acer dev..
A100 exploit is still working, at least on current firmwares.
Thanks to Jesse6749, ZeroNull and vdsirotkin (4pda.ru) :
see xda topic here:
http://forum.xda-developers.com/showpost.php?p=25036001&postcount=93
consider installing acer a510 drivers from their website(even if your a510 is currently recognized by your pc)
in addition, some user had bugs at the end of the script, but root is done (su + titanium backup working)
another tool should be mentioned :
http://forum.xda-developers.com/showthread.php?t=1661324
To unlock bootloader (Euclid's Brother ) :
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
As a reminder :
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
out of this :
(thanks nikagl)
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data
So you can use these commands:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/CAC of=/mnt/sdcard/cache.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/MSC of=/mnt/sdcard/misc.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/FLX of=/mnt/sdcard/flexrom.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/AKB of=/mnt/sdcard/AKB.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/mnt/sdcard/bootloader.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/DE2 of=/mnt/sdcard/DE2.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/sdcard/data.img
I hope a mod can move at least the AIO toolbox thread to this forum.
Instead of hoping, why don't you contact the A500 forum mod directly?
FloatingFatMan said:
Instead of hoping, why don't you contact the A500 forum mod directly?
Click to expand...
Click to collapse
Good idea. Done.
Update: Thread has been moved.
Has anyone been able to update their SU binaries?
I updated the superuser app and when I checked my binaries (and tried to update them), I get:
"remounting /system as rw... fail"
I'm thinking I need to update my busybox, but the steps in the OP links says I should not. Can anyone enlighten me on this?
salisbury_steak said:
Has anyone been able to update their SU binaries?
I updated the superuser app and when I checked my binaries (and tried to update them), I get:
"remounting /system as rw... fail"
I'm thinking I need to update my busybox, but the steps in the OP links says I should not. Can anyone enlighten me on this?
Click to expand...
Click to collapse
Using the recovery and root scripts I created I was able to update su, etc. I think the mempodroid exploit has some problem with newer version of busybox, also judging from the other thread (Full root for A10x / A5xx) - see my posts over there. The AIO tool also uses that mempodroid exploit... maybe it's better to start using the recovery & root script?
Regards,
Nika.
---------- Post added at 11:22 PM ---------- Previous post was at 10:32 PM ----------
nikagl said:
Using the recovery and root scripts I created I was able to update su, etc. I think the mempodroid exploit has some problem with newer version of busybox, also judging from the other thread (Full root for A10x / A5xx) - see my posts over there. The AIO tool also uses that mempodroid exploit... maybe it's better to start using the recovery & root script?
Regards,
Nika.
Click to expand...
Click to collapse
Sorry, got to recall this post. The new version of busybox does have some problems with mounting through busybox. Doing it directly works, but through busybox it fails. See my post here: 202
Regards,
Nika.
Thanks for the update. So for now... I just leave it as is, right?
Or should I try to update busybox? And yes, I'm using the mempodroid exploit.
Sent from my Acer Iconia A510
salisbury_steak said:
Thanks for the update. So for now... I just leave it as is, right?
Or should I try to update busybox? And yes, I'm using the mempodroid exploit.
Sent from my Acer Iconia A510
Click to expand...
Click to collapse
Yes, definitely leave it like it is.
How to UNROOT & LOCK
Is it poosible to lock and unroot an previously rooted A511? I am not 100% satisfied with the display and would like sending back my a511 and wait for a701.
loerkus said:
Is it poosible to lock and unroot an previously rooted A511? I am not 100% satisfied with the display and would like sending back my a511 and wait for a701.
Click to expand...
Click to collapse
Easiest methods:
Lock = install new ROM (FOTA, if available, or the 1.011 rom and then do FOTA)
Unroot = install new ROM (although that may not cleanup every trace) or factory reset (which is the best method -- but will wipe ALL your data)
Recovery = not possible yet - I don't recall seeing a stock-A511-recovery yet... you can try putting the A510 recovery on (I did that, it seemed to not work but at least wipes away most of the traces of your hack-attempt)
Regards,
Nika.
FOTA says my ROM is up-to-date. So I have to flash. I downloaded from the Stock-ROM forum Acer_AV041_A511_1.011.00_WW_GEN1.zip. But how can I flash it? Sorry to bother you but I don't want to brick my a511.
loerkus said:
FOTA says my ROM is up-to-date. So I have to flash. I downloaded from the Stock-ROM forum Acer_AV041_A511_1.011.00_WW_GEN1.zip. But how can I flash it? Sorry to bother you but I don't want to brick my a511.
Click to expand...
Click to collapse
I have downgraded twice with that ROM. Just rename it to update.zip, make sure the bootloader is unlocked and copy the zip to your external sdcard and reboot into recovery. It will start the downgrade automatically, reboots, will republish your apps (or something like that) and then you can do the FOTA to move up to 1.034 (I think - can't check as my tab is dead...).
Regards,
Nika.
nikagl said:
I have downgraded twice with that ROM. Just rename it to update.zip, make sure the bootloader is unlocked and copy the zip to your external sdcard and reboot into recovery. It will start the downgrade automatically, reboots, will republish your apps (or something like that) and then you can do the FOTA to move up to 1.034 (I think - can't check as my tab is dead...).
Regards,
Nika.
Click to expand...
Click to collapse
Thanks. Now in CWM I get the error:
...
...
Installing update...
assert failed: getprop("ro.product.name") == "a511_ww_gen1"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
loerkus said:
Thanks. Now in CWM I get the error:
...
...
Installing update...
assert failed: getprop("ro.product.name") == "a511_ww_gen1"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
what is your actual firmware region ?
WW, EMEA or PA ?
loerkus said:
Thanks. Now in CWM I get the error:
...
...
Installing update...
assert failed: getprop("ro.product.name") == "a511_ww_gen1"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
That means you don't have a ww_gen1 A511 device. Yours is probably German (for instance A511_EMEA_DE). You can check that in your device.prop file.
The following is on another forum (translated from Russian):
acer-club said:
On the firmware from another region will be ask only through Customise recovery (someone here wrote that your machines already have this), after removing the check of the firmware from the archive in the installation script (/ META-INF/com/google/android / updater-script) - something like this in the beginning of the installation script:
assert (getprop ("ro.product.name") == "a510_emea_cus1");
this part of the "a510_emea_cus1" on different firmware will be different. Remove all the line.
By necessity, that would not lose the unlock, you need to remove the fill from the new firmware bootloader'a (bootloader.blob file in the root of the archive firmware) and disable the recovery of stock recovery (file / system / etc / install-recovery.sh in the archive or rename the firmware removed), otherwise the whole tablet, and overwrite the unlock will be stitched completely stock firmware.
Next, fill up this way obtained the firmware on the SD card and flashed it through Customise recovery (recovery through the stock it does not work!).
Click to expand...
Click to collapse
It contains some info on what to do, but I think that's way to risky. It did also contain a good hint how to revert recovery! Try to rename the "install-recovery.sh" file back. It's either renamed by the script you executed for root or part of the instructions on how to install the cwm recovery. After this, try to boot a few times and I assume both the recovery and possibly even the unlocked bootloader will be reverted to stock! In that case you can also simply do a factory reset and it will remove the root as well
Rooting via the mempodroid exploid on Acer_AV041_A510_RV28RC02_WW_GEN1 worked as far as I can see (SuperUser and Titanium Backup install and run alright).
Only problem I see is that apps like Titanium Backup and ES File explorer are not able to mount /system as rw and thus are a little limited in there actions. They do not complain on gaining su, that works.
(Re)mount commands via adb shell:
mount -o remount,rw /system
mount -o remount,ro /system
do work as expected.
Any idea's on what is wrong / missing and how to correct it?
Edit:
It seems that a rw mount on / is going OK ???
i used aio tool and rooted and unlocked bootloader...2 questions:
1- how to install a rom now?
2- if i want, can i lock again bootloader and remove root in order to avoid acer assistence troubles?
if i can0t remove it, can i just leave it there? can i install any fota if acer releases it? or acer invalidates guarantee if i need it?
Not working
Hi, I tried this and unfortunately it failed.
PC: Windows 7 64bit
Acer A510: running Android 4.1.2, kernel 3.1.10+, build version Acer_AV051_A510_RV11RC01_WW_GEN1
The A510 is already unlocked using the fastboot method.
Logged inn as administrator, ran runit-win and got:
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
bob497 said:
Hi, I tried this and unfortunately it failed.
Click to expand...
Click to collapse
Install CWM 6.0.1.9 and flash in CWM this zip SuperSu by choose zip from external sdcard or choose zip from sdcard..
Howdy -- I was given a SGH-I747 formerly on AT&T. This was a hand-me-down from a coworker that doesn't know what the prior owner actually did to the thing.
It appears that the phone boot-loops for a bit until it lands in into ClockworkMod Recovery v6.0.4.7. The CyanogenMod logo appears at initial boot.
This recovery tool seems to have no external microSD card access. I already have ADB on my Win7 machine and was able to install a driver for the S3 to allow me to sideload via command prompt.
I attempted to do this with a copy of the stock ROM without root access.
Initially I was forced to update a line on the script to bypass the invalid number of arguments roadblock, but later encountered this:
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I presume something has changed on the primary partition that it wasn't expecting, but I haven't the slightest idea where to go from here.
Thanks for the brainpower
Moderator Edit: Thread Closed at request of OP.
Hello,
I was trying to update my phone(from settings>about phone) and I had no idea that I should not have done that because my phone is rooted; the downloaded update size was small around 12 megabytes as I remember and after restarting it got stuck into android system recovery <3e> (CWM), gave me that error "Installation aborted" and I can't boot into my system again. Unfortunately I haven't backed up my data and when I try to back them up using CWM it gives me this error "Write error, short write!" I tried recovering the backup file later from SD card on PC, it was damaged but I found out that it always crashes at 4 GB file size; I am using a 32 GB memory card and the size of data to be backed up is around 8 GB.
My questions are: Is there any other way to backup my files and applications data before attempting any repair methods?(My main concern) ;even if it was a physical way...
What should I do next?
This is what I have tried so far (without any luck),
- Wipe cache partition
- I tried installing Aroma file manager in CWM mode from SD card but it always gives me the error "Installation aborted".
- Connecting my phone to PC and choosing apply an update from ADB in CWM (The only way my PC can read my phone). I tried then pull, usb and reboot commands but it always gives me a message saying "error: closed". The only command that works is "adb sideload update.zip(Aroma also)" which gives me "Installation aborted" on the phone.
My mobile version is Acer_AV0K0_E39_1.024.00_EMEA_GEN2 (3 sims version)
=These lines are from the end of the log file for the first time the phone bootlooped trying to install the official update
(Unpacking new recovery...ApplyParsedPerms: chown of /system/bin/su to 0 failed: Operation not permitted
ApplyParsedPerms: chgrp of /system/bin/su to 0 failed: Operation not permitted
ApplyParsedPerms: chmod of /system/bin/su to 420 failed: Operation not permitted
ApplyParsedPerms: lsetfilecon of /system/bin/su to ubject_r:system_file:s0 failed: Operation not permitted
ApplyParsedPerms: removexattr of /system/bin/su to 0 failed: Operation not permitted
script aborted: set_metadata_recursive: some changes failed
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /cache/alu/update.zip
(Status 7)
Update.zip is not correct
Installation aborted.
write result : MOTA_RESULT_FILE
write result : remove_mota_file
write result : remove_mota_file(DEFAULT_MOTA_FILE)
fw_upgrade: status = 1
fw_upgrade: fw
fw_upgrade_result_fw: dir does not exist, create it.
fw_upgrade_finish)
I hope that there is someone here who can find a solution to my problem. Thank you for your time.
Hello again,
I am about to try something but I am afraid it might crash my phone even more, so I would love to hear an expert opinion first;
I downloaded the same stock rom as the one in my phone from here (vache-android .com /hubicAcer/E700/OS%20Images/EMEA_GEN2/update_Acer_AV0K0_E39_1.024.00_EMEA_GEN2-sds.zip) and then I am planning to flash using the method in this video to preserve my data (youtube .com/watch?v=b5H6EbaCKrw),and then if this method works and the system booted I am planning to back up my data and applications using titanium back and then do a clean install.
Do you think this might work? If not, What other methods can I try to backup my data?