hey, something similar happened to me and I am already very frustrated, I had done the whole process of installing the havoc os ROM and everything was going well, until when installing the MagisK from TWRP, it remained on the loading screen (a white circle and It started again and it did not start), I went back to TWRP and reinstalled the backup but when the process is going to finish the following appears: "failed to mount '/ product' (structure needs cleaning), it does not allow me to swipe, install, literally nothing process because it tells me that at the end. I need help, I already fixed the mount system but I haven't found anything for this ...
Did you backup that partition too?
Nvm I just remembered.
The /product partition in Android 9 is an extension of the /system partition
Try format it then mount it again then restore the backup.
Kenora_I said:
Nvm I just remembered.
The /product partition in Android 9 is an extension of the /system partition
Try format it then mount it again then restore the backup.
Click to expand...
Click to collapse
I lost the backup and it does not allow me to carry out any process literally, in the end it throws me that error, the only thing I did was format from the pc, reinstall another version of HavocOs and it came out the same, but I connected it to my pc and it showed me the Havoc battery charging animation, but fails to get past samsung home screen, again ...
Related
SOLVED
EDIT: Yup, I just reflashed AOKP, then restored /Data, /Cache, /ExtSD, while keeping /System.
Got it booting properly. Except Link2SD mount script (Which I recreated) and the logcat boot animation (Reinstalled), I did not found any other problem (Yet?).
************************************************************
Hi,
I've tried to install Xposed Framework on my LG P500 (ROM being AOKP); I knew at first that the /System partition had not enough space for installation, so I proceeded anyway, to see the message "Insufficient storage", I wanted to know how much space was required for the installation.
But well, seems there was at that point enough space on /System, and Xposed installed anyways. I preferred to uninstall it right away before rebooting to avoid problem. I suspect the uninstallation wiped the /system/bin/app_process backup.
I then booted in TWRP Recovery and took a full Nandroid backup.
But when I rebooted, heh, it freeze at the boot animation (I have a logcat. I can tell where the Logcat freeze, actually, instantly, just after LG logo).
I tried to flash Xposed Disabler, but it says "No backup found for app_process, nothing to be performed!". I suspect my backup was wiped after I uninstalled Xposed (But why do I still have a boot-loop?).
Could I just reflash AOKP, grab the file app_process and save it, restore the faulty Nandroid Backup, copy the file back, and voila?
Or interestingly, the Nandroid backup was a full one, so /Data, /Cache, /Ext-SD were saved. So if the /System partition only was damaged, could I just restore the /Data and /Ext-SD partition? I get I will have to recreate Link2SD mount script, but not much.
Do I need to reinstall everything?
Thanks for the help ?
Hello, I faced unique problem. Device Nexus 5 D820. I've read a lot of topics on how to flash stock dactory image, clean, and did everything the same as described there.
Problem is that I am not able to flash lollipop (Android 5+) factory images. I mean everything goes fine, but when it comes to final start of the system it stucks on flying dots (dots are moving) over 12-24 hours and won't open. However the KitKat (Android 4+) factory images flashes properly, the system loads in 10 minutes. I also tried to update from Android 4.4.4 by google update (Android 5+) notification, but it also gets stuck on the same flying dots. The problem began when my device running Android 5.1 several months suddenly rebooted and system asked me to enter password (I do not use any passwords on phone), I entered my google account password, then it stated that the data was corrupted and needed factory reset. In order to avoid this I just turned it off and on and it stucked in flying dots. When I tried to wipe cache first the following errors appeared:
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
Then, after several flash things these errors do not appear already, but problem still remains. I already delete all data, so no need to bother keeping data. Any Ideas what causes this problem?
When I boot from TWRP and do operations the following string appears during operations (wipe cache, etc.):
Updating partition details...
E: Unable to mount '/persist'
I had a similar problem.
Make sure you wipe dalvik and cache in recovery before rebooting.
Finally, nothing worked until I did a factory reset after flashing.
Be sure to first backup photos, documents, etc. in addition to nandroid and titanium backup.
Update: problem SOLVED
maybeme2 said:
I had a similar problem.
Make sure you wipe dalvik and cache in recovery before rebooting.
Finally, nothing worked until I did a factory reset after flashing.
Be sure to first backup photos, documents, etc. in addition to nandroid and titanium backup.
Click to expand...
Click to collapse
Thank you mate. But my problem is apparently more specific.
I find a solution which is exactly suits for my problem. Greatest thanks to @bitdomo :good::good::good::good::good::good::highfive:highfive:
Here is his topic
[GUIDE][FIX] Boot loop on Lollipop 5.0 and above (fix persist partition)
at first im just failing at wiping cache.
now i cant even restore my TWRP backup.
it is saying "Failed to unmount '/cache' (Device or resource busy)
now my phone got no OS :crying::crying::crying:
I was facing the same problem.recovery twrp>wipe>advance wipe and then select system>repare or change size>change file system>select FAT
after doing it try to restore your backup and if you get error the only way flash your phone to the last build number(avalaible for your phone) and then install twrp recovery(last version).
restoring backup should be work with this method.
you can try this method
Mount>select partitions to mount : cache
select cache and after doing it go for restoring.
R3yN said:
at first im just failing at wiping cache.
now i cant even restore my TWRP backup.
it is saying "Failed to unmount '/cache' (Device or resource busy)
now my phone got no OS :crying::crying::crying:
Click to expand...
Click to collapse
No need to restore /cache partition, exclude it The partition is used by TWRP that's why you can't unmount it.
I still have the same problem persisted. Can't wipe cache with this TWRP recovery. It says can't mount/unmont cache device or resource busy. Restore of the backup was impossible as well. Even when cache was excluded. Changing file types and repairing it also didn' work. In Mount cache is ticked permanently and it can't be unticked.
rrvuhpg said:
No need to restore /cache partition, exclude it The partition is used by TWRP that's why you can't unmount it.
Click to expand...
Click to collapse
Thanks man, i was having the same problem and for some reason, it didnt occur me to exclude the cache
omg i got that eror now, do u have new idea to fix it:crying: ?
have a rooted Honor 8 (FRD-L09).
So, I installed the new Magisk. I have been prompted to reboot.
So, I rebooted, and my phone asked me my password for decrypting the OS. I never encrypted the system. I tried 0000, my pin and others, but nothing did it, so I factory reset my phone.
The system did not load.
I looked up online for custom ROMs to boot, but none of them worked.
And that's my big errir : I wiped /system partition because it was a recurring error.
Now I have a bricked phone, with no OS on it.
What to do ?
Hello,
Did you flash a custom recovery (TWRP)?
What the phone do if you press & keep all buttons ( "Power" , "Vol-" and "Vol+" )?
delete
Update : I reinstalled the TWRP and fixed /system, but HURupdater ignore the update.zip and /data isn't writter (also, every line in TWRP starts with "Unable to mount /data")
Gabmiral said:
Update : I reinstalled the TWRP and fixed /system, but HURupdater ignore the update.zip and /data isn't writter (also, every line in TWRP starts with "Unable to mount /data")
Click to expand...
Click to collapse
Have you format /data partition and reboot ti ricovery?
I have an OP 7Pro (GM1917) that was working fine for a long time with OOS 10.3.8.
I hadn't done an upgrade for a long time, and so recently, I did an upgrade to OOS 11.0.5.1.GM21AA. After doing that, my device is unusable, and I fear that there might be something broken or damaged that causes firmware or storage to no longer function properly. All of the explanatory details follow, and please read all of that. What I'm wondering is whether the device is now permanently hosed, or perhaps if there is some way for me to fix it. Here are all of the details:
After the upgrade, my device went into a permanent boot loop when trying to boot to System.
I then did fastboot boot twrp-3.6.0_11-0-guacamole.img, and it indeed put me into TWRP. However, the /data partition is inaccessible. Whenever I try to format /data, I consistently get these messages:
Code:
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
Unable to wipe data
I go back to the bootloader and connect to my PC, and I then run these commands:
Code:
fastboot erase userdata
fastboot format:ext4 userdata
These commands successfully run with no error messages. I then go back into TWRP, but /data is still inaccessible, and I get the same error messages that I listed above when trying to format /data .
I then tried to decrypt /data, but when I do so, it asks for a password, and I have no idea what password to give. I never used any password on the device in the past. I am not allowed to decrypt /data without a password.
So, I decided to use the MsmDownloadTool to reflash my device back to OOS 10.3.8. This works fine with a different GM1917 device that I have (but which I never tried flashing to OOS 11). However, with this particular device, after going into EDL mode, I am told that I am "Connected", but a couple seconds later it gives me the "Sahara Connection Failed" message. I have double-, triple-, and quadruple-checked the device drivers, and it indeed is showing that the "Qualcomm qds 9008" driver is properly installed and active. Furthermore, as I mentioned, I have no problem using MsmDownloadTool on that PC with another GM1917 device.
I went further: I extracted payload.bin from the OOS 11.0.5.1.GM21AA installation bundle, and I extracted all of the *.img files. I flashed boot.img via fastboot and retried everything that I mentioned above, but nothing has changed.
I then went and flashed all of the *.img files. However, still nothing has changed.
When reflashing the set of all *.img files, in some cases, I was told that the file is critical and cannot be reflashed. I then ran these two commands ...
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
... but in both cases, I was told that the device is already unlocked. Trying to reflash all of the *.img files again gave me the same results: i.e., some got flashed, and others were not flashed due to being "Critical".
Also, some of the items I flashed were said to be "sparse" and their flashes were flagged with warnings, but as far as I can tell, they seem to have been flashed anyway.
Do these problems with /data and EDL and everything else mean that my device is somehow permanently damaged? Or are there perhaps one or more additional things that I can try in order to restore it to some sort of working state?
Thank you in advance for any thoughts or ideas.
This has been fixed.
I had forgotten that in the past, I was trying the OrangeFox dual-boot recovery on this device, and it had repartitioned /data.
I fixed this by booting into OrangeFox recovery via fastboot, and then using its adb sideload facility to flash that recovery. OrangeFox's adb sideload mechanism offers options to the user for repartitioning and rebuilding /data. I utilized those options and set /data back to "Stock", and after that, /data was accessible again.
At this point, I flashed OOS 10.3.8, and then flashed the appropriate TWRP and Magisk, now, my device is back up and running in that OOS version.
The EDL problem continues, but given that my device is now usable again, I am not overly concerned about this MsmDownloadTool issue at the moment. In my spare time, I'll continue to look into that.
All's well that ends well!
I think I also have the same issue but the good thing with mine is my device is still working..but every time I access storage via twrp it give me a 0mb or in accessible data no matter if I enter my password to decrypt data. Until now I just leave it as is for I haven't found any solution
I have the same issue but I can't boot at all. I'm only limited to twrp and fastboot. I was previously running 11.0.3 with Magisk and a Magisk module called xXx_nolimit, downloaded the OTA update and went to reboot to recovery before being prompted for a pattern passcode (I hadn't set any fingerprint or password) so I rebooted into twrp and clicked fix bootloader. Now as I reboot it just boots back into twrp.
I'm also getting these same messages:
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I'm currently running apbf to bruteforce the pattern passcode that I never set in hopes to decrypt my phone. Not even sure it will work though as I don't have FBE user 0 mounted? I have my dad's phone which basically has the exact setup as mine but I didn't update it yet. Anyway to use partition or parts data from his phone to fix mine? I really don't want to wipe my /data or /userdata as it's been a while since I backed anything up.
Edit:
All I have in my /data folder is:
/data/india
/data/recovery
/data/reserve
The edl issue happended to me too and I just needed to use another msmdownloadtool version.