Related
hi everybody.
yesterday i have flashed my p7310 from stock honeycomp to cm10.1-experimental.
descriped here: http://forum.xda-developers.com/showthread.php?t=2060530
works good, just the strange screen flickering after wakeup from standby.
see here: http://forum.xda-developers.com/showthread.php?t=1989398&highlight=wakeup
because this I tried to reflash it with GT-P7310_XAR_P7310UELA3.
descriped link above.
now I'm in a bad state.
actually cwm 5.5.0.4 is installed.
if I try to boot my rom it loops at samsung logo.
if I select "wipe data/factory reset" in cwm I get:
-- wiping data...
formatting /data
error mounting /data!
skipping format...
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure...
error mounting /sdcard/.android_secure!
skipping format...
data wipe complete
I have tryed to install stock rom P7310XXLPO_P7310XEULPO_XEU.zip via odin. install works, bootloop
installed ClockworkMod_Recovery_v5.5.0.4.tar via odin. install works
repartitioned via odin (p5_0614.pit) and install stock rom, install works, but still bootloop.
if i connect via adb i can push Clockwork_Recovery_6.0.0.8_GT-P7310.zip to /sdcard, but no access via cwm and "choose zip from sdcard". error: E: can't mount /sdcard/
if i list files via adb shell from /sdcard and /data there are no files.
can somebody help me?
greetz from germany
mitch
one more info.
in adb shell, if i try to mount /data manually, i get following message:
[email protected]:/ # mount /data
mount /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
i assume that this blk device has no filesystem. but how can i format it manually?
ok... i solved it.
who want's to know how i solved:
i formated /data with ext4 via adb shell.
[email protected]:/system/bin # /system/bin/make_ext4fs /dev/block/mmcblk0p8
where /dev/block/mmcblk0p8 is my /data (according to the fstab)
after that i was able to mount /data !!!
i flashed cwm 5.5.0.4 again via odin, flashed (odin) stock rom (works now!)
It seems that I have a similar (if not exactly the same problem). Problem is, I'm not exactly tech savvy enough to
understand/execute your solution on my own.
mitchgehtab said:
ok... i solved it.
who want's to know how i solved:
i formated /data with ext4 via adb shell.
[email protected]:/system/bin # /system/bin/make_ext4fs /dev/block/mmcblk0p8
where /dev/block/mmcblk0p8 is my /data (according to the fstab)
after that i was able to mount /data !!!
i flashed cwm 5.5.0.4 again via odin, flashed (odin) stock rom (works now!)
Click to expand...
Click to collapse
Can you tell us how you go about formatting your SDCARD? I have a similar problem and can't mount E: data/ whenever I try TWRP or CWM recoveries on my p7300. Can you give us step by step or at least a link where to start. Sorry, I am not familiar with ADB.
Thanks for your support with this tab.
mjramos15 said:
Can you tell us how you go about formatting your SDCARD? I have a similar problem and can't mount E: data/ whenever I try TWRP or CWM recoveries on my p7300. Can you give us step by step or at least a link where to start. Sorry, I am not familiar with ADB.
Thanks for your support with this tab.
Click to expand...
Click to collapse
Try to install a new twrp recovery using the following instructions. That fixed it for me:
http://forum.xda-developers.com/showthread.php?t=2602188
Hey guys.
So i have this razr i with TWRP 2.8.0.0 recovery installed on my phone and my bootloader is unlocked. I have installed several diferent roms on it over time, and this time i tried to install the unofficial Cyanogenmod 11 (http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855) but things went totally wrong when i formated the phone on recovery.
Here's what i did:
1- booted into recovery
2- went to the "wipe" tab
3- taped on "advanced wipe" and selected eveything (Dalvik cache/System/Cache/Data/Internal storage/Micro SDcard), then started formatting
4- after about an hour and a half it was still checking for md5... so i rebooted
5- when i rebooted i realized that everything was gone, including the rom files on the sdcard, so i passed the files from my pc again and tried to install but nothing happend.
6- now for unkown reasons all i see is:
Code:
E: Unable to mount '/data'
E: unable to recreate /data/media folder.
Updating partition details...
E: unable to mount '/data'
E: unable to mount internal 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
So... My PC has the motorola drivers installed and i've also tried on mac (i have a Macbook pro with widows and mac os), but none of the recognize my phone so i can't use adb or anything that could help with this.
Does anyone know what to do? I just want to install stock jellybean again and then try the cm11 rom.
adrex9 said:
Hey guys.
So i have this razr i with TWRP 2.8.0.0 recovery installed on my phone and my bootloader is unlocked. I have installed several diferent roms on it over time, and this time i tried to install the unofficial Cyanogenmod 11 (http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855) but things went totally wrong when i formated the phone on recovery.
Here's what i did:
1- booted into recovery
2- went to the "wipe" tab
3- taped on "advanced wipe" and selected eveything (Dalvik cache/System/Cache/Data/Internal storage/Micro SDcard), then started formatting
4- after about an hour and a half it was still checking for md5... so i rebooted
5- when i rebooted i realized that everything was gone, including the rom files on the sdcard, so i passed the files from my pc again and tried to install but nothing happend.
6- now for unkown reasons all i see is:
Code:
E: Unable to mount '/data'
E: unable to recreate /data/media folder.
Updating partition details...
E: unable to mount '/data'
E: unable to mount internal 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
So... My PC has the motorola drivers installed and i've also tried on mac (i have a Macbook pro with widows and mac os), but none of the recognize my phone so i can't use adb or anything that could help with this.
Does anyone know what to do? I just want to install stock jellybean again and then try the cm11 rom.
Click to expand...
Click to collapse
Can you boot into recovery? maybe you can try adb sideload.
Setarcos said:
Can you boot into recovery? maybe you can try adb sideload.
Click to expand...
Click to collapse
Yes i can, bootloader and recovery, but as i said my phone isn't recognized so adb sideload does not work.
I tried using mac because i read somewhere that you don't need drivers on there, but it didn't work either... unless i'm doing something wrong
adrex9 said:
Yes i can, bootloader and recovery, but as i said my phone isn't recognized so adb sideload does not work.
I tried using mac because i read somewhere that you don't need drivers on there, but it didn't work either... unless i'm doing something wrong
Click to expand...
Click to collapse
I've experienced with similar situation getting no adb in TWRP. However, when I chose Advanced/Adb sideload, adb sideload did work for me.
PS: Maybe you can try install aother recovery.
Hey! Apparently, your phone has now all the partitions corrupt, because of that failed format. Have you tried installing a stock ROM through RSD Lite?
I once had a similar issue, solved it with a clean SBF flash.
Also, to install a new ROM, you should:
1.Boot in TWRP
2.Go to 'Settings'
3.Check 'Use rm -rf instead of formatting.'
Then, the wiping process wont take more than a couple of seconds, and should install ROM's without problems.
Hope you solve it, and sorry for my english if I made any mistakes.
adrex9 said:
Hey guys.
So i have this razr i with TWRP 2.8.0.0 recovery installed on my phone and my bootloader is unlocked. I have installed several diferent roms on it over time, and this time i tried to install the unofficial Cyanogenmod 11 (http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855) but things went totally wrong when i formated the phone on recovery.
Here's what i did:
1- booted into recovery
2- went to the "wipe" tab
3- taped on "advanced wipe" and selected eveything (Dalvik cache/System/Cache/Data/Internal storage/Micro SDcard), then started formatting
4- after about an hour and a half it was still checking for md5... so i rebooted
5- when i rebooted i realized that everything was gone, including the rom files on the sdcard, so i passed the files from my pc again and tried to install but nothing happend.
6- now for unkown reasons all i see is:
Code:
E: Unable to mount '/data'
E: unable to recreate /data/media folder.
Updating partition details...
E: unable to mount '/data'
E: unable to mount internal 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
So... My PC has the motorola drivers installed and i've also tried on mac (i have a Macbook pro with widows and mac os), but none of the recognize my phone so i can't use adb or anything that could help with this.
Does anyone know what to do? I just want to install stock jellybean again and then try the cm11 rom.
Click to expand...
Click to collapse
Have u read the install instructions? The instructions stated that u needed to use the latest recoverys and u still use the 2.8.0.0 one.
The earlier versions have problems on some phones like the one u have now. Some do have the problem some don't. U can fix it by erasing the userdata through fastboot hopefully or by installing touchcwm (the earliest of recoverys for this device) and formatting it that way. Most of the time this fixes the problem.
casquee said:
Hey! Apparently, your phone has now all the partitions corrupt, because of that failed format. Have you tried installing a stock ROM through RSD Lite?
I once had a similar issue, solved it with a clean SBF flash.
Also, to install a new ROM, you should:
1.Boot in TWRP
2.Go to 'Settings'
3.Check 'Use rm -rf instead of formatting.'
Then, the wiping process wont take more than a couple of seconds, and should install ROM's without problems.
Hope you solve it, and sorry for my english if I made any mistakes.
Click to expand...
Click to collapse
hi, i've tried rsd lite allready but my pc didn't see it.
i'll try what you said, maybe it helps
Hazou said:
Have u read the install instructions? The instructions stated that u needed to use the latest recoverys and u still use the 2.8.0.0 one.
The earlier versions have problems on some phones like the one u have now. Some do have the problem some don't. U can fix it by erasing the userdata through fastboot hopefully or by installing touchcwm (the earliest of recoverys for this device) and formatting it that way. Most of the time this fixes the problem.
Click to expand...
Click to collapse
yeah, but the thing is that hadn't even installed it yet, it was just the format the f'd it up installing touch cwm is my goal right now though
casquee said:
Hey! Apparently, your phone has now all the partitions corrupt, because of that failed format. Have you tried installing a stock ROM through RSD Lite?
I once had a similar issue, solved it with a clean SBF flash.
Also, to install a new ROM, you should:
1.Boot in TWRP
2.Go to 'Settings'
3.Check 'Use rm -rf instead of formatting.'
Then, the wiping process wont take more than a couple of seconds, and should install ROM's without problems.
Hope you solve it, and sorry for my english if I made any mistakes.
Click to expand...
Click to collapse
i tried what you said but i still get this problem:
Code:
E; Unable to mount '/data'
E: unable to mount internal storage.
EDIT:
By the way, how do you do an SBF flash?
You have to download one from your region. You can make it to the fastboot menu? And it doesn't detect the phone?
casquee said:
You have to download one from your region. You can make it to the fastboot menu? And it doesn't detect the phone?
Click to expand...
Click to collapse
yeah, i can get into fastboot but the pc does not recognize it. its as if it would be off, nothing happens when you connect it to the pc
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.
This problem has been solved by @Didgesteve
Thank you very much, Didgesteve!
For everyone who is a genius(like me), read his post.
Hi Community,
short story: my device seems kind'a bricked, because i am not able to install a rom via twrp; error: unable to mount /data /cache and /system.
What I did:
I unlocked my bootloader via the official sony method > everything worked flawlessly
I bootet my device into fastboot mode and flashed twrp onto it > everything still workes fine
I wiped /data /cache and /system according to the normal cm13.0 installation process > still finr
I installed the cm13.zip from an external sd-card > no errors
I installed the gapps.zip from the sd-card > Nothing unusual
I booted into cm13, configured it and installed some apps > works as usual
I noticed that a new version of the rom was published, so I booted into twrp > worked
I wiped /data /cache and /system > worked
I reallized, that i could flash my external sd-card, too because i wanted to install the new cm13-version via adb-sideload > now the errors came in
So i thougt retrying wiping /data /cache and /system and the same errors occured > holy sh*t
Last I tried simply installing the cm13.zip from the external sd-card > same errors
What the errors are for wiping(those for install are basically the same:
Code:
could not mount /data and unable to find crypto footer
failed to mount /data (no such device)
Unable to recreate /data/media folder
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Unable to mount storage
Same goes for using the official cyanogen recovery and other cyanogenmod versions.
I am also not able to find/mount it via adb shell.
The images, etc:
CM13: http://forum.xda-developers.com/z3-compact/development/rom-cm13-t3277402/page7 version by @nelvinchi on 25th February 2016, 12:39 PM
TWRP: https://twrp.me/devices/sonyxperiaz3compact.html
Gapps: https://www.androidfilehost.com/?fid=24269982087021755
Additional information:
OS: Mac OSX El Capitan and Linux Mint 17.3
Sd-Card: SanDisk Ultra 64GB micro sdxc
Phone: Sony Xperia Z3 Compact D5803 (colorrange)
My ideas for fixing this:
-manually adding the partitions via adb shell
+required: correct partiton table and adb commands
+don't now, if this would work
Hope i didn't miss anything and there is someone out there, how can help me,
yours sincerely,
Niggl
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Have you got flashtool working? Have you tried pushing a stock tft? to see if you can repair it?
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
The chances of being able to repair it back into CM are slim, I suspect you're going to have to start from scratch, get stock working then go back to CM after.
**SOLVED**
Thank you for your help!
Didgesteve said:
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Click to expand...
Click to collapse
The partition tables were(because of bull**** or something like that) corrupted(I checked it: not because of the wiping, but i will not wipe /system at an update in the future)
Didgesteve said:
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
Click to expand...
Click to collapse
I can boot into recovery and fastboot/flash mode.
Xperia companion and sony bridge are both not working because of "modified software".
Flashtool worked for the stock tft.
So THANK YOU VERY MUCH,
you are my savior!
I hope nobody else, will be a genius like me
Thx again,
Niggl1999
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: