TWRP cannot access internal storage. - OnePlus X Q&A, Help & Troubleshooting
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
Related
[Q] TWRP will not mount or recognize OS
After I installed EnergyRom I have been having issues with TWRP (not blaming EnergyRom). I was trying to make a backup and I kept getting an error stating my SDcard did not have enough space (tried both internal and external, both had plenty of space). I tried another SD card, even reformatted it, but to no avail. I then upgraded TWRP 2.2 to 2.4 and then TWRP got really funky. It no longer recognizes or lists any files, keep getting unable to mount errors, and will not let me reboot, giving an error message 'No OS found'. But when I manually reboot everything seems to work just fine. Just updated to 2.5 and same exact issue(s). It also wont let me save the log file, so I am writing here: E: Unable to find partition size for '/misc' E: Unable to find partition size for '/staging' E: Unable to find partition size for '/data' E: Unable to find partition size for '/boot'' E: Unable to find partition size for '/recovery' Updating partition details... E: Unable to mount '/system' E: Unable to mount '/cache' E: Unable to mount '/cache' E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log' E: Unable to set emmc bootloader message. E: Unable to mount '/cache' Updating partition details... E: Unable to mount '/system' E: Unable to mount '/cache' Any help would be greatly appreciated.
SS823 said: After I installed EnergyRom I have been having issues with TWRP (not blaming EnergyRom). I was trying to make a backup and I kept getting an error stating my SDcard did not have enough space (tried both internal and external, both had plenty of space). I tried another SD card, even reformatted it, but to no avail. I then upgraded TWRP 2.2 to 2.4 and then TWRP got really funky. It no longer recognizes or lists any files, keep getting unable to mount errors, and will not let me reboot, giving an error message 'No OS found'. But when I manually reboot everything seems to work just fine. Just updated to 2.5 and same exact issue(s). It also wont let me save the log file, so I am writing here: E: Unable to find partition size for '/misc' E: Unable to find partition size for '/staging' E: Unable to find partition size for '/data' E: Unable to find partition size for '/boot'' E: Unable to find partition size for '/recovery' Updating partition details... E: Unable to mount '/system' E: Unable to mount '/cache' E: Unable to mount '/cache' E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log' E: Unable to set emmc bootloader message. E: Unable to mount '/cache' Updating partition details... E: Unable to mount '/system' E: Unable to mount '/cache' Any help would be greatly appreciated. Click to expand... Click to collapse Please tell me you didn't flash a normal twrp on the new 4.2.1 bootloader.
It would appear that you're recovery isn't compatible with your bootloader, or device all together. It also may be worth asking how you arrived at your new rom - 1. Initial steps, flashing recovery, etc 2. Clearing caches, factory resets, wiping x3, etc 3. Flash new rom, reboot let settle. If you've just moved to the custom rom, and the recovery was working fine prior to the new rom, list what you were coming from and going to, maybe I can help. I'm not intimately familiar with the Eee Pad but hopefully we can figure this out.
milestoneiii said: It would appear that you're recovery isn't compatible with your bootloader, or device all together. It also may be worth asking how you arrived at your new rom - 1. Initial steps, flashing recovery, etc 2. Clearing caches, factory resets, wiping x3, etc 3. Flash new rom, reboot let settle. If you've just moved to the custom rom, and the recovery was working fine prior to the new rom, list what you were coming from and going to, maybe I can help. I'm not intimately familiar with the Eee Pad but hopefully we can figure this out. Click to expand... Click to collapse You don't need to figure it out mate.. I know exactly what he has done. My post above wasn't really a question. That is what he has done.
JB TWRP flumpster said: You don't need to figure it out mate.. I know exactly what he has done. My post above wasn't really a question. That is what he has done. Click to expand... Click to collapse I upgraded the bootloader to 4.2 when I updated to Energy ROM. It was working just fine (the ROM is still working just fine), I was able to make a back-up. A few days later I wanted to flash another ROM, went to make a backup and then (see initial post). All the TWRP updates I did (2.4 and 2.5) are the JB blobs. When you say 'normal' bootloader what exactly do you mean, ICS?
SS823 said: I upgraded the bootloader to 4.2 when I updated to Energy ROM. It was working just fine (the ROM is still working just fine), I was able to make a back-up. A few days later I wanted to flash another ROM, went to make a backup and then (see initial post). All the TWRP updates I did (2.4 and 2.5) are the JB blobs. When you say 'normal' bootloader what exactly do you mean, ICS? Click to expand... Click to collapse When you had the first problem that would have been some silly problem. What came next is the problem. Energy and Hairybeans new versions are using the 4.2.1 bootloader. The versions of TWRP for ICS and Jellybean are not compatible with the 4.2.1 bootloader and gives the error you describe where nothing can mount. There are loads of people over on the TF300 forums who have done the same and bricked. In the 4.2.1 upgrade zips that NRG and myself provide there is a custom version of TWRP included that will work on the new 4.2.1 bootloader. On my thread (Hairybean) I have warnings all over the first post telling people not to install a "normal" version of TWRP onto the 4.2.1 bootloader and to use the downgrade zip if they want to go back to 4.1.1 bootloader and normal TWRP. Have a read of my last few posts on here and see if any of the ways will fix you. http://forum.xda-developers.com/showthread.php?p=40141480#post40141480 I will probably have to supply you with the Modded TWRP for 4.2.1 in blob file format also. If you need it let me know.
Thanks Flumpster. I was careful to use the Energy update but obviously lacked some common sense when updating the TWRP. If you wouldn't mind passing the modded TWRP blob I'd appreciate it. Can I extract it from your hairybean update zip?
SS823 said: Thanks Flumpster. I was careful to use the Energy update but obviously lacked some common sense when updating the TWRP. If you wouldn't mind passing the modded TWRP blob I'd appreciate it. Can I extract it from your hairybean update zip? Click to expand... Click to collapse No because that blob file contains the bootloader, recovery and partition table all in one. I will be at my computer in 20 mins and will upload it here. ---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ---------- Here is the blob recovery file for 4.2.1 bootloader. http://flumpster.lolcakes.com/android/twrp.blob Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread. fastboot -i 0x0b05 flash recovery twrp.blob If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android. su dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot normally (NOT to recovery) to complete installation.
Flumpster, thanks TWRP works fine and am backing up now. I still have the same issue of it saying I do not have enough room on my external, though I have over a gig of extra room, I am just going to save to the internal and then transfer it. Any idea why it reads only part of my external? Anyway, thanks again!
Wow Flumpster, I'm impressed with your helpfulness and willingness to lend your development skills! It's hard to find people willing to simply explain where someone goes wrong and provide them with the tools to correct it so efficiently. Hats off to you sir! Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
milestoneiii said: Wow Flumpster, I'm impressed with your helpfulness and willingness to lend your development skills! It's hard to find people willing to simply explain where someone goes wrong and provide them with the tools to correct it so efficiently. Hats off to you sir! Sent from my SAMSUNG-SGH-I957 using Tapatalk 2 Click to expand... Click to collapse Yeah, Flumpster, big thank you! Cheers
SS823 said: Yeah, Flumpster, big thank you! Cheers Click to expand... Click to collapse You're welcome mate.. Glad it's all sorted.
flumpster said: No because that blob file contains the bootloader, recovery and partition table all in one. I will be at my computer in 20 mins and will upload it here. ---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ---------- Here is the blob recovery file for 4.2.1 bootloader. http://flumpster.lolcakes.com/android/twrp.blob Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread. fastboot -i 0x0b05 flash recovery twrp.blob If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android. su dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot normally (NOT to recovery) to complete installation. Click to expand... Click to collapse The 2nd solution works for me.... You are the man flumpster... !! :good::good: Thank you
flumpster said: No because that blob file contains the bootloader, recovery and partition table all in one. I will be at my computer in 20 mins and will upload it here. ---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ---------- Here is the blob recovery file for 4.2.1 bootloader. http://flumpster.lolcakes.com/android/twrp.blob Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread. fastboot -i 0x0b05 flash recovery twrp.blob If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android. su dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot normally (NOT to recovery) to complete installation. Click to expand... Click to collapse Thanks for this flumpster it saved my aaaaaaasssss! The 2nd method worked for me.
alfalvarez81 said: Thanks for this flumpster it saved my aaaaaaasssss! The 2nd method worked for me. Click to expand... Click to collapse Flumpster - YOU ARE THE MAN! Your first solution worked like a charm for me. I have been stumped as to how to fix this problem and now I am able to create a backup, root, and flash CM 10.1! Cheers!
same issue, cant work around it I did the same thing, installing a newer generic twrp and get the same password prompt. I have one more wrinkle though that fastboot isnt working normally. I get twrp 2.6 on every boot. I cant do anything with the partitions, it cant enumerate the partition size or it cant mount them. I can push things to tmp and it sees them, but it wont flash them successfully. When i force it into fastboot, if i try to flash something, the command line appears like everything is ok, but the prime has hung at some point. Thats what happened when i tried method 1. If i force it into fastboot and then load android, the system boots. I then tried the second method i get no errors and it looks like it all succeeded. After it tries to reboot, it dumps back into twrp. I was thinking of trying rom manager to flash the recovery back, but havent used it before and i dont know if i can pick the recovery you've given out here. anyone have a tip to help? thanks
same issue, some progress (sorta) I erased my recovery partition through fastboot and tried to flash the trwp.blob here to it. My prime hung. On reboot though it booted into android just fine, my fastboot was fine as well. I can get into fastboot through the normal process, but i have no recovery. when i try to load recovery i get a unrecoverable boot error. So next is i am going to try to verify i have or have no recovery partition and then recreate it and try to flash twrp back into it.
help I am having same problem with prime. Every time I reboot it goes to twrp. 2.6 asking for password, and does not recognize any internal memory or sd card. how ever I can use adb reboot-bootloader, and do a cold boot to Linux and everything works just fine..I would like clarification on your instructions on how to repair. I'm just a novice. Any help will be greatly appreciated.
carlkelly176 said: I am having same problem with prime. Every time I reboot it goes to twrp. 2.6 asking for password, and does not recognize any internal memory or sd card. how ever I can use adb reboot-bootloader, and do a cold boot to Linux and everything works just fine..I would like clarification on your instructions on how to repair. I'm just a novice. Any help will be greatly appreciated. Click to expand... Click to collapse I dont know that i've actually fixed anything or just traded one problem for another. I cannot get a recovery flashed onto my device. My system boots normally and fastboot works, but nothing ive come up with will flash a recovery. On a brighter note, my system is faster, it hasnt bogged down and lagged like it always has. That may be just because of the wiping caches and such though. What i did was erase my recovery partition from fastboot.I've recreated it, i can see it in root explorer. Its about 420mb in size, i dont know if that size is correct. The only things in it are a couple of log files. my whole point in messing with this again was to try to flash the newest CM on it. bluetooth is a bit wonky on mine and i hoped a newer stack would help. good luck. If i get a working recovery, i will post.
I've got the same issue here, except i have a TF300T. I've downloaded the right blob now (4.2 for the TF300) the adb devices command shows my TF300T. Im just wondering now, how do I transfer the file to the 'internal sd card' of the tablet and access it if all i can do is entering the twrp recovery? thanks in advance. EDIT: Found a way to delete the wrong recovery and now im able to access the fastboot mode ok. However, the tablet freezes everytime I use the flash command on fastboot... flumpster said: No because that blob file contains the bootloader, recovery and partition table all in one. I will be at my computer in 20 mins and will upload it here. ---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ---------- Here is the blob recovery file for 4.2.1 bootloader. http://flumpster.lolcakes.com/android/twrp.blob Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread. fastboot -i 0x0b05 flash recovery twrp.blob If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android. su dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot normally (NOT to recovery) to complete installation. Click to expand... Click to collapse
[Q] [HELP] please please help me
Hi guys. I am trying to root my father's HTC desire 601 the whole day. After unlocking bootloader I had this problem : E: Can`t mount /cashe/recovery/command E: Can`t mount /cashe/recovery/log E: Can`t open /cashe/recovery/log E: Can`t mount /cashe/recovery/last_log E: Can`t open /cashe/recovery/log E: Can`t mount /cashe/recovery/last _install E: Can`t open /cashe/recovery/last_install I was looking for some advices here and when I was (I think) really close I do some missclicks and it happened something wrong (I think that I somehow delete stock rom and recovery if it is possible). My current situation is: unlocked bootloader and no root, S-ON, hboot-2.22.0000 when I turn my phone on by standard way (or reboot or go to recovery) it automaticaly goes to bootloader after short blink of HTC logo, I can´t do factory reset or anything other action from menu (always stack in bootloader) I have tried to lock bootloader (no response). Do you anyone know if it is possible to get my father´s phone to stock or any function condition, please? I am absolutely helpless. Thank you very much. Best regards Richard
rajchard said: Hi guys. I am trying to root my father's HTC desire 601 the whole day. After unlocking bootloader I had this problem : E: Can`t mount /cashe/recovery/command E: Can`t mount /cashe/recovery/log E: Can`t open /cashe/recovery/log E: Can`t mount /cashe/recovery/last_log E: Can`t open /cashe/recovery/log E: Can`t mount /cashe/recovery/last _install E: Can`t open /cashe/recovery/last_install I was looking for some advices here and when I was (I think) really close I do some missclicks and it happened something wrong (I think that I somehow delete stock rom and recovery if it is possible). My current situation is: unlocked bootloader and no root, S-ON, hboot-2.22.0000 when I turn my phone on by standard way (or reboot or go to recovery) it automaticaly goes to bootloader after short blink of HTC logo, I can´t do factory reset or anything other action from menu (always stack in bootloader) I have tried to lock bootloader (no response). Do you anyone know if it is possible to get my father´s phone to stock or any function condition, please? I am absolutely helpless. Thank you very much. Best regards Richard Click to expand... Click to collapse Unlock back the bootloader, then download twrp from here: http://forum.xda-developers.com/showthread.php?t=2874948 Flash it and flash either a custom rom or stock one from here: https://drive.google.com/folderview?id=0B6WBFlAKqe30a2ktU3ZEaUUzSTg&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU I hope it helps. Report if you get stuck somewhere. Sent from my HTC Desire 601
patrik.KT said: Unlock back the bootloader, then download twrp from here: http://forum.xda-developers.com/showthread.php?t=2874948 Flash it and flash either a custom rom or stock one from here: https://drive.google.com/folderview?id=0B6WBFlAKqe30a2ktU3ZEaUUzSTg&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU I hope it helps. Report if you get stuck somewhere. Sent from my HTC Desire 601 Click to expand... Click to collapse Thank you for response. I am stuck in the flash recovery point. I have tried flash two different recoveries and get everytime the same problem: c:\Android>fastboot flash recovery openrecovery-twrp-2.8.1.0-zara.img sending 'recovery' (9568 KB)... OKAY [ 1.108s] writing 'recovery'... (bootloader) signature checking... FAILED (remote: signature verify fail) finished. total time: 1.752s Do you know how can I solve it please?
rajchard said: Thank you for response. I am stuck in the flash recovery point. I have tried flash two different recoveries and get everytime the same problem: c:\Android>fastboot flash recovery openrecovery-twrp-2.8.1.0-zara.img sending 'recovery' (9568 KB)... OKAY [ 1.108s] writing 'recovery'... (bootloader) signature checking... FAILED (remote: signature verify fail) finished. total time: 1.752s Do you know how can I solve it please? Click to expand... Click to collapse Problem solved i will go to next step.
stuck on stock boot screen This worked on my Htc desire 601 after my phone only booted into white screen stock recovery screen. (it would keep rebooting to fastboot screen only, not twrp screen.) using ADB/FASTBOOT TOOLS i had to use command prompt from TOOLS folder to make it work, or else i kept getting errors, could not load file etc. I also put recovery .img in every folder i was using the command prompt until i got it working. Good luck! p.s. i had issues until i formated then full wipe install from twrp screen.
4.09 S-off - Can't factory reset/install, stuck in 'Encryption unsuccessful' bootloop
Hey guys, just ended my contract with Verizon and started using Cricket wireless. Up until this point everything went smoothly, just had to swap out the SIM and not much else. Because I no longer needed/wanted all the bloat and VW apps, I decided to s-off and root; I used Sunshine as I had the stock 4.09.605.5 and no other form of rooting or... soffing?... would work. As of this morning, All of that was accomplished and I was left with a bootloader noted below: Code: [COLOR="Magenta"]*** UNLOCKED ***[/COLOR] [COLOR="Olive"]MONARUDO PVT SHIP S-OFF RH CID-VZW_001 HBOOT-1.57.0000 RADIO-1.02.01.0818 OpenDSP-v12.120.274.0909 OS- eMMC-boot 2048MB Aug 27 2014,13:22:15.0[/COLOR] So at this point, I still had stock rom, but applied s-off, had root, and importantly - I think - I was using the built in android encryption. So at this point I flashed TWRP successfully using the WinDroid Universal toolkit and started the process of installing a new rom, specifically the ★ ☆ [ROM][5.0.1] Google Play Edition | Lollipop | v2.00 [02-06-15] rom, but ran into a few problems. first, I could not backup my current rom at all. I even flashed CWM and tried it there but only got 'Waiting to mount SD Card' timeouts so I switched back to TWRP. On my last try, I received nothing but errors, a selection of them below: Code: [COLOR="Red"]E:Could not mount /data and unable to find crypto footer. E:Unable to mount '/data' E:Unable to recreate /data/media folder.[/COLOR] Updating partition details... [COLOR="red"]E:Unable to mount '/data' E:Unable to mount storage.[/COLOR] ...and so on. I tried searching for fixes to this issue but did not get anywhere, and since I knew i wasn't going back to stock ever again, I pressed on with the install. I used a USB-OTG connection, copied the zip, and installed. There were a couple of similar error messages but the install was reported as successful. Upon rebooting the phone, it loads the Google Play bootloader animation, but the next screen brings up the 'Encryption unsuccessful' notice with the only option to do a factory reset. When I select that, it reboots into recovery, then starts/fails a Factory reset: Code: Running OpenRecovertScript (bunch of errors...) Then recovery closes, the boot animation starts, and then I'm back at the Encryption Unsuccessful messagebox. At this point I do not know how to proceed with fixing this; I have no problem formatting my phone as all my data is backed up elsewhere. I've linked a couple of screenshots to show the errors I am getting located here. Any and all help would be welcome here, thanks and please!!
1.) Never use toolkit to do anything. Use fastboot for flashing recovery. 2.) You need stock recovery installed to use fastboot's factory reset option.
I'm going to need some handholding here, bear with me: 1) I can get to the Fastboot page on my phone, and I can plug it in to get FASTBOOT USB, but adb does not see the device. Nevermind, I used adb and not fastboot. Still not sure on which steps I need to take there. 2) How do I go about reinstalling the stock recovery? Edit: I performed the following fastboot erase functions and got these responses: Code: C:\XXXXXXXXXXX>fastboot erase userdata ******** Did you mean to fastboot format this partition? erasing 'userdata'... FAILED (remote: not allowed) finished. total time: 0.010s C:\XXXXXXXXXXX>fastboot erase cache ******** Did you mean to fastboot format this partition? erasing 'cache'... OKAY [ 0.070s] finished. total time: 0.070s
Since you're unlocked, use fastboot to flash recovery. Once that's done then flash ROMs in recovery. Doas beaups says and don't use toolkits to flash things. If you want to start clean from square one, use an ruu to flash the stock ROM, recovery, etc. Then do as I said above: flash recovery in fastboot then flash a ROM in recovery.
So it turns out it had nothing to do with TWRP or the rom. I used the full format option and it worked, then installed the ROM again and everything works. Mods, feel free to nuke this thread as it's not really helpful in the end.
So the lesson is to make sure your phone is not encrypted before flashing/modifying things,except if you do a full reformat.
No ADB sideload in TWRP on Huawei
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
E:/ I Can't Mount / Cache ASUS Z010D
Good night, I have an ASUS Z010D device that entered a loop, when entering the recovery mode it throws a message E: / I Can't Mount / Cache also when applying any option in the menu it throws a mount error in the E: drive and several directories. I have tried various commands in adb and fastboot but have not been successful. Important: the bootloader locked and I have not managed to unlock it since the computer does not start the operating system. Thanks for the support you can give me!
@jesusz24 Seems to be a TWRP related problem. Or partition /cache doesn't exist.
answer jwoegerbauer said: @jesusz24 Seems to be a TWRP related problem. Or partition /cache doesn't exist. Click to expand... Click to collapse hi jwoegerbauer, if apparently it is a recovery problem. The cache partition allows me to format it without any problem through fastboot, which seems strange to me. The problem really is that I can't root the computer or unlock the bootloader before it loops. at the moment it does not let me install the twrp to try to distribute. Do you have any procedure to unlock the bootloader? thanks for him
@jesusz24 Never have installed TWRP or any other custom recovery on the mobile devices I have and/or I had, hence can't help you with your TWRP problem.