Note 3.16 and below are for HoneyComb bootloader 3.17 & up are for ICS patched bootloader.
This is built from my forked Amon Ra recovery source.
WARNING UNLESS YOU ARE VERY FAMILIAR AND COMFORTABLE USING COMMANDLINE/TERMINAL DO NOT MESS WITH THE EXT3|EXT4 MENU. MESSING WITH THE PARTITION FORMATS CAN LEAVE YOUR ICONIA IN A STATE THAT IS UNABLE TO BOOT NORMALLY AND REQUIRES FIXING VIA COMMANDLINE. Fix for ignoring this warning is done by running "iconia_repair.sh help" from command line in recovery.
Full source for both Apache licensed recovery and GPL licensed kernel & busybox are here
Recovery Features:
Special features for acer iconia :
Touch enabled UI
Can use usb flash drive or normal sdcard as sdcard to flash roms and to use in nandroid backup/restore.
Automatically runs itsmagic on boot
External sdcard mass storage works on iconia
Automatically backs up usb serial (uuid) and the start of mmcblk0 in nandroid backup.
Will not remove /data/media unless full ext wipe option is selected (off by default)
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup items with [X] to restore
Nand Restore Clockwork : browse to and restore cwm backup
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse.
Toggle Signature Verify : Toggle on/off signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all (data, cache, android_secure & dalvik if outside of /data)
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe system
Wipe sdcard
Wipe .android secure : Wipes froyo+ native .android_secure on sdcard
Toggle full ext wipe: Toggles full or quick wipe of ext partitions
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (
Mounts:
Gui mounts to avoid typing in terminal to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix Permissions
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check Battery Lvl
Ext3|4 menu: Formatting and re-formatting of partitions
Developer menu:
Make and flash boot from zImage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Trouble Shooting:
Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log which will be on your external sdcard. It should have detailed cause of error if its not self-explainatory upload it here as an attachment and then post details about the error. Posts without the log are a complete waste of my time and will be ignored as there is no usable info to assist me in troubleshooting it. You will also be told to go visit /dev/null.
Special Thanks:
Thanks to :
Amon Ra
Koush
Sc2k for itsmagic and getuid.ko
Gweedo767 & CEnnis91 for the touch ui
Skrilax_CZ for patched ICS bootloader & setbootmode
Download Section:
To flash on HC bootloader(requires root):
run itsmagic then
Code:
adb push recovery-ra-iconia-3.13-gnm.img /sdcard
adb shell
su
dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
To flash on ICS Patched Bootloader:
fastboot flash recovery nameofrecovery.img
V3.17 Recovery flashable zip : recovery-ra-iconia-3.17-gnm.zip
ICS recovery-ra-iconia-3.17-gnm.img
md5sum e74dd63395baed6d00c724024ab2d5cc recovery-ra-iconia-3.17-gnm.img
recovery-ra-iconia-3.16-gnm.img
md5sum 357a7033171585005db89d505b6b7c65 recovery-ra-iconia-3.16-gnm.img
recovery-ra-iconia-3.15-gnm.img
md5sum f40fc8fe8708df75583338d09be33ea0 recovery-ra-iconia-3.15-gnm.img
recovery-ra-iconia-3.14-gnm.img
md5sum d69390b62dd914a440ca2ae90ff95a0a recovery-ra-iconia-3.14-gnm.img
recovery-ra-iconia-3.13-gnm.img
md5sum 292d0a37cc7971baab2b32d6dae0d74c recovery-ra-iconia-3.13-gnm.img
Flashable zip for 3.13 is here http://forum.xda-developers.com/showpost.php?p=21727826&postcount=13
Changelog 3.14 :
Added menu option to wipe flexrom and also included it in the default wipe all
Added option to flash a zip from internal storage
Added warnings on using the ext3|4 menu
Added recovery shell script called iconia_repair.sh for users that ignore the above warning and have corrupted their partitions. To use call "iconia_repair.sh help" from adb shell in recovery.
Changelog 3.15
Fixed wipe boot option on emmc devices
Fixed ext3|ext4 format menu for iconia & updated the iconia_repair.sh script to match (still may error 1st time if users used this option on 3.13 or 3.14 to format use script to repair and it will work properly from there out)
Itsmagic is now built into recovery binary
Sdcard is now unmounted after flashing a zip from it.
Changelog 3.16
Fixed nandroid restore from usb stick
Added ability to nandroid restore a cwm backup from usb stick
Changelog 3.17
Updated for ICS patched bootloader
Removed auto run of itsmagic (still there from cmd line)
Updated Mass storage in recovery to 2.6.39 kernel
Compiled setbootmode into recovery -- call setbootmode from cmd line to use
Default quick wipe and nandroid backup skips /data/linux directory if present -- toggling full ext wipe will still remove and reformat 100% of /data
Note: nandroid backup folder is changed from nvmem=* to your devices serial # so you may need to manually move old RA backups into new folder.
Updated su & superuser.apk to current
Seems cool ill try it out in am.
Sent from my HTC Inspire 4G using Tapatalk
Thanks bro. Just downloaded it. Will give it a try in the am. Off to bed!
Just gave it a quick test. Seemed to work fine (touch controls & backup). Haven't tried a restore yet, which is the true test.
Much thanks! This looks extremely promising.
just curious, being a first time venturing a little bit with my a500, how does one run "itsmagic"? i'm having issues with my windows 7 x64 pc recognizing my tablet running thor's latest ICS build 89 over adb, so would it be possible for somebody to make this as a flashable zip from the recovery i already have installed? or is that crazy... i flash new recoveries all the time for my fascinate or droid 1 in CWMR so I'm just curious. thanks!
Same here ive looked at the old its magic thread from way back and still not sure how to call it.
would some one be able to put together s CWM .zip for us to save alot of the same posts?
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1665 KB/s (5001216 bytes in 2.932s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ # sync
sync
[email protected]:/ # sudo
sudo
sh: sudo: not found
127|[email protected]:/ # su
su
[email protected]:/ # exit
exit
[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # itsmagic
itsmagic
sh: itsmagic: not found
127|[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1932 KB/s (5001216 bytes in 2.527s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ #
this is what i get. not a directory? Does thor's ICS have something set up differently? I'd love to get a legit recovery up in here. Thanks.
---------- Post added at 11:56 AM ---------- Previous post was at 11:43 AM ----------
just for anyone looking in, joe9002 for example, I followed the steps from here to find out you have to run the second set of command in the terminal on the tablet. much easier with a usb keyboard, i might add. got it installed and running nicely. it ain't pretty, but the touch does work. I guess i was expecting more like TWRP with big icons, but not having to use the way too recessed volume buttons is awesome. thanks guys!!!!!
please provide a flashable zip....lazy kid)
easy install
i have used acer recovery installer
http://forum.xda-developers.com/showthread.php?t=1226191
josinpaul said:
please provide a flashable zip....lazy kid)
Click to expand...
Click to collapse
+1, would someone please do a cwm flashable zip for this ?
Thank a million
Sent from my A500 using Tapatalk
If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.
I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE
erica_renee said:
If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.
Click to expand...
Click to collapse
NOT logical at all!
You need a script run to install it. See post above!!!!
kjy2010 said:
I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE
Click to expand...
Click to collapse
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?
internetpilot said:
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?
Click to expand...
Click to collapse
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Oops...see that now in the OP. Thanks. Sorry, the running itsmagic as part of the install process through me for a loop. I know that I've seen Thor's CWM recovery automatically loading it, and I was worried that with this recovery we'd have to do it manually.
Alright. Maybe I'll be the guinea pig and try a restore.
kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
internetpilot said:
Alright. Maybe I'll be the guinea pig and try a restore.
Click to expand...
Click to collapse
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.
drellisdee said:
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.
Click to expand...
Click to collapse
Thanks again dell! We needed an alternative to the GPL non-compliant CWM that we had!
Your work is GREATLY appreciated and the touch screen is an added bonus!
Very nice addition to the A500, thanks for the hard work.
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Ikran said:
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Click to expand...
Click to collapse
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
ksilver89 said:
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
Click to expand...
Click to collapse
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Ikran said:
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
Click to expand...
Click to collapse
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
andyabc said:
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Ikran said:
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Click to expand...
Click to collapse
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
occupied icinme
andyabc said:
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Ikran said:
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Click to expand...
Click to collapse
Then you are just booting to it (not flashed) but anyway one you get on there you have to TWRP, Advanced and then Terminal command.
Go to the system folder and type the following commands IF you have the backup:
rm build.prop
mv build.prop.bak build.prop
Sent from my Nexus 4 using Tapatalk 4
ksilver89 said:
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
Click to expand...
Click to collapse
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
Go to the bootloader, it has Fastboot from there.
EDIT: Oh you where talking about ADB, try using the method I posted on the previous page.
Sent from my Nexus 4 using Tapatalk 4
Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
ksilver89 said:
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
Click to expand...
Click to collapse
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
It is worth mentioning that the command "fastboot oem unlock" will actually erase all the personal data (should also include sdcard folder) and make it a blank phone! Use with cautions!
andyabc said:
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
so the phone when i turn it on, the logo from google appears and under that the unlocked lock , next, the 4 colored lines of nexus should appear . my phone doesnt gets to that, after the image of google disappears , its just a black screen , think is that bootloop you were saying.
BUT i managed to install cwm 6.0.3.5 on the phone and i am able to boot into recovery now . twrp wouldnt load for some reason, just frozen on the google logo when it was suppose to load .
so at this point i am here as you said:
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here. ( cwm 6.0.3.5 )
ROM: Not Running
in cmd i did: adb devices >result:
C:\Program Files (x86)\WugFresh Development\data>adb devices
List of devices attached
00765833628b346b recovery
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Ikran said:
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Click to expand...
Click to collapse
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
ksilver89 said:
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
Click to expand...
Click to collapse
thanks it worked, i had to mount the /system partition for the shell command to work, the phone booted up now, and it works, but for some reason everything is wiped from the phone i had some backup , i will see if i can restore anything from it. if not c'est la vie.
Thanks again
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Rockstar600 said:
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Click to expand...
Click to collapse
Yes, maybe.
Nuu~ said:
Yes, maybe.
Click to expand...
Click to collapse
Okay,
Let me quote my problem,
I also posted it on MSkip's Toolkit thread,
I did search but wasn't able to find a proper solution,
I was on a 4.3, with latest TWRP installed,
I flashed a ROM that was 4.2.2 after I flashed the phone was not booting up, and was stuck on Google logo,
I did wipe in the TWRP and even re-installed the ROM, had the same issue again,
So, I thought to flash 4.2.2 Google Factory Image via this toolkit,
I downloaded the Factory Image from Google and placed it in the folder which says "Put factory image here"
Followed all the procedures, and flashed the 4.2.2 factory image in my phone,
Now the phone is stuck on the X logo,
I tried going into the stock recovery and did a factory reset, but again the same thing,
The phone isn't booting up,
Also one thing i noticed, while the phone is booting the "Google" logo stays around a minute, and then the X boot animation appears,
Any clue what to do??
I tried pushing the factory image via toolkit several times, but again I'm stuck at the same boot animation,
Please help me regarding this,
I'm at work, trying to search and find information as much as I can,
I can now boot on 4.2.2 but in settings the phone says that the base band is unknown, IMEI is gone,
And I cannot even see the internal storage when I connect my phone to PC.
Here is what I'm facing.
Also check this,
I got this error too, unable to post the image so posting the link http://imageshack.us/photo/my-images/9/jys1.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you need any other details, please just do ask me, I will try my best to answer you properly.
Thank you.
Hi !
I have a problem, my phone (nexus with cyanogenmod10.2) switch off when he have finished to boot, as if there was very low power battery.
So i want to reset all but i need a solution to save all my datas, on "sdcard" and in "system" memory
i read that i can using the cmd : adb pull "device files directory" "PC files directory"
but i don't know how to use it... i'm french and its hard to translate all...
so if there is a French who can explain me its perfect !
if the explanations are clear in english its perfect too
To use any of these command you need to install adb on your computer. Here is a guide: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that you open a command prompt window (windows key + r, type in "cmd", press enter). Then you put the phone into custom recovery and use the command "adb pull /sdcard/".
I've done these steps
But my problem is how to write, i need the "trame"(in french).
to be in recovery mode, i just have to boot in fastboot and select recovery mode and press power and next step is to sent my commands right?
the bg gg said:
I've done these steps
But my problem is how to write, i need the "trame"(in french).
to be in recovery mode, i just have to boot in fastboot and select recovery mode and press power and next step is to sent my commands right?
Click to expand...
Click to collapse
Correct.
Chromium_ said:
Correct.
Click to expand...
Click to collapse
Ok, but, i'm in the correct directory to use adb i write : adb pull /sdcard/ E:\Nexus4SDcard\ and nothing happens, as if i made a mistake... and i need to save all, sd card + system, so how can i do? what is the directory?
Someone can help me? 3 days without phone its hard :/
the bg gg said:
Ok, but, i'm in the correct directory to use adb i write : adb pull /sdcard/ E:\Nexus4SDcard\ and nothing happens, as if i made a mistake... and i need to save all, sd card + system, so how can i do? what is the directory?
Click to expand...
Click to collapse
If you looked at that other guide and have added adb to the environment variables
In your command prompt, do the following
E:
cd Nexus4SDcard
adb pull /sdcard
It should now being transferring
Sent from my Nexus 4 using xda app-developers app
finally i didn't write any directory for destination and it works fine but in this directory : C:\Program Files (x86)\Android\android-sdk\platform-tools, but its not a problem, using command prompt : "adb pull /"
how can i save and restore all my sms messages?
If the database is still intact it is located at /data/data/com.android.providers.telephony/databases/mmssms.db
You grab it the same way you tried to pull.
In recovery
adb shell mount /data
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Sent from my Nexus 4 using xda app-developers app
i have an error :/
"C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Device or resource busy"
and when i'm in the recovery mode i can't unmount /data
Sounds a little extreme... chances are, there's a better method.
If you have CM10.2, then no doubt you have a custom recovery already. I'm going to assume that this is not an actual battery issue. Is it crashing and rebooting or flat out turning off? I can't remember if CWM shows battery percentage, but TWRP does. What does it show?
What are you trying to back up? Just your /sdcard? Or your /data as well?
What happened to make it seemingly turn off once it's booted? Did you flash a new nightly?
You could always backup /data in your custom recovery as well and then do the wipe that doesn't erase the "sdcard" and then pick apart your backup later...