Related
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?
Hey guys,
I'm having a problem with ES file explorer. After several days I managed to root my HUawei U8800 Ideos X5 (Android 2.3.5) and obviously one of the next steps is installing CWMR. Unfortunately I'm failing here too. I tried to copy the recovery.img to the .cust_backup/image, but it keeps to say copy failed. Root access was given and I checked all four boxes in root settings. Someone in a german forum told me to update the binarys in SU, which failed too (it says sth like copy su to /system -> failed!). I'm not even sure ES FE would work if the binarys would be current.
Is there someone who can help me? Any ideas?
I already tried the app Mount /system (rw / ro). It didn't work with this too.
Thanks a lot.
no ideas?
You must have the /system folder mounted for read and write, default is read-only.
Different folders in the file structure could be located on different file systems, the easiest way to be sure that you have read and write access were you want to put files, imho, is by using root explorer.
If you are rooted and ES have root permissions then the problem is that the folder is non-writable. I don't know the app you tried to use to mount the /system as r/w but it's easy to do in root explorer or through adb shell with a little bit of *nix knowledge (su and mount -o remount,rw).
Should work from terminal emulator app as well.
C:\Users\...>adb push C:\recovery.img /.cust_backup/image/
failed to copy 'C:\recovery.img' to '/.cust_backup/image//recovery.img': Read-on
ly file system
before I typed
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Doesn't work. adb etc. is installed.
I'm really desperate about this now, I think something is really wrong with my system partiture or something like that. I consider formatting it, the problem I obviously have is that without CWMR I have no clue how to do that and how to flash an OS after it. Does someone have ideas about the whole issue? Interesting facts about my device: Often I'm not able to flash a stock ROM, it stops somewhere in the middle of the process. Rooting works often, but not always with SuperOneClick or zergrush. At the moment my superuser app says "root app_63" in a red font instead of "root root" in a green font, at least I have current binaries at the moment, but this doesn't work always as well. Seems like I am pretty alone with all these problems, that's why I want to format /system...
Please help me! Thanks
Give root explorer a try!
Sent from my OC ed mind.!
Why would you think that would work? ES File Explorer does basically the same...
Dont EVER try to format /system or u r gonna end up completely bricked. Just take your phone to a service centre and see what can be done. If you are under warranty, replace the mobile.
Hope i helped .
Sent from my GT-S5360 using XDA-Developers App.
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
void00 said:
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
Click to expand...
Click to collapse
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
sangalaxy said:
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
Click to expand...
Click to collapse
I tried deleting the folder through adb shell.
Issued following commands:
adb shell
su
# cd /data
# rm -r lost+found
Click to expand...
Click to collapse
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
void00 said:
I tried deleting the folder through adb shell.
Issued following commands:
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
Click to expand...
Click to collapse
try r+w+x
sangalaxy said:
try r+w+x
Click to expand...
Click to collapse
Still getting the same error. Operation not permitted.
void00 said:
Still getting the same error. Operation not permitted.
Click to expand...
Click to collapse
may be something preventing it
try a reset and simply format the data in cwm do backup first
sangalaxy said:
may be something preventing it
try a reset and simply format the data in cwm do backup first
Click to expand...
Click to collapse
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
void00 said:
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
Click to expand...
Click to collapse
ok so don't backup
if anything goes wrong you can still flash the stock right??
sangalaxy said:
ok so don't backup
if anything goes wrong you can still flash the stock right??
Click to expand...
Click to collapse
hmm, i'll try flashing CWM and then do a format of every partition and freshly flash the rom.
Will report back if there's the same problem.
UPDATE:
Formatted all the partitions including /data/media using CWM
Did a fresh install of rom.
I've got my internal memory back
Thanks!
my 2 cents...
my 2 cents... I've opened the lost+found folder with the file manager (this https://play.google.com/store/apps/details?id=com.rhmsoft.fm), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
fabiosirigu said:
my 2 cents... I've opened the lost+found folder with the file manager (this *edited original link*), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
Click to expand...
Click to collapse
I was having the same problem. My phone is Samsung Galaxy S2 (GT-i9100). I was on stock Jellybean. But it was starting to feel sluggish and slow. So, having heard about the new Android Kitkat's lower memory requirements and smoother performance, i decided to install Cyanogenmod 11 on it.
Installation was not without problems. At first i flashed Clockworkmod Recovery 6.0.2.9. The phone bricked into a bootloop with a yellow triangle on it. Flashing the Cyanogenmod 11 resulted an error of "Status 7". So i searched for the latest Clockworkmod Recovery, which was at 6.0.4.5. After flashing the 6.0.4.5, Cyanogenmod 11 installed successfully. Performance was really smooth. No lags, no jitter, and everything worked like a charm.
The problem started when i re-installed my applications. Suddenly i got a message of "insufficient storage". This has never happened before. Note, that i previously had large games on my phone like Real Racing 3 and Bard's Tale. This time, i haven't even installed those large games. So i looked at my Storage, and found out that i only had 141mb of free space. But the weird thing is, my reported Apps was only 353mb, from 1.97GB internal storage. So there was over 1GB of storage just vanished.
I browsed for a solution to this problem, and landed on this thread. After reading reply from fabiosirigu, i decided to brave myself, and deleted the content of the lost+found folder (but not the folder itself). I accessed the folder with the built-in File Manager from Cyanogenmod, and set it to "Root Access Mode", and select all folder in the folder, and deleted it. The deletion took quite a few minutes, which felt like ages. Just sat on my bed, crossed my fingers, hoped that nothing will go wrong.
After the deletion, i rebooted my phone. the cyanogenmod logo appeared, and the system booted as usual. I just exhaled a massive sigh of relieve. I went straight to the internal storage, and now it is showing the correct report, 1.67GB of free space.
Thank you for your reply fabiosirigu. Really solved my problem.
lost+found genesis
Let somebody correct me if I'am wrong.
lost+found directory is standard for some unix/linux filesystems. All ext(s) 2, 3 and 4 contains it by default.
The operating system collects unidentified, broken files and its parts inside of l+f dir.
No one of these junks is used by running system.
So - you can look in l+f for some lost, missing files. If you don't miss for any (who knows it better?) then you don't need l+f content.
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