Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Renatoskie said:
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Click to expand...
Click to collapse
Are you using TWRP by Vasishoth? Those "Failed to mount" errors are related to his TWRP, no user error. Nebrassy's TWRP doesn't have those errors.
Are you using a Custom ROM or Stock ROM?
You may have accidentally wiped "/metadata". That partitions is crucial and contains the encryption key for /data, and without the encryption key /data cannot be accessed, and therefore the system can't boot.
If that's the case, you might have bad luck and need to format data, in order to boot the system again.
dreamytom said:
Are you using TWRP by Vasishoth? Those "Failed to mount" errors are related to his TWRP, no user error. Nebrassy's TWRP doesn't have those errors.
Are you using a Custom ROM or Stock ROM?
You may have accidentally wiped "/metadata". That partitions is crucial and contains the encryption key for /data, and without the encryption key /data cannot be accessed, and therefore the system can't boot.
If that's the case, you might have bad luck and need to format data, in order to boot the system again.
Click to expand...
Click to collapse
Oh I see. I think it his, it was twrp-aliothin, the unofficial one. I using a stock ROM and decided to move to Pixel Experience through TWRP and I stuck there. Where to format the data? Is it in the TWRP? And what do I do after that, sir?
Renatoskie said:
Oh I see. I think it his, it was twrp-aliothin, the unofficial one. I using a stock ROM and decided to move to Pixel Experience through TWRP and I stuck there. Where to format the data? Is it in the TWRP? And what do I do after that, sir?
Click to expand...
Click to collapse
Yup that's Asishoth's TWRP. Both Nebrassy's and Asishoth's are unofficial tho. No official TWRP yet available for Poco F3.
Did Pixel Experience boot properly once, tho? Or has it never booted?
Yup I meant Format Data inside TWRP. It's in "Wipe". That may fix your problem, but I'm not sure...
Renatoskie said:
Hello guys.
I have encountered very big problem and I need your guys help. I wipe something wrong (the problem is I forgot what I wipe, I do have some experiences with Orangefox but no to TWRP) in the TWRP and now it says
Failed to mount ´/system_ext` (Invalid argument)
Failed to mount `/product` (Invalid argument)
I tried to copy file from the computer to do recovery, not possible.
I tried to do ADB Sideload, not detected.
I tried to do Fastboot, also not detected.
Right now when I tried to go to reboot to system, it goes back to the TWRP again and again.
Maybe anyone encountered this? Or has already a solution? Can you please assist me?
Any answers or helps will be very appreciated from me. Thanks.
Click to expand...
Click to collapse
Can you start it in fastboot?
Does your pc recognize it in fastboot?
If the answer is yes, try switching back to the stock you previously had using miflash.
Remember to select "clean all" instead of "clean all and block" otherwise the brick is insured...
You can also read this guide which contains a lot of information that may be useful to you.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
dreamytom said:
Yup that's Asishoth's TWRP. Both Nebrassy's and Asishoth's are unofficial tho. No official TWRP yet available for Poco F3.
Did Pixel Experience boot properly once, tho? Or has it never booted?
Yup I meant Format Data inside TWRP. It's in "Wipe". That may fix your problem, but I'm not sure...
Click to expand...
Click to collapse
I tried this and still not working honestly. It's still in the process of loading the Pixel Experience ROM. My bad actually, Pixel Experience ROM also provides a Recovery but it seem sketchy so I decided to use the TWRP one.
RollDload said:
Can you start it in fastboot?
Does your pc recognize it in fastboot?
If the answer is yes, try switching back to the stock you previously had using miflash.
Remember to select "clean all" instead of "clean all and block" otherwise the brick is insured...
You can also read this guide which contains a lot of information that may be useful to you.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
Click to expand...
Click to collapse
Oh yes thank you. Finally it worked. At first I didn't find the menu for Bootloader Fastboot, instead the Fastboot that the TWRP provided, which makes the device undetected with Mi Flash, CMD Fastboot Devices, Xiaomi Szaki Tools, but after I found the right menu which lead me ro Bootloader Fastboot, it can detect my device again, so I properly did what you told and voila, all worked again. Many thanks, Sir!
Renatoskie said:
Oh yes thank you. Finally it worked. At first I didn't find the menu for Bootloader Fastboot, instead the Fastboot that the TWRP provided, which makes the device undetected with Mi Flash, CMD Fastboot Devices, Xiaomi Szaki Tools, but after I found the right menu which lead me ro Bootloader Fastboot, it can detect my device again, so I properly did what you told and voila, all worked again. Many thanks, Sir!
Click to expand...
Click to collapse
I'm glad it worked.
however, if you want to enter fastboot mode easily do this:
1) turn off the phone;
2) hold down the "volume - and power" keys until the word fastboot appears.
Related
Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?
Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.
mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!
Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read
wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!
i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.
i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course
what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!
Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work
i tryed it, i get the same error :/
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?
colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
Click to expand...
Click to collapse
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
Click to expand...
Click to collapse
unfortunately no choice other than wiping everything.....
antisoma said:
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
Click to expand...
Click to collapse
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Hw4ng3r said:
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Click to expand...
Click to collapse
So do you think there would be workaround in future?
0xelectron said:
So do you think there would be workaround in future?
Click to expand...
Click to collapse
Hopefully there will be, but it doesn't look promising right now. @eng.stk is the one that was modding the TWRP, but has since stopped doing TWRP dev.
kipue said:
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
Click to expand...
Click to collapse
But I'm on official 3.2.8 with ext4 partition
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
nqk said:
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
Click to expand...
Click to collapse
Fastboot Format system and data
Then fastboot flash stockrecovery
Then boot to system
Sideload rom
Then fastboot boot twrp28
Then wipe data and install superuser in one go
candiesdoodle said:
Fastboot Format system and data
Click to expand...
Click to collapse
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
nqk said:
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
Click to expand...
Click to collapse
Yeah fastboot Format userdata
But since you don't have the dm-verity you can skip the fastboot Format. Boot into the modd twrp and when it asks for password, hit cancel and then format data (you will have to type 'yes').
Then flash SuperSU or superuser in the same session without booting. This will ensure dm-verity doesn't come up again as it will start in enforcing mode, thanks to SuperSU/superuser.
You may be able to flash twrp afterwards but I haven't tried it.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
Bought new OP5t
Update OOS 5.1.5 latest
Unlock bootloader
Flash TWRP recovery
Wipe everything except otg format
Install lingue os 15.1 gapps 8.1 pico
Boot normally
Then try to install red flare kenel, magisk zip boot to fatboot menu can't boot make nandroid backup twrp then try to restore also boot on bootloader menu try to download magisk apk download but it's blank can't install notification bar have strange one
Discover trust "get to know to assure how your device is safe"
I don't know what happened if someone could help me if I didn't something wrong please
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
Flash this solve your proplem
https://drive.google.com/file/d/14QnXJH9TWMZnYI9RItIPv8ivGUjz1q5S/view
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Tobias101 said:
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Click to expand...
Click to collapse
That's all I can help with I'm not professional sorry.
Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
brad:
It won't mount data for many reasons but just installing stock recovery and installing OOS would fix everything.
https://forum.xda-developers.com/on...-revert-to-oos-oreo-8-1-t3730952/post75096633
I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU).
The steps I took to change the ROM:
Formated data (errors started right away) then I did the usual wipes (cache, dalvik, data)
Whenever I try to wipe or format data I get error messages like: Error opening /data/XXX (Operation not permitted).
System is always mounted read-only no matter what I try and after I install any ROM many of these error messages pop up.
Orange Fox gives some error about key.
Flashing of the ROM suceeds, but system cannot boot, loading screen forever.
Can anyone point me some directions?
Thanks in advance and sorry about any possible bad grammar.
[ ]s
;-)
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Pavello said:
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Click to expand...
Click to collapse
Well , i have the same problem..and used pitch black also
Any update on this?
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
i gusse thats a problem in miui12.0.3
i was using pixel experience 10 then i flash miui 12.0.3 in fastboot when i tryd to flash orange fox i had the same problem
so i gusse u can downgred to miui 11 and flash twrp and it will work
I solved this by downgrading to 12.0.1
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
I am having this exact problem.
Under internal storage (sdcard) I see a bunch of hashed folders I cannot open.
Format data returns a multitude of "Error opening '/data/somefolder/asdf/asdf' (Operation not permitted) and marks the wipe as Failed. The attempted formatting also mentions "E:Error making /sdcard/Fox directory: Required key not available." "Failed to unmount '/data' (Device or resource busy)
I can wipe anything except Data. I also tried downgrading to 12.0.1 firmware but it does not fix it for me.
The ROM can be booted into, and magisk managed to be installed, but no google apps were installed.
Dibbo Sarker said:
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
Click to expand...
Click to collapse
I tried this, but no luck on my side.
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
A problem like this was the one I had since TWRP had the device encrypted but it did not inform me and it did not give me any sign that I had to write a password (password that I have no idea what it is).
What I did so that it did not give me an error was to install Orangefox and while there delete everything and install a file of these that I got from google.
I had to try one by one and restart to see if it asked me for a password in orangefox, luckily one worked and it no longer asked me to decrypt the files and I could install the rom and gapps normally
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
Thank youuuuuuuu! You have rescued my phone!
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
THANK YOU!
Why is my orange fox is not showing Vendor, System Etc ? How can i fix this ? I really need to wipe those as well..
Jona'san - sama said:
Why is my orange fox is not showing Vendor, System Etc ? I really need to wipe those as well..
Click to expand...
Click to collapse
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
Jona'san - sama said:
I really need to wipe those as well..
Click to expand...
Click to collapse
if you want to flash a rom = yes
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Can't wipe it still, I already try the Mount > ✓ Vendor ✓ System.. but in formatting it say's "Cant Mount the....blah..blah.."
I try to uncheck the "Mount System vendor, system as read-only" from the settings of mount.. but for some reason, if you go back to Mount options again, you can't check the system, vendor now
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Yes, I need it to flash a ROM
try this it worked
Had the same issue.
1. I installed twrp via ADB
2. Restarted to recovery mode into twrp
3. Installed the latest OrangeFox and restarted into recovery again.
4. It asked me for a password which is the pin I set then proceeded to format data.
5. After formatting data I restarted again to recovery.
Then I was able to install custom roms.
I am using derpfest Android 12 on my Poco x3 pro. I want to install magisk.zip through orange fox recovery installed on my phone. But I am not getting storage data on recovery, only a fox folder is there. Can somebody tell me is it a glitch or any Android 12 restrictions or something.