Develop Bugs

[Q] free beer if you fix my one x!

Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)

oh and ....
ALSO I've googled the problem and tried all of the options I can find which could help - please don't just send me a link to a page because i can guarantee I've probably already tried the solution and failed. When I boot into recovery, I can't use adb push to send files to the phone because it says it's not connected even if i try the option for mount data, or mount storage - the only time windows seems to manage to aknowledge it's existence is on the fastboot screen -
lazclark said:
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
Click to expand...
Click to collapse

Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app

thanks!
wow that was a quick reply - yes I've flashed the cm boot img and erased the cache - which version of CWM is the latest? - When you say mounting as USB storage is fixed, do you mean that windows will be able to see the device and write files to it?
(I'm really sorry for asking these questions - the problem is that I know a BIT about how android works but not as much as I should do)
treebill said:
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't

This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!

sorry hope i'm not wasting your time!
I ran the command as follows :-
fastboot flash boot boot_signed.img
(I got the img file from the ruu )
I'm not 100% sure if it worked, but at that stage I didn't see any errors
Michealtbh said:
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
Click to expand...
Click to collapse

CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache

thanks!
I'll give it a go - to be honest i don't insist on using cm10 at all - i just wanted to see what jellbean was like and it seemed like a reasonable way of achieving that.... i'd be quite happy with any decent rom if it can fix the lag problems i have and some of the other issues.....
great tutorial by the way! - once my phone has charged up again I'll try it
ORStoner said:
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
Click to expand...
Click to collapse

ahhhh!
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
BenPope said:
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
Click to expand...
Click to collapse

Thanks.
I use CM10 myself at the moment because of the aesthetics, but because of the amount of ram and battery it uses I wish I had stuck with ARHD.
Come October we should see Jellybean ARHD which will have great features like USB OTG without a powered hub.

lazclark said:
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
Click to expand...
Click to collapse
Mount as USB not working on that version, also charging not working either. It was not a great release in terms.of features, but it was updated quickly, that's quite an.old version now.
Do you know which tutorial you followed? It really needs updating, there are a lot of people on this old version struggling more than they need to.

Right, first you're going to flash a recovery which allows you to mount USB storage. Either cwm or TWRP, download the recovery.img and flash through fastboot using fastboot flash recovery rocoveryname.img.
Download a new rom and extract the boot.img from it. Flash that boot.img using the usual fastboot method.
Now boot into the new recovery, connect to your pc and mount USB storage from the option in recovery. Copy over the rom you downloaded. Unmount USB storage. Now do a full wipe through the menu in recovery - format /data, /system and /cache. Now flash the rom and reboot

[Help] Asus Zenfone 2 ze551ml bricked and denies ADB pushed files

Hello, I'm needing some help with my 4gb 2.3 ghz rooted Asus after attempting to installing xposed framework. I'm certain it is bricked. Currently it is still able to charge and access the boot loader, but I am not able to flash the phone. The ADB shell just responds with "Access Denied". The phone was encrypted before I tried the xposed install so I'm guessing it messed up the process and is blocking my from using ADB. I did try factory resetting, but I guess that just covers the user app data. I also had debugging enabled within the developer options before everything went haywire. Any suggestions would be helpful, otherwise I'll just have to send it to Asus support for a pretty penny. It doesn't have warranty and I'm positive they don't really help you when your phone is rooted.

Try to wipe /cache. If it doesn't work, backup all your important data and wipe /data in recovery.

HungNgocPhat said:
Try to wipe /cache. If it doesn't work, backup all your important data and wipe /data in recovery.
Click to expand...
Click to collapse
Ok, I did a data factory reset and wiped the cache. The problem i'm encountering now is i get status 7 in ADB when attempting to push a new zip of firmware to the phone. I know status 7 means the firmware cannot be installed due to system modification and root. So i'm thinking i'll have to reflash a pre-rooted system.img with droidboot.img and boot.img (recovery is functioning properly so i don't believe that i will need to flash recovery.img) I am also having a hard time finding detailed guides concerning flashing images and getting the zenfone 2 into fast boot. I did try a fastboot reboot fastboot command, but i,m thinking i'm missing a few important details on prerequisites to flash the phone.

HungNgocPhat said:
Try to wipe /cache. If it doesn't work, backup all your important data and wipe /data in recovery.
Click to expand...
Click to collapse
Ok, I did a data factory reset and wiped the cache. The problem i'm encountering now is i get status 7 in ADB when attempting to push a new zip of firmware to the phone. I know status 7 means the firmware cannot be installed due to system modification and root. So i'm thinking i'll have to reflash a pre-rooted system.img with droidboot.img and boot.img (recovery is functioning properly so i don't believe that i will need to flash recovery.img) I am also having a hard time finding detailed guides concerning flashing images and getting the zenfone 2 into fast boot. I did try a fastboot reboot fastboot command, but i,m thinking i'm missing a few important details on prerequisites to flash the phone.

Asus enthusiast 12 said:
Ok, I did a data factory reset and wiped the cache. The problem i'm encountering now is i get status 7 in ADB when attempting to push a new zip of firmware to the phone. I know status 7 means the firmware cannot be installed due to system modification and root. So i'm thinking i'll have to reflash a pre-rooted system.img with droidboot.img and boot.img (recovery is functioning properly so i don't believe that i will need to flash recovery.img) I am also having a hard time finding detailed guides concerning flashing images and getting the zenfone 2 into fast boot. I did try a fastboot reboot fastboot command, but i,m thinking i'm missing a few important details on prerequisites to flash the phone.
Click to expand...
Click to collapse
What adb command you ran? It should be "adb sideload filename.zip"
If you can't, rename your firmware file to mofd_sdupdate.zip, copy to external sdcard, boot recovery then it will install install the zip automatically. Root using temp cwm/twrp.
If the above method doesn't work for you, flash a pre-rooted firmware.

failed to flash ob 10 and can only boot into recovery now

Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.

Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.

You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?

zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).

SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.

After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .

zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.

I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.

Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.

Did you manage to fix it? I have the same probem.

Can't install anything in TWRP

i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file

SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/

well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery

SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything

Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again

SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!

StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this

Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working

Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79

SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare

Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/

SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

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.