Related
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
Code:
adb shell
mkdir 21system
mount -o rw /dev/block/mtdblock2 /21system
If you're lucky it will mount your 2.1 system partition as /21system
Most likely it will say "Device or resource busy"... But worth trying anyway.
Cheers
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
I did the same thing at least twice. I was able to save it without restoring by replacing my framework-res.apk before it rebooted or froze.
Basically, try to adb into it while it is still at the Sony logo or if you get the blackscreen after the logo.
One weird thing I did notice was that I was able to replace the framework-res.apk file apparently without using 'su'. After I killed it when I was doing adb at/after the logo I tried to 'su' but it gave some error and remained at the '$' prompt. I then did the 'dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk' command and it completed. Rebooted and it worked again.
Think my whole thing was tested second time with a script.
Try making a frameworkfix.cmd file and putting this in it.
@echo off
@echo.
@echo Installing Framework
@echo.
@adb shell su
@adb push framework-res.apk /sdcard/framework-res.apk
@adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
The keep trying to run it while at the Sony logo. Give it a few runs before you give up, I swear it worked for me.
thermoska said:
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
Heck just try the following from folder with your original framework.
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
or
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
thanks guys , but I do not need commands,
I know them already , I had permissions problem.
Instructions mentioned above did not worked for me
I've got permission denied
anyway thanks
thermoska said:
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
You can access the 2.1 /system partition through 2.2 with adb.
Use this to unmount 2.2 /system
Code:
su
busybox umount /dev/block/loop1
You can check if all worked well this way:
Code:
busybox ls -1d /system/* | grep xbin
If it gives you anything, it's 2.1 -- if not, try
Code:
busybox umount -l /dev/block/loop1
Now, you should have the old 2.1 /system structure available. Ignore all errors appearing *on the phone* it'll be screwed up, unusable. Until a restart.
Now through adb you can overwrite your 2.1 framework apk with dd
(assuming you already have it on the sdcard, else, well, push it there (adb push framework.apk /mnt/sdcard/ )
Code:
dd if=/mnt/sdcard/framework.apk of=/system/framework/framework.apk
for remount system, just do
Code:
busybox mount -o remount,rw /system
after you have the 2.1 system available.
I installed 2.2 to my nand (almost fully working) at one point this way =3
Or...
You can flash again just using system.bin and everything you had would be there.
;-)
You also will need loader.sin
I did this a couple of times and work for me; I only need to root again
Good luck!
PS: In the firmware folder, you need to leave ONLY this 2 files: System.sin and loader.sin. Backup and delete all other files like amss.sin, cache.sin, etc.
well thank you
This a good idea ..
Unfortunatelly I already reflashed the phone
Hope it will help to somebody in the future
ttxdragon said:
I installed 2.2 to my nand (almost fully working) at one point this way =3
Click to expand...
Click to collapse
Thought that would work, was going to do it with .003, but I guess the recovery tool will do that for us - now we see what Z has been working on - excellent news
Just curios. Any speed improvements when extracting the img files to nand and mount/run it from there ?
Even running from sdcard img files is a perfect backup solution by just copy the img files away from time to time. But of course r/w cycles of the card are increased --> less lifetime.
But otherwise running from images is nice, as you're able to mount them. (diskinternals linux reader but R-only)
Anyone knows a win32 prog to mount the img files r/w ?
Evening Folks,
Hoping someone can help. I've been trying to install a custom rom onto my mini pro (Any custom rom!). Done a lot of reading and have managed to root my phone but am now stuck when trying to install xrecovery and CWM.
I've put xrecovery, busybox, chargemon and the cwm zip file onto my sdcard. I've been trying to move busybox, chargemon and xrecovery to the /system/bin directory using Super Manager. But it keeps telling me I do not have enough space, even tho I have 150mb internal space free on the phone. As far as I can tell the three files I need to move are less than 1mb and I've deleted just about everything I trust myself to delete.
ALong the way I managed to muck up the google acount password and ended up resetting the phone to the factory defaults, so there is nothing on it. Currently the only downloaded apps are Root Checker, Super Manager and SuperUser.
So I'm hoping one of you fine chaps, and chapetts, is going to be able to point out the stupid mistake I'm making.
I have to escape sooon, so will not be able to reply util tomorrow. Thanks in advance.
SteveG
You realise the /system partition is seprate from the /data partition, so internal free space does not mean free space on the system partition. And did you remount the system partition yet? (This command in terminal emulator: mount -o remount,rw /system) Or you could simply use root explorer and save lots of trouble figuring out the terminal.
i would advise you to install xrecovery via aais, it is quite simple; download aais and put on your sd, download terminal emulator from the market (needs root, you are rooted you say so that is fine) type the commands:
su (start superuser, click allow)
cd sdcard/aais
sh install.sh (now you see the menu)
type 0 for installing xrecovery. phone will reboot and you're done. Download cwm for recovery.zip from xda and install cwm via xrecovery, now you can install custom roms.
ruifung said:
You realise the /system partition is seprate from the /data partition, so internal free space does not mean free space on the system partition.
Click to expand...
Click to collapse
Ah, no I didnt realise that. Anyway I can tell how much space in the system partition? Any reason why it should be full after a factory reset? If it is full, any suggestions?
ruifung said:
And did you remount the system partition yet? (This command in terminal emulator: mount -o remount,rw /system) Or you could simply use root explorer and save lots of trouble figuring out the terminal.
Click to expand...
Click to collapse
Nope, didnt realise I had to do this, , can you explain why?. Before I do anything else?
Ameijer said:
i would advise you to install xrecovery via aais, it is quite simple; download aais
Click to expand...
Click to collapse
From the market? Hehe, I didnt know what this was so I googled it. Found myself at the Association of Archaeological Illustrators and Surveyors. Strangley enough very little about Android on their website.
Ameijer said:
and put on your sd, download terminal emulator from the market (needs root, you are rooted you say so that is fine) type the commands:
su (start superuser, click allow)
cd sdcard/aais
sh install.sh (now you see the menu)
type 0 for installing xrecovery. phone will reboot and you're done. Download cwm for recovery.zip from xda and install cwm via xrecovery, now you can install custom roms.
Click to expand...
Click to collapse
If I do this where does the xrecovery file need to be for the install?
Thanks for replying guys. You have givne me some suggestions for the way forwards.
SteveG
AAIS is an automatic installer for xrecovery, sorry..was not clear enough apparently. You can find it here on xda (xrecovery automatic installation script or something like that) and works like a charm! No need to copy files yourself, run the script and you'll have xrecovery, afterwards install cwm via xrecovery..simple as that
AAIS did the trick (Although I had to use a magnifyng glass to use the terminal emulator. Currently waiting for the rom to finish installing.
Thanks for your help
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?
My phone is rooted. Script manager has su and I clicked the green skull
I can copy via terminal as well as file manager apps.
Can someone give me any help?
Every time I try something it does not work or give errors.
One example I am trying is this:
umount /data/data/app_dir/prefs/ mount -o bind /sdcard/data/wow/shared_prefs/ /data/data/jp.gree.modernwar/prefs/
I tried other copy commands but I get segmentation error etc
Feel like I am running in circles.
is there not a simple copy this folder sdcard/whatever to /data/data/app_dir
thank you
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