Hi all, probably mine is a noob question, since in android I'm quite a noob. I've been using gentoo for years though so I'm somehow confident with the shell and I'd love it to work on it on my rooted sgs2
So, basically, I searched but I didn't find (/me fool). When asking for write permission everyone is talking about /system, but not / in general. Is there a reason? If I need to copy&paste or just create a file directly in / how can I do?
Giving a #mount command shows me only this about "/" :
rootfs on / type rootfs (ro,relatime)
so there is no indication about a /dev/block adress or a "real fs" information (which for what I know is ext4). Also those informations looks like a "pseudo-filesystem" partition, like sysfs or fusefs for instance.
Looking at the rest of the "#mount" output (aka "cat /proc/mounts") I see the only other partition mounted in ro is /system, but it has a block device association and I can remount it in rw easily. Not the same with /
Can anyone clarify me please? Is there a way to mount / in rw?
This is because that's where we want to use. The system area is where modifications of the device (done by people who should know exactly what they are doing; e.g changing build.prop codes) is made. It can easily be made r/w but only if your device is rooted and in many cases S-OFF'ed. If you have root (and for some devices S-OFF), then you can just use a file explorer (which supports root functions e.g Root Explorer) to mount it as r/w (this is the easiest way).
Yes, my phone is rooted and S-OFF'd and everything's fine, I have no particular problem to fix, just wondering.
So what if anything goes corrupted in / (outside /system, /data or any other separate partition) and we need to restore it or just create a script or anything changing permissions or writing data on the / partition? Btw: for what I know about linux, the root partition (I mean "/" not "/root") must be a "real partition" with a proper fs and mount point, and not anything cached somewhere. Guess it must be the same in android too. So, where is it?
johnnystuff said:
Yes, my phone is rooted and S-OFF'd and everything's fine, I have no particular problem to fix, just wondering.
So what if anything goes corrupted in / (outside /system, /data or any other separate partition) and we need to restore it or just create a script or anything changing permissions or writing data on the / partition? Btw: for what I know about linux, the root partition (I mean "/" not "/root") must be a "real partition" with a proper fs and mount point, and not anything cached somewhere. Guess it must be the same in android too. So, where is it?
Click to expand...
Click to collapse
For Android (about corruption for the first question), people usually just reflash the rom since you wouldn't be able to boot the phone (at least fully) to be able to replace a missing file(s). Where is "/" you ask, if you open Root Explorer that's where you'll be.
I know where is "/" in that sense, I meant where is the partition or the mount point
anyway..... not a big issue. I must deduce in android, in any present past and future device, the /efs directory is mounted on a separate partition. All my guessing came mostly from that point, since I wanted to backup and most of all _restore_ that dir using the shell. Again, I don't need it now, I did my backup and I hopefully will never need a restore. Most of all in my sgs2 /efs is on a rw partition, so no issue at all even in case of deep trouble (/efs deletion).
And yep, I know about EFS Pro and similar tools, but wanted to try the sh way and to understand something more of android in general
why is the trouble EFS deletion? what is EFS partition for?
Sent from my Nexus S using XDA App
Speaking on this subject, I have tried but cannot remove the file "/sys/devices/virtual/sec/ts/touchkey_led" (trying to turn off lights behind capacitive buttons).
Does anyone know how to move/delete this?
No, led hack doesn't work on my device if you are wondering.
why is the trouble EFS deletion? what is EFS partition for?
Click to expand...
Click to collapse
/efs is where your IMEI and other critical (and legal) information of your device are stored. You should backup it as soon as you root your phone, before any other mod. Hence comes the troubles, since if you delete it for any reason, you are in deep troubles, expecially if you didn't backup it.
I have tried but cannot remove the file "/sys/devices/virtual/sec/ts/touchkey_led"
Click to expand...
Click to collapse
I'm not totally sure about what I'm saying on android, but on linux /sys is an in-memory filesystem, meaning it is generated by the system after (at) boot and it's where all your device are linked in for the kernel, so it basically manged by the kernel itself. That could be the reason why you cannot delete anything in there. But again, I'm somehow guessing so, wait for someone else to confirm (or deny)
johnnystuff said:
That could be the reason why you cannot delete anything in there. But again, I'm somehow guessing so, wait for someone else to confirm (or deny)
Click to expand...
Click to collapse
Actually you can delete items in there... but they will just be re-created .
Recently purchased Xolo A500, I have been trying to build CWM in builder.clockworkmod.com, but nothing works.
I have tried three times but none works.
Provided with a custom recovery.fstab but still wont work.
So can anyone help me out here.
I can provide the stock recovery.img
BTW, in recovery.fstab provided in builder.clockworkmod.com after it has finished the build the list is
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata length=-16384
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Sdcard location is wrong. It is mmcblk1p1
And mtd file in /proc/ is completely blank so I have no idea from where to get the partitions.
But I have researched enough and understand partitions and after analysing the partitions file I have extracted most of the blocks from the phone.
So now I have dumped the recovery and system partitions.
So I modified the recovery.fstab file like this
# mount points fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/cache ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p13 length=-16384
/misc emmc /dev/block/mmcblk0p19
/recovery emmc /dev/block/mmcblk0p16
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p12
/sys_boot vfat /dev/block/mmcblk0p3
/FOTA emmc /dev/block/mmcblk0p17
Has my recovery.fstab got any errors???
The online CWM builder doesn't work???
So Can Anyone Build For Me A CWM Recovery????
did u got any success
even I am waiting for same if you get any sucess please help
Thanks
kank_fraud said:
Recently purchased Xolo A500, I have been trying to build CWM in builder.clockworkmod.com, but nothing works.
I have tried three times but none works.
Provided with a custom recovery.fstab but still wont work.
So can anyone help me out here.
I can provide the stock recovery.img
BTW, in recovery.fstab provided in builder.clockworkmod.com after it has finished the build the list is
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata length=-16384
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Sdcard location is wrong. It is mmcblk1p1
And mtd file in /proc/ is completely blank so I have no idea from where to get the partitions.
But I have researched enough and understand partitions and after analysing the partitions file I have extracted most of the blocks from the phone.
So now I have dumped the recovery and system partitions.
So I modified the recovery.fstab file like this
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 /dev/block/mmcblk0p15
/data yaffs2 /dev/block/mmcblk0p13
/misc mtd misc
/recovery mtd /dev/block/mmcblk0p16
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system yaffs2 /dev/block/mmcblk0p12
Out of this I don't have any info abt the /boot partition and /misc partition
Although I think /boot partition can be at /dev/block/mmcblk0p8
I have already dumped that partition but I don't know how to analyse any of these files in a windows machine.
Has my recovery.fstab got any errors???
The online CWM builder doesn't work???
So Can Anyone Build For Me A CWM Recovery????
Click to expand...
Click to collapse
Please help
mithani said:
even I am waiting for same if you get any sucess please help
Thanks
Click to expand...
Click to collapse
Dear Sir,
Please help me, i done rooting of Xolo A500, but i done one mistake yesterday, i have done Factory Reset to it, after dt my device is showing that
not rooted, bt still showing Superuser.apk, n i've tried to root again,but it shows error "system/bin/sh : chmod not found", n my wifi is also not working, please help me Sir..:crying:
If you have been able to root the phone, the first thing you should have done is backup all the partitions necessary.
boot is mmcblk0p8
system is mmcblk0p12
recovery is mmcblk0p16
The first thing I done with the phone I recieved after 5mins is root the phone.
I didn't check it before that
So can you guys tell me how did you find the performance of the phone.
Cuz mine, everything is crashing
Phone, messeging, apps, launcher, etc...
I regret actually buying this phone.
Well the first thing I would say anyone should do is backup there boot, recovery, system partitions and whatever else you want to after you root.
I can upload the boot and recovery partitions but i am very sorry I won't be able to upload my system partition.
I backed it up when I was actually using the phone and my persona; data is there i presume.
I totally forgot how I backed up the partitions right now.
I'll post the method I used once I can remember again.
I gave up on building CWM cuz I have failed so many times that I am completely fed up of it.
I am totally new to working in linux and first I need to figure that out.
Usually you use 'cat proc/mtd' to view the partitions, but its empty in our case.
So use 'cat proc/partitions' instead
But you will only get a list of the partitions without any labels.
Out of that,
/boot mmcblk0p8
/cache mmcblk0p15
/data mmcblk0p13
/misc mmcblk0p19
/recovery mmcblk0p16
/sdcard mmcblk1p1
/system mmcblk0p12
/SYS_boot mmcblk0p3
/FOTA mmcblk0p17
/emmc mmcblk0p18
/persist mmcblk0p14
And lots more partitions are there.
I made an image of the whole NAND chip by using mmcblk0 only.
And also the other partitions individually
You can use this command to back up your partitions.
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img bs=4096
And change the names and partitions accordingly I have mentioned.
It should work.
It only works for rooted phones btw.
I have reset my phone a couple of times after I rooted and I didn't loose root.
And please can anyone confirm me about the performance of the phone.
I am having nightmares personally
I wish I could port Gingerbread instead.
Please ppl, reply.
And if anyone can upload there freshly rooted system.img partition, I'll be glad.
Maybe I recieved a phone with a very unstable ROM
Flash the recovery with
fastboot flash recovery XoloA500_Recovery_Original.img
And before you flash any new recovery, try this command
fastboot boot recovery.img
Replace recovery.img with the name you have for your recovery
If it hangs or reboots, that means the recovery is most probably won't work for you.
If still you want to try, flash it
If it doesn't work, flash the stock back
Same can be done for a boot.img you want to try.
Somebody please use the above method and dump a clean stock rooted system.img.
I used to believe backup is useless, but when you have a device that is not supported by any developer, its better to backup before you mess with it urself.
EDIT: DD command might not work for the system partition
I am not quite sure as I haven't tried to restore the backup
So please be cautious.
I am not to be blamed if any mishap happens to you or your phone.
Currently I am out of station to try anything.
I don't use laptops cuz I find it inconvenient.
Research and post your findings
I have also used this 'http://android.podtwo.com/romdump/' to dump my ROM
Use all available methods and backup your ROM in all the various methods possible.
Afterall no one is supporting our device yet.
Require Xolo A500 system.img Pleaseeee
:crying: Please somebody upload system.img of Xolo A500, please its a request to you friends.....Please :crying:
---------- Post added at 07:20 PM ---------- Previous post was at 07:04 PM ----------
kank_fraud said:
Well the first thing I would say anyone should do is backup there boot, recovery, system partitions and whatever else you want to after you root.
I can upload the boot and recovery partitions but i am very sorry I won't be able to upload my system partition.
I backed it up when I was actually using the phone and my persona; data is there i presume.
I totally forgot how I backed up the partitions right now.
I'll post the method I used once I can remember again.
I gave up on building CWM cuz I have failed so many times that I am completely fed up of it.
I am totally new to working in linux and first I need to figure that out.
Usually you use 'cat proc/mtd' to view the partitions, but its empty in our case.
So use 'cat proc/partitions' instead
But you will only get a list of the partitions without any labels.
Out of that,
/boot mmcblk0p8
/cache mmcblk0p15
/data mmcblk0p13
/misc mmcblk0p19
/recovery mmcblk0p16
/sdcard mmcblk1p1
/system mmcblk0p12
/SYS_boot mmcblk0p3
/FOTA mmcblk0p17
/emmc mmcblk0p18
/persist mmcblk0p14
And lots more partitions are there.
I made an image of the whole NAND chip by using mmcblk0 only.
And also the other partitions individually
You can use this command to back up your partitions.
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img bs=4096
And change the names and partitions accordingly I have mentioned.
It should work.
It only works for rooted phones btw.
I have reset my phone a couple of times after I rooted and I didn't loose root.
And please can anyone confirm me about the performance of the phone.
I am having nightmares personally
I wish I could port Gingerbread instead.
Please ppl, reply.
And if anyone can upload there freshly rooted system.img partition, I'll be glad.
Maybe I recieved a phone with a very unstable ROM
Flash the recovery with
fastboot flash recovery XoloA500_Recovery_Original.img
And before you flash any new recovery, try this command
fastboot boot recovery.img
Replace recovery.img with the name you have for your recovery
If it hangs or reboots, that means the recovery is most probably won't work for you.
If still you want to try, flash it
If it doesn't work, flash the stock back
Same can be done for a boot.img you want to try.
Click to expand...
Click to collapse
------------------------
Sir,
Please upload system.img, bcz nobody is given any response, i'm totally depends on ur help.
please sir, bcz my handset was in service center before some days, n again... my dad will kill me.
Please sir kindly use moborobo for backup ur personal data, Sir Please help me Sir please :crying::crying::crying:
Why don't you people research a day or 2 before hanging your phone to death.
And kid, system.img, how the hell do you plan to restore that???
I have just made a fluke backup, not necessary that it will work.
You need an update.zip, which I don't have and I don't know or currently have any resource to make one.
You shouldn't have messed with things you don't know.
Specially a phone that has no developer support currently.
You better send it for service.
I can't help you.
Neither do I have any source, nor do I have the full knowledge.
I have not tried ever to build a ROM before.
And as we don't have CWM for our phone, I am not willing to risk it just for the sake of fun.
And the moment I return station, I personally am gonna send the phone for service as I am sick and tired of it.
Its a headache to use this phone.
Why don't you people research a day or 2 before hanging your phone to death.
And kid, system.img, how the hell do you plan to restore that???
I have just made a fluke backup, not necessary that it will work.
You need an update.zip, which I don't have and I don't know or currently have any resource to make one.
You shouldn't have messed with things you don't know.
Specially a phone that has no developer support currently.
You better send it for service.
I can't help you.
Neither do I have any source, nor do I have the full knowledge.
I have not tried ever to build a ROM before.
And as we don't have CWM for our phone, I am not willing to risk it just for the sake of fun.
And the moment I return station, I personally am gonna send the phone for service as I am sick and tired of it.
Its a headache to use this phone.
Anyone want to knock yourself out by flashing my stock rooted system.img, knock yourself out
http://www.mediafire.com/?3vs68fl1lpsoc9u
If you break your precious phone, I am not responsible
fastboot flash system system.img
CWM for Xolo A500
Well by luck I found a CWM that boots but it doesn't backup
After a bit of modification, I have been able to successfully create a nandroid backup.
But sadly its chinese and I have no idea on how to translate to english, so please ask someone else.
http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
It is originally for the GreenOrange M2S mobile and it also works with the Videocon A30
After a bit of modification, it seems to be working for our Xolo A500
Its in chinese so figure it out yourself.
For now I all I can say is if you want to backup, do not flash
Use this command 'fastboot boot cwm1.img'
Your phone will boot to CWM and from there, select the 3rd option from the bottom and select the first option you see that has 'SD' written on it.
This will back up your current ROM to your microsd along with the stock recovery, I think
Please reset your phone before you backup
And reset your phone after restore
Now you can try flashing this CWM and see what else you can figure out.
Please post your findings.
If nobody would share, we would all be dumb and mentally handicapped
Seems to me this is CWM 6
Many more options I see which I can't figure out just by guessing
These are newly introduced or what, even I have no Idea.
Well hope somebody now can develop a ROM for our phones
CWM6 has incremental backups, no more system.img
As far as I can say
On the main menu
- reboot
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
My phone's performance is really good, no force close or anything, but my phone is just a rebranded Lava XOLO A500, but I think the ROM is still the same, because inside the phone, I can still signs of XOLO A500, so I'd like to help
EDIT:
Thanks for the partition info! I'll try and help you make CWM for our phone
Are you talking about the Cherry Mobile Burst.
If your ROM is stable, can you use the CWM I posted in here and take a backup and upload it.
I'd like to try.
For partitions unpack stock recovery and find the file recovery.fstab and if you also have like the A500 a recovery_mmc.fstab. This is where the real partition Table is, But its missing the emmc partition. EMMC partition in the A500 is mmcblk0p18
kank_fraud said:
Are you talking about the Cherry Mobile Burst.
If your ROM is stable, can you use the CWM I posted in here and take a backup and upload it.
I'd like to try.
For partitions unpack stock recovery and find the file recovery.fstab and if you also have like the A500 a recovery_mmc.fstab. This is where the real partition Table is, But its missing the emmc partition. EMMC partition in the A500 is mmcblk0p18
Click to expand...
Click to collapse
I flashed this CWM and it works.. I even have my nandroid back up.. now I'm looking for custom rom for xolo a500/cherry mobile burst..
hit thanks!
If anybody want a CWM flashable stock ROM the download this and flash away
http://www.mediafire.com/?u1oxl5suz7tsuz2
Perform a factory reset if you desire
Download this CWM http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
Its chinese so becareful while pushing the buttons.
Its rooted but install superuser from Play Store and update su binary
Has a few build.prop tweaks otherwise a full stock
Break a Leg!!!
kank_fraud said:
If anybody want a CWM flashable stock ROM the download this and flash away
http://www.mediafire.com/?u1oxl5suz7tsuz2
Perform a factory reset if you desire
Download this CWM http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
Its chinese so becareful while pushing the buttons.
Its rooted but install superuser from Play Store and update su binary
Has a few build.prop tweaks otherwise a full stock
Break a Leg!!!
Click to expand...
Click to collapse
hey man!! I need your help.. I tried to make my own splash image using terminal emulator and I ended messing up my /dev/block/
now, my phone doesnt have wifi, the icon is gone. my phone cant detect my sim card, and the signal icon is gone..
is there a way to restore this?? please help!! thanks!!
If you have installed cwm. Then just restore your backups if you have other just download a stock rom for your android phone and simply flash it
Nyk Sharma
Can someone help me build twrp recovery for HTC desire 620 dual sim.
Brand: htc
Model: desire 620 dual sim
Root: no
Able to flash img:yes
S-off:no
Recovery:stock
Hey. I tried this swapper2 app from the market and this little thing formated some partition from my phone thinking it was the swap one. Now phone won't go pass the samsung logo with sound.
I can get into recovery and into download mode. I tried flashing a brand new pcodin EMB5 flash, with no .pit nor repartition. No go. Rooted with CF-root (which also gives me CWM recovery). Recovery gives me the error: can't mount /efs so i'm guessing my /efs got formated. I have a backup made by copying the /efs files to another folder when all was working. What i'm guessing needs to be done is get my /efs partition created again (or at least mounted, not sure it's state) so i can copy it's contents there again.
What's the best way of doing this? I've seen people saying they can just use adb, mount /efs with the commands:
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
and copy it's contents. But i need my phone to boot first to use adb, right? Doesn't seem to be working from recovery or download mode.
Would reflashing with odin using the pit file, repartition option or even the Clear ESF option work? I'm not very clear about what "clear efs" does.
Any other ideas?
Thanks!
EDIT:
I've managed to solve my problem, phone's up and running again. I'll post the entire process later for anyone else, god knows i'd have loved to see this written somewhere instead of all the inconclusive bits and pieces scavenged around the internet.
Update:
On recovery (CWM) /efs is the only partition it can't mount.Log says
"w:failed to mount /dev/block/mmcblk0p3 (invalid argument)
Error mounting /efs"
From what i understand, mmcblk0p3 is the /efs partition. Would restoring an image of mmcblk0p3 work? I have my /efs contents but not an image of it. Would it be possible to get an image from some other phone, restore it on mine and just replace it's contents later?
If so, would anyone be so kind to send me one image of mmcblk0p3 for the gt-i9000?
Thank you.
adb works from recovery.
no, no one will send you their efs folder
Yes, i managed to get adb working with recovery. i figured as much. to be honest, but i though if someone had an image from a broken phone or simply wouldn't mind sharing, it wouldn't hurt to ask since i've seen them around for other phones before. I couldn't care less about other phone's contents, just want to replace them with mine.
I will try to recreate this partition via adb with fdisk or something. Can anyone share the details of the mmcblk0p3, like size, blocks, etc?
Any other ideas are also appreciated.
efs contains fragile data, like the IMEI. Having it, it is relatively easy to unblock the phone locked as the result of stolen one claim.
I doubt if someone would share this content, first. Second, any effort related with IMEI cloning is not welcomed here.
spamtrash said:
efs contains fragile data, like the IMEI. Having it, it is relatively easy to unblock the phone locked as the result of stolen one claim.
I doubt if someone would share this content, first. Second, any effort related with IMEI cloning is not welcomed here.
Click to expand...
Click to collapse
I'm well aware and not trying to clone anything. But I'll change my request then: think it's possible for someone to extract the efs image, mount it elsewhere (in linux or something, should be an ext4, right?) delete it's files, save and send it to me? The partition structure should still be there (which is what i want) but no delicate files for me to use. I can then restore it to my phone, hopefully mount it manually in adb and copy my /efs contents.
Think this would work?
Thank you
Hy !
i am beginner in rom cooking. I compile with succes Android from Google and ran good in emulator. After that i try to compile Cyanogenmod for my smartphone (jfltexx - Galaxy S4).
Compile with no problems so i try to understand how i can flash my phone and i found Archikitchen.
After somes trys (at the first time i don't understand what is /dev/block/ and where find /boot), finally i have my zip.
Of course, i flash it and it's no working (obviously it would be not funny isn't it ?). My phone start on kernel, display Galaxy S4 logo, after few seconds reboot on recovery mode.
I made a second zip after compile again (make clean, repo sync, source build/envsetup breakfast jfltexx, make -j8) and not working again (compile good but problem with my second zip).
At this point i want to understand how it is works. use Archikitchen is easy but i don't understand process to make a zip. In my folder (~/cyanogen/out/target/product/jfltexx/), i have :
- boot.img
- kernel
- ramdisk.img
-ramdisk-recovery.img
- recovery.img
- system.img
- userdata.img
I don't know exactly how android boots but i know it looks kernel and ramdisk in /boot and after it mounts /system and /data.
I use dd to flash my new recovery from phylz touch to TWRP and i want to do the same thing with my files (system.img to /system, userdata.img /data etc ...) but i think it's not a good idea because i don't know how use boot.img and ramdisk.img to make /boot.
So many questions for a noob, apologize if they are already a thread for all, i didn't found it.
Thx a lot.