Related
I think a lot of people have this problem when use TWRP recovery wipe system.When flash system.img use mfastboot or RSD,fastboot tips "sp space is not enough"
I'm sorry my English is not very good.
But in fact,I don't know why this happens,In theory,TWRP recovery impossible to rewrite the SP partition,however,tragedy has occurred yet.
I found format this partition will not be error occurred.but it is not allowed formatted this partition on the fastboot mode,It tips you Permission denied.So,I used another method.
I created an empty partition fill with 0(I named sp-empty.img),and put it into the internal storage,then import it use adb shell.
Code:
Code:
adb shell
su
cat /sdcard/sp-empty.img > /dev/block/mmcblk0p26
Miracle happened,this error don't show again when I flashed the system.img again.
But I found a BUG,In the official recovery,I can't wipe cache partition,the phone will be forced restart!!!
It is not affect to OTA.I can wipe the data partition normally.
empty sp download:
http://forum.xda-developers.com/attachment.php?attachmentid=2868807&stc=1&d=1406222848
I'm hope who can tell me why really.thanks everyone.
Dusty tears said:
Miracle happened,this error don't show again when I flashed the system.img again.
But I found a BUG,In the official recovery,I can't wipe cache partition,the phone will be forced restart!!!
It is not affect to OTA.I can wipe the data partition normally.
Click to expand...
Click to collapse
Any news about "sp space is not enough" after TWRP wipe data/system?
Causes, consequences?
Maybe we should do a dump of /dev/block/mmcblk0p26 from stock firmware and flash it in this way?
..
Zorge.R said:
Any news about "sp space is not enough" after TWRP wipe data/system?
Causes, consequences?
Maybe we should do a dump of /dev/block/mmcblk0p26 from stock firmware and flash it in this way?
Click to expand...
Click to collapse
Maybe you should make a backup.
Thank you, Dusty Tears!
This solved my problem perfectly. I was getting the "sp space is not enough" error when flashing to system because I accidentally wiped it in TWRP. The instructions were a little unclear, so if bigger novices than me come across this, you must have root access and enter these commands with USB debugging enabled. These commands are used while running the OS, not in bootloader or recovery.
UltimatePG said:
Thank you, Dusty Tears!
This solved my problem perfectly. I was getting the "sp space is not enough" error when flashing to system because I accidentally wiped it in TWRP. The instructions were a little unclear, so if bigger novices than me come across this, you must have root access and enter these commands with USB debugging enabled. These commands are used while running the OS, not in bootloader or recovery.
Click to expand...
Click to collapse
So how do we do it from fastboot/bootloader? fastboot or mfastboot flash sp sp-empty.img??
stealtheye said:
So how do we do it from fastboot/bootloader? fastboot or mfastboot flash sp sp-empty.img??
Click to expand...
Click to collapse
I don't know. The problem didn't prevent me from flashing a rom, so it wasn't a big deal for me to do it through the OS.
I would like to know if this SP partition will remain empty or if after flashing system.img it will be rewrited? I'm a little concerned, because when people brick their motos for downgrading, among the error messages that appear in the bootloader there's this one: "No SP partition found".
deleted.
xt1052 sp space is not enough
please help me i do the mfastboot flash system system.img but there is a red words that tells "sp space is not enough", i do the instruction you gave about the adb shell, it tells /system/bin/sh: su: not found and about the cat /sdcard/sp-empty.img > /dev/block/mmcblk0p26 when i hit enter it said permission denied can you help me fix the "sp space is not enough", and also when im inside the TWRP i cannot wipe anything and TWRP cant read the internal storage. :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
I tried the repartition method manually and did all the steps carefully without doing it wrong everything was right until i tried to reboot i get a error node not found
i can reboot my phone to recovery and fastboot but whenever i try to flash a rom i get a error during the process saying failed to mount the system1 at system!
btw i have cwm r11
please help i need my phone to work again
quick help would be highly appreciated
thanks
guys should i use the mi flashtool and flash the fastboot stock rom ?
The miflash only works with the original partitions. Try to change the partitions to original and late try use the fast boot. If you cant acces to the storage, use adb to push your zip.
This tutorial can help you:
http://forum.xda-developers.com/showthread.php?t=1667929
thats the problem i cant flash any roms on the phone whenever i try to there is an error in the middle of the process saying cant mount system and mounting system error
and can i not use the miflash right away cause the main problem here is my system partition not working properly
thank you so much guys i solved the problem if anyone finds himself in this situation contact me through pm i would help you
Hi,
I know this is a strange requset.
Because my Nexus 6 is stuck at Google logo and can't boot into system or TWRP.
This is begin at when I try to flash 5.11 OTA(TWRP flashable) file.
After install without error, I have stuck at Google logo.
Then I notice that my system is rooted, noforce encrypt and use F2FS filesystem.
I gusee that the problem is new kernel didn't support F2FS, so I flashed Zen kernel with fastboot.
This step let me can boot in to system normally, but I still can't get into TWRP.
Because I want to fix TWRP, so I tried fastboot erase cache.(This is big mistake.....I should backup all file before try this command)
After fastboot erase cache, I still can't get into TWRP, and I lose system again.(Stuck at boot Animation)
I think it is cause by "fastboot erase cache" didn't create F2FS filesystem cache partition.
Does someone can help me that give me a F2FS filesystem cache partition img file?
I just want to get into system and backup all file.
Then do a full factory reset, hope this can bring back my TWRP.
chowtom said:
Hi,
I know this is a strange requset.
Because my Nexus 6 is stuck at Google logo and can't boot into system or TWRP.
This is begin at when I try to flash 5.11 OTA(TWRP flashable) file.
After install without error, I have stuck at Google logo.
Then I notice that my system is rooted, noforce encrypt and use F2FS filesystem.
I gusee that the problem is new kernel didn't support F2FS, so I flashed Zen kernel with fastboot.
This step let me can boot in to system normally, but I still can't get into TWRP.
Because I want to fix TWRP, so I tried fastboot erase cache.(This is big mistake.....I should backup all file before try this command)
After fastboot erase cache, I still can't get into TWRP, and I lose system again.(Stuck at boot Animation)
I think it is cause by "fastboot erase cache" didn't create F2FS filesystem cache partition.
Does someone can help me that give me a F2FS filesystem cache partition img file?
I just want to get into system and backup all file.
Then do a full factory reset, hope this can bring back my TWRP.
Click to expand...
Click to collapse
do fastboot format cache then fastboot format userdata. Then TWRP should work.
Thanks for quick reply,
That is what I want to do.
But it will wipe all my data, so I want to get into system and backup data before do fastboot format userdata.
danarama said:
do fastboot format cache then fastboot format userdata. Then TWRP should work.
Click to expand...
Click to collapse
chowtom said:
Thanks for quick reply,
That is what I want to do.
But it will wipe all my data, so I want to get into system and backup data before do fastboot format userdata.
Click to expand...
Click to collapse
Oh I see.
Have you tried adb access whilst bootloop?
Failing that, another option would be edit the ramdisk to change the /cache mount to ext4. I imagine the kernel you have has set it as f2fs
I'll happily format my cache as f2fs and take a nandroid of it to create a cache image, but im not sure if that would be fastboot flashable?
danarama said:
Oh I see.
Have you tried adb access whilst bootloop?
Failing that, another option would be edit the ramdisk to change the /cache mount to ext4. I imagine the kernel you have has set it as f2fs
I'll happily format my cache as f2fs and take a nandroid of it to create a cache image, but im not sure if that would be fastboot flashable?
Click to expand...
Click to collapse
Try it and I can know is flashable or not.
I have tried adb access, adb can connect my device, but can't access sdcard,
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
/system/bin/sh: cd: /storage/sdcard0: No such file or directory
chowtom said:
Try it and I can know is flashable or not.
I have tried adb access, adb can connect my device, but can't access sdcard,
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
/system/bin/sh: cd: /storage/sdcard0: No such file or directory
Click to expand...
Click to collapse
You can try /data/media/0 for sdcard
Nandroid isnt in .img format.
I've just dd'd a cache.img and fastboot flashed that. Lets see if it boots. If it does, I'll format it and dd it again.
Edit > Well it booted (though it is optimising now)...
I'll try and format and dd the image for you, though not sure it will work. Do I need a special version of TWRP to format F2FS?
danarama said:
You can try /data/media/0 for sdcard
Nandroid isnt in .img format.
I've just dd'd a cache.img and fastboot flashed that. Lets see if it boots. If it does, I'll format it and dd it again.
Edit > Well it booted (though it is optimising now)...
I'll try and format and dd the image for you, though not sure it will work. Do I need a special version of TWRP to format F2FS?
Click to expand...
Click to collapse
https://twitter.com/dhacker29/status/568070387306766336
This one can format F2FS, but I am not sure TWRP will check kernel support F2FS or not.
And I can't access /data/media via adb.
Code:
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd media
cd media
/system/bin/sh: cd: /data/media: Permission denied
chowtom said:
https://twitter.com/dhacker29/status/568070387306766336
This one can format F2FS, but I am not sure TWRP will check kernel support F2FS or not.
And I can't access /data/media via adb.
Code:
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd media
cd media
/system/bin/sh: cd: /data/media: Permission denied
Click to expand...
Click to collapse
Yeah I found that one eventually and it let me format.
Now I just need to find somewhere to upload a 256MB image
danarama said:
Yeah I found that one eventually and it let me format.
Now I just need to find somewhere to upload a 256MB image
Click to expand...
Click to collapse
MEGA or Google driver?
chowtom said:
MEGA or Google driver?
Click to expand...
Click to collapse
Dev-host.
---------- Post added at 10:40 AM ---------- Previous post was at 10:17 AM ----------
Had to go Mega in the end
Here you go:
https://mega.co.nz/#!UoF0RIpA!ew9AYAqn-C2vxxO8VMjXnp1jOM8eD6JqXdsrEyJimGM
Not sure it will work though.
danarama said:
Dev-host.
---------- Post added at 10:40 AM ---------- Previous post was at 10:17 AM ----------
Had to go Mega in the end
Here you go:
https://mega.co.nz/#!UoF0RIpA!ew9AYAqn-C2vxxO8VMjXnp1jOM8eD6JqXdsrEyJimGM
Not sure it will work though.
Click to expand...
Click to collapse
It works!!!
Huge thanks for your help.
Now I can start to backup my data.:laugh:
chowtom said:
It works!!!
Huge thanks for your help.
Now I can start to backup my data.:laugh:
Click to expand...
Click to collapse
wow, that was surprisingly easy.
Well dd copies at block level, so it *should* have worked, but I've never really tested it before.
Finally, I recover my data and didn't lost any one.
The step what I do is:
1. Use fastboot to flash cache img which provided by danarama.
2. Reboot to test, result is System ok and TWRP still fail.
3. Boot to system and backup all data with MTP.
4. Use fastboot erase userdata to factory reset my Nexus 6.
5. After step 4, I can get into TWRP. Redo the Convert to F2FS procedure.
6. Reboot to system and skip all initial SETUP. Copy all sdcard data to nexus 6 by MTP.
7. Back to TWRP, restore the data partition(F2FS) which backup a weekago.
8. Reboot to test, both System and TWRP boot correctlly.
There is a file on my xt1068 with path /data/data/com.google.chrome/app_webview/Cache/8f7f69bc88662934_0 .I am unable to delete this file through any method.It is not visible in es file explorer or any other file manager,i have tried deleting the folder but it fails even after providing root permissions.I have tried deleting it by wiping data partition via TWRP and CWM but both failed.I also tried deleting it using aroma file manager and TWRP's flile manager but no luck.Due to this file i can't create or restore nandroid backup.While installing any new ROM i need to go to the TWRP's file manager and i manually delete all the folder's except the one i mentioned above,to perform a clean install.I have also tried restoring to stock firmaware using fastboot but after installation of rom the file still remains there.
My TWRP always shows this message:"E:Unable to stat '/data/data/com.google.chrome/app_webview/Cache/8f7f69bc88662934_0'
Please help me with this.
I would also be interested in a solution as I have a similar / same problem.
If I try and delete it via an adb shell I get : "rm failed for org.mozilla.firefox.old, I/O error"
Some threads have said the problem might be solvable by repairing the partition using tools like fsck.
I've unmounted the /data partition and tried to use fsck.f2fs from the recovery (TWRP) but get this error:
Assertion failed!
[fsck_chk_node_blk: 187] ni.blk_addr >= SM_I(sbi)->main_blkaddr
I'd like to solve this problem so i can again make nandroid backups and play around with my phone.
Thanks for the help
Daniel
I have the same problem but I think I have all the emmc memory as Read-Only, because I can't change the Recovery (vía fastboot) or flash another ROM or restore a Backup or even format anything.
I can enter to TWRP and Fastboot mode but any change I made is saved..
Sent from my Optimus 4X HD using XDA Free mobile app
Oliverrlh said:
I have the same problem but I think I have all the emmc memory as Read-Only, because I can't change the Recovery (vía fastboot) or flash another ROM or restore a Backup or even format anything.
I can enter to TWRP and Fastboot mode but any change I made is saved..
Sent from my Optimus 4X HD using XDA Free mobile app
Click to expand...
Click to collapse
corrupted emmc memory -- this could be because a set to read only.... or true failure - no cures (yet) for this and tbh the rumoured way is by linux commands to set permissions again and no one seems to have progressed or got results in last 9 months or so.
It magically got solved after flashing radium redefined ROM.
Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!
Youshouldsmile said:
Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!
Click to expand...
Click to collapse
You can extract the persist.img file from the MIUI Q beta fastboot ROM
i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !
sar78mad said:
i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !
Click to expand...
Click to collapse
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.
i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..
sar78mad said:
i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..
Click to expand...
Click to collapse
Bro could please tell us step by step ? i am getting mad. please
Eng.Raman said:
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.
Click to expand...
Click to collapse
perfect
I read my computer partitions. After finding the number of the block that corresponds to my team, copy the persist of the rom stock to my internal memory in twrp and then flash with your command and add my block.
in my case note 10 pro (sweet)
dd if=/sdcard/persist.img of=/dev/block/sdf7
VERY CAREFUL NOT TO USE THIS COMMAND ON ANOTHER computer. each person must read the exact block that corresponds to your mobile reference.
I guess your problem is more of hardware issue ,but have to test to know.
I come to this conclusion because magisk does not modify partitions nor system files , I would start with a clean fastboot flash of the phone (be careful of the lock checkbox).
Then judge from there , if phone still presents anomalies then my first assumption is true.