[HELP]Need Persist partition dump - Moto Z Questions & Answers

Hi, is there anyone there that can dump their persist partition and provide me the link. I accidentally deleted the persist file on root explorer and now I'm always getting an error /persist invalid argument on recovery. Your help will really means a world to me. Thanks

Related

CWM Restore: "/system" error

While trying to restore an old backup of stock 2.3.6 on my Atrix 4g (ATT) from Jokersax CM9, I recieved an error while restoring "/system". This is what showed up:
Rom Manager version 5.0.0.7
August 22, 2012
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM Manager to report the issue.
A bit of background...So, I rooted and unlocked the bootloader of my Atrix 4g about two weeks ago, and everything went fine. I then decided to flash Jokersax CM9 on my Atrix, so I backed up the stock 2.3.6 that I was on at that time. I then used CM9 for the next two weeks, but then decided I wanted to go back to stock, and I received the error. Btw, I used ROM Manager for backups and restore, and had flashed CWM recovery properly. Also, the backups I had created of CM9 earlier wouldn't restore because of the missing MD5 file.
I was curious why it wouldn't restore properly. Is it just a bad backup or is something wrong with my internal sd card? Anyway, what should I do if I want to restore the backup?
Thanks in Advance!
Anything interesting or useful in /sdcard/clockworkmod/recovery.log?
No file
ravilov said:
Anything interesting or useful in /sdcard/clockworkmod/recovery.log?
Click to expand...
Click to collapse
Actually if I go into /sdcard/clockworkmod, I can't find the recovery.log file. It might have been moved but I don't recall ever messing with the files.
Md5sum miss match possibly?
Sent from my MB860 using xda premium
Md5sum mismatch
stevendeb25 said:
Md5sum miss match possibly?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
If it was Md5sum mismatch, how would I fix it?
Actually I didn't rename the backup and it has no spaces, so I don't know what it would be...
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
ravilov said:
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
Click to expand...
Click to collapse
I'll definitely try that, I'm not gonna have a chance to do it soon though. I'll get back to you as soon as I do.
Thanks for all the answers anyway!
Did this work? I have had a similar issue with my Atrix, too. I can do an "Advanced Restore" and restore all partitions but /system.
Issue restoring stock rom backup
I loaded epritner's CM10 rom and am getting the same error when attempting to restore the backup of the stock rom. Reviewing the report.log i see that there is a space issue writing to the \system partition but dont know how to proceed. Any help would be appreciated. Attached is the log output...
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.11 (14-Mar-2010)
Setting current mount count to 1
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: 11/81920 files (0.0% non-contiguous), 20632/327680 blocks
deleted
nvmm_sorensondec.axf
deleted
Protips.apk
deleted
CarDock.odex
deleted
GoogleServicesFramework.odex
deleted
Glam_alert.ogg
deleted
libopencore_player.so
deleted
tar: write error: No space left on device
defaults.xml
deleted
Error while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Atrix4g", "boot", "system", "data", "cache", "sd-ext")
in2slack said:
I loaded epritner's CM10 rom and am getting the same error when attempting to restore the backup of the stock rom. Reviewing the report.log i see that there is a space issue writing to the \system partition but dont know how to proceed. Any help would be appreciated. Attached is the log output...
Click to expand...
Click to collapse
in2slack, did you try these steps from ravilov? If so, did you get an error?
ravilov said:
According to your log, there is nothing wrong with your backup, or else the "Checking MD5 sums" part would have caught it.
There is also no way of a MD5 sum mismatch, for the same reason.
The only thing I can think of is there's something wrong with copying the backup to the phone (specifically, the /system partition). You can hook the phone to the computer right after you try restoring the backup and run adb shell, then run this:
Code:
cat /cache/recovery/log
cat /cache/recovery/last_log
See if that has something revealing.
Or, maybe the recovery has some problems wiping your /system for some reason. In that case, you can also try this (also within adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=512 count=1000
That will wipe the beginning of the /system partition, so the recovery will be forced to format it. Use this at your own risk.
Then after that try restoring your backup again.
Click to expand...
Click to collapse
Were you able to find a solution? I'm facing the exact same issue
Same here I installed the AtrICS ROM for a play around after backing up my MIUI ROM. Decided to go back to the MIUI ROM and I get the error when trying to restore. I've got a load of application data that I've lost if I can't get this ROM restored. It seems that the AtrICS ROM, as good as it is, has changed something.
Any thoughts anyone? It seems to be a file system thing? As if the System partion is the wrong type, or not large enough?
I went back from atrICS to epinter by backup today. I had no problems what so ever so it is not an atrICS related issue, my steps were:
1. format /cache
2. format /data
3. format /system
4. format /dalvik-cache
5. recover epinter
have you tried to use format system before recovery? maybe there is some residual file that can't be overwritten...
Thanks for your reply.
I did try formatting System before restoring and still got the same error when restoring.
However, I ignored it and rebooted and I was back at MIUI and able to recover my files
I've the exact same problem.
In the /cache/recovery/last_log, I've found a message:
write error: No space left on device
Click to expand...
Click to collapse
I don't understand why there is no space left on /system... the size of partitions should not change, isn't it?
After checking /system partition size and system backup, I saw that the backup completely fills the partition:
[email protected]:/ # df
Filesystem Size Used Free Blksize
[...]
/system 309M 309M 3K 1024
[...]
Click to expand...
Click to collapse
I faced the same issue
I faced the same issue and would request experienced users to take a look at my log file and advise me
Okay did anyone try anything of this I faces same problem and idk what to do.
Solved - Non conventional method
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
danilocps87 said:
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
Click to expand...
Click to collapse
Sorry to ressurect the topic, but I can't restore even /system and /data.. gives me error, and MD5 is fine.
Backing up .android_secure...
.
com.trust5.odp-1.asec
com.quoord.tapatalkxda.activity-1.a
com.loudtalks-1.asec
com.whatsapp.wallpaper-1.asec
com.music.download-1.asec
com.facebook.orca-1.asec
me.pou.app-2.asec
com.kiloo.subwaysurf-2.asec
com.davidamado.MetalGearOuterHeaven
Backing up cache...
.
lost+found
dalvik-cache
recovery
last_log
log
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
chmod: /sdcard/clockworkmod/blobs/02c/§☻‼/♀~|♫: No such file or directory
chmod: /sdcard/clockworkmod/blobs/235/∟/☺>☼>♣~: No such file or directory
Backup complete!
Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
system.ext4.dup: OK
.android_secure.vfat.dup: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-06-30.03.16.22//data.ex
t4.dup
Restoring data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Unable to copy file ./backup/processed
data
user
0
idd
etc
bluetooth_bdaddr
wlan_macaddr
light_themes
GNB_DEBUG.txt
backup
processed
Error while restoring /data!
Click to expand...
Click to collapse
Can someone answer that? Thank you!!
I have the same issue
danilocps87 said:
I solved this problem using a non conventional method.
I used "advanced restore" to restore boot, data and cache.
So, I copied "system.ext3.tar" to my computer and extract it using winrar. Then, using the files I created a flashble zip and flash it using "install zip" option.
It worked!
If someone wants, I could post a tutorial here later.
Click to expand...
Click to collapse
Can you please post a tutorial? I am experiencing the same issue.
Edit : I've searched the whole internet and some say that i can't restore the system because my cwm backup of the stock system is to large (315 MB to be precise) while the system partition has 320 MB.It look like i need to have more free space, like 10-15MB .Any ideas on how i might to that?

CWM builder doesn't work. Help me to build one!!!

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

S3 won't boot after app gone wrong - need opinion plz

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

[Q] edit ubifs file image

I have mtk6572 type device which use ubifs
file system for ROM flashing.. I am having its
stock ROM which is having system image in
ubifs format. I want to edit it . tried kitchen it
tries to convert to ext4 partition but explorefs
doesn't open saying 'could not find valid
super block '. also tried mount process in
Linux but to no success. can anyone help me
to edit ubifs file image and after that to
repack it.
thanks.

Failed to mount '/cpefs' (Read-only file system)

Hi guys.
I get this message in TWRP:
Failed to mount '/cpefs' (Read-only file system)
Does it mean something bad!?
Thanks guys.
Largewoodenspoon said:
Hi guys.
I get this message in TWRP:
Failed to mount '/cpefs' (Read-only file system)
Does it mean something bad!?
Thanks guys.
Click to expand...
Click to collapse
Same me
Sent from my SM-G965F using Tapatalk
what is your s9+ version?, it appear in twrp?
I have the same Problem with S9 plus G965F.
It boots permanent in Samsung Logo repeated.
even can not flash stock Firmware via Odin in download modus.
Can anyone help me please?
Flash latest twrp 3.2.1-2. This mesage "Failed to mount '/cpefs' (Read-only file system)" is gone.
Doesn't cause any issue, but updating to 3.2.1-2 fixes it as well as slow restore from backup as seen by the changelog on XDA
i have updated mine to 3.2.3-1 but it doesnt fix the problem, i tried following a couple of guides in youtube like changing the file system from ext4 to ext2 but still no luck, it didnt even let me change the file system for Data
i was on Android P when i tried that, but right now i just went back to full stock P without TWRP because i'm stuck with formatting Data (the most important part to clear out the restriction)
Any solution? i'm facing same.

Categories

Resources