I have a problem, and I'm dealing with it since this saturday. I really need my phone this evening so I really want help. My phone has since saturday a bootloop with every rom. Today I found out that it could have something in common with a error in the recoveryscreen which says it can't mount /data. CWM and the stock recovery both have this problem. Can please anyone help me? I'm really confused, because I have tried everything.
//I've discovered that the problem is that the /data partition is crashed. Is is possible to recreate the internal partition table?
install a stock rom then re-install cwm 5.0.2.7
Msulviu said:
install a stock rom then re-install cwm 5.0.2.7
Click to expand...
Click to collapse
I have done that already a few times.
Try flashing an ext4 converter, or re dd'ing an empty RFS format partition into place.
Already done. When I try to use ext4formatter in CWM it doesn't give an error, but when I try to do the data reset I will get an error again because it can't mount (and unmount) /data.
//And how do you add a RFS partition on the phone? Or do you mean on the SD?
Factory reset?
Have you tried doing a factory reset with Kies?
be_born said:
Have you tried doing a factory reset with Kies?
Click to expand...
Click to collapse
Thank you for trying to help, but your answer is stupid. It's impossible to go to Kies without a (working) rom...
I think I just found something interesting to know. I tried again to install Cyanogenmod 7.2 (ported by Phiexz) and in the Aroma installer I looked at the System Info. Almost everything looks fine, but this is not good I think:
Data Size : -1MB
Free : -1MB
(/mnt/sdcard) : -1MB
Free : -1MB
Click to expand...
Click to collapse
Are those partitions crashed? And how do I resize or reformat them back?
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Or reflash back to the stock recovery and use that to format the partitions back to RFS.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Darkshado said:
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Click to expand...
Click to collapse
I did use Phiexz's first yes. But I can't install yours. And where do I have to use dd commands? :$
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Darkshado said:
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Click to expand...
Click to collapse
I did know how to install a zip, but I tried 2 times and I think both were a bad download. Now I'm installing your Ext4 Converter.
// YOUR EXT4 CONVERTER WORKED!!! After a week without a phone it finally worked! Thank you so much!
Glad to hear that!
I had a similar problem of being unable to mount /system after installing a CM9 beta (can't remember which) and ended up solving it like that.
Hey guys i have a question relating to this dscussion. I have my gio running CM9 and i recently used BML5 to find my phone's unlock code. I have a nandroid backup of Rooted stock ROM, and when i tried to flash back to it, it said "Could format dev/block/stl13". I have the CWM 5.0.2.7 with RFS and EXT4 support, so it should work. What is the problem?
That's the thing; the exact behavior of those RFS+ext4 CWM builds when changing from one type to the other hasn't been very well documented.
I'm not sure they can format back to RFS properly.
You could always try that empty RFS partition set and attempt a restore afterwards.
What can i do if dd says, that it can't open '/dev/block/stl13': Invalid argument? I placed the data.rfs to the root directory of sdcard. Am I doing something wrong?
Can't mount /data
Hello, I have a bricked phone, and no idea why, and so far I'm unable to fix it. I've been waiting for an RMA so I can send it back to GSM Nation to evaluate and hopefully fix. My problem started when Samsung support told me to do a factory reset of my Samsung Galaxy S3, and it rebooted, then said it could not find or mount /data or anything therein. I have Not, repeat NOT, rooted my phone, it had the stock Android 4.3 OS and updates from T-mobile. The tech at the Samsung Experience Shop in the Best Buy store could not reflash it, when Kies tries to talk to the phone in Side Load mode it freezes or something, nothing happens. I downloaded ODIN 3 on Dad's win XP laptop, and in ODIN download mode the computer sees it as a new device with no driver to make it talk to it, and the drivers I've downloaded simply will not install. The installers die as soon as they run having done nothing. I am using my Samsung Chromebook to write this and have no Linux machine to work with. I am at a loss. Can you help me? Maybe I could re-install android using a microSD card?
I have the solution for data partition crash or any other partition
please do it with your responsibility but your phone is alreay bricked so it doesn't matter
hi every one i 've been through this problem for a long time and just yesterday hamdo lilah i discovered the solution it is by repartitioning your partitions with a pit file . i tried this method with samsung galaxy fit and it works even the pit file is for samsung .all you have to do is open odin included in the package then select pit file included then click start and there you go 'even if it doesn't show PASS ' after that just flash a stock rom ' or maybe any rom ' and that's it you are ready to go . i uploded the package on gulfup cause i have no account in mediafire enjoy if you face any problem just contact me or add a replay
gulfup.com/?rP8hfs
Related
Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.
Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2
drixjp said:
Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.
Click to expand...
Click to collapse
Wrong section. Questions don't belong in the General Section. As for your problem, the best solution would be to just flash a stock ftf as mentioned by m1st3r1
m1st3r1 said:
Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app
drixjp said:
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot
m1st3r1 said:
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot
Click to expand...
Click to collapse
Like i said, it's a. 55 rooted with stock Rom. Boot loader unlock alowed: yes. I tryed every kind of fix in cwm already and nothing works.
Something I never tryed is via fastboot. How do I proceed with that?
Sorry, my android life just started yesterday, I don't have much knowledge
EDIT: Ok I solved. Actually it's not like a fix, it's just like putting a silver tape to handle the problem. For some reason I'm able to advance restore system backup via CWM recovery. Every time that I do that, my CWM recovery is fully functional again, i can install mod, rom, etc. But, when I reboot into system again, the problem comes back, but I can still use my android without any problems, I just can't install anything via CWM recovery. So basically, now, every time that I want to install something in recovery, first I need to advanced restore system, and than install the rom, mod or whatever. Than I backup again in case I want to install anything else in the future, to repeat the same procedure with the last backup.
I was just having some problems when I was trying to restore the system with a md5 missing error... something like that. I solved this problem by just creating a file.txt in the backup folder and than renamed it to nandroid.md5. Magically it was fixed.
Sent from my LT26ii using xda app-developers app
Hello lovely android people,
I am a newbie, so im guessing this probably isnt the right place to post this type of question. Please feel free to guide me to the right place.
So the question...
I rooted my galaxy ace2 (gt18160) and install Pimp My Rom app from the market. Did some changes with it and now the phone wont start up, stuck in the bootloop where the logo appears and it does not go anywhere from there.
Ive been researching for solution since yesterday, and found out that I could re-flash the firmware using o2 stock using odin.(although im not quite sure this is a correct solution)
Since there's a possibility of all the data getting deleted, I want to get some files out of the device using ADB pull.
I used adb shell to look for the files I need. At first I could see the sdcard in the root directory / but could not access it without su. After doing su command I can go inside the sdcard directory (where my files are), but it appears to be empty.
ls -l /mnt lists the sdcard with unusual d--------- permission.
Im stuck and dont know how I can grab my files from the sdcard folder.
any suggestion will help.:cyclops:
Thanks
mnt/sdcard is only a symlink to storage/sdcard0 (mount for the internal sdcard) so it does make sense that adb can't cope with that path.
Still, it is impossibibble to delete stuff from either of your sdcards via odin or recovery. Flashing via odin doesn't wipe the data partition either, so as ong as u select the right firmware for our phones, nothing can go wrong really
Thanks for your reply Carpe-Dimi.
after checking /prop.partiitons, it seems that sdcard hasnt been mounted.
The problem now is that there are 18 partitions and I dont know which is the sdcard?
I tried mounting the first mmcblk0. Give me the 'device or resource busy' error.
Excuse my arrogance but I would have liked to find out why I cant access the sdcard or why I cant mount the partitions.
...and thanks again for letting me know that flashing does not wipe the data. :good:
SOLVED!
As Dimi said, flashing does not wipe data partition. But I was able to recover my files in recovery mode as it automatically mounted the mmcblk0p8 partition.
Then installed stock firmware.... tried new jelly bean, then went back to stock as its slow and laggy.
Cheers
Hi guys,
Newbie to the forum and android just need a bit of help as im pretty stuck at the moment and i dont know whats gone wrong.
I wanted to install Jelly Bread v5.0 or something other that the restricted phone carrier os on my phone when i got it (i wont mention just incase) so heres what i did.
rooted the phone using an update.zip from on this forum somewhere.
installed: signed_cwm-5.0.2.7-flashablezip-ext4only.zip
then installed: Jelly Bread v5.0
was ok for a while and working but then i wanted to play with other ROMS (in this case i now wanted to try cm-10.1.4-GT-S5660-gio++.zip)
I enter recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, wipe batt stats
Then install cm-10.1.4-GT-S5660-gio++.zip
Then it hung for 35mins at loading blue circle screen.
I then took battery out and enter recovery, and attempt to wipe data/fatory reset and it says:
--Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/stl13
Formatting /Cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/ .android secure...
Data wipe complete
Also i cant wipe dalvik cache it just does nothing blinks 1 second then back to menu.
From here (silly me i forgot to backup) ive tried to flash a few stock roms but still getting boot loops and the same above errors.
Is there any way i can format and write /data and /sd-ext?
Anyone know what i can do to fix this please?
Thanks for any help in advance.
update
Hi guys,
Just an update.. have tried several stock ROMS via ODIN always flashing CWM and flashing custom ROMS but nothing with flash and reformat the /dev/stl13 block. im always getting this error and i believe its causing my boot loop issues.
I found this thread via google:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
is there anybody on here that could guide me through using ADB shell to rebuild/reformat the /dev/stl13 block?
I dont feel confident enough to do it. (Have already installed shell on my laptop though)
This is driving me crazy trying to fix. My first android ROM flash gone wrong
(i got it working fine with Jellybread but wanted to try something else)
Any help appreciated.
Cheers
Richie
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Darkshado said:
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
Click to expand...
Click to collapse
Hey dude,
Thanks for the reply.
I have tried flashing back to stock (latest from samfirmware) and it still wont let me mount data.
Although its giving me my orignial load screen (my carrier) but still boot loops.
Ive tried look for another stock ROM i can use but alot of the links are down/broke or withdrawn etc.
I note with stock recovery i just can't mount data but after i install CWM 5.0.2.7 ext4 only it cannot format ext to block stl13.
Could this possibly mean that my internal memory has failed or it just needs to be repartitioned?
Will continue to look for another stock rom that can hopefully fix the problem.
You don't care about the errors failing to mount in the stock recovery. It's expected since it isn't set to work with an ext4 partition.
Just run the format operations from the stock recovery.
Most "stock" ROMs released here were made to run on ext4 since performance was that much better and most CWMs built also run ext4, unless explicitly stated to run RFS.
I can't think of any tools to repartition the Gio, otherwise we would have been all over it back in the day to solve the /system space shortage.
Harakhti said:
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Click to expand...
Click to collapse
Do you suggest to flash stock via Odin?
And then correct me if im wrong but to get to CM10,1 i go in this order after a stock flash:
1. Install CWM 6.0.3.2
2. run ext formatter
3. install ROM (in this case CM10.1??
Cheers for any help in advance.
Im quite new to Android.. but not new to flashing etc (BIOS, PSP's other devices etc) but this is my first android phone and i didnt like the Phone Carrier custom ROM and network lock. So attempted to try something else. Got Jellybread running fine but decided to have a look around. And now im phone less (well not really using my old nokia n97) but it is sooo painful! lol
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Darkshado said:
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Click to expand...
Click to collapse
Sorry man i had not read your reply before my previous post.
As stated in my previous post, I have flashed 2 stock ROM's from samfirmware via Odin and it passes.
On one of the ROMS (an NZ ROM) it gives me the error: E:format_Volume: rfs format failed on /dev/stl13
On the other ROM (The Aus ROM) it gives me the error: Unable to mount /data
On both im getting boot loop.
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Darkshado said:
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Click to expand...
Click to collapse
It formats the /cache partitions just not the /data as it cant mount it.
Warranty service? I will have to pay? as i have bought the phone 2nd hand and i dont think its under warranty.
I did see the other post and have downloaded "Samsung GT-S5660M Galaxy Gio - RFS format data and cache partition images to dd back into place"
But i cannot find the post again with the directions. Also when pushing these images from the SD card am i meant to be in stock recovery or RFS CWM?
Cheers Darkshado for all the help so far.
I had the explanation right below that download link here and a more detailed one here.
hmm doesn't look good eh?
Darkshado said:
I had the explanation right below that download link here and a more detailed one here.
Click to expand...
Click to collapse
Could it possibly be a physical hardware failure?
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
you can install a rom after downloading and flashing ext4 formatter.zip
Darkshado said:
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
Click to expand...
Click to collapse
Have been extremely busy with other projects and work lately and haven't had net the past week (so painful!)
but otherwise latest results are attached. Can you make anything of it? Does this look normal?
Cheers again.
Richie
Looks normal at first glance, though I don't have a Gio to compare with.
You could try and dig into how these phones are partitioned exactly and go from there, but you'll probably be on your own since most people who were interested in early MSM7227 devices have moved on.
Unless the underlying memory is defective, it's possible your only option left at this point is to try a JTAG repair.
However, depending on how much you'd be charged for such an operation locally, and taking into consideration the value of your typical used Gio (I've seen them go for 50$CAD in local classifieds)... You're probably better off cutting your losses and getting another phone.
Good luck,
Darkshado
Sent from my SGH-T889V using xda app-developers app
Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
joloxx9joloxx9 said:
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
Click to expand...
Click to collapse
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Click to expand...
Click to collapse
Could you please tell me How can I fix IT?
joloxx9joloxx9 said:
Could you please tell me How can I fix IT?
Click to expand...
Click to collapse
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Click to expand...
Click to collapse
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
joloxx9joloxx9 said:
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
Click to expand...
Click to collapse
for future reference, there is a "Repair filesystem" option in twrp. It says it runs e2fsck, which works for ext4. It won't hurt an f2fs filesystem, but I don't think it will repair it either. I'm seriously considering switching my /data to ext4 just so I have proper recovery tools.
My OP3T does have fsck.f2fs on the system, which means you can fix your data by opening a Terminal session from TWRP and then running :
Code:
fsck.f2fs /dev/block/dm-0
should fix your data corruption should you see this error again. For ext4, you use e2fsck rather than fsck.f2fs. This is also what you would use on /system (which is /dev/block/sde20 on my phone) should that ever be mounted read/write and get corrupted (pretty low chance even if you do mount it read/write as writes are low frequency and ext4 has a rock solid journal).
WARNING: Device numbers are for my OP3T and may be different on other devices or even on non-US devices.