I upgraded to Cyangenmod 2.2 Froyo on my Kyros, but I decided to downgrade back to Eclair. So I wiped/factory reset. And restored my backup with 2.1 Eclair. I was able to root but I was unable to install clockworkmod recovery. And after doing more research I found that flash_image command is not in my system/bin folder so I'm unable to use the command in adb. I tried copying a flash_image.zip which i found on the forum to my sdcard so i could be able to copy it to system/bin but I can't because it's read-only. The only thing i cant think of now is change the permissions on system/bin directory and copy the flash_image file there, but how to do that??? And if that doesn't work what else can I do??
I tried downloading the update.zip from coby and copy the flash_image file into the file since coby removed the flash_image from the new update. When I tried to update from the the update.zip its giving me verification failed. So its impossible to modifiy the update the file without verification failure. And the old update file isnt working either, seems that when you update the to the new update.zip it prevents you from downgrading.
Solved!
I got it. Make sure your device is rooted, and you have SuperUser.
I downloaded Root Explorer, mounted the "system" directory as RW and then change the permissions on the directory, (I ticked everything, basically full access), then did the same for the "bin" folder. Then I copied my "flash_image" file what I got from my old backup and copied it to the "bin" folder.
I undid the permissions and flashed the recovery.img (which installs the ClockwordMod) with adb and then I was able to install the Android Market and Google Apps.
Got it solved on the same day, just didn't have the time to post it.
Please help ( i'm afraid i bricked the coby 7015)
Hi guys !!!
My coby kyros is in permanent bootloop . The only thing I can do is make it enter into recovery mode ( the original from coby stock ) . I did wipe data and cache but when I try to recover from update.zip it fails because I am using a modified version of this update that was intended for rooted devices - ( so in recovery mode it does not work since it needs the upadte from original stock )-
Is there a way to flash the correct update.zip to the coby via Windows XP ADB ( I have tried to use adb shell but it list no devices and I followed all the steps from another post to install the USB drivers for adb and it worked , but adb list no devices ) - HELP PLEASE
Thanks in advance
Gardelvis
Hi guys !!!
I resolved my problem simply rebooting the PC and adding an adb push command to copy the correct update.zip in the sdcard
Gardelvis
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..
Hi Guys!
Newbie here. I have root my phone I have installed busybox from Google Play. I want to update my busybox to 1.21 so I installed it. I have launched the application and then clicked install. I have chosen "Normal" for normal installation. Then I tried installing the busybox into "/sdcard/busyboxfree/" to see if it would run so I entered "/sdcard/busyboxfree/" to the installation path after selecting "Normal" rather than "Smart". And then an error occured saying my su binary was not found. And then I tried opening a adb session and typed "su" (screenshot attached). I can see the SU app grant superuser permission for adb but the adb shell got stucked (see screenshot). So I tried navigating to /system/bin/ and /system/xbin/ to search for the su binary but I can't find it. I also lost some sh commands like "ls" and "rm" so I am using the busybox to do those commands. I can use the busybox so I suppose it is still in my system.
I have done some restoration such as Factory reset / Wipe Data, and restoring userdata using recovery mode (I don't have CWM so stock recovery). And then I tried rooting it again using the same process I have made rooting it before but now it is not working, I can't get the root back. So I decided to ask the huge developer community and experts to consult what to do about this. :victory:
But I have followed instructions from a post at XDA. I have dumped the mtd6 "recovery" and mtd11 "system" before I did the busybox installation (see screenshot mtd.png). Is this enough to restore things back? How do I flash these dumped images? I will be attaching a link to download the dumped images.
My question is, is there a way to gain SU permissions (root)? Do I just need to push/replace/configure/etc binaries or files? Any help will be appreciated. Thanks!
Click to expand...
Click to collapse
My phone is a re-branded phone from CloudFone. Model is Excite 350g. Original Phone model is "Mobistar Touch Cream 350".
Downloads
System Dump Image
Recovery Dump Image
Links:
Rooting Process for CloudFone Excite 350g by mrichiem
It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.
So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.
I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.
I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works
Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26