I finally flashed a non Sense ROM onto my dev edition M8, and now I can't even touch /data. I got the enter password to decrypt storage bug while using Paranoid Android, so I followed the steps here to get back to a working system, but the ROM never booted to the password screen. It froze on the boot animation, the went in a loop, I tried to wipe data through recovery, the screen went blank after a few seconds, and then tried to boot the system again. I can't get it to wipe via fastboot either as I get a "FAILED (remote: not allowed)" when trying erasing and formatting data/userdata. I also can't delete anything from /data in recovery. Does anyone have a fix for this? Flashing other ROMs also suddenly quit and go back to trying to boot the system.
Edit: Flashing a stock recovery to wipe /data fixed it. Why didn't I think about that sooner?
Related
Im in desperate need of help.
My one X randomly locked up and on a hard reboot (held power button) it now no longer boots to CM, instead it boot loops.
On booting to recovery (CWM) I was presented with a black screen. So using fastboot I was able to flash TWRP 2.4.0.0 and successfully boot to it.
It opens with a password prompt to which I can click cancel and get to the options. This is where it complains things get complicated :/
If I try to wipe anything:
E: error unable to mount '/cache'
It will do the same with /data and /system.
adb sideload so far has failed me,
failed to write data 'protocol fault (no status)'
It seems once one attempt fails the phone seems to go into some locked status until the battery is fully drained and recharged. Which makes everything so long and tedious to troubleshoot.
adb push cm.zip /sdcard returns an error. But this is all in vain as I have cm10.1 on the /sdcard but twrp fails to flash it.
Any help would be greatly appreciated! Ive been without internets at work for days now :crying:
bump.
Update your twrp to latest 2.7 or whatever its near the top in development thread. Then fastboot erase cache, flash boot image for desired ROM fastboot erase cache, boot to recovery flash ROM then gapps, wipe davlic and cache, enjoy..
Sent from my alarm clock.
myheroduane said:
Update your twrp to latest 2.7 or whatever its near the top in development thread. Then fastboot erase cache, flash boot image for desired ROM fastboot erase cache, boot to recovery flash ROM then gapps, wipe davlic and cache, enjoy..
Sent from my alarm clock.
Click to expand...
Click to collapse
Brilliant mate. There was an option in 2.7 to repair the partitions. I had to set /data back to ext4 (even though it said it already was) then repair the partition, and voila. Its all working again
Hi everyone. I've been having this problem since I started rooting my Note, and I haven't the slightest clue how to fix it. Basically, when I boot to TWRP recovery and try to do a wipe (the default wipe which includes wiping cache, Dalvik, and formatting data), the recovery hangs on "Formatting /data using make_ext4fs function," and after about two minutes the application restarts. If I attempt to flash a ROM after that, I get "Can't mount /data," and other can't mount errors and even though Aroma loads fine, the tablet gets stuck on the boot screen (Samsung logo). Someone on the TWRP website suggested that the tablet is encrypted but I never encrypted the device myself.
Thanks for reading!
P.S. I see similar errors to the picture at the botttom of this thread: formatting data using make_ext4fs function
I've recently tried to update my radio and bootloader to the latest versions, i was on a custom rom (7.1.1), I've updated the bootloader and radio via fastboot and wiped the cache then rebooted then my phone was stuck in a never ending boot and all is saw was the boot animation, i decided to reboot the phone so i held the power button until it restarted and to avail, the same thing happened. I rebooted to twrp and tried to wipe the cache and dalvik/ART cache and i got an error that it cannot be mounted and the partition size was at 0mb and twrp could not repair it either, and it could not format any of my partitions, so i tried to return to stock and i tried to flash the images from the stock .zip provided by google and it said that it could not load any images. I can access download mode and twrp, any solutions? (someone said to flash the vendor image after flashing both the radio and bootloader images? could that have cause my problem because it did not flash it?
i was on the latest vendor already)
thanks.
EDIT: after continuously trying to wipe the cache & dalvik/ART cache in twrp it worked and it recognized the partitions and it wiped and my device was able to boot, i'm not sure what caused the problem but it boots properly now, although i'm not sure if i can flash in fastboot again, otherwise it works.
Was running the pixel experience rom, have been for a month.. and I had a very strange issue today, the whole phone just froze, I force restarted it, and everytime It would reboot it would just hang/freeze or unlock and display nothing on my screen but the wallpaper.. ended up trying to restore from an old backup I had, but realized it was when I was running an oreo rom.. got stuck in a loop for fastboot, used twrp to re-install this rom, and it was taking forever to boot, at the G logo.. so stupidly instead of having patience and waiting, I rebooted and formatted data, or tried too, (read it somewhere) and its just been hung on that for hours now "formatting data" Dunno what to do.. I should have just waited on the initial boot after re-installing this rom, forgot it took forever.. dunno if should just keep waiting.. or try an flash back stock rom, and re-do everything.. I think my data partition is corrupted, or unmountable.. so not for sure how to proceed.
Format data or wipe data ?? Formatting data will remove encryption and everything will be erased
Wipe data just erases data partition
Try to clean flash once again by wiping system data cache
Here is the issue now.. when I would go to format data, it would just stay stuck on formatting data with ext4 or w/e ... I left it for an hour or more, and nothing.... so decided to use miflash an restore everything. it goes all the way... but never actually says success just still says flashing, even with the green bar full and says finished 200s or something.. the last part of the log always stops after:
"[3:52:43 AM 49c50e2d]:err:writing 'vendor' 2/2...
[3:52:43 AM 49c50e2d]:errKAY [ -0.000s]
[3:52:43 AM 49c50e2d]:err:finished. total time: 23.850s"
so I've let that set for 20 minutes or more, then finally I just manually kick it out of fast boot, and it'll start to boot with MI Logo, and it has the white bar at the bottom, the bar loads all the way then it just hangs there, ive left it over night an its just stuck there
Even now I can fastboot flash a recovery image, and boot into it, but its unable to mount data, missing crypto header.. maybe I should just let the "format data" take its time maybe eventually it will?
Hi all,
My AFT wouldn't boot this AM. Booted to TWRP and tried a wipe cache but got an error with cache not present, went into advance wipe and fixed this.
Installed latest pre-rooted rom. No errors rebooted but wouldnt boot.
Installed previous version 5.2.4.0 firetv goes into a boot loop (white amazon logo then back to Twrp screen)
Also tried installing the unbrick image again no joys.
Any ideas?
thanks
I've had this issue before, make sure system is mounted and if it boots up factory reset from settings but make sure you have access to a pre rooted rom on either USB or ext xd
bamemanxxa3416 said:
I've had this issue before, make sure system is mounted and if it boots up factory reset from settings but make sure you have access to a pre rooted rom on either USB or ext xd
Click to expand...
Click to collapse
When I go into TWRP recovery and check whats mounted everything appears to be mounted.
When I do an advanced cache wipe or normal wipe. Messages respond success no errors Just will not boot.
This all started because I turned on the AFT and it was dead and would only boot to twrp and when checked the cache was in error tried the usual wipe/advance wipe still errors. the did a change system and redid the ext4 this brought back a "clean system" no more errors on installing due to cache and everything looked good. Just still no boot.