Related
**THE USUAL WARNINGS APPLY**
1/11/11: Updated CWR to 3.0.0.5. Now installs properly through ROM Manager. Nandroid backup works, don't know about restore. Not sure if partition wiping is working I would assume it is. Flashable zips from SD card are working, tested with Quickie OC kernel (HIGHLY RECOMMEND!!!). Attached the CWR 3.0.0.5 image to this post, it is not a flashable zip just the image file zipped. So we have some real progress. w00t!!!
1/2/11: Looks like CWR has been released for NC. I didn't see it up see here you go. Easiest way to get it installed is by downloading ROM Manager in the market and flashing it through the apk. Attached is the .zip, I believe you just rename it "update.zip" and put it on the root of your SD card. Then reboot into recovery. Again your best bet is to use ROM Manager. Link to website: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Awesome, will try this later today, thanks for bringing it to attention
Afraid i cant thank you from my nook, but rest assured i eil soon
install failed here, too.
Failed for me too....
Sent from my Nooted Rook XDA App
Not ready for prime time yet. You need to install uRecRam to use it. give it a day put so for out to be automated. At least that is where it was last night when I went to sleep.
Sent from my rooted droid x
As per the previous post. This is not ready yet and could result in a bricked NC.
http://nookdevs.com/NookColor:Building_Clockwork_Recovery
Unable to post url's
Also I don't think it is backing up all partitions.
Sent from my rooted droid x
Failed me too. Started the process and then failed. Looks like it is close though. Pretty exciting.
WOW, this is great news. Seems like real soon we will be able to make backups.
Awesome. Not too long now until ROMs start getting put together. Hope the teardown reveals working Bluetooth.
Here are the steps to actually making this work if you are the adventurous type. This may brick your device blah blah. I am not responsible, etc. You should only attempt this if you genuinely understand the commands you are performing.
Make sure neither /media or /sdcard are mounted in your OS!
Save this:
http://koush.tandtgaming.com/test/clockwork-b3-nook-uRecRam
adb push clockwork-b3-nook-uRecRam /media/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /system/boot/uRecRam > /system/boot/uRecRam.bak
cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Now do the three fingered salute to get into CWM Recovery. VolUp/Down are up/down, respectively. The Nook/home button is Select and the power button is Back.
@Mistar Muffin
worked for me
starkruzr said:
Awesome. Not too long now until ROMs start getting put together. Hope the teardown reveals working Bluetooth.
Click to expand...
Click to collapse
That would be awesome!
Great job,
I tried to compile a scrip with the following but it doesn't work if i put it in a batch file but it works if I run it from DOS. Go figure...
Code:
adb push clockwork-b3-nook-uRecRam /media/
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell mkdir /system/boot/
adb shell mount -t vfat /dev/block/mmcblk0p1 /system/boot
adb shell "cat /system/boot/uRecRam > /system/boot/uRecRam.bak"
adb shell "cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam"
adb shell umount /system/boot
adb shell rmdir /system/boot
I will work on the batch for the community to run so it make it easy for noobs...no ETA
Would installing this hose the ability to factory reset (the 8 failed boots/bootcnt method)?
Flashed and it works.
Yes you will loose that ability in it's current state.
I do not recommend using this until it has the capability to backup all of your data. At this point an error can still leave you with no return path, you have been warned!
Edit: Scratch that. I see what I did.
Even if it might not be wise for most to use this yet, very happy to see this available. Looking forward to nandroid . . .
I saw that the nook color comes up in rom manager, does this mean we don't need to install that other file uRecRam.
Sent from my LogicPD Zoom2 using XDA App
It seems that nobody is talking about deodexing the Droid X2. Just thought I would let everyone know that xUltimate 2.2.8 works on the Droid X2 with the newest drivers installed. I am currently manually deodexing my root GB Droid X 2.
Some Members Might Not Wanna Take The Risk. With All The ROMs Are Already Deodexed. Me Personally I've Had That Program Downloaded Since The First Time It Was Posted And Have Used It Numerous Times. Now That You Mentioned This, You Should Go Bump That Thread.
If anyone can instruct me on how to successfully create an update zip I would gladly do it for those that don't want to take the risk of deodexing manually. But I am really shocked that a deodexed GB is not in the TBH App and no one seems to be talking about it.
I'm Gonna PM You A Few Websites To Learn How To Do It.
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
dimitri407 said:
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
You Need To Manually Transfer Them Over USB First. Both App And Frame Place Them On Your SD Card.
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
dimitri407 said:
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
Click to expand...
Click to collapse
When You Did "su", Did You Grant The Superuser Request On The Phone?
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
dimitri407 said:
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
Click to expand...
Click to collapse
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
I can't figure it out either. I did this to my Droid X with no problems. But the Droid X 2 just wants to be a pain when I am trying it.
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
I am wondering, since it is not working in adb shell then could I do it in the terminal?
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
So I finally got everything to work but to do so I had to copy the done_app and the done_frame folders to /data/local/tmp then run the cp commands.
For some reason, I could not get to the SD Card or the External SDCard.
you both need to quit hijacking threads and grow up. If I was the mod I would ban both of you.
Sent from my DROID X2 using XDA App
mistawolfe said:
Lol. You beg for 'em. Signature...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Can we please stop hijacking my thread. This is suppose to be about Deodexing the Droid X 2.
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
dimitri407 said:
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
Click to expand...
Click to collapse
Oh God Yes. It's Gonna Faster And Smoother. The Point Of Deodexing Is It Recompiles The Odex Inside The Apk For Easier Themeing And The System Is Able To Read The Apks Faster. Definitely Gonna Help Battery If The System Isn't Working As Hard.
when you connect USB, you MUST be in "charge only" mode w/ usb debugging enabled. ANY OTHER MODE will fail to allow complete access to /sdcard or /sdcard-ext...
or at least that was my experience.
I'll Challenge That I Used PC Mode To Run The Deodex App And Then To Transfer The Completed Files Without Switching Modes. Anytime I Run ADB Operations My Phone Is In PC Mode.
I will check both settings today. But by mounting the partition, it should become available either way. But we will see.
I am trying to re-root after the 2.3.6 update, I did not remove root before the OTA update.
I made sure USB connection was set to none, and USB debugging was on. I see that is saying that I am out of space, problem is I don't know how I could possibly be able to be out of space, I have plenty of room on both the internal and external cards. Below is the output with the error. Any help would be appreciated. Thanks.
C:\moto-fastboot-win32>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (30720 KB)... OKAY [ 2.682s]
writing 'preinstall'... OKAY [ 3.447s]
C:\moto-fastboot-win32>moto-fastboot.exe reboot
rebooting...
C:\moto-fastboot-win32>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: No space left on device
[email protected]:/#
same thing happened here
same here
i have the same problem, do i reboot?
any update on this?
Hi there... I had the same issue when I installed the 2.3.6 ATT OTA update when I lost root... I tried RootKeeper application but it didn't work after the OTA installation. I looked for information about this error but didn't find much or complex solutions as to free space from that system dir... so then I thought about if the copy command would have an overwrite option and it did, so I tried it and it worked for me.... I'm rooted again!
I see this is an old post but in case you still need it, it may help you too. I used line bleow to overwrite and the rest you know it.
cp -f /preinstall/su /system/bin/su
by the way, I got an error in the line "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk" telling me that the application or file already existed as I already had superuser installed... I guess it should work without re-installing it, in my case the reinstallation was to a different superuser version... anyway if you want to skip that error and proceed with the re-installation you can use option -r as shown in line below.
PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk
cheers!
avelezmtz,
Thanks for the idea, but it did not work for me, I still got the no space left error. Do you know if there a way to delete the SU file and then try to copy it? Thanks
I tried the, PATH=/system/bin:$PATH pm install -r /preinstall/Superuser.apk, command and it was able to reinstall the apk which it never has before so that's good, but it's still not rooted.
If anyone else has any ideas let me know. I am thinking about backing everything up and doing a factory reset and seeing how that goes.
First... as suggestion, if you will be playing deleting files, ensure you have clockworkmod backup or anyother way to restore a previous backup just to be safe.
I think rm command should delete su, but I'm not sure if it would help since the error is not a permissions error, so the ovewrite option should work if the space in the system dir is enough... if you still wanna try the removal of su I think line below will do it.
rm /system/bin/su
Another option I saw somewhere it was about freeing up space by deleting apk files from /system/app dir which is mounted in the same volume, however it would depend on how big those files are. Of course you should back them up first maybe copying them to /sdcard/ for instance. In the post I saw that they removed swype.apk and that was enough for them but in my case it didn't help and as the ovewrite worked I didn't try removing more apps.
If you want to know the space on that dir you can use
df /system/bin/
avelezmtz,
Thanks for all the help, I am now rooted again!!
Using your suggestion I deleted Superuser.apk and Swype.apk from the /system/app directory.
After that I was able to rerun all the commands and get root back. Thanks for all the help, I appreciate it. Sure beats wiping the phone and starting all over again.
I have a problem with my Yu Yureka which running on CM 12.1 and Rooted (su) twrp
1. When I was trying to to flash any zip file like CameraNext Mod, it was flash successfully. After reboot the system, I can't find the CameraNext Mod, it was not in menu.
2. Sometime when i tried to flash other zip file like xposed framework, it was not completely installed. there was error and the error message was " cp:write error: no space left on device"
plz help me with right direction..
Hello All,
I'm new here. I believe I supposed to write a reply to this thread, but I couldn't. So, sorry to all mods.
Anyway, after applying battery hack files (services.jar & systemUI.apk), my RAZR is now stuck on boot.
However, I can connect my handset to PC and access the shell via ADB. The problem is, silly me, I was so excited that I forgot to backup the services.jar & systemUI.apk in same directory. It's on the sdcard however.
How to mount the sdcard onto the android system, so that I can overwrite the files by original ones from the sdcard?
I'm using XT910, it was AsiaRetail, but I flashed using the latest eu.en.33 & deodexed, which was working fine.
Any helps are appreciated. Thanks.
iman38 said:
Hello All,
I'm new here. I believe I supposed to write a reply to this thread, but I couldn't. So, sorry to all mods.
Anyway, after applying battery hack files (services.jar & systemUI.apk), my RAZR is now stuck on boot.
However, I can connect my handset to PC and access the shell via ADB. The problem is, silly me, I was so excited that I forgot to backup the services.jar & systemUI.apk in same directory. It's on the sdcard however.
How to mount the sdcard onto the android system, so that I can overwrite the files by original ones from the sdcard?
I'm using XT910, it was AsiaRetail, but I flashed using the latest eu.en.33 & deodexed, which was working fine.
Any helps are appreciated. Thanks.
Click to expand...
Click to collapse
when you say stuck on boot, do you mean bootloop?
If you were on deodexed system it should work i don't see why...
Anyway if you have a backup of your file it's fine, if you don't have i'll send it to you in 2hours.
Code:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/services.jar /system/framework/
reboot
No need to mount sdcard it's mounted automatically.
Maybe the change i made, make it unworking on .33. I tried on it before the 1% just with toggle so maybe it's not working.
sevenup30 said:
when you say stuck on boot, do you mean bootloop?
If you were on deodexed system it should work i don't see why...
Anyway if you have a backup of your file it's fine, if you don't have i'll send it to you in 2hours.
Code:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/services.jar /system/framework/
reboot
No need to mount sdcard it's mounted automatically.
Maybe the change i made, make it unworking on .33. I tried on it before the 1% just with toggle so maybe it's not working.
Click to expand...
Click to collapse
Yes, I deodexed using xUltimate 2.4.2 ; Deodexing was successful and my phone was running fine after deodexed.
So my only suspects are the services.jar and systemui.apk
It's not bootloop, it's stuck on the Motorola Animation. Normally, it would vibrate and enter the android, now it's stuck there. But as I said, I can connect using adb and access su.
The sdcard is not mounted (I guess the boot process halted somewhere before it mount the drives automatically).
So, do you know the exact command to mount the sdcard? external sd card in my case.
Btw, if I reflash using the fastboot file, SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml.zip from droid-developers, will it work? I'm afraid it will make it worse, so I need confirmation before the last resort of re-flashing my phone.
Btw, I was using battery app and tick the 1% hack, it did show 1% decrement, but have it's own notification. If your patch works, then it's great
tia
Try:
Code:
busybox mount -t vfat /dev/block/mmcblk0p1 /sdcard
or
busybox mount -t vfat /dev/block/mmcblk0 /sdcard
or try to fastboot this one:
http://forum.xda-developers.com/showthread.php?t=1747800
might be the same as you mentionned, latest fastboot ICS for EN.EU
sevenup30 said:
Try:
Code:
busybox mount -t vfat /dev/block/mmcblk0p1 /sdcard
or
busybox mount -t vfat /dev/block/mmcblk0 /sdcard
or try to fastboot this one:
http://forum.xda-developers.com/showthread.php?t=1747800
might be the same as you mentionned, latest fastboot ICS for EN.EU
Click to expand...
Click to collapse
Sorry for late replied. I flashed my phone using latest fastboot. At first, it was panicking since it failed in step 6 (system_signed or something) and my phone keep displaying white text of "failed fastboot" even after I powered it down. But with little hope, I tried again and it's succeeded. Thank God the flashing didn't erase anything.
Thanks anyway.
Btw, if I want to do my own mod of those files (1% battery hack), what should I do?
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