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
Related
I am quite new to android development, but definitely interested in learning. I found dsixda's kitchen thread and wanted to try my hand at "building" a stock rooted rom for the Samsung Galaxy Axiom on US Cellular. USCC is a small carrier, and the Axiom, while capable, will probabaly not see much developer support.
Anyways, I downloaded and set-up all the files and got the kitchen up and running. The Axiom is not supported by the kitchen, so I tried following the instructions to add a device. I *think* I got it right, but I wanted to make absolutely sure before I flashed the rom, and potentially bricked my wife's new phone. I was hoping someone could look at the new file I made to go into the "edify_defs" folder.
Here's the data from the stock rom's recovery.fstab file:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p14
/data ext4 /dev/block/mmcblk0p15 length=-16384
/cache ext4 /dev/block/mmcblk0p17
/recovery emmc /dev/block/mmcblk0p18
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/mmcblk0p11
/modem emmc /dev/block/mmcblk0p1
Click to expand...
Click to collapse
Here is the file I created using the template:
# US Cellular Samsung Galaxy Axiom SCH-R830
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p14
cache_mnt=\/dev\/block\/mmcblk0p17
boot_mnt=\/dev\/block\/mmcblk0p7
data_mnt=\/dev\/block\/mmcblk0p15
sdcard_mnt=\/dev\/block\/mmcblk1p1
fix_boot2=yes
Click to expand...
Click to collapse
Thanks,
Mike
re read your file
woodardhsd said:
I am quite new to android development, but definitely interested in learning. I found dsixda's kitchen thread and wanted to try my hand at "building" a stock rooted rom for the Samsung Galaxy Axiom on US Cellular. USCC is a small carrier, and the Axiom, while capable, will probabaly not see much developer support.
Anyways, I downloaded and set-up all the files and got the kitchen up and running. The Axiom is not supported by the kitchen, so I tried following the instructions to add a device. I *think* I got it right, but I wanted to make absolutely sure before I flashed the rom, and potentially bricked my wife's new phone. I was hoping someone could look at the new file I made to go into the "edify_defs" folder.
Here's the data from the stock rom's recovery.fstab file:
Here is the file I created using the template:
Thanks,
Mike
Click to expand...
Click to collapse
im new to this dev rom thing to but i would like to point out in the template it states # Set this mount point for the modem.bin in Samsung devices like the Galaxy S2 and apparently you are using a samsung device and in your original statement of file it stated MODEM at the bottom so wouldn't there need to be a place in regards to your modem such as modem_mnt=....... ( .... <<being the \/dev\/block\/ etc etc
woodardhsd said:
I am quite new to android development, but definitely interested in learning. I found dsixda's kitchen thread and wanted to try my hand at "building" a stock rooted rom for the Samsung Galaxy Axiom on US Cellular. USCC is a small carrier, and the Axiom, while capable, will probabaly not see much developer support.
Anyways, I downloaded and set-up all the files and got the kitchen up and running. The Axiom is not supported by the kitchen, so I tried following the instructions to add a device. I *think* I got it right, but I wanted to make absolutely sure before I flashed the rom, and potentially bricked my wife's new phone. I was hoping someone could look at the new file I made to go into the "edify_defs" folder.
Here's the data from the stock rom's recovery.fstab file:
Here is the file I created using the template:
Thanks,
Mike
Click to expand...
Click to collapse
If you're only making a stock rooted ROM, why not use the original file? Rooting doesn't change your mount points.
Sent from my SPH-D710 using xda premium
I posted this question in several threads and I got no answer, so once again, can someone post here a boot.img from stock rom, base 1.18, or a boot.img from nand backup of the same rom. I''m interested only for boot.img from STOCK rom, not from custom rom that can be obtained here on forum?
If someone has factory rom on his/her phone and he installed custom recovery and rooted it, please make a nand backup and post me boot.img from backup.
Thanks in advance.
So, nobody willing to help?
I'm sorry man, don't know how I could get it, I already flashed sense revo R3 :l
Sent from my awesome fridge
Thank's anyway.
However you can help me in another way. First a question, can you remove apps from system partition without reappearing after reboot? Then, did you flash boot.img separately from fastboot or you just flashed the rom.zip? And when you give me the answers, can you post me a file located on the system root of phone (the same location where system, data, sdcard and the rest of the stuff is mounted) called default.prop?
nlooooo said:
I posted this question in several threads and I got no answer, so once again, can someone post here a boot.img from stock rom, base 1.18, or a boot.img from nand backup of the same rom. I''m interested only for boot.img from STOCK rom, not from custom rom that can be obtained here on forum?
If someone has factory rom on his/her phone and he installed custom recovery and rooted it, please make a nand backup and post me boot.img from backup.
Thanks in advance.
Click to expand...
Click to collapse
here u go bro. as requested, its stock rom base 1.18, customer recovery and rooted.
Yup, will do, but it'll take some time, just coming back from iceskating.
Sent from my awesome fridge
MaartenXDA said:
Yup, will do, but it'll take some time, just coming back from iceskating.
Sent from my awesome fridge
Click to expand...
Click to collapse
I think I'm getting somewhere, now I need your stuff to post me.
And I'm sure you've made a nand backup of your current rom so if you're willing post me your boot.img from the backup, not from the rom I already have it.
Don't have a backup
But the system app removal worked.
I'm on Sense Revolution R3, used aroma file manager 1.80 to remove the files, worked like a charm.
Sent from my awesome fridge
MaartenXDA said:
Don't have a backup
But the system app removal worked.
I'm on Sense Revolution R3, used aroma file manager 1.80 to remove the files, worked like a charm.
Sent from my awesome fridge
Click to expand...
Click to collapse
Aroma yes, but how about using Titanium Backup, wipe data first, then uninstall and reboot? The point is to do it when phone booted.
And I need that default.prop, please.
nlooooo said:
Aroma yes, but how about using Titanium Backup, wipe data first, then uninstall and reboot? The point is to do it when phone booted.
And I need that default.prop, please.
Click to expand...
Click to collapse
Here it is, sorry had to use .zip, .prop is invalid
No doesn't work with titanium and delete data.
Then it's not a problem with secure kernel, cause you boot with unsecure, this is from your default.prop
ro.secure=0
Click to expand...
Click to collapse
so this means that you successfully flashed boot.img when you flasher rom. Have you ever flashed it separetely, I mean when you installed previous versions of rom?
And one more question which SU app do you have Superuser on SuperSU?
nlooooo said:
Then it's not a problem with secure kernel, cause you boot with unsecure, this is from your default.prop
so this means that you successfully flashed boot.img when you flasher rom. Have you ever flashed it separetely, I mean when you installed previous versions of rom?
And one more question which SU app do you have Superuser on SuperSU?
Click to expand...
Click to collapse
Yeah, I flashed the one with R1 or R2, to fix the WiFi bug.
MaartenXDA said:
Yeah, I flashed the one with R1 or R2, to fix the WiFi bug.
Click to expand...
Click to collapse
So definitely, boot.img flashing via recovery is mandatory to get it all working.
Apps uninstalling still looks kinda weird to me. You didn't tell me about SU app.
@nlooooo
Do you still want the boot.img that not yet go thru android kitchen ?
I have one that in CWM backup.
ckpv5 said:
@nlooooo
Do you still want the boot.img that not yet go thru android kitchen ?
I have one that in CWM backup.
Click to expand...
Click to collapse
Thanks but I've already got it, I unpacked it to see default.prop settings, but it all seems that uninstalling of system apps doesn't depend on the way how kernel boots, even if it boots as unsecure apps still can't be uninstalled.
However I confirmed my claims that boot.img can't be flashed installing rom, only via fastboot.
Yep.. correct.
What I notice is the system/app folder's permission is rwxr-xr-x instead of the normal rwxrwxrwx and I can't find where the permission is set.
ckpv5 said:
Yep.. correct.
What I notice is the system/app folder's permission is rwxr-xr-x instead of the normal rwxrwxrwx and I can't find where the permission is set.
Click to expand...
Click to collapse
Maybe it's set here in ramdisk in int.protou.rc
on emmc
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
devwait [email protected]
mount ext4 [email protected] /system ro barrier=1
devwait [email protected]
# exec /system/bin/e2fsck -p [email protected]
mount ext4 [email protected] /data nosuid nodev barrier=1 noauto_da_alloc
mount ext4 [email protected] /cache nosuid nodev barrier=1
mount ext4 [email protected] /devlog nosuid nodev barrier=1
I'm not a programmer so I dont know, or maybe in init.rc.
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
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
I'm getting Segmentation fault, I guess there's some kinda hardware error on my phone. Gonna take it to Sammy's tomorrow.
Code:
mke2fs -F /dev/block/mmcblk0p11
Segmentation fault
sh-4.2#
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Will this work with a Galaxy S4? I545
Enea307 said:
Hi thnx for your Guide. I have the EFS problem, after installin 4 diferent rom in 2 hours my imei and baseband lost.( dont now why) i dont have a backup. I was thinking if it take the EFS from another S3 does it work?
Click to expand...
Click to collapse
No. Read General > Sticky roll-up thread > "IMEI / EFS - Know this stuff"
is normal this output? (i'm meaning the tar.gz unfinding file)
Code:
*****************************************
* BACKUP EFS *
*****************************************
WARNING: Do you wish to Continue? (This will make EFS BACKUP) [Y,N]?Y
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
761 KB/s (9357 bytes in 0.012s)
7 KB/s (39 bytes in 0.005s)
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_
Creating filesystem with parameters:
Size: 20971520
Block size: 4096
Blocks per group: 32768
Inodes per group: 1280
Inode size: 256
Journal blocks: 1024
Label:
FLEX_BG size: 0
Blocks: 5120
Block groups: 1
Reserved block group size: 0
Created filesystem with 59/1280 inodes and 2432/5120 blocks
40960+0 records in
40960+0 records out
20971520 bytes transferred in 7.271 secs (2884269 bytes/sec)
unknown option -- ZBusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-cal
l binary.
Usage: tar -[cxtzjahmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
2684 KB/s (9962352 bytes in 3.623s)
2805 KB/s (20971520 bytes in 7.299s)
remote object '/sdcard/SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz' does n
ot exist
7-Zip (A) 4.65 Copyright (c) 1999-2009 Igor Pavlov 2009-02-03
Scanning
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz: WARNING: Impossibile trovare
il file specificato. [COLOR=Red](impossible to find the specify file)[/COLOR]
Creating archive SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.zip
Compressing getprop.txt
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.raw.img
Compressing SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.md5
WARNINGS for files:
SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS.tar.gz : Impossibile trovare il file
specificato.[COLOR=Red] (impossible to find the specify file)[/COLOR]
----------------
WARNING: Cannot find 1 file
-
-
Finished. Output file is SM-N9000ZWEXXV_N900XXUCMJ3_RF1DA111EAY_EFS BACKUP
Premere un tasto per continuare . . .
well in the zip there are only the txt + md5 + .raw.img
Thanks for this great tutorial. It was my final step to recover my efs partition, without any backup. I copied the efs folder from another device and modified the files according my devices info (bluetooth mac, serial etc). Worked great on my SGS4
By the way I had the same error:
Code:
mke2fs /dev/block/mmcblk0p10
Segmentation fault
You get this error if you run adb shell when you booted to your ROM.
You need to run adb shell in recovery mode
Great tutorial but i hope you can help me, I can't seem to properly find the SDcard. When I type cp -r /externalsd/efs/* /efs
it comes back with cp: can't stat '/sdcard/efs*' : No such file or directory
I cleared my whole sdcard card except for efs directory. I also tried sdcard instead of externalsd but same thing.
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
hi..
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
I have successfully fix my efs partition follwing this thread.
you are receiving such message in cmd. I faced it too.
Sol: Use Philoz Recovery 5.0.
Fix permissions.
there you are.. done..
Philz 6.0 do not have an option for "fix permission".
hope it helps..
I wrote a script that attempts to recover your nv_data.bin from a corrupted EFS partition for the i9300. Thus if you don't have a backup and your EFS is corrupt, try the script. The script is still in Alpha phase and may not work for other devices. Feedback would be much appreciated.
You can find the script at: https://github.com/chriscz/efs_recover
I dont have /efs backed up
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
vamshipulumati said:
Hi ,
If i dont have /efs backed up , can I copy any other mobile (same model) efs data to my mobile and try?
Thanks and Regards
Vamshi Pulumati
Click to expand...
Click to collapse
No, it won't work and trying to clone another imei is illegal.
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
How to register for a new IMEI ? Is it possible?? Could you please help me with any site or link?? I don't want to replace motherboard..
Any help are highly appreciated.
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
boomboomer said:
No, it isn't possible and discussion about changing imei is banned on xda.
Take your phone to a service centre and pay then to recode it for you, make sure it works on 4.3 before you pay.
Click to expand...
Click to collapse
Hey I would like to tell you that a miracle happened for my S3. Yesterday i tried to do same as per in this guide. After taking backup of broken efs backup i tried to clear the efs folder with this command "mk2fs /dev/block/mmcblk0p3"
After that i just flashed 4.4.4 based stock ROM and somehow phone booted up perfectly. No network issues. Bluetooth wifi sim card everything works. IMEI & Serial No is there. But when i'm checking network unlock status it is showing as everything locked. But still I can use everything... I'm amazed.!!!!
Do you have any idea how this happened??
@boomboomer
Same problem with a Samsung gt-i9070 - Galaxy S Advance
Hi!
My i9070 has the same problem, but when i run the command: "mke2fs /dev/block/mmcblk0p3" shows the "Segmentation fault" error message.
Some one can help?
Thanks.
Bro U stated to format but How to format /efs partition
/efs not backed up
boomboomer said:
No, it won't work and trying to clone another imei is illegal.
Click to expand...
Click to collapse
I Dont have efs backed up and I also have formatted efs partition from adb shell and using that Dev type commands now i am in factory mode and my network is not working please give me any solution.
kaynpayn said:
I'm just writting this because i've recently had this problem. I managed to sort it out by my own but didn't really find it written anywhere, just bits and pieces scavenged from so many pages that might point to a solution (granted, part of my problem was also finding what was really my problem since the phone stopped working so fast i didn't really had the time to get what happened)
I was trying out swap for my S3, i had created a swap partition in my external card and then followed a guide here from xda to use an app called swapper2 (from market) to enable swap. I must have done something wrong because what it did was format my /efs partition instead as if it was a swap partition. Phone stopped working on the spot, obviously, and wouldn't past samsung's bootscreen.
Also, keep in mind while this worked for me there might be other ways of doing this which may be simpler. This is just what i figured for a solution.
When this helps:
- you accidentally formated your /efs partition
- you have a backup from your /efs partition, files copied with root explorer but not an image you can just flash back to the partition.
- your phone boots to download and to recovery but not to main system (which every tutorial i found seemed to assume to be able to do, i just figured their /efs was not as screwed as mine was)
- your recovery won't mount the /efs partition because it expects it to be ext4 but it's formated to something else and it showing the message:
"e: failed to mount /efs (Invalid argument)"
What doesn't work:
- any kind of standard solution like reflashing a stock rom with odin, with or without .pit file, clear EFS, whatever. It will flash, just won't solve since, apparently, nothing touches the /efs partition because it's so sensible. Even custom recoveries do mount it and apparently format and replace every single other partition but the /efs, which is why i had to do it manually.
Solution:
- simply format the /efs partition back to ext4 and copy your backup files there
What's needed:
- phone drivers installed on the computer. If you had kies installed, this should be covered already. Think you can't have it running while doing this though. Also, for what's worth, i've done this with windows 8 x64.
- updated android sdk tool, mainly adb. If adb is saying device not connected or not found, you may be using an outdated adb.exe (i was). I used adb.exe that came with this software here:
http://forum.xda-developers.com/showthread.php?t=1308546
- root. If your rom isn't rooted you can always flash CF-root from odin in download mode.
http://forum.xda-developers.com/showthread.php?t=1695238
- busybox, am not really sure if i actually got to need this, think so for the formating tool. Can't hurt to have more options though. This is how to install:
http://www.omappedia.com/wiki/Android_Installing_Busybox_Command_Line_Tools
- custom recovery that allows root through adb, i used Philz which is pretty awesome
http://forum.xda-developers.com/showthread.php?t=2002953
- backup files from your /efs. I had mine unzipped and copied to my externalsd while in windows. They were in an efs folder in the sd card. You can push this through adb to the phone later, but i found this way simpler.
How to:
- get into recovery (vol up+home+power button) and plug your phone to the computer. You'll hear an usb connected sound from windows after a bit.
- in recovery, navigate to Mounts and try the "mount /efs". It'll fail. Now, navigate to advanced and "view log". You'll see below that the phone tried to mount a partition and failed, in my case, it had unsucessfully tried to mount /dev/block/mmcblk0p3 which is the partition /efs uses. Take note of this partition name.
- On windows, open a command line (type cmd on you start menu), navigate to where you have adb.exe and type:
adb shell
If all went well, command prompt has changed. You can now issue commands directly to your phone from terminal.
- type "su" to get root permissions. Your command line should change to something like [email protected] Before i had this working i needed to use "Fix permissions". It's an option in the recovery menus on the phone.
- this step is optional but i did it anyway. I created an image of the partition i was going to mess with. If anything went wrong i could always flash it back even if it was broken. By the way, this is what i should have done in the first place instead of just copying /efs files. Would have made the process so much simpler... also, do this if you ever get the phone back working again. Type:
dd if=/dev/block/mmcblk0p3 of=/externalsd/efs.img
The /externalsd/efs.img is just a place you can save stuff to, like your external sd card. You can check what's your mounting point for the card with the command "mount" and look for something relevant like "externalsd".
Also, you may want to copy that efs.img to somewhere else from your phone (like your computer) for safekeeping. Literally remove card from phone, put in computer and copy files there. Notice you may need to reboot phone to recovery if you remove your card so it detects and mounts your card again. Sure, you can also do that from the command line, but it's just easier to reboot the phone.
- Now, we'll format the partition to something your phone can mount (ext4) and is expecting. Be careful, by doing this, you're actually erasing what's left of your partition and replacing by something clean. Type:
mk2fs /dev/block/mmcblk0p3
If all went well, you should see some kind of small report about what was just done.
- To mount this we'll need a mounting point. Type:
mkdir /efs
this will create an /efs folder in root, if it doesn't exist already, and to mount, type:
mount -t ext4 /dev/block/mmcblk0p3 /efs
- if all went well, you now have access to the /efs folder and can copy you files back:
cp -r /externalsd/efs/* /efs
where externalsd was my external sd card mounted on my phone.
- Check if your /efs folder has it's contents properly
ls /efs
I had to reboot the phone to recovery once more at this point and use the "fix permissions" option again.
After this, my phone booted up normally again.
Click to expand...
Click to collapse
I have restored my s6 edge by following this method. The EFS partition name is "sda3" for s6 edge if anyone want to restore s6 edge. There is typo in command "mk2fs /dev/block/mmcblk0p3" it should be mke2fs i think.
After restoring EFS my phone recovered from boot loop. But the imei is still invalid. Do you know any method to repair imei for s6 edge?. Thank You
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
Blackwatch said:
I am getting stuck trying to fix this as I have a boot loop or corrupt /efs or something. I have tried to get my phone working by installing my ROM ( Omega v58 ) and also by trying to flash the latest stock 4.3 through Odin v3.09. I havent tried total stock 4.0.3 yet. No matter what I have done though I can't get past the boot logo ( or the walking Omega droid ). My phone just sits there and hangs
I have followed your steps and I have Philz ( 6.07.9.19 ) installed ( but not busybox unless it is sat there somehow from the Omega install ) but when i try to get adb shell running nothing happens or works..as you can see
What am i doing wrong? OR is my phone totally borked?
Click to expand...
Click to collapse
You don't have to run "su" command. "#" shows you already have root access.
Hi there!
Today I finally found how to make our codinas' kernels universal, i.e. allow to install kernel on whatever ROM and finally separate recovery from kernel. It's well known, bootloader decides what will be loaded - kernel or recovery. That probably may explain why AnyKernel installer(or other similar) doesn't work on codina, because we can't move recovery partition anywhere.
But there is also a little trick that allow us load recovery and boot.cpio from different partition - https://github.com/ChronoMonochrome/Chrono_Kernel/commit/df9094f1f12618ad9599da266792d6b2f8106170 - just an another approach
Don't worry, we won't touch bootloader at all.
As can be seen, /dev/block/mmcblk0p17 (kernel2 partition) will be used for storing recovery.cpio and boot.cpio. On stock that may not work (I don't know for what exactly uses Kernel2 partition, besides of manually restoring of kernel1 partition. I only know that is almost useless on custom ROMs, and we can use it as we want )
First do some preparations:
Download this kernel and needed recovery/boot scripts(4.4.x.cpio.zip, 4.4.x_f2fs.cpio.zip, etc... 4.4.x.cpio means that it support only ext4) from my google drive (folder ramdisks), unzip recovery (twrp or cwm) and rename to recovery.cpio, then move it to external SD card. Then do it with boot scripts that you've downloaded (e.g. 4.4.x_f2fs.cpio.zip - unzip and rename to boot.cpio)
Well, that all that needs for installation. Read following instruction very carefully, otherwise that may cause brick Keep in mind, all that you do at your own risk! I'm not responsible if you brick your phone!
Installation method:
1) reboot into recovery, plug your phone to your PC, enable adb:
Code:
adb shell
2) Format kernel2 partition to ext4 file system:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p17
Think twice before you hit 'enter' button - wrong command may cause hardbrick!
3) create /ramdisk folder and mount kernel2 partition
Code:
mkdir /ramdisk
mount -t ext4 /dev/block/mmcblk0p17 /ramdisk
move your recovery.cpio and boot.cpio to this folder, give 777 permissions:
Code:
chmod 777 /ramdisk/recovery.cpio
chmod 777 /ramdisk/boot.cpio
4) install downloaded kernel
Now you can change recovery via changing /ramdisk/recovery.cpio - just make a backup of this file, and then replace with one of another recoveries. If you want to install another ROM or change filesystem of partition then replace /ramdisk/boot.cpio with one of needed boot scripts. Don't forget to give 777 permission (probably 644 is enough, but I didn't test it) to both of these files.
This method tested and working on 4.4.x TC ROM + twrp recovery + kernel with full F2FS support.
Well, now it's time to create uncompressed kernel, that may slightly decrease the boot time
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
sorset said:
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Click to expand...
Click to collapse
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
Click to expand...
Click to collapse
Yes, you can roll back to usual kernels. it doesn't matter what written on kernel2 partition - real kernel or anything else...
ChronoMonochrome said:
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Click to expand...
Click to collapse
Ok, thanks , But why do you mount kernel2 partition inside of OS? As I understand boot.cpio is necessary before booting OS . And inside of OS is just an extra storage! (is that true?)
sorset said:
And inside of OS is just an extra storage! (is that true?)
Click to expand...
Click to collapse
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Ace 2 has 15 - 20 Partitions my Friend
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
And what ? We actually talking about kernel2 partition.
ChronoMonochrome said:
And what ? We actually talking about kernel2 partition.
Click to expand...
Click to collapse
sorry, i meant @sorset
ChronoMonochrome said:
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Click to expand...
Click to collapse
You are right , but I remember days that 1.44MB floppy disk was a large STORAGE and 16MB was HUGE
sry , I have another question , So can I remove its line from fstab to prevent mounting?
I'm confused
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
Yes,With counting internal storage , 17 exactly , but thats not the point , I'm afraid.
sorset said:
sry , I have another question , So can I remove its line from fstab to prevent mounting?
Click to expand...
Click to collapse
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
Click to expand...
Click to collapse
I don't get it rephrase please
ChronoMonochrome said:
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
I don't get it rephrase please
Click to expand...
Click to collapse
I didn't too
There is an Image named boot.img in kernel flashable zip archive that extracts into partition 15 (named kernel) as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image , and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
sorset said:
as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image
Click to expand...
Click to collapse
originally kernel + recovery
, and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
Click to expand...
Click to collapse
In my mod kernel(mmcblk0p15) and recovery (mmcblk0p17) are splitted.
Thank you. I see.
This is probably the best (and only?) way to rebuild the ramdisk without having to compile anything, which is an excellent base for my NoUMS patches
:good:
<remove>