How to use ADB shell. Please back up your sd card before trying this
For all those not sure on how to install ADB shell and then the gingerbread ready xrecovery 0.3, Here is a simple tutorial on how to do it.
First download the xrecovery gingerbread ready zip from http://forum.xda-developers.com/showthread.php?t=859571 Then
1. Download http://forum.xda-developers.com/showpost.php?p=13430042&postcount=25 and put all the files into a folder in C drive, preferentially name the folder adb and extract the zip file into it.
(thanks doomlord for the link)
2. Connect phone to usb and computer and enable unknown sources and enable usb debugging.
3. Reboot into your current xrecovery
4. Go to start on the bottem left of your windows, then Run...
5. Type cmd and then press okay( run cmd )
6. Type cd \adb and press enter
7. Type adb.exe and press enter
8. Type adb shell and press enter
9. Type rm -r /sdcard and press enter
10. Type mkdir sdcard and press enter
11. Type chmod 777 sdcard and press enter
12. Now go to your phone and install custom zip x recovery gingerbread ready
13. Reboot and go back into your new xrecovery
This is for all those that have problems mounting recovery images all credits go to zdzihu and doomlord just providing a simpler way to install it
(btw this is a compilation of instructions from zdzihu's post and doomlord's post and i take absoulutely no credit for it)
good luck with that. All it does is erase, or make your old directory totally unavailable.
uh? it doesent erase anything all my files are still in my sd card just help to fix the cant mount image problem when ur flashing custom zip if your using like prerooted version of 2.3.3 doomlords etc.
my sdcard is coming up blank now in xrecovery....., and I can't connect with the usb either
### Plezzz BACK YOUR SD CARD OR ANY MOUNT/DRIVE UP BEFORE rm -rf /* ANYTHING. ###
All this is going to do is remove everything stored on your sdcard inclueing your security certs if u have passwords or screen locks. Also the only thing that xrec stores on your sd and backups zip an the logo.this will not remove any configs or xrec from the phone.
rm -r /sdcard/xrecovery <--- This Will Remove The Xrec data storeed on the phone but still this will not work .
and this is in the xrecovery install 1.0 see http://forum.xda-developers.com/showthread.php?t=859571
This is a dublepost
Great, thanx for tutorial?!
Weird im not a developer so i dun know why this is happening but my sd card is working perfectly and nothing has been erased. on ericwills rom for the past few hours and it is flying
For all those who dun want to mess around with adb shell, i suggest you to take a look at doomlords thread http://forum.xda-developers.com/showthread.php?t=1196808 if your recovery has some problems mounting images
fyi depending on your computer, it may end up corrupting your sdcard as well.
what computer os are u using? do a full reformat of your sd card?
Related
So, I am probably getting a new eris tomorrow,s othat means I could root my phone which got me thinking, could someone make a tutorial on how to load a custom ROM (with a mac) on to my eris
This is ripped from Ivan's tutorial with OS X steps added.
Index:
I: Gaining root: an unlocked hboot
II: Prerequisites: Tools to flash
III: Flashing a rooted/modded recovery
IV: Flashing a custom ROM (rooted version of leaked 2.1 ROM)
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
II: Prerequisites - Android SDK - These instructions are for Windows XP. You must adapt them to your version of Windows.
First we must install the Android SDK as it has the tools we need for both this walkthrough as well as to make your life in the Android world easier.
1. Visit the Android SDK site.
2. Visit the Java site and download the latest Java JDK.
3. Extract the Android SDK zip file into your root folder.
4. Go to the Tools folder and double click on android.
5. Click on Settings and check the box to force HTTP instead of HTTPS.
6. Choose to download the newest sdk platform (ver. 7 I believe).
7. Enable your phone's USB debugging mode: Settings > Applications > Development > check USB Debugging
8. Connect your phone via USB to your Mac.
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up terminal and go to your tools directory, and execute these commands:
* cd [location of your tools folder... drag and drop it]
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
I did this from memory, so forgive me if it's not 100%.
Its basically the same thing for mac, if not easier since you don't have to worry about drivers.
Just download the sdk for mac, and then when doing commands just add "./" before them like
./adb shell
http://www.thefuzz4.net/home/AndroidPhones/Eris/HowToRootYourHTCEris.aspx
^^ that has some information about how to do it on mac.
Just remember for mac you don't have to worry about drivers.
Thanks stopxstart will definitely try when I get my new eris
This method is a pain in the butt, http://forum.xda-developers.com/showthread.php?t=926749here is a better method!
PERFORM AT YOUR OWN RISK! (I will clean this up as I have more time)
Okay! I have seen several threads on here regarding getting Nookie Froyo working off EMMC. Here is my take on it, I have spent time psuedo bricking my Nook Color over and over, and bringing it back to a factory state. Also all credit for this work goes to the people who actually got all this to work... I am simply compiling the information needed to make this as simple as possible.
First things first… If you make your device not-bootable… it is not the end of the world! Thanks to samuelhalff you can simply just recover using CWR and his recovery image from http://forum.xda-developers.com/showthread.php?t=914690&highlight=emmc . (To make things easier you can get a CWR image that is bootable from your SD card to assist with this from here: http://forum.xda-developers.com/showthread.php?t=922870 .) Please be advised that after the recovery you MUST factory restore Data using the power + n method!
Prereqs:
1. Ubuntu 10.1 (this is what I am using and can verify that it works with no issues.)
2. ADB working over USB.
3. A micro SD card of at least 2gb (more than one helps speed things up!)
4. IOMonsters bootable SD CWR (http://forum.xda-developers.com/showthread.php?t=922870)
5. Nooter 0.2(Thanks Pokey9000, and MBM!) (http://www.mediafire.com/?cfddu9wt9d8dunl)
6. Modified boot files for Nookie Froyo (http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2 )
7. Nookie Froyo 0.5.9 (http://forum.xda-developers.com/showthread.php?t=883175)
8. The factory boot image (http://forum.xda-developers.com/showthread.php?t=919353)
How to:
1. If you are not already completely stock please do so now. (including wiping data.)
2. Boot from your SD card into Nookie Froyo 0.5.9
3. Configure your display to timeout at 30 minutes (so you have time to type this all in!)
4. Type the Following in your adb shell:
adb shell mount -o remount,rw /dev/block/mmcblk1 /
adb shell
mkdir tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
cd tmpfolder
rm -r *
cd ..
cp -r system/* tmpfolder
umount tmpfolder
mount /dev/block/mmcblk0p1 tmpfolder
exit
adb push [folder-containing-extracted-boot.zip] tmpfolder
adb shell
umount tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
exit
adb push [folder-containing-extracted-volds.zip] tmpfolder/etc/
adb shell
umount tmpfolder
rm -r tmpfolder
exit
5. Turn your NC off and take out the sd card and pop it into your computer and image Nooter 0.2 onto it.
6. Boot your NC up with Nooter 0.2
7. SSH into your NC from the console (sudo –s root console) with the following command “ssh [email protected]” (if you have to reconnect and you get an error about keys type: “ssh-keygen -R 192.168.2.2”)
8. Eject your sd card (unless you have 2) and put (copy the file, do not image boot.img to the sdcard!) the factory boot.img file onto the sd card (might need to use gpart to wipe out the card and format for fat32, pop it back into your NC.
9. In the ssh console type:
mkdir sdcard
mount /dev/mmcblk0p1 sdcard
cd sdcard
dd if=boot.img of=/dev/mmcblk1p1
10. Power off NC and remove sdcard.
11. Reboot NC and hold down power + n to factory restore data.
12. Boot from your nooter card again the same as before.
13. Once booted, eject your sdcard from the nc and load up the modified boot files from nookie froyo. (just place the files in the root of the sd card)
14. Put the sdcard back into your nc and type:
mkdir sdcard
mount /dev/mmcblk0p1 sdcard
15. Then mount your boot partition and backup the existing files:
mkdir boot
mount /dev/mmcblk1p1 boot
cd boot
mkdir bak
mv * bak
cd ..
cp /sd/* /boot/
16. Reboot your NC and enjoy Froyo on EMMC!
Until I read to part 7 I was thinking of trying this on windows. Have ubuntu also but don't have sdk on it. And not sure of how to get sdk on ubuntu. Can this be done on windows? What if I did 1 threw 5 on windows sdk,then finished it up with ubuntu?
Wondering the same...no Ubuntu here...just Windows 7 (32 & 64 bit). Hoping someone can verify Windows works.
I must say, I followed it up to step 9, and I get totally lost in the weeds from there..
I also suggest this lives in the NookDevs wiki, as it's easier for folks to tweak and make it easier to understand, add info etc to it there.
What if I di 1-5 on windows then the rest with the terminal emulator on the nook? That is if nooter preinstalls emulator.
At step 9 u need to open up an ssh tunnel via the console in ubuntu..if you go on nook devs under rooting they have an ssh connection tutorial... this could be done in windows if you had an ssh client and the dd package or something similar.... however the process at this point in time is fussy and works well on ubuntu 10.1 after i do some more tweaking i may just zip up the premade image...
Sent from my Nook Color (zoom2) using Tapatalk
ericman77 said:
What if I di 1-5 on windows then the rest with the terminal emulator on the nook? That is if nooter preinstalls emulator.
Click to expand...
Click to collapse
Not sure on that... nooter only provides a ramdisk and allows ssh and adb....
Sent from my Nook Color (zoom2) using Tapatalk
U go to the same place as to get it for windows... u could do ur adb stuff in windows and the ssh stuff in ubuntu
Sent from my Nook Color (zoom2) using Tapatalk
K thanks think I will try that then.
I somewhat successfully used this method. However, I had some issues with step 9 since I am on Mac OS X. I could not mount my sdcard at all. No matter how I formatted the card, the system type could not be identified. Nonetheless, I was able to boot into Froyo and just completed the rest of the guide within Froyo.
*Corrections Needed to Guide*
Step 9: Error on mount point. Should be "mmcblk1p1" and not "mmcblk0p1"
Step 14: Mounts are incorrect again, they need to be reversed (sdcard & boot)
Can someone give me a hand...in step 9 where is says 'mount /dev/mmcblk0p1 sdcard' it says file directory doesnt exist. When i list the files i see mmcblk0 so i use that one. when i go to do the "dd if=boot.img of=/dev/mmcblk1p1" i get boot.img does not exist. LS on that shows that the file isnt there. I wrote the boot.img to the sd card and the files that are part of the show but not the image i burned. Can someone get a little more direction on that part. Thanks...
something must be kooky with my NC as i literally copied and pasted this stuff into my console and got it to run... well as long as its working! (maybe people should double check the mounts prior to imaging....)
modembug said:
At step 9 u need to open up an ssh tunnel via the console in ubuntu..if you go on nook devs under rooting they have an ssh connection tutorial... this could be done in windows if you had an ssh client and the dd package or something similar.... however the process at this point in time is fussy and works well on ubuntu 10.1 after i do some more tweaking i may just zip up the premade image...
Click to expand...
Click to collapse
Well, not that I didn't understand the commands, just I can't quite figure out what 9 on is doing
so on step 9 prior to running those commands you need to Place the file onto the sdcard, do not image boot.img to the sdcard... you need the actual file so when you are in the shh console you can dd the image file to that partition... make sense?
I am working on a flashable zip file that should simplify this process greatly.... Stay tuned!
modembug said:
so on step 9 prior to running those commands you need to Place the file onto the sdcard, do not image boot.img to the sdcard... you need the actual file so when you are in the shh console you can dd the image file to that partition... make sense?
Click to expand...
Click to collapse
Yup makes sense ... had been at it for your 5... several went down for two hours. Then had issues with rndis driver but good now that was going to be my next step in the morning. Thanks... will continue where I left off.
Sent from my DROIDX using Tapatalk
I'm looking forward to the flashable version!
Sent from my LogicPD Zoom2 using XDA App
having some issues with the flashable zip... still working at it, just need to replicate these steps in the script... Hopefully later today ill have something
I need a way to manually delete the files in /boot and in /system instead of formatting those partitions in CWR... I think if that was done instead it would prevent the bootloop..
Windows
You should be able to do this in Windows.
Use:
Putty forSSH.
http://www.chiark.greenend.org.uk/~sgtatham/putty/
Win32 Disk Imager to write images to SD Card.
https://launchpad.net/win32-image-writer/+download
Ok...im am on the last two lines....this is what i am getting
when i type mv * bak...i get can't rename 'bak' invalid argument.
I checked and bak is there with files in it.
when i do cp /sd/* /boot/ i get can't stat '/sd/*' no such file or directyory
i have even tried changing sd to sdcard and still nothing. I see the steps should copy from the sdcard to the boot directory, but keep getting that error. thanks for any help you can provide. Everything up until that point works perfectly;
Hey there , I'm a new Lg P500 User and I am really Unclear how to flash a custom recovery mod / megatron v1 / screen lag touch fix by milk_os
About Phone
Model: LG-P500
Android Version: 2.2.2
Kernel Version: 2.6.32.9
Software Version:V10F
Rooted with Superuser using GingerBreak .
The original thread: http://forum.xda-developers.com/showthread.php?t=1044765
Also Installed with busybox from the market.
So if anyone can show me a step by step guide to how to install custom recovery mod , megatron v1 and touch screen lag fixer by milk_os. I will reward
you with $100 Singapore by PayPal.I believe in meritocracy
Links
Custom Recovery Mod:http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
Megatron V1: http://forum.xda-developers.com/showthread.php?t=870640
Touch Screen Bug: http://forum.xda-developers.com/showthread.php?t=929941
Let the hack rage begin!
Thank You.
danialrocker said:
Hey there , I'm a new Lg P500 User and I am really Unclear how to flash a custom recovery mod / megatron v1 / screen lag touch fix by milk_os
About Phone
Model: LG-P500
Android Version: 2.2.2
Kernel Version: 2.6.32.9
Software Version:V10F
Rooted with Superuser using GingerBreak .
The original thread: http://forum.xda-developers.com/showthread.php?t=1044765
Also Installed with busybox from the market.
So if anyone can show me a step by step guide to how to install custom recovery mod , megatron v1 and touch screen lag fixer by milk_os. I will reward
you with $100 Singapore by PayPal.I believe in meritocracy
Links
Custom Recovery Mod:http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
Megatron V1: http://forum.xda-developers.com/showthread.php?t=870640
Touch Screen Bug: http://forum.xda-developers.com/showthread.php?t=929941
Let the hack rage begin!
Thank You.
Click to expand...
Click to collapse
lol luckly i live in singapore
first of all, lets start with custom recovery
1. Download the custom recovery file from here and here
2. DO NOT rename them, and put them neatly inside the ROOT of the SD CARD (that means it should be at /sdcard/ on androids
3. next, get Terminal Emulator from the market. search it.
4. Get a nice keyboard to work on for a while. you need to type A LOT
5. get titanium backup and backup everything. menu > batch
6. reboot phone.
7. Turn on phone and go to terminal and type the following
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
Click to expand...
Click to collapse
*there should be no error except at stage 5 there could be, but not always.
8. good. flash complete. now grab the megatron ROM and the lagfix. they both should be .zip . DONT OPEN IT.
9 put the two inside the root of SD card
10. go to terminal, write
su
*press enter*
reboot recovery
11. you should have a menu of things. go to flash zip or sth (you will know) w/ ur volume buttons
12. press menu and you will be able to choose the two zips. flash any of them first, and do the second afterwords.
13. YAY DONE
14. no need for bucks thanks. just press the thanks button down there. its free.
*PM or EMAIL ME IF YOU WANT FURTHER HELP*
*[email protected]*
Also, isnt 2.2.2 not rootable??
I think it has to be downgraded to 2.2 and then rooted..
Edit:
Sorry, My mistake.. Didnt realize 2.2.2 is rootable now..
2.2.2 it's now rootable
It says that "/system/etc/install-recovery.sh ": No such file or directory.
I'm sure that I placed both of the files on the root of my sdcard
Well, I guess the hardest part is getting the recovery. Well I share my method so, here we go.
What you need:
1. terminal emulator(download from market - free)
2. recovery installer(download here)
3. your ROM which is megatron(download here)
4. Touch-screen bug fix(download here)
5. Back-up all your SD contents to your PC.
-. optional: if your file explorer doesn't support unrar/unzipping, download one. but since you have a PC just use winrar.
when you have everything, lets start.
1. extract contents of "recovey_installer.rar" to the root(meaning the base) of your SDcard.(it contains 3 files, so you should also see 3 new files on your SD card).
2. open terminal emulator, enter these lines(press enter after each line):
Code:
su
sh /sdcard/rf.sh
just wait and this should reboot you directly to recovery.
3. now in recovery(remember: "vol + and - button" is "up and down" "menu button is ok/select" and "back button" is back) select options:
Partition sdcard > partition SD
4. when asked choose your desired partition size then choose swap size as 0. This should format your SD card.(initially this will leave you with an ext2 partition, if you want ext3 then upgrade it to ext3 and so on using the same menu)
5. when done, press back repeatedly and reboot.
6. now, move your ROM(megatron) and the touchscreen-lag-fix files to the root of your SD card.
7. open terminal again and enter these commands
Code:
su
reboot recovery
just wait and it should bring you back to recovery.
8. in recovery, choose option:
- flash zip menu
- to avoid hiccups just toggle the signature verification
- flash zip from sdcard
- first flash your rom(megatron), when done immediately flash touchscreen-bug-fix
- press back repeatedly then reboot.
9. enjoy
danialrocker said:
It says that "/system/etc/install-recovery.sh ": No such file or directory.
I'm sure that I placed both of the files on the root of my sdcard
Click to expand...
Click to collapse
just ignore that error message. this line is only there for those with different phone models which has the mention file in the phone internal storage. so this shouldn't affect optimus one users.
@ungaze, i did your way . It took me to android system recovery .
Anyway it didnt ask me for partition sdcard. So should i just reboot my phone?
congratulations, you now have recovery. you should see some options.
press volume buttons to navigate up and down(menu button=select/ok). Choose the option:
- Partition sdcard
- Partition SD
If you want to explore your phone a bit more, you could just reboot your phone for now. Just remember, to go back to recovery you could open terminal and enter:
Code:
su
reboot recovery
or when phone is off, press and hold "power/lock button"+"home button"+"vol down button" until recovery menu shows up.
Alright , did that . My friend told me about nandroid how can i do that before i flash the other roms ?
theres a menu option "backup/restore" open it and choose "nand backup". when done, there should be a folder in your SD named "nand" copy the contents to a pc or somewhere safe as this will serve as your backup file.
Okay, i did a nandroid and ready to flash roms . Wish me well =)
Anyway why do i receive E:Bad boot message when i reboot recovery.
everyone has it. it's perfectly fine. good luck
Anyway, as I was nandroid-ing i saw this video http://www.youtube.com/watch?v=s5GWgjJT2zo in the end, it shows the guy having no reception?
edit: He didnt have it on at the first place anyway. Sorry for the inconvenience.
i didnt view the link but im guessing hes using amon_ra v1.1, the method i gave you installs amon_ra v1.2 which fixes most bugs with ext4 and nand recovery/backup
By toggl-ing signature verification do you mean to enable or disable it?
disable. this is really not necessary as the zips youre about to apply are surely signed. but in case you have problems in the future, just remember that disabling sig veryfication may fix the problem.
Thanks man, how do i donate to you?
Btw i just screw my phone. Stuck at android screen page ;(. How do i restore the nandroid backup? Should i wipe my phone first, then do nandroid restore?
Will it restore me my version 2.2.2?
When i nandroid it , my phone was on ver 2.2.2
Ungaze?
Sent from my LG-P500 using XDA Premium App
Check your inbox
I need help to fix my tab,
I've been running pershoots OC kernel with task's roms for several months with no problems and i've been keeping up to date with each version with out any problems.
I just rebooted my tab today and now suddenly out of the blue, the screen shows static and corrupted rbg lines after a few seconds of the samsung logo. And now it is stuck like this after repeatedly trying to turn my device on. I can get into CWM recovery but i dont a restore file on it because i moved them off my tab to my PC to save space.
Is there anyway to move the files back on to the tab to restore it or maybe move the stock kernel so i can flash it and see if that fixes it?
If you don't care about the data in your tab (all your apps and the /sdcard partition), you could try returning to stock via Odin. Here is a good guide (is the last part "Re-“Stocking” Yer System…"): The Guide
Other option (I recommend this one) is adb, in cwm just push the files you want to flash to the /sdcard .
Thanks! I'll try by android debug bridge and see if i can figure this out..
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Mercatorn said:
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Click to expand...
Click to collapse
Are you mounting the partition? My guess is you forgot to do it.
Enter the follow commands (one by one) in the terminal (cmd prompt):
Code:
adb shell
Code:
mount /data
Code:
exit
Code:
adb push fileyouwanttoflash.zip /data/media
Now the file should be in /sdcard, just install it from cwm.
If at the moment you're trying to choose the zip from sdcard you get an error telling you "Couldn't open directory" and "No files found", reboot cwm.
Other way to do it is in cwm (so you don't have to do the "adb shell" and "adb mount")
In cwm, choose "install zip from sdcard", then "choose zip from sdcard", then "+++++Go Back+++++"
And from your cmd promt:
Code:
adb push fileyouwanttoflash.zip /sdcard/
Now, flash the file from cwm. (Again, if there's some error, reboot cwm).
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
EDIT:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
lalalalas said:
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
Click to expand...
Click to collapse
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
leadtk said:
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
Click to expand...
Click to collapse
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Quallenauge said:
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Click to expand...
Click to collapse
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
leadtk said:
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
Click to expand...
Click to collapse
From the guide, install using adb. http://forum.xda-developers.com/showthread.php?t=1871912
Originally Posted by surdu_petru
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /local/ ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
If you are a Linux user. http://forum.xda-developers.com/showpost.php?p=48731942&postcount=1
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
leadtk said:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
Click to expand...
Click to collapse
I do not know what i am doing wrong but when i type adb shell ..all i get is BUSYBOX v1.7.2 (2012-10-19 CEST) built in shell (ash) Enter help for a list of built in commands ...
I did have ics blue v04 rom on my tablet that i was trying to go from to 4.4.2 ..
I did this before and had the write problem . any help you can give would be appreciated