If somebody is still running old firmware would be so kind to upload the following folder:
/bin
/etc
/* (all files (not folders) on the root
if you open root explorer its right there!
with this I don't mean /system/bin and /system/etc I have those.
Thank you very much!!!!
slade
Hi Slade !
Just flashed my mini pro with SEUS & rooted it BUT there's no "bin" folder on the root of my device, but there is a "sbin" folder
cache
config
d
data
dev
etc
proc
root
sbin
sdcard
sqlite_stmt_journals
sys
system
Click to expand...
Click to collapse
Do you want the "sbin" folder ?
(I'm with the 2.1.1.A.0.6 fw)
I already got the files via pm but sbin folder would be nice to have as well.
Thank you!
Sent from my U20i using XDA Premium App
I uploaded it on MU but there's only 1 file on the "sbin" folder, only ~130kb
http://www.megaupload.com/?d=ARHET2GY
I put it into Attached Files too
& sorry for my fu**ing poor english
Your english is perfect as i can understand what you are saying !
And thank you for the upload when i get home i'll start digging into the files i got and see if we have room for improvements :-D
Sent from my U20i using XDA Premium App
Related
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
racht said:
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
Click to expand...
Click to collapse
yess, thank you! now i found a mkfs.yaffs2 for arm processors for android. it's verry slow.
so i made my sdcard to ext2, and now i try to "extract" my img.
so ... It's used to ?
trapacska said:
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
Click to expand...
Click to collapse
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
propc said:
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
Click to expand...
Click to collapse
it's cool! thank you. now i try to debrand the oroginal x8 rom.
trapacska said:
it's cool! thank you. now i try to debrand the oroginal x8 rom.
Click to expand...
Click to collapse
you know what. i've found a better method to change permissions
1-mount original system.img
Code:
mkdir tmp/1
sudo mount -o loop /your/system.img/path /tmp/1
2-clone permissions from original system.img to your system folder
Code:
chmod -R --reference /tmp/1 /your/new/system/path
and the permission fix done!
EDIT: tested. and worked. I've finally created my own modified ROM (running on sdcard)
EDIT2: some problem with root permissions, will work on it
thank you i found a way to fix permissions too:
1. unyaffs original system.img
2. in busybox shell mount it to r/w
3. copy xrecovery and su and superuser to fresh rom.
(for me it works well without xrecovery fix permissions)
if there is some error, you can fix it with xrecovery
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
bnight said:
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
Click to expand...
Click to collapse
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
propc said:
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
Click to expand...
Click to collapse
/system/framework (for a skin)((but the all folder))
trapacska said:
/system/framework (for a skin)((but the all folder))
Click to expand...
Click to collapse
thanks. will try porting from htc legend 2.2 rom later.
Hello,
I do not have enough messages to start discussion in http://forum.xda-developers.com/showthread.php?t=859571, so, I am doing it here.
After updating my x10 mini to 2.1.1.A.0.6 (with full wipe) and reinstallation of xrecovery it stopped working. It just does not appear if I press back button several times during start.
I tried both .apk and manual method, checked permissions, changed it to 777, but xrecovery still does not appear.
Is something wrong with bootloader in this version, or is there any other reason? How to handle the issue?
Thank you in advance, having xrecovery is crucial for me.
Xrecovery works fine on 2.1.1.A.0.6. (I am using it right now to backup my 2.1.1.A.0.6 system)
double check your busybox install and make sure you are using the old xrecovery 0.1 for mini (the new versions of Xrecovery don't support mini or pro)
Kiwi
Could you please attach busybox, changemon and xrecovery.tar in the post?
illi4 said:
Hello,
I do not have enough messages to start discussion in http://forum.xda-developers.com/showthread.php?t=859571, so, I am doing it here.
After updating my x10 mini to 2.1.1.A.0.6 (with full wipe) and reinstallation of xrecovery it stopped working. It just does not appear if I press back button several times during start.
I tried both .apk and manual method, checked permissions, changed it to 777, but xrecovery still does not appear.
Is something wrong with bootloader in this version, or is there any other reason? How to handle the issue?
Thank you in advance, having xrecovery is crucial for me.
Click to expand...
Click to collapse
Do you have the right busybox version? I think its this one http://db.tt/pkNQiaV
Put it in /system/bin folder
Sent from my U20i using XDA App
HerrKuk said:
Do you have the right busybox version? I think its this one
Put it in /system/bin folder
Click to expand...
Click to collapse
Did it!
Thank you
Yeah, it was the same here. xrecovery 0.3 doesn't work on e10i with 2.1.1.A.0.6.
Installed xrecovery 0.1 again and it works well.
Thx for this thread!
With the xrecovery.tar and chargemon from this thread: http://forum.xda-developers.com/showthread.php?t=878426 and the busybox from http://db.tt/pkNQiaV I'm now currently running xRecovery on 2.1.1.A.0.6. Perfect!
Thank you man! This worked like a charm on my x10 mini FW:2.1.1.A.0.6!
yeah ok so i downloarded the xrecorery 0.1 and unzipped it on my pc and got this
(folder) etc
(folder) res
(folder) sbin
(folder) temp
busybox
chargemon
default.prop
init
init.rc
and a recovery rar
but no apk??????
plzzzz help me i am getting really crazy now
freebordjunky said:
yeah ok so i downloarded the xrecorery 0.1 and unzipped it on my pc and got this
(folder) etc
(folder) res
(folder) sbin
(folder) temp
busybox
chargemon
default.prop
init
init.rc
and a recovery rar
but no apk??????
plzzzz help me i am getting really crazy now
Click to expand...
Click to collapse
this might help
http://forum.xda-developers.com/showthread.php?t=878426
plus, you only need the modified chargemon, busybox and xrecover.tar, and have them moved to /system/bin
if it doesnt work, i think you need to edit chargemon. look into the original thread for further instructions.
Now Working
Got this apk here and now it´s working.
xrecovery on x10mini pro 2.1.1.A.0.6
http://forum.xda-developers.com/showthread.php?p=13791318
it was driving me crazy.
Hi everybody
My problem is with my GPS signal. I searched in the forum and I found a topic ( http://forum.xda-developers.com/showthread.php?t=1060963 ) with a correct gps configuration. I followed the steps but when I edit gps.conf file I can't do becouse I haven't permissions. In other topic talk about how I can do to give file permissions with:
- adb shell
- su
- mount -o remount,rw /dev/block/mtdblock3 /system
I following this steps but when I edit the gps.conf file (with root explorer) and I put the new configuration and reboot the terminal, the file don't change and has the old configuration.
What's the problem? I don't know
Sorry for my bad english
Thanks !!
Your problem is that the phone is s-on. You can't edit /system when your phone is on. Boot into Clockwork Recovery, mount usb + system, and debug with abd or a program like Android Commander. Then reboot your phone.
pepijn499 said:
Your problem is that the phone is s-on. You can't edit /system when your phone is on. Boot into Clockwork Recovery, mount usb + system, and debug with abd or a program like Android Commander. Then reboot your phone.
Click to expand...
Click to collapse
Thanks you man !! I could edit the file and the gps works perfectly.
I hope this post will serve to other people's
Thanks for all !!
I've been away from a computer for a couple of weeks now, but I needed to edit my gps.conf yesterday, so here's what I did. It was actually pretty enjoyable.
I used Root Explorer throughout.
I created a new folder where I would carry out all of my operations on my SD card. I then copied the existing gps.conf to that folder.
Then I edited the file with Root Explorer's built in text editor and created a folder named "system" and a subfolder inside that folder named "etc". Then I moved gps.conf into "etc".
Next, I longpressed the "system" folder and zipped it. From there, I flashed it with CWM and the GPS has been working flawlessly since.
Sent from my HTC Legend using XDA App
Asovse1 said:
I've been away from a computer for a couple of weeks now, but I needed to edit my gps.conf yesterday, so here's what I did. It was actually pretty enjoyable.
I used Root Explorer throughout.
I created a new folder where I would carry out all of my operations on my SD card. I then copied the existing gps.conf to that folder.
Then I edited the file with Root Explorer's built in text editor and created a folder named "system" and a subfolder inside that folder named "etc". Then I moved gps.conf into "etc".
Next, I longpressed the "system" folder and zipped it. From there, I flashed it with CWM and the GPS has been working flawlessly since.
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
I don't knew this interesting way.
Thanks for share it.
Hey
I would like to edit the default.prop of my device so I can use some Android debugging tools.
I know I need to change the file in the ramdisk, but I have no idea how to do this.
Can anyone help me with this?
Thanks!
Try a tool like Root Explorer to mount the folder read/write, then edit/save to your heart's content.
Thanks, but that wont work, as the file gets replaced every reboot by the original one
Sent from my GT-I9100 using xda premium
You need to modify the Ramdisk - split the kernel/boot image.
firefds said:
Thanks, but that wont work, as the file gets replaced every reboot by the original one
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Everytime you modify Default.prop it will create a .bak file. Just press back button and whoop back in again . You will see a Default.prop.bak just delete it before rebooting your device.
Hope it helps.
Thanks for your help.
I managed to do this by using this guide for preparing the environment:
http://forum.xda-developers.com/showthread.php?t=1186409
And this guide for unpacking and repacking the kernel:
http://forum.xda-developers.com/showthread.php?t=1294436
I installed a long time ago a xrecovery using an android app. This xrecovery (Ithink it is the latest...) is still working, but my problem is that xrecovery or CWM are preinstalled with the kernels. So I have now 2 xrecovery...
Some one know how can I remove it? I didn't tried to reinstall the android app to see if there was a uninstall function, because I did not found it (and I was a bit lazy to use the pc for that
Uhhh just like reflash to generic and then redo everything you have done
Sent from my X10i using xda premium
Delete the following files:
In: /system/bin/
chargemon
charger
Click to expand...
Click to collapse
In: /system/xbin/
sh
xrecovery.tar
Click to expand...
Click to collapse
jakuburban said:
Delete the following files:
In: /system/bin/
In: /system/xbin/
Click to expand...
Click to collapse
i would do it this way so you dont break offline charging
delete /system/bin/chargemon
rename /system/bin/charger to chargemon
then delete the /system/xbin/recovery.tar
that will remove it all.
Pvy
pvyParts said:
i would do it this way so you dont break offline charging
delete /system/bin/chargemon
rename /system/bin/charger to chargemon
then delete the /system/xbin/recovery.tar
that will remove it all.
Pvy
Click to expand...
Click to collapse
Pvy, I have the same issue. I want to remove xrecovery from my xperia x8, running on stock kernel with stock rom, but I don't see file with name "charger" in system/bin. There is only chargemon!? Then, when I go to system/xbin i don't have recovery.tar either. I saw a file named xrecovery.tar, but it is located in system/bin. Please tell me how to remove xrecovry safely from my phone and how to restore the offline charging. Thanks in advance
carevicata said:
Pvy, I have the same issue. I want to remove xrecovery from my xperia x8, running on stock kernel with stock rom, but I don't see file with name "charger" in system/bin. There is only chargemon!? Then, when I go to system/xbin i don't have recovery.tar either. I saw a file named xrecovery.tar, but it is located in system/bin. Please tell me how to remove xrecovry safely from my phone and how to restore the offline charging. Thanks in advance
Click to expand...
Click to collapse
How did you instal it...
Sent from my Transformer TF101 using Tapatalk 2
pvyParts said:
How did you instal it...
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I installed it by simply placing the necessary files with root explorer manually
carevicata said:
I installed it by simply placing the necessary files with root explorer manually
Click to expand...
Click to collapse
Well I'd recommend reversing those steps.
Sent from my Galaxy Nexus using Tapatalk 2
pvyParts said:
Well I'd recommend reversing those steps.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
OK, I'll give it a try, thanks BTW can I flash CWM via xrecovery by install.zip? Done this way can make xrecovery to disappear and it will be replaced by CWM My final goal is to flash nAa's jb kernel in order to put on Mini CM10. That's why I desperately need to remove xrecovery in order to install CWM.