Related
I have tested the following with the frest 2.1 2.0b2 build and it does enable Apps2SD.
Ver 3 now should work on fresh fine, and damageless (sometimes I found enabling apps2sd on damageless causes lockups at boot, these can be fixed by doing WIPE for DATA for now) :/
MAKE NANDROID BACKUP
This has been tested on: Fresh 2.0b2
ADDED INSTRUCTIONS TO ENABLE ON DAMAGELESS
Also this has been edited so the first few pages refer to the old style before I had signed zips working. xD
Flash the Update Zip Attached VIA recovery menu. That means copy it to the root of your sdcard (aka /sdcard/).
I tested this after a fresh wipe with a blank ext2 partition and one vfat (normal). I did not even boot it first run but you should be able to flash this on an existing rom. Others can test on other roms but I am using this for now on fresh 2.1 2.0b2.
Afterwards run the following after booting
FOR VER 3 SIGNED
Code:
[B]
adb remount
adb shell
cd /system/bin
ln -s /system/xbin/busybox /system/bin/sed
ls -l /system/bin/sed # make sure it exists
cd /
apps2sd on
# should say apps2sd enabled
reboot[/B]
FOR VER 1 SIGNED
Code:
[B]
adb remount
adb shell
cd /system/bin
busybox --install /system/bin
ls -l sed # make sure it exists
cd /
chmod 755 /system/bin/apps2sd
chmod 755 /system/xbin/apps2sd
apps2sd on
# should say apps2sd enabled
reboot[/B]
FOR VER 3 SIGNED for DAMAGELES
Code:
[B]
adb remount
adb shell
cd /
apps2sd on
# should say apps2sd enabled
# below fixes up the scripts generated by the 'apps2sd on' line.. who ever wrote that had it put DOS CR/LF on the ends and thats whats breaking APPS2SD on damageless!
cd /system/etc/init.d
dos2unix 04apps2sd
dos2unix 05userinit
reboot[/B]
Enjoy
Will this work on the other 2.1 ROMs?
I have only tested on fresh 2.1 2.0B . I would think that logically this should work on the other fresh 2.1 2.0 and perhaps Damageless's. As for darchstar's try it I havent run that rom in a few days.
kkruse said:
I have only tested on fresh 2.1 2.0B . I would think that logically this should work on the other fresh 2.1 2.0 and perhaps Damageless's. As for darchstar's try it I havent run that rom in a few days.
Click to expand...
Click to collapse
If someone could test this out and let me know if it works on my ROM then I would love to just use the same method to get it going with the author's permission (credit will be given).
i keep no space left on device when i do this command
cat /dev/zero > /dev/mtd/mtd2
networx2002 said:
i keep no space left on device when i do this command
cat /dev/zero > /dev/mtd/mtd2
Click to expand...
Click to collapse
same for me
cat: write error: No space left of device
If I remember right it is a different file than what he posted...
I will have to check.
Maybe you can help me w/ this... When I adb shell in recovery I get "/#" instead of "#" & I can't "mount -a"...
networx2002 said:
i keep no space left on device when i do this command
cat /dev/zero > /dev/mtd/mtd2
Click to expand...
Click to collapse
Another one with this issue.
Running Fresh 2.1 2.0b2 on a clean install.
Already have a partitioned SD card with apps installed (from fresh 1.1 rom)
Has anyone besides OP gotten this to work?
mrcharlesiv said:
Maybe you can help me w/ this... When I adb shell in recovery I get "/#" instead of "#" & I can't "mount -a"...
Click to expand...
Click to collapse
/# would mean you are adb into recovery......I think
Aye, / # means you are in recovery mode on the phone is all.
Not sure why you aren't able to mount -a. I'm curious if anyone has gotten this method to work yet..?
So I went ahead and did every step despite the errors it gave just to see what happens... It's booting....
EDIT: Seems like it worked. My internal memory dropped by a/b 20 megs and I'm reinstalling everything. Idk.
mrcharlesiv said:
So I went ahead and did every step despite the errors it gave just to see what happens... It's booting....
EDIT: Seems like it worked. My internal memory dropped by a/b 20 megs and I'm reinstalling everything. Idk.
Click to expand...
Click to collapse
K, I attempted to reboot and it hangs at the HTC screen, so I'm going to boot back into recovery and try to continue from the out of space error.
Last night I tried adding a2sd, e2fsck to /system/bin of Fresh and made a directory SD in /system
Then I added to the init.rc
on property:cm.filesystem.ready=1
class_start default
start a2sd
and
service a2sd /system/bin/logwrapper /system/bin/sh /system/bin/a2sd
disabled
oneshot
then mkbootimg and placed that boot.img into fresh's zip and resigned it.
It flashed ok. But still didn't take. I'm still learning, the stuff I did to iniit.rc I was just basically copying and pasting from other roms with a2sd init.rc's I was going to start a thread until I saw this one.
I was able to boot back into recovery and complete the setup past the out of space error (I still get it though) and reboot. It booted up, but apps are still installing to the internal memory, so it did not work.
mrcharlesiv said:
So I went ahead and did every step despite the errors it gave just to see what happens... It's booting....
EDIT: Seems like it worked. My internal memory dropped by a/b 20 megs and I'm reinstalling everything. Idk.
Click to expand...
Click to collapse
Try this from CMD Prompt
Adb remount
Adb shell
# cd /data/app
#pwd
let us know what you get
if data/app it didnt work.
So I've reinstalled about 15 apps and my internal memory is staying at 73...
I'm still kinda worried about those errors I got.
mrcharlesiv said:
Maybe you can help me w/ this... When I adb shell in recovery I get "/#" instead of "#" & I can't "mount -a"...
Click to expand...
Click to collapse
same here... anyone know where to go from here?
mrcharlesiv said:
So I've reinstalled about 15 apps and my internal memory is staying at 73...
I'm still kinda worried about those errors I got.
Click to expand...
Click to collapse
did you try doing what swaze said?
swaze said:
Try this from CMD Prompt
Adb remount
Adb shell
# cd /data/app
#pwd
let us know what you get
if data/app it didnt work.
Click to expand...
Click to collapse
kashb91 said:
did you try doing what swaze said?
Click to expand...
Click to collapse
Way to rain on my parade! Yeah it didn't work. Idk why my memory dropped and stayed lower then?
How to Flash a ROM Without an SD Card
This is for all those who don't have a working sdcard, sdcard slot, etc. but want still to flash a new rom
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork - I recommend Darch's unofficial (CDMA Hero refer to my signature if you need it)
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\ROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "ROM.zip" with the name you're using)
Code:
adb push ./ROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:ROM.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
Brief rundown of what we just did:
Wiped /data/ to free up space for the zip
Put our ROM.zip onto the /data/ partition since we don't have an SD Card to work with.
Told the recovery to flash from our /data/ partition instead of /sdcard/
I did some digging around the AmonRA github to look for the commands it actually performs while in recovery I figured out exactly how to do what I wanted.
(namely THIS PAGE for those of you who are interested in seeing the exact page I found them on)
Good knowledge man. Thanks for the guide
Root-Hack-Mod-Always™
I got excited when i read the title having lost my sdcard, unfortunately my lap top in Frys customers service n i never went back for it, bs they said it was water damage lol idiots are wrong so my guarantee didnt cover it,anyways i think most of us knew this method, thnkz anyways........WHAT I WANT TO KNOW IS HOW OR IF POSSIBLE TO CHANGE THE PATH TO THE STOCK BROWSER DOWNLOADS TO INTERNAL STORAGE????????????? PLS IF ANY1 KNOWZ LET ME KNOW
gotablunt said:
I got excited when i read the title having lost my sdcard, unfortunately my lap top in Frys customers service n i never went back for it, bs they said it was water damage lol idiots are wrong so my guarantee didnt cover it,anyways i think most of us knew this method, thnkz anyways........WHAT I WANT TO KNOW IS HOW OR IF POSSIBLE TO CHANGE THE PATH TO THE STOCK BROWSER DOWNLOADS TO INTERNAL STORAGE????????????? PLS IF ANY1 KNOWZ LET ME KNOW
Click to expand...
Click to collapse
/sigh. I'd try to help if I knew what this post was even about. All I got was something about a laptop at Frys.
Anyway, nice post OP.
gotablunt said:
I got excited when i read the title having lost my sdcard, unfortunately my lap top in Frys customers service n i never went back for it, bs they said it was water damage lol idiots are wrong so my guarantee didnt cover it,anyways i think most of us knew this method, thnkz anyways........WHAT I WANT TO KNOW IS HOW OR IF POSSIBLE TO CHANGE THE PATH TO THE STOCK BROWSER DOWNLOADS TO INTERNAL STORAGE????????????? PLS IF ANY1 KNOWZ LET ME KNOW
Click to expand...
Click to collapse
Fail. Put the blunt DOWN.
+1 OP
You first mentioned
kyouko said:
My example which I'll be using for this tut is: C:\AndroidSDK\toosl\kyoukoROM.zip
...
Code:
adb push ./kyoukoROM.zip /data/
Click to expand...
Click to collapse
But later, you use this:
Code:
adb shell
recovery --update_package=DATA:mau5.zip
Click to expand...
Click to collapse
I am confused on whether we use 'mau5.zip' as it is in the final command or change it to the name of our rom, which would be kyoukoROM.zip in your case?
HQRaja said:
You first mentioned
But later, you use this:
I am confused on whether we use 'mau5.zip' as it is in the final command or change it to the name of our rom, which would be kyoukoROM.zip in your case?
Click to expand...
Click to collapse
It would be the name of the file you are trying to flash.
How do you flash the recovery without an SD card tho?
EDIT: I figured it out. I will post my steps later.
Here is what I did:
Rooted phone
Attempted to push Flash_image - failed due to filesystem permissions
Steps for Flash_Image:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system/bin
chmod 777 /system/bin
exit/ctrl+c
adb shell
adb push flash_image.zip /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
Flashing Recovery:
adb push Recovery.img /system/bin/
adb shell
flash_image recovery /system/bin/Recovery.img
rm /system/bin/Recovery.img
reboot recovery
Then proceeded to follow the steps in this guide successfully
Stuke00 said:
Here is what I did:
Rooted phone
Attempted to push Flash_image - failed due to filesystem permissions
Steps for Flash_Image:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system/bin
chmod 777 /system/bin
exit/ctrl+c
adb shell
adb push flash_image.zip /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
Flashing Recovery:
adb push Recovery.img /system/bin/
adb shell
flash_image recovery /system/bin/Recovery.img
rm /system/bin/Recovery.img
reboot recovery
Then proceeded to follow the steps in this guide successfully
Click to expand...
Click to collapse
tip: use 'adb remount' instead of the manual mount commands. Do that before you adb shell. Just saves a bit of typing.
good work!
HQRaja said:
in the final command or change it to the name of our rom, which would be kyoukoROM.zip in your case?
Click to expand...
Click to collapse
I changed the OP to make it more consistent.
But see the quote below
sirmx said:
It would be the name of the file you are trying to flash.
Click to expand...
Click to collapse
Stuke00 said:
How do you flash the recovery without an SD card tho?
EDIT: I figured it out. I will post my steps later.
Click to expand...
Click to collapse
Good to hear you got it. I realized later that I should have mentioned how to flash it without an SD card
Cool! Favorited in case I ever need it. Really useful I would imagine!
sirmx said:
tip: use 'adb remount' instead of the manual mount commands. Do that before you adb shell. Just saves a bit of typing.
Click to expand...
Click to collapse
So would that be like this:
Code:
adb remount
adb shell
adb push flash_image.zip /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
Just confirming because I am about to feature this method on the blog I write for (with credit to Stuke00 and a link to his post) and don't wanna mess up. =)
EDIT: Forgot to mention that you rock! Thanks for the earlier help too.
EDIT 2: Nevermind, did some reading on what 'adb remount' does and found out it remounts /system with read+write access so I guess this is it. Though please do correct me if I am still wrong (which I am often).
Covered this method
Oh and in case you guys are interested in seeing my coverage of your methods, here it is...
The original method by kyouko: http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
The recovery method by Stuke00: http://www.addictivetips.com/mobile/how-to-flash-a-recovery-to-an-android-device-without-sd-card/
Thank you guys, I can't do my work and earn my living without you. Keep it up! =)
EDIT: I'll have this last line as a part of my signature now.
Is this possible with Clockwork?
refthemc said:
Is this possible with Clockwork?
Click to expand...
Click to collapse
Dunno, I don't have plans for using it ever again nor have I looked at Clockwork's github - if there is one.
But it should be able to if you can find out what scripts/commands are run when you use the menu. If you want to you can check the github link I have in the OP to see where I found the commands that are run, and then look for something similar in clockwork's source.
You'd be looking for something similar to:
Code:
--update_package=root:path - verify install an OTA package file
Thanks for the awesome guide! Saves me a lot of trouble, I don't have to take out my sdcard or manually enable USB in recovery anymore!
for me
for me it did not work in data but it worked in cache
kyouko said:
Brief rundown of what we just did:
Wiped /data/ to free up space for the zip
Put our ROM.zip onto the /data/ partition since we don't have an SD Card to work with.
Told the recovery to flash from our /data/ partition instead of /sdcard/
Click to expand...
Click to collapse
Hi, I try to install a ROM from CACHE but I'm getting this in my command line:
recovery --update_package=CACHE:rom.zip
sh: /sbin/postrecoveryboot.sh: not found
Click to expand...
Click to collapse
And my phone do nothing, how many time it take to install? normally using sdcard took no more than 5 minutes but using ADB nothing happens. Any help?
reynierpm said:
Hi, I try to install a ROM from CACHE but I'm getting this in my command line:
And my phone do nothing, how many time it take to install? normally using sdcard took no more than 5 minutes but using ADB nothing happens. Any help?
Click to expand...
Click to collapse
what recovery are you using?
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, set flash_image permissions to rwxrwxrwx
5.Download Android Terminal Emulator on Play store
6. Run Terminal Emulator and open up preferences.
7. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
12. CONGRATULATIONS AND YOU ARE BACK TO YANNOU90's RECOVERY
DOWNLOAD LINK:
Flash_Image and Recovery.zip
mrchezco1995 said:
......
2. Flash_image and Recovery (You can download it here on this thread)
......
Click to expand...
Click to collapse
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
beegeevee said:
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Click to expand...
Click to collapse
Deivi_Z said:
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
Click to expand...
Click to collapse
Download link fixed. Uploaded it to mediafire instead. Thanks for reminding guys.
permission denied
followed all the steps....still got the "Permission Denied" message
followed all the steps....still got the "Permission Denied" message
Click to expand...
Click to collapse
Check superuser and make sure Terminal is allowed. And type su in all lowercase, not uppercase like SU. That wont work
Sent from my HTC Explorer using XDA
mrchezco1995 said:
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, download Android Terminal Emulator on Play store
5. Run Terminal Emulator and open up preferences.
6. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
...
After this step what I get is as follows
usage: flash_image partition file.img
sh-3.2#
Click to expand...
Click to collapse
Superuser worked fine on terminal. But also got permission denied on last command in terminal.. should I push it via ADB?
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
[BTW, if you're wondering, the first command identifies as root, the second remounts /system as RW, the last copies the file]
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Thank You. U completed this thread. Decided to use fastboot (faster) instead of terminal emulator way.
SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Mine worked for me on terminal without any problems, but thanks for filling up what I just missrf for others. Hehe
Sent from my HTC Explorer using XDA
mrchezco1995 said:
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
]
Click to expand...
Click to collapse
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
SherazHashmi said:
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
Click to expand...
Click to collapse
Why don't you try step 3 from jaggyjag's rooting tutorial....
Sent from my HTC Explorer A310e using xda app-developers app
My HTC Explorer's recovery was stuck green logo, but what thing that helped to get back my clockword recovery
is just downloading you recovery file and renamed it recovery.img
And...
I used Android SDK tool, and used the below command in command prompt and then I reboot the mobile, and I got back:
fastboot flash recovery recovery.img
Thanks for this valuable thread
SU not found !
after changing the INITIAL COMMAND
i restarted d terminal and now the initial command just gets printed and after that i typed 'su'...d output was 'su not found'..
wats d problem ???
I even tried d fastboot method...dats epic, whenever i try to install any .zip from it dis is wat i see
"Installing update...
Installation aborted."
Plz suggest nythng else other than REFLASHING it...its just that sumthng is restricting it to install :laugh:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
iamwin said:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
Click to expand...
Click to collapse
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
R. SAINT said:
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
Click to expand...
Click to collapse
got it man!
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Mayank T said:
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Click to expand...
Click to collapse
My initial response to such a situation would be start the phone in fastboot mode and then flash the recovery from there. Download the ZIP here: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100, extract it and double click "recovery.bat" once the phone is in fastboot mode (start phone holding volume down, select fastboot from menu instead of recovery).
This assumes you're on Windows. If you're on Mac/Linux, find the fastboot binary for your platform and run the following command in a terminal:
Code:
./fastboot flash recovery recovery.img
where recovery.img is taken from the ZIP I linked above.
Alternatively, you could install a more up-to-date recovery such as TWRP or a newer build of CWM (not sure of links for the latest versions of either, but have a look around the forum and you should find them. Also some older builds of CWM had bugs [hence this thread exists], but I think the newer builds work fine on the Explorer; not 100% sure as I still use yannou90's build)
when i'm trying to update firmware im geting this:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
255|[email protected]:/ $
and because of that i can't go to the next step
what's wrong with it??
bobnur said:
when i'm trying to update firmware im geting this:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - [COLOR=Red]Permission denied[/COLOR]
255|[email protected]:/ $
and because of that i can't go to the next step
what's wrong with it??
Click to expand...
Click to collapse
adb shell
su
then type your commands
Maybe give link to commands or post commands to be used.
tobdaryl said:
adb shell
su
then type your commands
Maybe give link to commands or post commands to be used.
Click to expand...
Click to collapse
my tab is not rooted...
su just works with rooted tabs...
bobnur said:
my tab is not rooted...
su just works with rooted tabs...
Click to expand...
Click to collapse
Updating can usually be done by unzipping update once and placing the new zip on sdcard or external sdcard, reboot and accept request to update - shows in notification area
Have you tried that method?
also
fastboot -i 0x0B05 flash system update.blob
fastboot -i 0x0B05 reboot
tobdaryl said:
Updating can usually be done by unzipping update once and placing the new zip on sdcard or external sdcard, reboot and accept request to update - shows in notification area
Have you tried that method?
also
fastboot -i 0x0B05 flash system update.blob
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Somehow it doesn't work...
Is it some other ways??
bobnur said:
Somehow it doesn't work...
Is it some other ways??
Click to expand...
Click to collapse
I don't know of others without being rooted or flashing a recovery ( twrp ).
Maybe someone else has a better idea!
tobdaryl said:
I don't know of others without being rooted or flashing a recovery ( twrp ).
Maybe someone else has a better idea!
Click to expand...
Click to collapse
My knowledge of linux/android is limited, but I agree with post #2. You need to have root (su) permissions in order to move that file, because I'm assuming its on the root of your tablet's internal memory. So, you could either use the "su" command, type in the appropriate password and THEN move the files, or use the (safer) sudo command, which will allow you to perform just one action. If you login as superuser (using su w/ password), you have unlimited access and could potentially really break stuff if you're not careful.
Another idea is that since you're moving it from the /data partition, and that partition is currently in use, it would deny you permission. Theoretically speaking, you could unmount the partition through CWM and then just access your tablet in fastboot mode (don't boot into Android, as it needs that /data partition).
Just my two cents, and I'm not responsible if your tablet breaks, or if the zombies eat it. You know, whichever comes first
[SOLVED]
there may be other causes of this error, so there is no guarantee this will always be the fix.
"E: can't mount /sdcard"
in my case was "E: can't mount /sdcard" caused by some corrupted files in /data.
see here:
[email protected]:~$ adb shell
~ # mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: Invalid argument
i was able to fix this with instructions from this thread: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
boot phone into recovery, and ensure you are able to to see your device with the command:
sudo adb devices
then use this command:
adb shell ‘e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata’
it should prompt you to hit enter to repair several times. simply hit enter each time you are prompted until it resolves.
after that you should be able to access your data through recovery or adb pull.
the "/data/media/0/0/" problem
i thought we were passed this bug, but somehow i caused it again.
it isn't particularly difficult to fix, provided you have proper access to your data.
i just used solid explorer to move the contents of to "/data/media/0/0" to "/data/media/0" and "/data/media/0/clockworkmod" to "/data/media/clockworkmod".
any sort of root file manager should be fine.
original thread:
current situation: nexus 5 has no system data. i can get into fastboot and CWM recovery, but CWM can't perform any functions due to "E: can't mount /sdcard"
[update/edit:
[email protected]:~$ fastboot devices
0370333c437f5965 fastboot
[email protected]:~$ adb devices
List of devices attached
0370333c437f5965 recovery
]
is there anything i can do from fastboot?
should i reflash the recovery or use a different recovery?
do i have to flash stock images?
anyway to back up my data to my pc first?
full story (in case something dumb i did is relevant):
ok, so i flashed the L preview from vomer's thread (http://forum.xda-developers.com/google-nexus-5/development/rom-n5-l-developer-preview-t2796003), and yes i made a nandroid backup (wish i'd copied it to my pc now...)
i dirty flashed because i'm dumb and thought i would format /data anyway. it didn't, but actually didn't cause too many problems (no force closes, but the home button didn't work.)
i went back to recovery and formatted /data, /cache, and dalvik, then reflashed the L zip and made a backup of this fresh install.
messed around with L for awhile, but wanted to go back to my previous setup. so i went back to recovery to restore my nandroid. there was only that most recent backup in the list.
i poked around and realized my files were now located inside "/sdcard/0/0/" so i formatted /data, /cache, and dalvik and flashed my rom (latest aokp, 4.4.4) and gapps. the phone booted up fine but got infinite play services force closes. i assume this is because flashing my rom hadn't actually cleared /system first.
so i go back into recovery once more, format /system, and try to flash the rom again.
E: can't mount /sdcard
i'm assuming my data (and my backup) is still there somewhere in /sdcard/0/0/ but i have no idea how i might access it.
any help would be appreciated. i can definitely return to stock and start over, but i'd much rather have my data.
Click to expand...
Click to collapse
Fastboot flash the stock userdata.img
You'll need to adb pull everything from /data/media first
Yes you should use another recovery but not for this reason
Sent from my Nexus 5 using Tapatalk
rootSU said:
Fastboot flash the stock userdata.img
You'll need to adb pull everything from /data/media first
Yes you should use another recovery but not for this reason
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i'm not super familiar with this. i've only really used adb with guides for specific tasks.
do i just use "adb pull /data/media /where/i/want/it/to/go"
i'm using ubuntu if that matters.
Yep.
Boot into recovery
Open terminal
mkdir sd_backup
adb shell
mount /data
exit
adb pull /data/media/* /sd_backup
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yep.
Boot into recovery
Open terminal
mkdir sd_backup
adb she'll
mount /data
exit
adb pull /data/media/* /sd_backup
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ahh, the "/data/media/*" was the part i was looking for.
not sure i understand the
"adb shell
mount /data
exit"
part.
vonlupe said:
ahh, the "/data/media/*" was the part i was looking for.
not sure i understand the
"adb shell
mount /data
exit"
part.
Click to expand...
Click to collapse
In what respect?
They're commands. Type them in the terminal
Sent from my Nexus 5 using Tapatalk
rootSU said:
In what respect?
They're commands. Type them in the terminal
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
[email protected]:~$ adb devices
List of devices attached
0370333c437f5965 recovery
[email protected]:~$ adb shell
~ # mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: Invalid argument
~ # exit
Try and do "adb root" first..
Sent from my Nexus 5 using Tapatalk
rootSU said:
Try and do "adb root" first..
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
[email protected]:~$ adb root
adbd is already running as root
[email protected]:~$ adb shell
~ # mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: Invalid argument
~ #
not sure if this is relevant or weird or not, but "datadata"??
[email protected]:~$ adb shell
~ # ls
boot fstab.hammerhead sdcard
cache init seapp_contexts
charger init.rc sepolicy
data internal_sd storage
datadata mnt sys
default.prop proc system
dev property_contexts tmp
emmc recovery ueventd.goldfish.rc
etc res ueventd.hammerhead.rc
external_sd root ueventd.rc
file_contexts sbin
fstab.goldfish sd-ext
~ #
vonlupe said:
[email protected]:~$ adb root
adbd is already running as root
[email protected]:~$ adb shell
~ # mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: Invalid argument
~ #
Click to expand...
Click to collapse
[email protected]:~$ adb root
adbd is already running as root
[email protected]:~$ adb shell
~ # mount /data
~ # exit
[email protected]:~$
Click to expand...
Click to collapse
Could be your data partition is screwed too. Can you still boot into L? if not, I think your data is done for. Basically you have to format data going to and from L.
No idea what "datadata" is.
rootSU said:
Could be your data partition is screwed too. Can you still boot into L? if not, I think your data is done for. Basically you have to format data going to and from L.
No idea what "datadata" is.
Click to expand...
Click to collapse
no, i formatted /system, that's when everything broke.
thanks for all your help! i'm going to keep poking around, as i'd rather like to keep my data. i have the stock 4.4.4 images if i need to wipe though.
vonlupe said:
no, i formatted /system, that's when everything broke.
thanks for all your help! i'm going to keep poking around, as i'd rather like to keep my data. i have the stock 4.4.4 images if i need to wipe though.
Click to expand...
Click to collapse
Just fastboot flash the L system.img and boot.img
rootSU said:
Just fastboot flash the L system.img and boot.img
Click to expand...
Click to collapse
hmm, will that work?
will it boot without userdata.img?
it's just usuerdata that wipes everything, right?
vonlupe said:
hmm, will that work?
will it boot without userdata.img?
it's just usuerdata that wipes everything, right?
Click to expand...
Click to collapse
Userdata wipes data if flashed and no it is not a requirement. Will it work, not sure. Try it.
Also flash a cache.img just incase because dodgy cache can prevent mounting too
Sent from my Nexus 5 using Tapatalk
AHA!!
i found this thread: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
which instructed me to run
‘e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata’ in adb shell.
and it worked!!!
i was able to mount /data and am currently running adb pull /data/media/ (no asterisk, btw)
and backing up all my data.
will update OP if this resolves everything.
Cool
Sent from my Nexus 5 using Tapatalk