Related
Hi,
i've rooted my vodafone 858 but it didn't install super user although i can type "su" command in adb shell.
now i'm trying to delete files located in /mnt/asec (downloaded packages) due to low phone memory.
so i tried to do it but when i do the command "rm" for files located in there it tells me permission denied so i entered super user mode and i tried "rm" it tells me "unable to chmod <path> read-only file system" so how can i get past the read only?
Wich way did u use to root ur phone?
I think you´ll need the superuser.apk and the terminal emulator.apk
In the emulator u might type in you commands like su and the emulator will request root acces.
This way worked for me
Get superuser + busybox and why not use some root file manager to remove them?
Sent from Galaxy Ace which just landed on "MOON"
Hello Friends,,
I Bought New TAb In India I.e. Penta IS701C having Following Features
1 Ghz Processor
512 Mb RAM
4 Gb Internal (500 Mb system, 2.5 Gb Internal Storage card)
Cg 400 GPU
Etc.
Ive Roote Device
With Unlock Root I got "su" file In /system/bin
and superuser.apk in /system/app
but i didnt got the su file in
/system/xbinyesterday my friend bought same tab
i noticed that the su file in /system/bin, /system/xbin is given by manufactures.
suppose mine might be deleleted by me from the "ADB shell" comands
Ive Formated My Whole Tab And Bingo I Got All 3 Files In All Foleders
i,e. su in /system/bin, /system/xbinand superuser.apk in /system/appbut still having problem
superuser apk shows
remounting as rw... legacy
busybx shows
your device is rootedBusybox locatio: /bin
busybox virsion v1.18.3
system storage: 103 MB
Phone Model; Penta IS701C
ROM virsion: Penta IS701C 20120717
when i download any file or run any script it says
Script Exited with errorsoutput: No output was genrated
errors:
su: must be suid to work properly
WTF?
I thing Ive Tried But Cant find what wrong is going on !
If some One or Thechnician Having solutions About This Problem please try to help me and Get Me Out..
Hope Soon Get The Solution....
I have a IS703C can we root this by unlock root???
mayurhsoni said:
Ive Roote Device
With Unlock Root I got "su" file In /system/bin
and superuser.apk in /system/app
but i didnt got the su file in
Click to expand...
Click to collapse
I too got this device from Flipkart. But I am unable to even UnlockRoot this. The Unlockroot keep telling to try install device drivers. But its not finding the right one itself. Which drivers are required?
I did enable the USB debugging option in tablet. ANy link or help is much appreciated.
BSNL-PENTA-IS701c
Dear friend,
I found solution at another place,
Though it is for model is703c it works for is701c aLso.
I have successfully rooted my tablet using this method
step 1.) Root you tab with unlockroot,
after rooting you got a superuser app installed in ur tab. now update it to the latest
version(also install the elite. included in attactment)
2.)now install terminal emulator.
3.)ok, now u have su file in /system/bin/su
so write this command in emulator system/bin/su and hit enter. you ll now get root
permission.
4.) now from emulator type this:
rm /bin/su and hit enter.
5.) copy su from /system/bin/su to /system/xbin/su
for this write this command in emulator:
cp /system/bin/su /system/xbin/ and hit enter.
6.)now make a copy of ur su file from /system/bin/su
for this type command:
cp /system/bin/su /mnt/sdcard/
7.)now delete su from /system/bin/su
command: rm /system/bin/su and hit enter.
Thats it.. now update ur binary from superuser app. !!\
reboot the tablet and you have a rooted tablet now
i have used this method on my is701c tablet successfully
BSNL-PENTA-IS701c
mayurhsoni said:
Hello Friends,,
I Bought New TAb In India I.e. Penta IS701C having Following Features
1 Ghz Processor
512 Mb RAM
4 Gb Internal (500 Mb system, 2.5 Gb Internal Storage card)
Cg 400 GPU
Etc.
Ive Roote Device
With Unlock Root I got "su" file In /system/bin
and superuser.apk in /system/app
but i didnt got the su file in
/system/xbinyesterday my friend bought same tab
i noticed that the su file in /system/bin, /system/xbin is given by manufactures.
suppose mine might be deleleted by me from the "ADB shell" comands
Ive Formated My Whole Tab And Bingo I Got All 3 Files In All Foleders
i,e. su in /system/bin, /system/xbinand superuser.apk in /system/appbut still having problem
superuser apk shows
remounting as rw... legacy
busybx shows
your device is rootedBusybox locatio: /bin
busybox virsion v1.18.3
system storage: 103 MB
Phone Model; Penta IS701C
ROM virsion: Penta IS701C 20120717
when i download any file or run any script it says
Script Exited with errorsoutput: No output was genrated
errors:
su: must be suid to work properly
WTF?
I thing Ive Tried But Cant find what wrong is going on !
If some One or Thechnician Having solutions About This Problem please try to help me and Get Me Out..
Hope Soon Get The Solution....
Click to expand...
Click to collapse
it will be nice to start a new sub-forum thread for pents is701c just like they have for other tablets. Does any one know how to do so
OK, so I have a rooted I9300 and for some reason for the last few weeks I cant update the subinary and titanium wont get root access.
I did many google searches, tried a few thing eg (http://forum.xda-developers.com/showthread.php?t=1900217) , tried rooting again (even though I know Im rooted but nothing works.
So the next thing I want to try is to unroot my phone and root again.
My question is, because I cant access titanium to back everything up,
is there a way to unroot WITHOUT losing all apps and data?
Thanks a lot in advance.
Make nandroid backup and restore apps using titanium when your phone are rooted again.
Use MybackupPro to backup messages/contacts/bookmark/system setting/bookmarks.
Sent from my GT-I9300 using xda app-developers app
Uninstall super su via Google Play and reinstall .
jje
Cant use nandroid. It needs busybox which requests root access.
JJEgan said:
Uninstall super su via Google Play and reinstall .
jje
Click to expand...
Click to collapse
Tried it- it wont uninstall but go back to an earlier version.
Reinstalled the latest version and Im getting the same message.
Root checker app says "This device does not have proper root access".
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
qwerty12 said:
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
Click to expand...
Click to collapse
I tried rooting again- didn't change anything.
I do have CWM.
Tried using ADB, but it requests root access and fails to get it...
tomerstern said:
I do have CWM.
Click to expand...
Click to collapse
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
If you don't already have ADB setup and the correct drivers installed (if you already have Kies installed then you have the drivers installed). do the following. You can check, if you wish, by seeing when you connect your phone in recovery - you should have a SAMSUNG Android ADB Device under SAMSUNG Android Phone or an Android Debugger Bridge device in Device Manager. If not:
Download http://dl.google.com/android/repository/platform-tools_r14-windows.zip and extract the three files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to a place of your choosing
install the drivers: http://www.mediafire.com/?2243ouw1701zp8l (Extracted from Kies_2.5.0.12094_27_11.exe)
disconnect and reconnect your phone
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
That should unroot your phone.
Go to "Install ZIP from sdcard" and choose to install a zip from the internal sdcard.
Exit out of the root shell (Ctrl+C or, alternatively, "exit" and you'll be sent back to the command prompt) on your computer and download the SuperSU ZIP.
Go back to the command prompt and type this "adb push " (including the space) and drag the CWM-SuperSU-v0.96.zip onto the command prompt window, add a space and type "/data/media". You should have something like "adb push <path to CWM-SuperSU-v0.96.zip> /data/media"
This should put the SuperSU ZIP onto the root of your internal memory card. Choose go back on your phone and select to install a ZIP from the internal memory card again. You should see CWM-SuperSU-v0.96.zip. Install it, reboot, update SuperSU from the Play Store and run SuperSU from the app drawer. You should get a prompt asking you to update the su binary. Do so.
Grab Android Terminal Emulator on the Market, and run "su". If all went well, SuperSU should ask you for permission. Grant it and if the $ turned into a # and the command "id" says uid=0 (root) then you're rooted!
OK, Im really sorry and embarrassed to say that I got confused with my tab 10.1.
I Do not have CWM installed.
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
What can I do now?
Thanks again and sorry for the confusion..
tomerstern said:
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
Click to expand...
Click to collapse
Flashing CF-Root should always get you CWM as it's done through ODIN, which does not care if your phone is rooted or not. When you're flashing CF-Root, make sure the auto reboot option remains ticked. If your phone doesn't boot into CWM after ODIN reboots it, then take note of the following:
Chainfire said:
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
qwerty12 said:
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
Click to expand...
Click to collapse
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
tomerstern said:
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
Click to expand...
Click to collapse
Under the mounts and storage option, select mount /system. It will change to "unmount /system" if selected correctly.
The commands are run from an "adb shell" session, which you can get to by doing this:
Extract those three ADB files from that platform-tools ZIP to a folder somewhere (I chose C:\adb out of randomness). Open that folder and while holding down the shift key, right-click a blank, white area in the folder and select "Open command window here". You can then type "adb shell", which will allow you to run those commands.
qwerty12 said:
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
Click to expand...
Click to collapse
There isnt mount system there. I see unmount system.
I see mount data, preload etc.
OK, that's fine, you may move on to running those commands.
Two problems:
1. running "chattr -i /system/xbin/su"
resulted in a "chatter not found" message.
2. Trying to push the su zip resulted in this message: "error: device not found".
tomerstern said:
"chattr -i /system/xbin/su"
Click to expand...
Click to collapse
If rm worked on /system/xbin/su, then ignore it as you don't need it anyway.
2. Trying to push the su zip resulted in this message: "error: device not found".
Click to expand...
Click to collapse
Reconnect the phone and try again?
not working after numerous attempts.
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
tomerstern said:
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
Click to expand...
Click to collapse
That should be fine
moved it to internal memory and after shutdown, power+home+volume up wont take me to cwm anymore but to android system recovery.
Why? How do I get back to cwm? Install it again with Odin?
BY THE WAY, I can still see supersu is installed on my device. Does it mean what we did did not work?
OK, I can confirm this method works
I just installed the zip of the supersu and now Ive got full root privileges.
The reason I couldnt get into cwm was that for some reason I get a short android upgrade each time I boot up. This upgrade deletes cwm. Thats why I found out that I need to install CWM and then immidiately press power-volume up-home, before i let the device power up.
I want to give a big thanks to qwerty12 for the help and much needed patience.
I AM DUMB..... not dumb bot lost in all this stuff. I need step by step guide to root my desire x. The hasoons all in one toolkit does not work for me. I tried a lot.
This is what root checker says:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Ok, since you managed to unlock bootloader that means that you have ADB installed and have sufficient knowledge to root phone manually do this:
If you already have clockworkmod recovery installed (I explained you how to check it in the other thread where you posted your question skip to step 3.
1. go here:
http://forum.xda-developers.com/showthread.php?t=1952224
and download clockworkmod recovery, rename to recovery.img and put it on your pc on root of c: partition.
2. Reboot phone to fastboot, connect to PC and execute commands
fastboot flash recovery c:\recovery.img
fastboot reboot bootloader
fastboot erase cache
3. Boot phone to bootloader (not fastboot!!!) and choose option recovery
4. Go here:
http://androidsu.com/superuser/
download superuser form ARM devices as a flashable zip and put it on your sd (option in clockwork to mount sd as USB device)
5. Flash downloaded superuser .zip from recovery as a flashable zip.
6. Reboot, go to app drawer and you should see Superuser app. Open it.
Hasoon's tool is awesome but I prefer manual method.
I dont know how to "execute commands"
should i open command prompt and enter "fastboot flash recovery........." ? it does not work. I am not programmer, dont know how to use it but thank you for your reply. I am gonna try and try
nlooooo said:
Ok, since you managed to unlock bootloader that means that you have ADB installed and have sufficient knowledge to root phone manually do this:
If you already have clockworkmod recovery installed (I explained you how to check it in the other thread where you posted your question skip to step 3.
1. go here:
http://forum.xda-developers.com/showthread.php?t=1952224
and download clockworkmod recovery, rename to recovery.img and put it on your pc on root of c: partition.
2. Reboot phone to fastboot, connect to PC and execute commands
fastboot flash recovery c:\recovery.img
fastboot reboot bootloader
fastboot erase cache
3. Boot phone to bootloader (not fastboot!!!) and choose option recovery
4. Go here:
http://androidsu.com/superuser/
download superuser form ARM devices as a flashable zip and put it on your sd (option in clockwork to mount sd as USB device)
5. Flash downloaded superuser .zip from recovery as a flashable zip.
6. Reboot, go to app drawer and you should see Superuser app. Open it.
Hasoon's tool is awesome but I prefer manual method.
Click to expand...
Click to collapse
Execute command in the same way you did when you flashed unlock_code to unlock bootloder. You have to guide prompt to the folder with platform-tools that you installed installing ADB. The part c:\recovery.img is a path where you stored recovery.img (I told you to put it on root of c: partition) and it needs ta be named 'recovery.img'.
No no no no no please. I cant believe it.
ROOT CHECKER is now saying CONGRATULATIONS!!!! you have root access.
MAN THANK YOU!
but why is my phone not wiped? everything like before, just rooted. is this normal? every site is telling that root will factory reset your device.
THANK YOU AGAIN!
nlooooo said:
Execute command in the same way you did when you flashed unlock_code to unlock bootloder. You have to guide prompt to the folder with platform-tools that you installed installing ADB. The part c:\recovery.img is a path where you stored recovery.img (I told you to put it on root of c: partition) and it needs ta be named 'recovery.img'.
Click to expand...
Click to collapse
janickonajkrajsi said:
No no no no no please. I cant believe it.
ROOT CHECKER is now saying CONGRATULATIONS!!!! you have root access.
MAN THANK YOU!
but why is my phone not wiped? everything like before, just rooted. is this normal? every site is telling that root will factory reset your device.
THANK YOU AGAIN!
Click to expand...
Click to collapse
ROOTING WILL NOT WIPE YOUR DEVICE!!!
Bootloader unlocking resets phone, flashing superuser zip will only install superuser.apk to system/app folder and su binary file to system/bin (or system/xbin for SuperSU), which will allow you to have root privileges to phone system partition.
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