Hi all!
I recieved my new OPX yesterday, brand new from oneplus store.
The phone immediatly updated through the ota to:
OnePlusXOxygen_14_OTA_019_all_201611071506
After that i followed this guide:
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
I installed all the drivers and managed to unlock the bootloader without any problem.
(it said "device tampered: no, device unlocked: yes" using the command: fastboot oem device-info
The problem starts at twrp.
I have downloaded twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img and i can flash it to recovery using
fastboot flash recovery recovery.img (after renaming it to recovery.img)
After that I use the command: fastboot boot recovery.img
I can enter TWRP, but I cannot do anything. It cannot mount anything and on all the storages there is 0mb.
After this I can reboot normal and the normal recovery is back, so my phone isnt bricked or anything like that
I did try to download OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip and flashed it but the twrp problem still persists.
I tried the other twrp for the new bootloader by Nachiket.Namjoshi, but with the same result.
I have no Idea what to do, can anyone help me? Why can´t I access files from twrp?
Does it have something to do with my phone being brand new?
/regards Bror David
brordavid said:
Hi all!
I recieved my new OPX yesterday, brand new from oneplus store.
The phone immediatly updated through the ota to:
OnePlusXOxygen_14_OTA_019_all_201611071506
After that i followed this guide:
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
I installed all the drivers and managed to unlock the bootloader without any problem.
(it said "device tampered: no, device unlocked: yes" using the command: fastboot oem device-info
The problem starts at twrp.
I have downloaded twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img and i can flash it to recovery using
fastboot flash recovery recovery.img (after renaming it to recovery.img)
After that I use the command: fastboot boot recovery.img
I can enter TWRP, but I cannot do anything. It cannot mount anything and on all the storages there is 0mb.
After this I can reboot normal and the normal recovery is back,
so my phone isnt bricked or anything like that
I did try to download OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip and flashed it but the twrp problem still persists.
I tried the other twrp for the new bootloader by Nachiket.Namjoshi, but with the same result.
I have no Idea what to do, can anyone help me? Why can´t I access files from twrp?
Does it have something to do with my phone being brand new?
/regards Bror David
Click to expand...
Click to collapse
Hello, recieved your PM,
I'm guessing something wrong has been done on your part, however, its okay, no harm will be done
from the OP i could infer that your TWRP isnt getting flashed, as (if i understand it correctly) OnePlus Recovery is restored when you reboot
i would suggest you to follow this guide and my recovery.
and when you unlock, always let your phone boot completely before rushing to flashifying stuff.
follow this guide and postback with any info (if more than this)
also, the build number issue is what i cannot confirm, as I have only seen 1 OPX in my life (yes, believe me) and that was mine, since Im currently on a different ROM i cannot post my build number.... @Joshwin Aranha could maybe help you with build number.
Nachiket.Namjoshi said:
Hello, recieved your PM,
I'm guessing something wrong has been done on your part, however, its okay, no harm will be done
from the OP i could infer that your TWRP isnt getting flashed, as (if i understand it correctly) OnePlus Recovery is restored when you reboot
i would suggest you to follow this guide and my recovery.
and when you unlock, always let your phone boot completely before rushing to flashifying stuff.
follow this guide and postback with any info (if more than this)
also, the build number issue is what i cannot confirm, as I have only seen 1 OPX in my life (yes, believe me) and that was mine, since Im currently on a different ROM i cannot post my build number.... @Joshwin Aranha could maybe help you with build number.
Click to expand...
Click to collapse
Thanks for reply!
I believe that I manage to flash twrp. In fastboot I get this:
target reported max download size of 536870912 bytes
sending 'recovery' (15860 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.223s]
finished. total time: 0.726s
I can boot into twrp, and I see the different options (backup, restore, etc), but when I choose backup I cannot choose any storage. All of the storages is listed as 0mb. I can see folders under install menu (boot, cache, data, dev, etc, external_sd.....), but no files appears. In the logs in TWRP I get a lot of errors regarding cannot mount storages.
My only option from here is rebooting into os again, and when I do that, twrp gets overwritten by oneplus recovery.
BTW, all the storages works as they should in OP:s recovery.
The errors im having in twrp are these:
Erimary block device 'dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find partition size for 'boot'
E:Unable to find partition size for 'recovery'
E:Unable to find partition size for 'misc'
E:Unable to find partition size for 'efs1'
E:Unable to find partition size for 'efs2'
E:unable to set bootloader message.
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/firmware' (invalid argument)
Failed to mount '/system' (invalid argument)
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Failed to mount '/persist' (invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Full SELinux support is present
Failed to mount '/cache' (invalid argument)
Failed to mount '/cache' (invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP enabled
As I wrote to Nachiket.Namjoshi, I have compared my phone with a co-workers OPX and there are differences in build numbers
My is:
ONE E1003_15_161107 and my co-worker: ONE E1003_14_161107.
brordavid said:
Thanks for reply!
I believe that I manage to flash twrp. In fastboot I get this:
target reported max download size of 536870912 bytes
sending 'recovery' (15860 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.223s]
finished. total time: 0.726s
I can boot into twrp, and I see the different options (backup, restore, etc), but when I choose backup I cannot choose any storage. All of the storages is listed as 0mb. I can see folders under install menu (boot, cache, data, dev, etc, external_sd.....), but no files appears. In the logs in TWRP I get a lot of errors regarding cannot mount storages.
My only option from here is rebooting into os again, and when I do that, twrp gets overwritten by oneplus recovery.
BTW, all the storages works as they should in OP:s recovery.
The errors im having in twrp are these:
Erimary block device 'dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find partition size for 'boot'
E:Unable to find partition size for 'recovery'
E:Unable to find partition size for 'misc'
E:Unable to find partition size for 'efs1'
E:Unable to find partition size for 'efs2'
E:unable to set bootloader message.
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/firmware' (invalid argument)
Failed to mount '/system' (invalid argument)
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Failed to mount '/persist' (invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (invalid argument)
Failed to mount '/cache' (invalid argument)
Full SELinux support is present
Failed to mount '/cache' (invalid argument)
Failed to mount '/cache' (invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP enabled
As I wrote to Nachiket.Namjoshi, I have compared my phone with a co-workers OPX and there are differences in build numbers
My is:
ONE E1003_15_161107 and my co-worker: ONE E1003_14_161107.
Click to expand...
Click to collapse
Hi there, sorry for joining late to the party
So about the TWRP, I'm not sure what is going on, because the command is correct, and the log you posted is over my head, its kinda mind boggling if the Recovery flashed correctly, which as I understand it did, then it should't throw those errors. @Nachiket.Namjoshi that's your thing bro.
Regarding build numbers, I'm confused, at the outset I'd anyway like you to post a screenshot of your About Phone section, and the other thing, you stated at the beginning of your thread that you OTA updated to OnePlusXOxygen_14_OTA_019_all_201611071506, but in your second reply you say that it say's ONE E1003_15_161107, can you clarify this ? Because as of now I'm still running OnePlusXOxygen_14_OTA_019_all_201611071506, i.e Oxygen OS (OOS) 3.1.4. And my build number is ONE E1003_14_161107.
Joshwin Aranha said:
Hi there, sorry for joining late to the party
So about the TWRP, I'm not sure what is going on, because the command is correct, and the log you posted is over my head, its kinda mind boggling if the Recovery flashed correctly, which as I understand it did, then it should't throw those errors. @Nachiket.Namjoshi that's your thing bro.
Regarding build numbers, I'm confused, at the outset I'd anyway like you to post a screenshot of your About Phone section, and the other thing, you stated at the beginning of your thread that you OTA updated to OnePlusXOxygen_14_OTA_019_all_201611071506, but in your second reply you say that it say's ONE E1003_15_161107, can you clarify this ? Because as of now I'm still running OnePlusXOxygen_14_OTA_019_all_201611071506, i.e Oxygen OS (OOS) 3.1.4. And my build number is ONE E1003_14_161107.
Click to expand...
Click to collapse
Welcome to the party. :laugh:
My co-worker suggested that I should erase recovery before flashing the twrp doing this:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot boot recovery.img
I did this, but I have still problem with twrp.
At first boot after i bought OPX the phone updated itself (cant remember the actual name on that beacuse the system downloaded it, but it was 3.1.4), after that i unlocked bootloader and all the other stuff, usb debugging etc.
After I failed the first time with twrp, I flashed this one hoping that twrp would work after flashing:
OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip (from op:s download page)
Here is a screenshot of my "about phone section"
https://drive.google.com/open?id=0B9XjA60WaKGVSXZ4OHEtdVQ3X0k
Might there be problem with the fastboot/adb environment?
/regards Bror David
brordavid said:
Welcome to the party. :laugh:
My co-worker suggested that I should erase recovery before flashing the twrp doing this:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot boot recovery.img
I did this, but I have still problem with twrp.
At first boot after i bought OPX the phone updated itself (cant remember the actual name on that beacuse the system downloaded it, but it was 3.1.4), after that i unlocked bootloader and all the other stuff, usb debugging etc.
After I failed the first time with twrp, I flashed this one hoping that twrp would work after flashing:
OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip (from op:s download page)
Here is a screenshot of my "about phone section"
https://drive.google.com/open?id=0B9XjA60WaKGVSXZ4OHEtdVQ3X0k
Might there be problem with the fastboot/adb environment?
/regards Bror David
Click to expand...
Click to collapse
no, most likely not.
one final question, as per OP you said you are back into Oxygen Recovery when you reboot to recovery after flashing, is that correct?
im going to leave a method here for you to try.... I'm not sure if it will work as I cannot get handson to your device.. but after reading your issue
only thing that pops up to my mind is: messed up partitions..
here is what you should try:
boot to fastboot mode
use following commands in same order
Code:
[LIST]
[*]fastboot flash recovery recovery.img
[*]fastboot format userdata - [B][COLOR=Red]NOTE: THIS WILL FORMAT YOUR ENTIRE INTERNAL DATA SO BACKUP FIRST[/COLOR][/B]
[*]fastboot boot recovery.img
[/LIST]
reboot to recovery again (to test)
Nachiket.Namjoshi said:
no, most likely not.
one final question, as per OP you said you are back into Oxygen Recovery when you reboot to recovery after flashing, is that correct?
im going to leave a method here for you to try.... I'm not sure if it will work as I cannot get handson to your device.. but after reading your issue
only thing that pops up to my mind is: messed up partitions..
here is what you should try:
boot to fastboot mode
use following commands in same order
Code:
[LIST]
[*]fastboot flash recovery recovery.img
[*]fastboot format userdata - [B][COLOR=Red]NOTE: THIS WILL FORMAT YOUR ENTIRE INTERNAL DATA SO BACKUP FIRST[/COLOR][/B]
[*]fastboot boot recovery.img
[/LIST]
reboot to recovery again (to test)
Click to expand...
Click to collapse
No, I can boot into TWRP, but I cannot flash/backup anything at all in TWRP as I cannot access the storages.
After I reboot from TWRP to OOS TWRP gets overwritten and Oxygen Recovery is back.
I cannot backup anything. I'm not rooted
Will the OS also disappear?
brordavid said:
No, I can boot into TWRP, but I cannot flash/backup anything at all in TWRP as I cannot access the storages.
After I reboot from TWRP to OOS TWRP gets overwritten and Oxygen Recovery is back.
I cannot backup anything. I'm not rooted
Will the OS also disappear?
Click to expand...
Click to collapse
well you can backup your data in internal storage, it gonna be gone if you use that command, but hopefully its worth it (90% chance)
EDIT: you should really try those steps. im 9-% positive that should solve the problem
Nachiket.Namjoshi said:
well you can backup your data in internal storage, it gonna be gone if you use that command, but hopefully its worth it (90% chance)
EDIT: you should really try those steps. im 9-% positive that should solve the problem
Click to expand...
Click to collapse
Sorry, it didnt work. All the steps seems fine (as you can see).
C:\Users\David\Downloads\Oneplus X (onyx)\twrp variant två ny bootloader>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15860 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 0.222s]
finished. total time: 0.727s
C:\Users\David\Downloads\Oneplus X (onyx)\twrp variant två ny bootloader>fastboot format userdata
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.877s]
sending 'userdata' (136970 KB)...
OKAY [ 4.294s]
writing 'userdata'...
OKAY [ 1.809s]
finished. total time: 7.989s
C:\Users\David\Downloads\Oneplus X (onyx)\twrp variant två ny bootloader>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.500s]
booting...
OKAY [ 0.026s]
finished. total time: 0.531s
I can enter twrp, but all the errors are still there.
I also tried to reboot from twrp to twrp, and twrp is still there, but with all the errors.
TWRP takes a while to boot, but I guess thats beacuse of all the mounting errors.
(I tried all of your steps twice)
It's strange, because in oxygen recovery everything is mountable..
I'm really grateful that you are helping me. Any other suggestions?
I have exactly the same symptoms on my new OPX, got it last Thursday. mfg 13.11.2016
ONE E1003
/ Mattias
Mattias N said:
I have exactly the same symptoms on my new OPX, got it last Thursday. mfg 13.11.2016
ONE E1003
/ Mattias
Click to expand...
Click to collapse
Thank god I'm not alone.
It must be something hardware wise then?
A little update.
I had a remote session today with oneplus support (they are really helpful!) and I guess they did some kind of brick restore thingy. It didn't work. After the remote session the phone stops at the oneplus logo (but now I can't access storages in oxygen recovery either) , so I'm returning the phone and letting oneplus repair it.
I'll keep you updated when there are more news.
Thanks for your help here at xda, oneplus x has a great community here.
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Oneplus_X_Flasher said:
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Click to expand...
Click to collapse
Another with the same problem. There is something strange going on. Have you tried a remote session with oneplus or are you returning it?
I know I shouldn't think like this, but it feels good not being the only one with this problem. =)
hello, yes we tried a remote session with oneplus but the technican also can't help. Yes! something strange ist going on with the newer OPX Generation. Three OPX with DOM 2015 no problem to Flash CM13 and this one with DOM 2016 unable to Mount Partition in Recovery
in this thread, is perhaps the same problem...only already destroyed with the original Rescue Builder from OP http://forum.xda-developers.com/oneplus-x/help/bricked-oneplus-x-removable-drive-t3518620/page2
Same problem here
I received new onyx yesterday. I have exactly the same problem!!! tried the same things.
I didnt have these problems on my last onyx
do you have OOS 3 or OOS 2 on your new OnePlus X? I think the problem is a bug in OOS3/Android 6
Oneplus_X_Flasher said:
hello, yes we tried a remote session with oneplus but the technican also can't help. Yes! something strange ist going on with the newer OPX Generation. Three OPX with DOM 2015 no problem to Flash CM13 and this one with DOM 2016 unable to Mount Partition in Recovery
in this thread, is perhaps the same problem...only already destroyed with the original Rescue Builder from OP http://forum.xda-developers.com/oneplus-x/help/bricked-oneplus-x-removable-drive-t3518620/page2
Click to expand...
Click to collapse
I am one of the people who had a bricked device (black screen, white led) and was lucky (tricked them) to get my device/mainboard exchanged, see http://forum.xda-developers.com/oneplus-x/help/bricked-oneplus-x-removable-drive-t3518620/page2
I was on ONE E1003_14_161107 before and now with the new mainboard I also have ONE E1003_15_161107 and twrp can't find the partitions.
After I read your post I am sure ONE E1003_15_161107 is a build to stop twrp from working and so stop people rooting and messing with their phones.
i dont think so...oneplus has no problems with the rooter and flasher so why do that intentionally?^^ the support also dont know about the problem with the locked internal Storage.
where do i find the " ONE E1003_15_161107" ? is it on the sticker of the original Oneplus X Box?
you can find it in Settings --> about phone --> Build number
I have also ONE E1003_15_161107
Hi
I'm running TWRP 3.3.1 and am rooted. I have no ADB sideload, at least it appears to be loading but does nothing.
I think the problem(you tell me)is that TWRP repeatedly shows the /data partition as not mounting e.g. 'Failed to mount /data (invalid argument)'. Whenever one attempts to carry out a process with TWRP this always comes up.
I have tried the following:
1) Repair the partition with e2fcsk
2) Change the filesystem to fat or ext3 and then back to ext4.
3) Wipe the partition
Still no go. This can't be normal. I should say I'm running ADB and Fastboot from linux and all commands work so it can't be a driver problem. The device is being seen.
I have googled this but there are no clear answers.
thanks
Cliff
cliffhanger54 said:
Hi
I'm running TWRP 3.3.1 and am rooted. I have no ADB sideload, at least it appears to be loading but does nothing.
I think the problem(you tell me)is that TWRP repeatedly shows the /data partition as not mounting e.g. 'Failed to mount /data (invalid argument)'. Whenever one attempts to carry out a process with TWRP this always comes up.
I have tried the following:
1) Repair the partition with e2fcsk
2) Change the filesystem to fat or ext3 and then back to ext4.
3) Wipe the partition
Still no go. This can't be normal. I should say I'm running ADB and Fastboot from linux and all commands work so it can't be a driver problem. The device is being seen.
I have googled this but there are no clear answers.
thanks
Cliff
Click to expand...
Click to collapse
I'm going to try downgrading TWRP
I'm going to try downgrading TWRP
cliffhanger54 said:
I'm going to try downgrading TWRP
Click to expand...
Click to collapse
Seems to have worked . Why? This was on Huawei 5c
Cliff
cliffhanger54 said:
Seems to have worked . Why? This was on Huawei 5c
Cliff
Click to expand...
Click to collapse
Seems I was premature. Mounting of /data cured, sideload not still doesn't work
Hello,
the device was downgraded and rooted using bibikalka howto few years ago
now it is bricked for unknown reason
it stacks on Fire logo and if I am booting to the recovery mode and trying "wipe cache partition" or "wipe data/factory reset" then
it shows the error "failed to mount cache (Invalid argument)"
how can I unbrick it ?
nicktm said:
Hello,
the device was downgraded and rooted using bibikalka howto few years ago
now it is bricked for unknown reason
it stacks on Fire logo and if I am booting to the recovery mode and trying "wipe cache partition" or "wipe data/factory reset" then
it shows the error "failed to mount cache (Invalid argument)"
how can I unbrick it ?
Click to expand...
Click to collapse
Either reinstall the firmware via adb sideload, or if you want to root again, downgrade to 4.5.3 using the adb sideload and then follow one of the tutorials to root and install another lollipop Rom.
I have tried to run:
adb sideload update-kindle-20.4.5.3.bin
but got:
E:failed to mount /cache
E:failed to set up expected mounts for install; aborting
Installation aborted.
Drunkpilot said:
Either reinstall the firmware via adb sideload, or if you want to root again, downgrade to 4.5.3 using the adb sideload and then follow one of the tutorials to root and install another lollipop Rom.
Click to expand...
Click to collapse
I have tried to run:
adb sideload update-kindle-20.4.5.3.bin
but got:
E:failed to mount /cache
E:failed to set up expected mounts for install; aborting
Installation aborted.