After setting up your dual boot by following this guide http://forum.xda-developers.com/showthread.php?t=920347
ADDED AUTOMATIC SCRIPT
just extract the zip file to \Android\platform-tools and run OC.bat to overclock the processor to 1.1Ghz
PLEASE NOTE THIS IS FOR 0.5.6 ONLY AND HASNT BEEN UPDATED FOR 0.6.6 or 0.6.7
if someone wants me to post how to do for 0.6.6 and 0.6.7 I will, but do note its far from automated.
run Original.bat if you wish to revert back to your original speed(should be 800Mhz).
-------------------------------------------------------------
you can setup froyo to be OC'd by following these steps.
*Note extract uFImg into your /android/platform-tools folder then just copy paste everything line by line (uFImg is inside OC.zip if you wish to use this manual method)
Code to enable 1.1Ghz Overclock
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk1 /
mkdir boottmp
mount /dev/block/mmcblk0p1 boottmp
exit
adb pull boottmp/uFImg uFImgbak
adb push uFImg boottmp/uFImg
adb shell umount boottmp
adb reboot
For 0.6.6 and 0.6.7 switch
Code:
mount /dev/block/mmcblk0p1 boottmp
to
Code:
mount -t vfat /dev/block/mmcblk0p1 /boottmp
Credits to minotauri for this
Code to restore original clock (800Mhz)
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk1 /
mkdir boottmp
mount /dev/block/mmcblk0p1 boottmp
exit
adb push uFImgbak boottmp/uFImg
adb shell umount boottmp
adb reboot
800Mhz Froyo gave me a score of 1424 in quadrant
1100Mhz Froyo gave me a score of 1802 in quadrant
guide was modified from the one originally posted here: http://forum.androidcentral.com/bar...-how-overclock-nook-1100mhz-stock-nookie.html
Overclock kernel was taken from dalingrin here: http://forum.xda-developers.com/showthread.php?t=925451
This is my first time posting a guide like this, please post if you have any questions and feel free to PM me for help.
As always no warranty is implied or given with this guide and overclocking your processor can result in negative side effects.
Edit: Nevermind, can't view attachments while only looking at a single post
Thanks for this. I was really hoping this was possible!
Link3737 said:
Edit: Nevermind, can't view attachments while only looking at a single post
Thanks for this. I was really hoping this was possible!
Click to expand...
Click to collapse
No problem.
edit: Nevermind I found it in another folder, turns out i just moved it. Also updated the zip to include uFImgBAK
I was finally able to make this work, however I wanted to use an updated kernel, and the script requires that the uImage file be renamed to uFImg. I did this manually, but it took a while to figure out and pushing uImage to uImage will cause the stock rom boot to fail.
i think your batch file is missing a line.... and that line i cant seem to get working.
adb shell mount /dev/block/mmcblk0p1 boottmp
C:\android\platform-tools>adb shell mount /dev/block/mmcblk0p1 boottmp
Usage: mount [-r] [-w] [-o options] [-t type] device directory
minotauri said:
i think your batch file is missing a line.... and that line i cant seem to get working.
adb shell mount /dev/block/mmcblk0p1 boottmp
C:\android\platform-tools>adb shell mount /dev/block/mmcblk0p1 boottmp
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Click to expand...
Click to collapse
This was posted before 0.6.6 came out or 0.6.7 . I don't know why but it doesn't work with those. Its still possible to overclock but its a bit more complicated and involves imaging your internal boot partition with dd, and manually deleting and injecting the new uFImg. If you think you're up to it let me know and i'll make a guide, otherwise this is 0.5.6 only.
nevermind - i got it working with froyo .67. I did this:
Code:
adb shell
mkdir /boottmp
mount -t vfat /dev/block/mmcblk0p1 /boottmp
exit
adb push uFImg /boottmp
adb reboot
minotauri said:
nevermind - i got it working with froyo .67. I did this:
Code:
mount -t vfat /dev/block/mmcblk0p1 /boottmp
Click to expand...
Click to collapse
Interesting, and thanks. I didn't know the mount command was fixed in 0.6.7 and I knew the remount command was no longer working so I thought it required to be placed into an image and reflashed.
Thanks for the update, will add it to the first post.
Related
So I'm totally unable to do anything to my /system in CWM via ADB.
Code:
> adb remount
remount failed: Operation not permitted
> adb push item.apk /system/app/item.apk
Failed: Permission denied
adb shell
$: su
Segmentation fault
$: rootsh
~# mount /system
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
~# su
# mount /system
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
# mount /system/app
can't find /system/app in /etc/fstab/
Pressing "unmount /system" in CWM results in "Error unmounting /system!" message. I tried pressing "Fix Permissions" but it didn't help. The only thing it did was that "su" results in "Segmentation fault" instead of "Permission denied". I just flashed my Lite'nin ROM again but it didn't fix anything.
I do have root access in normal OS so I can probably do some stuff in terminal emulator. But why is /system busy all the time?
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
kaukassus said:
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Thanks. That apparently mounted the /system but adb was still unable to push the files there. Maybe that is because "su" is still not working, only "rootsh". So I moved the file to my sdcard and then moved it to /system in shell.
Jiia said:
Thanks. That apparently mounted the /system but adb was still unable to push the files there. Maybe that is because "su" is still not working, only "rootsh". So I moved the file to my sdcard and then moved it to /system in shell.
Click to expand...
Click to collapse
since you are using a Secured Kernel(probably the CF-Root with CWM), you have to push the files to /sdcard
and then copy the files from the sdcard to the /system directory.
you can only push files with adb directly to the /system directory, when you are using an insecured kernel.
kaukassus said:
since you are using a Secured Kernel(probably the CF-Root with CWM), you have to push the files to /sdcard
and then copy the files from the sdcard to the /system directory.
you can only push files with adb directly to the /system directory, when you are using an insecured kernel.
Click to expand...
Click to collapse
Oh. Thanks for the info, that cleared things up! I thought you only need to have a custom recovery in order to push with adb but apparently it's about the kernel.
kaukassus said:
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
this not working for me ,still can't mount the system i can't rm9 at ADB at all please help me !
All right... I guess it's time to "ask the experts". My linux background has not been very much help here... ARGH!
Okay, I have two script that I have written that are supposed to mount /system as RO and RW respectively. Very simple:
To mount rw:
Code:
#!/system/bin/sh
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
To mount ro:
Code:
#!/system/bin/sh
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
I manually ran the mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system command and adb pushed them to /system/xbin as mountro and mountrw and chmod both to 755.
In ADB I try to execute:
Code:
/system/xbin/mountrw
and get an error stating:
Code:
/system/xbin/mountrw: not found
I even try:
Code:
/system/bin/sh /system/xbin/mountrw
and I get this error:
Code:
mount: No such file or directory
Okay, so I figured out that it is having a problem trying to find the mount command, so I modify the script to:
Code:
#!/system/bin/sh
/system/bin/mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
I then re-run this:
Code:
/system/bin/sh /system/xbin/mountrw
and I'm still getting this friggin' error message!
Code:
mount: No such file or directory
When I run it through Script Manager I get the same error:
Code:
mount: No such file or directory
This should just friggin' work damn it! (Sorry, very frustrated.)
Also, it would be nice NOT to have to type the path to the script. I can run ZepplinRox V6_SuperCharger script from the ADB command line just by typing from the directory I have it in:
Code:
sh V6_SuperCharger_for_Android-update9_RC3.2.sh
No absolute path, no ./ path... WTF? ARGH!
Okay, I KNOW this is friggin' possible just by the fact that I can run Zep's script in ADB...
So, any takers? Thanks in advanced...
Friggin' Ciao.
[EDIT]
Okay, I figured out a work around for this... I probably should not work on this after working at work all day... But, that is another story...
I have heavily modified the script files I have created. They are still called mountrw and mountro and the contents are as follows:
mountrw:
Code:
#!/system/bin/sh
# This mounts the /system file system as Read Write in order to modify or add
# files to the /system file system.
busybox mount -o remount,rw / 2>/dev/null
busybox mount -o remount,rw rootfs 2>/dev/null
busybox mount -o remount,rw /system 2>/dev/null
mountro:
Code:
#!/system/bin/sh
# This mounts the /system file system as Read Only which is the default when
# Android is booted.
busybox mount -o remount,ro / 2>/dev/null
busybox mount -o remount,ro rootfs 2>/dev/null
busybox mount -o remount,ro /system 2>/dev/null
So, after poking around in ZepplinRox's V6_SuperCharger script, I found those values repeated several times, so that helped point me in the right direction. The next problem I had was getting the scripts to "run from anywhere". I still haven't figured that one out yet, and the VERY MESSY solution to that is to put the two scripts in /. I know, I know, I know... that is the most dangerous place to put it.
So, when I first log into the ADB shell all I have to type is
Code:
sh mountrw
and when I'm done, type
Code:
sh mountro
So, As the work around, this works. I really don't recommend anyone else doing this because of the data security risks that you open your phone up to... Yes, I'm aware of them and that is why I am asking now for some help in having the ability to run a script globally, from anywhere in the android file structure. I don't mind typing the "sh" in front of the script since I sometimes must do that in linux. I have noticed that the $PATH of Android doesn't allow scripts to be executed unless you type the absolute path to the script, or are in the same directory as the script.
Okay, so again to ask: Is there any way to execute a script without having to type the absolute path to it? Thanks!
Ciao! (MUCH calmer now then when I first wrote this post...)
[/EDIT]
I don't use adb much at all.
Usually I move stuff around with root explorer and use terminal emulator a lot.
I assume you ran everything as superuser as I sometimes forget to type su first
Maybe the sh command work on the supercharger script because it has the .sh extention.
You can try typing "bash mountrw" since that works when I install the script to /system/xbin/V6
But after reading your post I looked and saw I forgot about permissions so I did chmod 755 and now this works...
su
V6
heh..
I don't have tp type "bash V6" anymore
zeppelinrox said:
I don't use adb much at all.
Usually I move stuff around with root explorer and use terminal emulator a lot.
I assume you ran everything as superuser as I sometimes forget to type su first
Maybe the sh command work on the supercharger script because it has the .sh extention.
You can try typing "bash mountrw" since that works when I install the script to /system/xbin/V6
But after reading your post I looked and saw I forgot about permissions so I did chmod 755 and now this works...
su
V6
heh..
I don't have tp type "bash V6" anymore
Click to expand...
Click to collapse
Yes, I ran everything as su. (I'm a linux admin guy, so su and sudo is next to natural for me...)
Okay, so you put the mountrw script in /system/xbin/V6/ ??
Also, it is an sh script. I identify that in the first line of
Code:
#!/system/bin/sh
I have changed it to bash and same problem. Oh well. I think I can live with the scripts at /
Thanks though!
Ciao!
I was following a thread at DroidXForums on how to do it and when I get the "cp /sdcard/done_app/* /system/app/" command, it says that there is no file or directory there. The instructions from the DroidXForums is below and when I have the ability to post links I will post a link to the thread.
Could I get some help?
Unzip xUltimate v2.2, and launch "Main.exe"
If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
Run option 1. After option 1 is done, run option 2.
Now these well take a while. Run option 3.
IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
Now run option 4, and wait.
Exit xUltimate, and put the phone in USB mass storage.
Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
Open a command prompt, and do the following:
Code:
adb shell
su (note: super user will be promp on your phone)
stop
mount -o rw,remount -t emmc /dev/block/mmcblk0p12 /system
cp /sdcard-ext/done_app/* /system/app/
cp /sdcard-ext/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t emmc /dev/block/mmcblk0p12 /system
reboot
I belive
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
are wrong to use on the Photon should be
adb shell
su (note: super user will be promp on your phone)
stop
mount -o rw,remount -t emmc /dev/block/mmcblk0p12 /system
cp /sdcard-ext/done_app/* /system/app/
cp /sdcard-ext/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t emmc /dev/block/mmcblk0p12 /system
reboot
I shall try that. I will edit this later tonight and let you know how it goes!
Edit: Still no luck even when following your code.
well a simple way to deodex rom is use one thats already out Jokers think he has a pretty much stock rom with just a few minor tweaks.
if not there is always Yay's deodexd update zip
http://forum.xda-developers.com/showpost.php?p=16328237&postcount=1 scroll down its the
Stock Deodexed and Zipaligned ROM UPDATED WORKING DATA link
---------- Post added at 08:42 PM ---------- Previous post was at 08:39 PM ----------
i checked that link and first line says must be ROOTED are you?
ZeroManArmy said:
I was following a thread at DroidXForums on how to do it and when I get the "cp /sdcard/done_app/* /system/app/" command, it says that there is no file or directory there. The instructions from the DroidXForums is below and when I have the ability to post links I will post a link to the thread.
Could I get some help?
Unzip xUltimate v2.2, and launch "Main.exe"
If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
Run option 1. After option 1 is done, run option 2.
Now these well take a while. Run option 3.
IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
Now run option 4, and wait.
Exit xUltimate, and put the phone in USB mass storage.
Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
Rangerbry said:
i checked that link and first line says must be ROOTED are you?
Click to expand...
Click to collapse
I am rooted and the way I fixed it was to put the phone in Charge Only Mode, and it worked. I am unable to see in the log file created by Test.exe if I am fully deodex'd.
Code:
(21:42:24.89 Wed 11/23/2011)
****
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android\platform-tools
****
C:\Windows\system32\java.exe
****
Main ADB
Android Debug Bridge version 1.0.26
****
PATH ADB
Android Debug Bridge version 1.0.29
****
[ro.build.id]: [4.5.1A-1_SUN-198_7]
[ro.build.display.id]: [4.5.1A-1_SUN-198_7]
[ro.build.version.incremental]: [CM]
[ro.build.version.sdk]: [10]
[ro.build.version.codename]: [REL]
[ro.build.version.release]: [2.3.4]
[ro.build.date]: [Mon Oct 3 13:59:39 EDT 2011]
[ro.build.date.utc]: [1317664779]
[ro.build.type]: [user]
[ro.build.user]: [eaz002]
[ro.build.host]: [fl36bld22]
[ro.build.tags]: [release-keys]
[ro.build.product]: [moto_sunfire]
[ro.build.description]: [sunfire-user 2.3.4 4.5.1A-1_SUN-198_7 CM release-keys]
[ro.build.fingerprint]: [sprint/moto_sunfire/sunfire:2.3.4/4.5.1A-1_SUN-198_7/CM:user/release-keys]
[ro.build.version.full]: [Blur_Version.45.3.7.MB855.Sprint.en.US]
****
adb server is out of date. killing...
* daemon started successfully *
TA28700TGP
So was I Deodexed?
How can I do this without a sd card... thanks in advance.
Sent from my LG-VM670 using Tapatalk
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Curiousn00b said:
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Click to expand...
Click to collapse
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
tvall said:
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
Click to expand...
Click to collapse
developer++ said:
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
Click to expand...
Click to collapse
Thanks alot guys, I really appreciate it, but I get stuck at
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
C:\android-sdk\platform-tools>
I'm starting to learn more, as I knew alot back when I first rooted my phone. As time went by..... easier ways were made.
Help plz.
EDIT: Been messing around with it, but still no go. This is what I got. Keep in mind I messed with some stuff if it doesn't look right..... :s
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Bump...
Sent from my LG-VM670 using Tapatalk
I have made inline comments. Just take note of it.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
Click to expand...
Click to collapse
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
Click to expand...
Click to collapse
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
Curiousn00b said:
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Click to expand...
Click to collapse
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
developer++ said:
I have made inline comments. Just take note of it.
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
Click to expand...
Click to collapse
I tried again about 8 hours ago. I got through everything with no error, but when I got to recovery, it was still the old one. I'll try again once I get home.
Sent from my LG-VM670 using Tapatalk.
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
_Arjen_ said:
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
Click to expand...
Click to collapse
Rom manager bricks the Optimus.
Dan_Jacques said:
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
Click to expand...
Click to collapse
Sent from my LG-VM670 using Tapatalk
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Curiousn00b said:
Rom manager bricks the Optimus.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
well most time i did it via rom manger and all time it was a sucess ,still lgmdp is good option but rom manger does it quiet easily just make sure u ahve a good internet connection so that its not disrupted when downloading better connected via wifi orelse better to go wth lgmdp method
Curiousn00b said:
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
developer++ said:
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
Click to expand...
Click to collapse
I never found out how to change the thread name.
And ill edit the post tomorrow. I also have another question.
Sent from my LG-VM670 using Tapatalk
Can someone with a sd card, and adb, test this out? I don't want to test it out, cause without a sd card mounter, if it doesn't work, I'm screwed. If it doesn't work, I'm sure you have a nandroid on your sd card, hopefully. Please and thank you.
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
Sent from my LG-VM670 using Tapatalk
I have an Acer A210 and have modified the boot.img to have ro.secure=0 and ADB root. Then I had to mount the /system partition but that is not so easy:
Code:
C:\>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
C:\>adb push busybox /data/local/tmp
1065 KB/s (777216 bytes in 0.712s)
126|[email protected]:/data/local/tmp # chmod 755 busybox
chmod 755 busybox
[email protected]:/data/local/tmp # ./busybox mount -o remount,rw /system
./busybox mount -o remount,rw /system
mount: permission denied (are you root?)
Currently the only way to mount /system rw is this:
Code:
cd /system/xbin/
mount -o remount,rw /dev/block/platform/sdhci-tegra.3/by-name/APP /system/
So now I have root (pushed su and busybox from A510 and installed SuperUser from ChainsDD) but installed applications that want to mount /system rw cannot do that. I think because of the mounting problem. Also a custom CWM 6.0.1.4 cannot mount /sdcard but it works with ADB.
Thanks for help with that!
MaluNoPeleke said:
So now I have root (pushed su and busybox from A510 and installed SuperUser from ChainsDD) but installed applications that want to mount /system rw cannot do that. I think because of the mounting problem. Also a custom CWM 6.0.1.4 cannot mount /sdcard but it works with ADB.
Thanks for help with that!
Click to expand...
Click to collapse
Acer implemented in kernel "system RW protection" (I don't know how to call that)- kernel prohibits such operations. Only workaround is compiling a custom kernel with this feature disabled.
As for recovery- check /etc/fstab if sdcard mountpoint (stored in init.rc or init.[device name].rc) matches the one recovery uses (/etc/fstab)
Thanks for that! Is it hard to disable the system rw security in the kernel? I haven't done that before. Is there a tutorial from another Acer tablet?
How can I check the fstab content in the recovery? It was built by the recovery builder.
Thanks!
MaluNoPeleke said:
Thanks for that! Is it hard to disable the system rw security in the kernel? I haven't done that before. Is there a tutorial from another Acer tablet?
Click to expand...
Click to collapse
It's a kernel config option only, for a510 it's CONFIG_ACER_SECURE_MOUNT and it is accessible in menuconfig or by hand- in .config change "CONFIG_ACER_SECURE_MOUNT=yes" to "# CONFIG_ACER_SECURE_MOUNT is not set" (as for kernel compilation- there are many tutorials floating around)
MaluNoPeleke said:
How can I check the fstab content in the recovery? It was built by the recovery builder.
Click to expand...
Click to collapse
Start recovery and just
Code:
adb shell
cat /etc/fstab
or
Code:
adb pull /etc/fstab [path on your pc]
I've never used any recovery builder but kernel and ramdisk/initramfs (where recovery is placed) are separate files, you can unpack boot.img and just modify what you need (note- linux machine required, virtual one will do)
Is it already disabled in the source code?
Code:
[email protected] ~/Dokumente/kernel $ grep -R -i 'CONFIG_ACER_SECURE_MOUNT*' ./*
./arch/arm/configs/picasso_mf_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_m_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./fs/Makefile:ifeq ($(CONFIG_ACER_SECURE_MOUNT),y)
It seems that it's disabled.
Is there a zip file for Acer 210 tablet now 4/2013
dobie62 said:
Is there a zip file for Acer 210 tablet now 4/2013
Click to expand...
Click to collapse
There is a real lot available for A210:
Pure root (German)
CWM recovery (German)
Custom Kernel
CM 10.1 like ROM
What are you looking for?
regards Uwe
This is it but in English please.
A210
Are the A210 and the A510 similar enough to use the same kernel, ROM's or Recovery?