I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.
alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.
Related
Hey guys,
My work switched to Google Apps for their email so i wanted to test it out on my phone. Doing so required them to encrypt my phone. What this appears to have done is encrypt the data partition. So now when i go into (TWRP) recovery and try to do a backup / wipe / or anything else, it says it is "Unable to mount /sdcard" I'm unable to do a factory reset of any kind so i'm essentially stuck on this rom (ARHD) until i can figure out how to wipe data and get the /sdcard to be not encrypted. Does anyone have any ideas? I'm imagining that with the modified recovery not being able to access the data partition that i'm going to have to do some adb type stuff?
Please help! I want to keep flashing new roms!
Anyone??
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Guich said:
I think you can't decrypt your data partition...
Did you try to wipe your data partition with the latest TWRP?
Click to expand...
Click to collapse
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
jrun said:
That's the thing, the recovery can't mount /sdcard so wiping isn't an option from recovery
Click to expand...
Click to collapse
Hi! Only TWRP recovery can solve your issue just do this...
Boot to TWRP recovery->Wipe
From there there are 2 options the left is the advance wipe and on the right is Format Data
Just select the format data button and it should reformat the whole data partition.
1st one would prompt so many errors and reformat then reformat it again 1 time and it should fully reformat your phone.
In theory it should reformat data partition even when encrypted but just in case it fails and I won't be able to go back to this thread just boot in bootloader and type
"fastboot erase userdata"
Well none of that works. TWRP doesn't support decryption yet for this device.
sevenalive said:
Well none of that works. TWRP doesn't support decryption yet for this device.
Click to expand...
Click to collapse
What I instructed basically doesn't decrypt the partition. It reformats it.
Riyal said:
What I instructed basically doesn't decrypt the partition. It reformats it.
Click to expand...
Click to collapse
I know what you instructed, it doesn't work. Only way I got it to work. Flash the stock recovery. Boot into system. Take off the encryption, phone reboots and removes the encryption, data is formatted. Then flash TWRP again.
I basically ran into this exact problem. I was hoping that I'd still be able to back up the encrypted device, but forget about it. What a pain in the ass.
Someone should make add something to the guides about how encrypting your device makes nandroid backups impossible.
I was formatting my HTC One to give it to a family member. I was going to sideload or push a rom and flash it, but twrp keeps saying it cant mount /data/ or internal storage. I got to sideload android revolution HD GPE but when it boots its asks for a password to decrypt the storage which i have never done. In twrp it still says it can't mount internal storage or data and I need help getting out of this mess. :/
xXxG0dzRAgexXx said:
I was formatting my HTC One to give it to a family member. I was going to sideload or push a rom and flash it, but twrp keeps saying it cant mount /data/ or internal storage. I got to sideload android revolution HD GPE but when it boots its asks for a password to decrypt the storage which i have never done. In twrp it still says it can't mount internal storage or data and I need help getting out of this mess. :/
Click to expand...
Click to collapse
inside TWRP select wipe and then select format data, this will however completely wipe your phone and you will need to push or sideload a new rom then flash it, try and use TWRP 2.6.3.3, it makes all the difference.
Seanie280672 said:
inside TWRP select wipe and then select format data, this will however completely wipe your phone and you will need to push or sideload a new rom then flash it, try and use TWRP 2.6.3.3, it makes all the difference.
Click to expand...
Click to collapse
I flashed CWM to see if it worked instead but still said cant mount /data and can't mount /sdcard. I formatted /data and now trying to sideload android revolution again to see if that will work. If not I will try to use TWRP 2.6.3.3. I was using 2.7.1.1 beforehand.
Also the whole reason im here is because I wiped my phone completely with TWRP. Just planned on wiping it all then sideloading a rom to give it that "new phone" sort of feel. No empty random folders and all that. No left over files.
xXxG0dzRAgexXx said:
I flashed CWM to see if it worked instead but still said cant mount /data and can't mount /sdcard. I formatted /data and now trying to sideload android revolution again to see if that will work. If not I will try to use TWRP 2.6.3.3. I was using 2.7.1.1 beforehand.
Also the whole reason im here is because I wiped my phone completely with TWRP. Just planned on wiping it all then sideloading a rom to give it that "new phone" sort of feel. No empty random folders and all that. No left over files.
Click to expand...
Click to collapse
The TWRP 2.7.x.x series all seem to have one or another problem going on with them, most users here swear by 2.6.3.3 or 2.6.3.4, however you will also find that most custom rom's require TWRP recovery over CWM.
also, don't forget to erase the cache after flashing each recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Seanie280672 said:
The TWRP 2.7.x.x series all seem to have one or another problem going on with them, most users here swear by 2.6.3.3 or 2.6.3.4, however you will also find that most custom rom's require TWRP recovery over CWM.
also, don't forget to erase the cache after flashing each recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ended up reflashing twrp with fastboot and then flashed Android revolution HD71.1 on it. The format of data in CWM worked to fix the mounting problem I had. Twrp probably could have fixed it too if I tried wiping data again. Will remember that next time for the other HTC One I'll be doing this to in the next few days.
I am working on Ubuntu 15.04 and I used the Heimdall suite to do the necessary flashing.
Before I start: I created this post to share my experience with trying to flash a custom ROM on the GT-i9000 and receive some suggestions, though my main concern is the fact that I am unable to mount /system and /data. And yes, I have read posts concerning this issues, but they were too vague, so I decided to write my own.
First I figured I should flash a custom recovery, so I tried flashing the latest CWM for the galaxysmtd in Download Mode and it appeared to have been successful, though when I pressed the 3-button-combo (UP-HOME-POWER), It would boot the default Android System Recovery.
I tried flashing a few CWM and TWRP recoveries (though I didn't try PhilZ Touch, because goo.im is down and I couldn't find a proper PhilZ Touch recovery anywhere else), though I noticed that none of them would work, even though the flash was successful. So I figured I could try flashing a kernel, which would include some recovery - and it worked, to my surprise, though after attempting to wipe a few folders, I got the error: unable to mount /system and /data.
So I came to realise that the only way for me to get a working custom recovery was to flash a kernel, which should include a working recovery. So I ended up flashing Mackay_kernel_0.692_twrp_CMC-signed.zip, which includes TWRP v2.8.0.0. The recovery seems to work fine, though the same error persists: unable to mount /system and /data.
I tried formatting /system and /data, though to no avail: it just forced the recovery to reboot (I have attached the recovery log to this post).
Any help is much appreciated!
I am glad to inform that I managed to resolve the issue by reverting to the stock firmware, ROM and kernel by using Odin v1.83. Though this leaves me with the default recovery, which isn't able to flash a 5.1 ROM.
I tried flashing a kernel with CWM and then flashing a 5.1 ROM with said CWM recovery by installing its .zip, though this method causes the same issue: unable to mount /system and /data.
hi
i have a problem with formatting Data in twrp recovery on huawei P9 eva-L09C432B182
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_174811.jpg
ive tried this ROM:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-newworld-7-tecalote-t3543296
and it installs, but i get message after boot:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_180017.jpg
i can actually see navi bar for a sec and volume buttons still work(can set alarm and sound loudness)
and here is install image of Rom:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_175844.jpg
only error is mount: failed to mount /dev/block/dm-0 at /dat: No such file or directory
so i can only use twrp recovery and fastboot to fix this.
mkfs.f2fs -t 0 /dev/block/mmcblk0p42 process ended with error: 255
unable to wipe Data.
error changing file system.
every other is good for format(System and Cache) to f2fs and ext4 just Data folder has problem with format but wipe works :crying:
Are you using the last version of TWRP? Twrp 3.0.3.0
henryco11 said:
Are you using the last version of TWRP? Twrp 3.0.3.0
Click to expand...
Click to collapse
no i use 3.0.2.0
i think 3.0.3.0 is only for updated huwei with nougat and EMUI5?
Why you decrypted it?
It should work normal after you reset it.
dkionline said:
Why you decrypted it?
It should work normal after you reset it.
Click to expand...
Click to collapse
reset what excatly? factory reset works but Data is in ext4 format. i can wipe it but cant format it.
what if i erase this mmblck0p42 file and then flash twrp in fastboot will the file be reinstalled or will it be after i flash ROM in recovery again?
i made a mistake by formatting it in first place from f2fs to ext4 but before even factory reset didnt work, now it works and only think is left is this encryption error.
jure482 said:
hi
i have a problem with formatting Data in twrp recovery on huawei P9 eva-L09C432B182
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_174811.jpg
ive tried this ROM:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-newworld-7-tecalote-t3543296
and it installs, but i get message after boot:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_180017.jpg
i can actually see navi bar for a sec and volume buttons still work(can set alarm and sound loudness)
and here is install image of Rom:
https://dl.dropboxusercontent.com/u/67361401/IMG_20170309_175844.jpg
only error is mount: failed to mount /dev/block/dm-0 at /dat: No such file or directory
so i can only use twrp recovery and fastboot to fix this.
mkfs.f2fs -t 0 /dev/block/mmcblk0p42 process ended with error: 255
unable to wipe Data.
error changing file system.
every other is good for format(System and Cache) to f2fs and ext4 just Data folder has problem with format but wipe works :crying:
Click to expand...
Click to collapse
Why is your data partition ext4?
Normally it is on each p9 device f2fs.
This can only occur if you were on Nougat between and had installed the TWRP-n which has no Decryption Support and if you had by yourself formated data with this TWRP to ext4.
To install NewWorld Rom you must be on Marshmallow Firmware (because of Android 6 Bootloader) and your data partition must be f2fs.
In the meantime there's a new TWRP for Android 7, which has already Decryption Support.
But you cannot use this TWRP for installing NewWorld. You must have the one, which I have linked in my OP.
On which Firmware or Rom have you been, before you tried to install NewWorld?
If you were on Nougat, NewWorld could not flashed, cause you must be on Marshmallow.
Please answer my questions that I can realize in which situation you are.
i have Marshmallow Firmware and yes i formatted data to ext4 myself
the problem occured when i wanted to get nougat but OTA update failed but it booted back into 6.0 normally just root didnt work so i went in TWRP and flashed supersu 2.79 which i had before, then i was stuck in bootloop, manged to get to fastboot but Hisuite says no update packeg for this phone. i flashed back stock recovery and tryed to factory reset but didnt work, flashed twrp back and factory reset then it said data format error so i went and changed it to ext4 after factory reset worked but i cant put it back to f2fs.
aldo i wiped all cache, dalvik/ARTcache, Data, internal storage and system
jure482 said:
i have Marshmallow Firmware and yes i formatted data to ext4 myself
the problem occured when i wanted to get nougat but OTA update failed but it booted back into 6.0 normally just root didnt work so i went in TWRP and flashed supersu 2.79 which i had before, then i was stuck in bootloop, manged to get to fastboot but Hisuite says no update packeg for this phone. i flashed back stock recovery and tryed to factory reset but didnt work, flashed twrp back and factory reset then it said data format error so i went and changed it to ext4 after factory reset worked but i cant put it back to f2fs.
aldo i wiped all cache, dalvik/ARTcache, Data, internal storage and system
Click to expand...
Click to collapse
Okay, you are now on Stock Marshmallow (which version?) and you maked factory reset after formatting data to ext4
Which phone EVA model to you have?
It is recommended to flash Stock Recovery with adb and flash latest official Marshmallow Full Firmware once again (downloaded and unzipped) with 3 Button (Force Update) from the folder dload on your phone (update.app and if present meta-inf must be in this folder only) Force Upgrade to Marshmallow Firmware should solve your problem (Bootloader get closed, data should be formatted to f2fs automatically)
Tecalote said:
Okay, you are now on Stock Marshmallow (which version?) and you maked factory reset after formatting data to ext4
Which phone EVA model to you have?
It is recommended to flash Stock Recovery with adb and flash latest official Marshmallow Full Firmware once again (downloaded and unzipped) with 3 Button (Force Update) from the folder dload on your phone (update.app and if present meta-inf must be in this folder only) Force Upgrade to Marshmallow Firmware should solve your problem (Bootloader get closed, data should be formatted to f2fs automatically)
Click to expand...
Click to collapse
thanks soo much i did what you said on pm. went to bootloader and flashed your twrp then wiped again arpcache, cache, system, data, reboot to twrp then installed your ROM which still said that mount dev-0 error but i still rebotted and bam it booted longer with this very nice animation you have and showed emui and now im at select language page!
Flashing your twrp in bootloader fix the problem and formatted Data to f2fs thank you again.
also i used command recovery --wipe_data --set_filesystem_encryption=off before all above to make sure ecryption is off not broken.
im now on home screen it looks nice just 3 navigation buttons on bottom look smaller then i had before, thanks again.
Hello,
As stated in the titled I have tried to root my OP 3T and it horribly wrong. First I got the error message telling me it couldn't mount my /system partition. I googled how to fix it and discovered that I had to wipe the partition as it might be corrupt. Just to be sure that it was indeed corrupt. The size was stated as 2913MB but the used space was stated as 1728265MB. I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...The only thing i can boot into was fastboot and recovery. I then tried to install the LineageOS and it worked. I can finally boot to a OS. However when going in the recovery again and wiping the cache I get a slew of errors. Almost all of them are "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)". There is also one other error: "Unable to mount storage"
How do I fix this?
uptivuptiz said:
First I got the error message telling me it couldn't mount my /system partition.
I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...
Click to expand...
Click to collapse
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.
redpoint73 said:
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.
Click to expand...
Click to collapse
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.
uptivuptiz said:
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.
Click to expand...
Click to collapse
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).
Dirk said:
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).
Click to expand...
Click to collapse
Thanks! I will try that when i get time tomorrow. There will come an update.
uptivuptiz said:
Thanks! I will try that when i get time tomorrow. There will come an update.
Click to expand...
Click to collapse
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.
Dirk said:
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.
Click to expand...
Click to collapse
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again
uptivuptiz said:
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again
Click to expand...
Click to collapse
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)
Dirk said:
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)
Click to expand...
Click to collapse
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...
uptivuptiz said:
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...
Click to expand...
Click to collapse
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.
Dirk said:
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.
Click to expand...
Click to collapse
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.
uptivuptiz said:
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.
Click to expand...
Click to collapse
You wouldn't be the first. It's a common issue. You know you can just move the zip to Internal Storage and flash it with TWRP? The Recovery is MTP enabled. Useful to know for future reference. :good: