Related
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).
Hi guys,
This might be a common question/issue but i've tried to search and tried many ways. However i still am not able to do it successfully.
I'm trying to ADB push a ROM zip into my internal sdcard on my phone. Here's the steps i have used:
1. Open cmd in windows and locate the ADB path.
2. Plug phone into USB and boot into recovery.
3. Mount /sdcard/
Whenever i try that it always gives me "Error mounting /sdcard/". Why is this so? Do i need this step to do an ADB push?
I also tried doing ADB push without mounting /sdcard/ and it says file transfered in my cmd prompt window on my PC but i couldnt find the ROM zip file anywhere in /mnt/sdcard/.
Am i doing something wrong here?
Btw i'm using an SGS2 GT-i9100 with CM9 - 20120722 nightly (CWM version 6.0.1.0)
shadowcaster31 said:
Hi guys,
This might be a common question/issue but i've tried to search and tried many ways. However i still am not able to do it successfully.
I'm trying to ADB push a ROM zip into my internal sdcard on my phone. Here's the steps i have used:
1. Open cmd in windows and locate the ADB path.
2. Plug phone into USB and boot into recovery.
3. Mount /sdcard/
Whenever i try that it always gives me "Error mounting /sdcard/". Why is this so? Do i need this step to do an ADB push?
I also tried doing ADB push without mounting /sdcard/ and it says file transfered in my cmd prompt window on my PC but i couldnt find the ROM zip file anywhere in /mnt/sdcard/.
Am i doing something wrong here?
Btw i'm using an SGS2 GT-i9100 with CM9 - 20120722 nightly (CWM version 6.0.1.0)
Click to expand...
Click to collapse
And you are sure USB debugging is enabled on your phone? No need to do any kind of mount for ADB push command to work.
fxrb said:
And you are sure USB debugging is enabled on your phone? No need to do any kind of mount for ADB push command to work.
Click to expand...
Click to collapse
Yes USB debugging is turned on. Do i need to be in recovery to do ADB push?
shadowcaster31 said:
Yes USB debugging is turned on. Do i need to be in recovery to do ADB push?
Click to expand...
Click to collapse
No. Just connect the phone and enter ADB devices. Your phone should show up then.
fxrb said:
No. Just connect the phone and enter ADB devices. Your phone should show up then.
Click to expand...
Click to collapse
Great i can use adb devices. But now idea why it doesnt show my device ID correctly.
anyway i tried ADB push like this:
1. put my rom zip in the same folder as adb.exe
2. open cmd
3. type in "adb push ROM.zip /sdcard" (without the quotes)
4. i get error "failed to copy to 'ROM.zip' to '/sdcard': Is a directory"
Any idea how do i copy something into my /sdcard path?
edit: okay nvm i solved it. forgot another / after /sdcard.
Hello XDA members! i need some help from the experts.
I recently played with my phone and modify the system/apps, I was trying to delete bloatwares and useless applications, and I deleted DefaultContainerService.apk. Since my phone needs a "refreshment", I factory reset it. So Yeah... I have no root explorer or any file explorer to move the default container service to the system/apps again, all I have is the Default System Apps: Camera, gallery, phone, Messaging, play Store, Browser, etc.
I CAN'T INSTALL ANY APPS, AND I'M STUCK LIKE THIS FOR 4 DAYS NOW. PLEASE GET ME IMMEDIATE HELP!
{SOLVED!!!}
You had to ask your question in "forum.xda-developers.com/forumdisplay.php?f=1236" Q&A, Help and Troubleshooting,
But i will help you.
You MUST have ROOT permission and BUSYBOX to remount your /system/ partition.
Step 1: Go to "Settings > Developer Settings" and Enable "USB Debugging".
Step 2: Download Android SDK and Install "Android Platform Tools" on your PC.
Step 3: Connect your device with USB to your PC.
Step 4: Copy your "DefaultContainerService.apk" into somewhere in your PC.
Step 5: Open ADB Shell using:
Code:
adb shell
Step 6: Run these commands:
Code:
su
busybox mount -o remount,rw /system
chmod 777 /system/app/
NOTE: After running the "su" command, you should unlock your phone and if you see Superuser prompt, allow access to it. and if you are using the CM10.1, you should set the root access to "Apps and ADB" in the "Developer Settings" or the same for Koushikdutta's Superuser app.
Step 7: Push the DefaultContainerService.apk to your /system/app/ using:
Code:
adb push DefaultContainerService.apk /system/app/
Step 8: Restart your phone.
Step 9: Finished! But if it didn't work, you can push a file manager to /system/app/ with this tutorial and copy the file with it, or you can push a terminal emulator.
Please after this, post your threads at the right section.
DataUnit said:
You had to ask your question in "forum.xda-developers.com/forumdisplay.php?f=1236" Q&A, Help and Troubleshooting,
But i will help you.
You MUST have ROOT permission and BUSYBOX to remount your /system/ partition.
Step 1: Go to "Settings > Developer Settings" and Enable "USB Debugging".
Step 2: Download Android SDK and Install "Android Platform Tools" on your PC.
Step 3: Connect your device with USB to your PC.
Step 4: Copy your "DefaultContainerService.apk" into somewhere in your PC.
Step 5: Open ADB Shell using:
Code:
adb shell
Step 6: Run these commands:
Code:
su
busybox mount -o remount,rw /system
chmod 777 /system/app/
NOTE: After running the "su" command, you should unlock your phone and if you see Superuser prompt, allow access to it. and if you are using the CM10.1, you should set the root access to "Apps and ADB" in the "Developer Settings" or the same for Koushikdutta's Superuser app.
Step 7: Push the DefaultContainerService.apk to your /system/app/ using:
Code:
adb push DefaultContainerService.apk /system/app/
Step 8: Restart your phone.
Step 9: Finished! But if it didn't work, you can push a file manager to /system/app/ with this tutorial and copy the file with it, or you can push a terminal emulator.
Please after this, post your threads at the right section.
Click to expand...
Click to collapse
Hey, I've tried it, but when I command to copy the file, it doesn't show any connected devices, is it because of the driver?
Pegasus195 said:
Hey, I've tried it, but when I command to copy the file, it doesn't show any connected devices, is it because of the driver?
Click to expand...
Click to collapse
If when you go to use ADB it doesn't show any connected devices (First make sure your device is plugged in to your computer, and USB debugging is enabled in developer options) make sure you have installed the proper USB drivers for your device. ADB will not see the device if the devices USB drivers are not installed.
Sent from my Nexus 10 using xda premium
shimp208 said:
If when you go to use ADB it doesn't show any connected devices (First make sure your device is plugged in to your computer, and USB debugging is enabled in developer options) make sure you have installed the proper USB drivers for your device. ADB will not see the device if the devices USB drivers are not installed.
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
before I typed in "adb shell", i tried "adb devices", and it appears, but after I write adb shell, it disappears.
Pegasus195 said:
Hey, I've tried it, but when I command to copy the file, it doesn't show any connected devices, is it because of the driver?
Click to expand...
Click to collapse
I don't know! it should worked, i have same problems but i always use this way to copy files to my /system partition.
If you are on windows and you have the original Google's ADB Driver installed, go to "Device Manager" and see if you have any devices under "Unknown devices" section.
* If there was any devices, you should select it and right click on it.
* Select "Update Driver".
* In the opened window, choose "Let me choose my driver".
* Select show all devices.
* Select "Google" in left section and "Android Adb interface" in right section.
* Update the driver using this method.
* Now, it should works.
Pegasus195 said:
before I typed in "adb shell", i tried "adb devices", and it appears, but after I write adb shell, it disappears.
Click to expand...
Click to collapse
When you type adb shell are you given a shell prompt? Either a new command line beginning with "$" or "#"? Once you type adb shell if you get a shell prompt that's normal and the adb devices command will no longer work until you exit the shell. Also, if you are given a shell prompt when you type adb shell your device is connected.
Sent from my SCH-I535 using xda premium
I've finally Restored My Phone! Thank You Guys for helping me! I've thanked all of you, you have saved my phone!
Hi everyone...
I need some help.... I m on suvi v6 Jupiter rom n I accidently deleted my defaultcontainerservice. Apk from root directory to solve installation problem of some Apk... But after deleting this Apk I m unable to install any of the Apk.....
So how can I get back defaultcontainerservice.apk if someone have it for mmx a110 can u Plz upload defaultcontainerservice.apk for me I m in serious need of some software to be installed.... Thanks for the help in advance......
Sent from my Micromax A110 using xda premium
ONE LOVE said:
Hi everyone...
I need some help.... I m on suvi v6 Jupiter rom n I accidently deleted my defaultcontainerservice. Apk from root directory to solve installation problem of some Apk... But after deleting this Apk I m unable to install any of the Apk.....
So how can I get back defaultcontainerservice.apk if someone have it for mmx a110 can u Plz upload defaultcontainerservice.apk for me I m in serious need of some software to be installed.... Thanks for the help in advance......
Sent from my Micromax A110 using xda premium
Click to expand...
Click to collapse
Here's the APK: http://d-h.st/PXm
Thanks bro.......
Sent from my Micromax A110 using xda premium
DataUnit said:
You had to ask your question in "forum.xda-developers.com/forumdisplay.php?f=1236" Q&A, Help and Troubleshooting,
But i will help you.
You MUST have ROOT permission and BUSYBOX to remount your /system/ partition.
Step 1: Go to "Settings > Developer Settings" and Enable "USB Debugging".
Step 2: Download Android SDK and Install "Android Platform Tools" on your PC.
Step 3: Connect your device with USB to your PC.
Step 4: Copy your "DefaultContainerService.apk" into somewhere in your PC.
Step 5: Open ADB Shell using:
Code:
adb shell
Step 6: Run these commands:
Code:
su
busybox mount -o remount,rw /system
chmod 777 /system/app/
NOTE: After running the "su" command, you should unlock your phone and if you see Superuser prompt, allow access to it. and if you are using the CM10.1, you should set the root access to "Apps and ADB" in the "Developer Settings" or the same for Koushikdutta's Superuser app.
Step 7: Push the DefaultContainerService.apk to your /system/app/ using:
Code:
adb push DefaultContainerService.apk /system/app/
Step 8: Restart your phone.
Step 9: Finished! But if it didn't work, you can push a file manager to /system/app/ with this tutorial and copy the file with it, or you can push a terminal emulator.
Please after this, post your threads at the right section.
Click to expand...
Click to collapse
I have same problem here. How to install busybox because I cannot install anything T_T
WORKS ONLY with ROOTED Devices.
If your device is not rooted, email me (address on the bottom of the message).
Download ES File Explorer (.APK) from Google and out it somewhere reachable on your PC.
Download Defaultcontainerservice(.APK) and put it on your SD Card.
Plug your device to your PC using the USB DEBUGGING MODE.
Download Android Commander from Google, run it, and from there, you should see your device files.
From left panel, go to your ES File Explorer (.APK) and install it to /system/app to the right.
Once installed, unplug your phone, ES File Explorer should be installed on your device; then, run it.
Click on the blue device icon from top left, swipe down and go check ON on Root Explorer (by clicking the ON button) and then click on Root Explorer (The name itself).
From there go to SD card and copy your Defaultcontainerservice(.APK) and then go to DEVICE /system/app/ and copy it there.
Restart your phone and you should be just fine.
If you encounter any issues, email me at [email protected].
Hope this helped. Bye.
I am Brazilian and I'm having the same problem
I deleted DefaultContainerService.apk and now I'm having trouble downloading anything and other problems , please help me...
Whats fastboot? Cause i wanna install a rom for goophone i5 and im using Android Ultimate Toolbox pro and i dont have any recovery on the phone cause i cant flash it, and whenever i try to flash a recovery image with Toolbox it says i need to be fastbooted... Give me a hand please
HeavenKinder said:
Whats fastboot? Cause i wanna install a rom for goophone i5 and im using Android Ultimate Toolbox pro and i dont have any recovery on the phone cause i cant flash it, and whenever i try to flash a recovery image with Toolbox it says i need to be fastbooted... Give me a hand please
Click to expand...
Click to collapse
Fastboot is a command line utility used to modify and interact with the Android filesystem through USB on your computer. You can easily download and setup ADB (Android Debugging Bridge) and Fastboot using this utility found here http://forum.xda-developers.com/showthread.php?p=42407269. You will also need to make sure you've installed the USB drivers for your device in order for fastboot to function properly. To access fastboot run the following command from command line (Make sure USB debugging is enabled in developer settings first):
Code:
adb reboot bootloader
You can then flash your recovery image with the command:
Code:
fastboot flash recovery recovery.img
Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
Fastboot is a command line utility used to modify and interact with the Android filesystem through USB on your computer. You can easily download and setup ADB (Android Debugging Bridge) and Fastboot using this utility found here http://forum.xda-developers.com/showthread.php?p=42407269. You will also need to make sure you've installed the USB drivers for your device in order for fastboot to function properly. To access fastboot run the following command from command line (Make sure USB debugging is enabled in developer settings first):
Code:
adb reboot bootloader
You can then flash your recovery image with the command:
Code:
fastboot flash recovery recovery.img
Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i did the recovery command and it says waiting for device, what do i need to do?
Now if i try to fastboot using that comand it says:
ADB server is didn't ACK
*failed to start daemon*
error:
And if i write the comand to fast bood and then use Android Ultimate toolbox to flash the recovery image it just sits at waiting for device and if i cancel it and do it again it just says i need to fastboot...
if you want to flash recovery so use mobile uncle tools android app !
work on chinees device good
anabhi said:
if you want to flash recovery so use mobile uncle tools android app !
work on chinees device good
Click to expand...
Click to collapse
When i try to use MobileUncletools and i flash the recovery image, it asks if i want to boot into the new recovery, it turns off the phone, and when it turns it back on it just freezes in the apple logo
Ok so if i try to boot into fastboot with ADB and then go to Android ultimate tools pro to flash recovery, it says the device isnt in fastboot...
bump
HeavenKinder said:
Ok so if i try to boot into fastboot with ADB and then go to Android ultimate tools pro to flash recovery, it says the device isnt in fastboot...
Click to expand...
Click to collapse
You can also flash recovery from ADB shell as root by running the command (Make sure that the recovery image your using is meant for your device, and is placed on your internal storage):
Code:
cat /mnt/sdcard/recovery.img > /dev/block/{path-to-recovery-partition-block}
shimp208 said:
You can also flash recovery from ADB shell as root by running the command (Make sure that the recovery image your using is meant for your device, and is placed on your internal storage):
Code:
cat /mnt/sdcard/recovery.img > /dev/block/{path-to-recovery-partition-block}
Click to expand...
Click to collapse
Can you give me an example please? cause i tried it and it said:
"the filename, directory name, or volume label syntax is incorrect.
bump
Bump
HeavenKinder said:
Can you give me an example please? cause i tried it and it said:
"the filename, directory name, or volume label syntax is incorrect.
Click to expand...
Click to collapse
For example if I wanted to flash a recovery on my Nexus 10 without using fastboot just using adb shell I would run a command similar to this one:
Code:
cat /mnt/sdcard/clockworkmodrecovery.img > /dev/block/mmcblk0p4
If you can provide me with output of your recovery log file by going to /cache/recovery/log I can tell you which partition is your recovery partition that you need to flash.
shimp208 said:
For example if I wanted to flash a recovery on my Nexus 10 without using fastboot just using adb shell I would run a command similar to this one:
Code:
cat /mnt/sdcard/clockworkmodrecovery.img > /dev/block/mmcblk0p4
If you can provide me with output of your recovery log file by going to /cache/recovery/log I can tell you which partition is your recovery partition that you need to flash.
Click to expand...
Click to collapse
Wheres the cache file?
HeavenKinder said:
Wheres the cache file?
Click to expand...
Click to collapse
The /cache directory is located in the root (/) directory you can access the /cache directory and subsequent directories using any root file browser such as this one. You should then be able to get to recovery/log file and view it's contents.
shimp208 said:
The /cache directory is located in the root (/) directory you can access the /cache directory and subsequent directories using any root file browser such as this one. You should then be able to get to recovery/log file and view it's contents.
Click to expand...
Click to collapse
But if i don't have Google Play on the phone, how can i install the application? Do i have to search a way to flash it into the device?
HeavenKinder said:
But if i don't have Google Play on the phone, how can i install the application? Do i have to search a way to flash it into the device?
Click to expand...
Click to collapse
You can also use ADB shell to access the file contents by navigating to the /cache/recovery/log directory and looking at the output. Running the following command should show the output of the recovery log:
Code:
cat /cache/recovery/log
shimp208 said:
You can also use ADB shell to access the file contents by navigating to the /cache/recovery/log directory and looking at the output. Running the following command should show the output of the recovery log:
Code:
cat /cache/recovery/log
Click to expand...
Click to collapse
'cat' is not recognized as an internal or external command, operable program or batch file
HeavenKinder said:
'cat' is not recognized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
Make sure you run the command from ADB shell. For example first navigate to the directory where you have a ADB and Fastboot setup on your computer then open a command prompt window from that directory and run the following commands:
Code:
adb shell
cat /cache/recovery/log
shimp208 said:
Make sure you run the command from ADB shell. For example first navigate to the directory where you have a ADB and Fastboot setup on your computer then open a command prompt window from that directory and run the following commands:
Code:
adb shell
cat /cache/recovery/log
Click to expand...
Click to collapse
No such file or directory...
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