Welcome everyone to my second thread (i'm not expert in threads ),
As usually, you may do it, but please consider you do it "at your own risk",
even if it doesn't brick your phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This thread is about repairing a broken RFS /system and /data partition.
As seen there i'm sure someone here had this problem on a Galaxy Young,
http://forum.xda-developers.com/showthread.php?p=11868531
I found a solution when i tought i have an empty userdata.img image (i formatted /data and made a cat /dev/stl11)
I tested if i may repair my broken RFS partition, which was broken by a Online Nandroid Backup (My CWM backups never broke /system)
I renamed userdata.img to system.img, i opened cygwin and made a .tar.md5 package, flashed it, YEAH!,
problem fixed without downloading 100MB of stock ROM package.
After that history, i finally created the "Unbricker" package, which rewrites /system and /data
(not cache, cache cannot be integrated in an Odin package)
I flashed it and re-formatted corectly using CWM /data and /cache, wiped and reinstalled my ROM.
Hope it will help you, the download link for : http://d-h.st/tnu :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks i got this but i didnt know how to repair i only knew that i can unbrick by odin.
sent from my GT-P1000 using XDA Premium
hamada3381 said:
Thanks i got this but i didnt know how to repair i only knew that i can unbrick by odin.
sent from my GT-P1000 using XDA Premium
Click to expand...
Click to collapse
Hi, i just discovered after your reply it sharps /system partition, i updated link for /data, you may if you used it flash stock ROM,
then restore your nandroid backup using a different version of ClockWorkMod than one by BroadcomCM (this CWM print error formatting /system etc.. hope it will get fixed :good
I'm making an aroma package, will be called 'sharped repair'
Related
So it has come to my attention that when you restore a firmware via nandroid backup It does not restore the default ext4 partition that you convert. I found this out today when I had hoped my constant flashing would lead to XXKPN not booting unless I used CFRoot when flashing from Cranium [XXKPH]. Only to find out the firmware booted . Now this got me in surprise only because default partition is rfs and not supposed to be able to boot if set partition format was ext4. All default Samsung firmwares come with rfs partition.
Code:
Note: Next time you flash to a new firmware and back, you are required to flash the ext4 script then restore your nandroid backup for that respective firmware.
Misledz said:
So it has come to my attention that when you restore a firmware via nandroid backup It does not restore the default ext4 partition that you convert. I found this out today when I had hoped my constant flashing would lead to XXKPN not booting unless I used CFRoot when flashing from Cranium [XXKPH]. Only to find out the firmware booted . Now this got me in surprise only because default partition is rfs and not supposed to be able to boot if set partition format was ext4. All default Samsung firmwares come with rfs partition.
Code:
Note: Next time you flash to a new firmware and back, you are required to flash the ext4 script then restore your nandroid backup for that respective firmware.
Click to expand...
Click to collapse
I thought everyone knows this Because
1. before converting to ext4 you make backup. And if it will restore filesystem you will never get ext4 (it will always put rfs from backup)
2. when you make backup you can see that it backups files, not partition.
Mods please Sticky this thread and lock it by Misledz's permission before the thread is noob killed
Tapashocked via my gt-I9003 with a random keyboard of my choice !
I think mod should murge this info in already available sticky thread. Making lot of thread sticky will not be a good idea.
vishal24387 said:
I think mod should murge this info in already available sticky thread. Making lot of thread sticky will not be a good idea.
Click to expand...
Click to collapse
I have to agree, although this is helpful information, having too many stickied threads could become a problem.
falex007 said:
I thought everyone knows this Because
1. before converting to ext4 you make backup. And if it will restore filesystem you will never get ext4 (it will always put rfs from backup)
2. when you make backup you can see that it backups files, not partition.
Click to expand...
Click to collapse
I too already know this by reading skin's original post on ext4.
Instructions were to make nandroid backup -> convert to ext4 -> restore backup -> reboot.
After that u will have ext4 partitions.
So after you anything restore from backup, u will still have ext4.
Yeah but this came as a surprise, I didn't expect that the file system gets overwritten. Some cases flashing to another firmware kicks you into a bootloop due to ext4 previously there, but there are times when the firmware boots which got me in wtf is happening kind of scenario.
When I used cranium or any custom ROM usually does Ext4 by default, but upon flashing XXKPN on top of it, it worked? Which isn't supposed to, So what I'm confused is, What is responsible for the rfs file format, the pit? or the firmware? , and does clearing cache partition reset to rfs?
Because flashing XXKPH->XXKPN->XXKPH without use of pit works and this is without CFRoot
Yes for what this pit file for ? Means for what partition.is it convert file system to rfs ?
I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
No it converted to rfs
Sent from my GT-I9003 using XDA App
Ok... What about I wipe date from cwm? Does that revert the partitions back to rfs as well?
I don't think by wiping your data cache u can revert back to rfs. you have to reflash for rfs.
e398rokr said:
I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
Click to expand...
Click to collapse
Wiping doesnot changes the partition format. When you flash a new firmware the partitions will be converted to rfs.
send from gt-i9003 using android keyboard
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Lucasred said:
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Click to expand...
Click to collapse
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
sirilpta said:
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
Click to expand...
Click to collapse
Could be the reason, but many guys at another forum did it and it worked perfect for them, i think the error could be in the flash of kph, so the whole process went bad
Lucasred, i had the same problem twice. But i had tried it with XXKPQ.
can i converted file system too ext4 on KPU
google translate
user_i9003 said:
can i converted file system too ext4 on KPU
google translate
Click to expand...
Click to collapse
Yes, I'm using it.
For the others: the restore of the nandroid backup after the conversion failed whenever I tried to convert the phone before deodexing it. Try to deodex first, and then convert.
What I found weird was that the error was "not enough space", but when I tried to restore the backup on rfs it worked, doing the same after the ext4 conversion gave the error. I don't know how you could convert the partitions in ext4 with an odexed rom, I didn't look for any solution, maybe if you don't want to deodex your rom you could try to remove some system apps or something like that before the nandroid backup, in order to get more space.
Hi all, I'm having a serious problem in my TF101 C10...
I cannot boot any OS (it get stuck into Android screen), but only into Recovery. When I try to wipe Factory Reset I get the following message:
Formatting /data...
Skipping erase of data/media.
Error removing /data/data/com.android.gallery3d/cache/156C764383426C78.bin!
Also I cannot Unmount the /data partition!!!
Can anybody help me?
Thanks in advance!
Can you update your recovery before trying to wipe ?
Unsure if that is possible, but if you can find a new recovery .zip, maybe you can flash it and then see if the wipe works
sandroaw said:
Hi all, I'm having a serious problem in my TF101 C10...
I cannot boot any OS (it get stuck into Android screen), but only into Recovery. When I try to wipe Factory Reset I get the following message:
Formatting /data...
Skipping erase of data/media.
Error removing /data/data/com.android.gallery3d/cache/156C764383426C78.bin!
Also I cannot Unmount the /data partition!!!
Can anybody help me?
Thanks in advance!
Click to expand...
Click to collapse
Push a different recovery using easy flasher... preferably TWRP...
Sent from my Transformer using xda app-developers app
udupa82 said:
Push a different recovery using easy flasher... preferably TWRP...
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
Thank you for the reply udupa82, I've already tried the TWRP and didn't solved it, the same problem....
sandroaw said:
Thank you for the reply udupa82, I've already tried the TWRP and didn't solved it, the same problem....
Click to expand...
Click to collapse
Did you out try formatting your internal memory ( wiping) using twrp...? Also reformat your micro SD using your computer and then copy just the ROM back on to it.... now in trap wipe everything and try installation of the ROM..
Sent from my Transformer using xda app-developers app
udupa82 said:
Did you out try formatting your internal memory ( wiping) using twrp...? Also reformat your micro SD using your computer and then copy just the ROM back on to it.... now in trap wipe everything and try installation of the ROM..
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
Yup, I tried to wipe using TWRP but I always get the error message of that file that cannot be deleted. I also tried the wiping option into coldboot but it doesn't helped either because the /data dir is not wiped...
I had the same problem what I did to resolve it was i formatted my internal storage via TWRP and tried to load the ROM and it booted fine.
http://forum.xda-developers.com/showthread.php?t=1245892 use super wipe script to completely reformat partitions
VITUSH said:
http://forum.xda-developers.com/showthread.php?t=1245892 use super wipe script to completely reformat partitions
Click to expand...
Click to collapse
Thank you VITUSH, it worked! I installed the ARHD 3.6 and is working fine!!
Thanks a lot!
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
Click to expand...
Click to collapse
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Are you using latest 2.8.6.0/2.8.6.1?
davebugyi said:
Are you using latest 2.8.6.0/2.8.6.1?
Click to expand...
Click to collapse
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
I am using 2.8.6.1 (latest version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
trionic said:
I am using 2.8.6.1 (last version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
Click to expand...
Click to collapse
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
real_pac said:
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
Click to expand...
Click to collapse
I installed again with TWRP Manager and everything works perfectly now (no error message). Thanks again
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
[...]
Click to expand...
Click to collapse
I faced this error once on twrp 2.8.6.1 a week ago. I wanted to restore my nandroid and the error repeatedly happened while restoring data-partition. I then booted the system and deleted some files from internal storage (which was about half full at the time the error occurred). Afterwards I rebooted to twrp and could successfully restore my complete nandroid. It's a bit shocking if you face this error when restoring a nandroid, because the restore process wipes the data partition first and then begins the restore.
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
That tip worked for me (i9192), I just install the last TWRP (I think this is not needed) and wipe /Data with ext4, wipe again to F2FS and restore, thank you.
I somehow lost the ability to MOUNT /DATA from inside TWRP. Do I need to format DATA to fix this ?? or maybe just re-flash the encryption breaker instead ? I would rather not lose all ...
Thanks for any help here !!
Thibor69 said:
I somehow lost the ability to MOUNT /DATA from inside TWRP. Do I need to format DATA to fix this ?? or maybe just re-flash the encryption breaker instead ? I would rather not lose all ...
Thanks for any help here !!
Click to expand...
Click to collapse
repair the file system, try exfat.
mine got the same thing too and I changed its format to exfat after that it got mounted and then I re-flashed the stock ROM via ODIN
after that my phone got into bootloops, at first I got scared like WTF but then I rebooted into the official recovery and through there I wiped data/factory reset and wiped the cache as well, after it everything went normal AF
though I lost my data stored in the internal partition (idk it had to wipe the app-data partition but instead it wiped every partition out and yeah my EFS didn't got affected at all but you should be careful)
Format.type yes. Then flash encryption breaker. U have to flash encryption breaker after flashing anything basically. U can change file system but u won't actually fix the issue and therefore never do nandroid backups
fullofhell said:
Format.type yes. Then flash encryption breaker. U have to flash encryption breaker after flashing anything basically. U can change file system but u won't actually fix the issue and therefore never do nandroid backups
Click to expand...
Click to collapse
What's this encryption breaker?
Can I too get this mystery file?
sosukeaizen said:
What's this encryption breaker?
Can I too get this mystery file?
Click to expand...
Click to collapse
Its also called boot image patch and its listed in the twrp postings
Virgin mobile Galaxy j727P
fullofhell said:
Its also called boot image patch and its listed in the twrp postings
Click to expand...
Click to collapse
It's also part of THE SR5 superSU 2.8.2 ZIP !