Related
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Sounds like uv messed up the partitions. unsure if theres a fix on this
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
jd1639 said:
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
Click to expand...
Click to collapse
This is happening without any problems but it does not change the problem.
I'm lost ...
in TWRP i have
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
worfeur said:
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
Click to expand...
Click to collapse
What version of twrp are you using?
jd1639 said:
What version of twrp are you using?
Click to expand...
Click to collapse
I use twrp 2.6.3.2
worfeur said:
I use twrp 2.6.3.2
Click to expand...
Click to collapse
Try to flash this in fastboot, fastboot flash recovery recovery.img. Where recovery.img is the file below. If it installs, wipe cache within it
http://d-h.st/nbu. It's 2.6.3.4
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
N5
1. you unlock it
2. recovery with software.
Thanks
Wergin said:
1. you unlock it
2. recovery with software.
Thanks
Click to expand...
Click to collapse
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
worfeur said:
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Click to expand...
Click to collapse
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
WoodburyMan said:
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
Click to expand...
Click to collapse
Sorry, I do not know the firmware that was installed
It is a device used
habitformer said:
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
Click to expand...
Click to collapse
when I flash a custom-recovery (stock or cwn) TWRP 2.6.3.2 always returns
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
WoodburyMan said:
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
Click to expand...
Click to collapse
thank you for your help
I have access to adb fastboot mode by boot recovery.img (recovery stock google)
and using the control slidload ADB
but impossible to get the command line
but when I type ADB Devices, my phone is found
otherwise I can not do a stock restoration because the bootloader does not update (KKX11D then I flashed back KKX11K) when I do well:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Beauenheim said:
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
Click to expand...
Click to collapse
thank you I'll try it tonight but I think I already tried
worfeur said:
thank you I'll try it tonight but I think I already tried
Click to expand...
Click to collapse
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
jd1639 said:
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
Click to expand...
Click to collapse
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
worfeur said:
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
Click to expand...
Click to collapse
Can you format data in 2.6.3.2? I'm thinking you have a bigger problem as you've already tried to flash the factory image and it did not work.
Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
You must use fastboot commands while being into the bootloader, not adb.
mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.
ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.
This is my friend's phone and when she showed me, it was asking for android's password with the title "Decryption unsuccessful".
I then tried mi-flash and it didn't gave any errors but when it rebooted it went to fastboot screen. It was on latest MIUI7 stable when this happened. I tried formatting again from recovery, I got the below error logs.
/data, /system and /cache - (invalid argument)
Even recovery is gone and it only boots to fastboot screen. I can only go to recovery by doing
fastboot boot recovery.img (recovery is twrp 3.0.2-0) from fastboot.
I think the only possible way is to full format the partitions and bring it to stock but I am not finding any threads to point me to proper directions. Any one here care to help revive this mi4i.
warlord060816 said:
This is my friend's phone and when she showed me, it was asking for android's password with the title "Decryption unsuccessful".
I then tried mi-flash and it didn't gave any errors but when it rebooted it went to fastboot screen. It was on latest MIUI7 stable when this happened. I tried formatting again from recovery, I got the below error logs.
/data, /system and /cache - (invalid argument)
Even recovery is gone and it only boots to fastboot screen. I can only go to recovery by doing
fastboot boot recovery.img (recovery is twrp 3.0.2-0) from fastboot.
I think the only possible way is to full format the partitions and bring it to stock but I am not finding any threads to point me to proper directions. Any one here care to help revive this mi4i.
Click to expand...
Click to collapse
Anyway
Can i ask you,your friend using ext4 or f2fs??
I faced this issue if i format my data partition as f2fs at miui
Yeah, full format is good
faizauthar12 said:
Anyway
Can i ask you,your friend using ext4 or f2fs??
I faced this issue if i format my data partition as f2fs at miui
Yeah, full format is good
Click to expand...
Click to collapse
Thanks for replying.
I have the phone with me so I can answer queries right away. Its in ext4 format. Didn't tried f2fs. but the recovery I have, is not providing me f2fs file system type? How did you get that?
no idea, on doing full format. any thread links, please?
warlord060816 said:
Thanks for replying.
I have the phone with me so I can answer queries right away. Its in ext4 format. Didn't tried f2fs. but the recovery I have, is not providing me f2fs file system type? How did you get that?
no idea, on doing full format. any thread links, please?
Click to expand...
Click to collapse
here is a step
http://forum.xda-developers.com/showpost.php?p=35368127&postcount=7
about recovery here
faizauthar12 said:
here is a step
http://forum.xda-developers.com/showpost.php?p=35368127&postcount=7
about recovery here
Click to expand...
Click to collapse
I followed the format instruction and successfully formatted userdata, system and cache but when I went to recovery to wipe the partitions it again said the same thing (Failed to mount '/system' (invalid argument) and the same error for cache and data.
warlord060816 said:
I followed the format instruction and successfully formatted userdata, system and cache but when I went to recovery to wipe the partitions it again said the same thing (Failed to mount '/system' (invalid argument) and the same error for cache and data.
Click to expand...
Click to collapse
which recovery you're using?
why you wipe your system data and cache?
what do you want to do? (flash a rom,explain it )
faizauthar12 said:
which recovery you're using?
why you wipe your system data and cache?
what do you want to do? (flash a rom,explain it )
Click to expand...
Click to collapse
Recovery - twrp 3.0.2-0
Those mounts were not visible when I check the mounts using df command and for the above errors I tried to format as it showed successful operation.
I have the latest fastboot rom for flashing but unless the mounts work, I am hopeless.
Here are the recovery logs
Below output shows that userdata partition is encrypted. I think this is preventing the partitions to be mounted
warlord060816 said:
Recovery - twrp 3.0.2-0
Those mounts were not visible when I check the mounts using df command and for the above errors I tried to format as it showed successful operation.
I have the latest fastboot rom for flashing but unless the mounts work, I am hopeless.
Here are the recovery logs
Click to expand...
Click to collapse
how about using TWRP unofficial ?
a weird error i ever seen till now
faizauthar12 said:
how about using TWRP unofficial ?
a weird error i ever seen till now
Click to expand...
Click to collapse
I'm eager to try the twrp you have linked but just wanted to ask few qs.
1. The version I am using is also listed in the link you've provided. Is there a way to check or after flashing I would find differences in the functionality?
2. Which version you want me to try?
3. Since I updated my above post with the image showing the encryption flag on data partition, can that be fixed in your unofficial TWRP you've linked?
warlord060816 said:
I'm eager to try the twrp you have linked but just wanted to ask few qs.
1. The version I am using is also listed in the link you've provided. Is there a way to check or after flashing I would find differences in the functionality?
2. Which version you want me to try?
3. Since I updated my above post with the image showing the encryption flag on data partition, can that be fixed in your unofficial TWRP you've linked?
Click to expand...
Click to collapse
well, just give it a try
since i'm using my own unofficial(because it has f2fs )
i'm not face any of those error
which Miui you're using??
i think any of rom and recovery just support miui6
faizauthar12 said:
well, just give it a try
since i'm using my own unofficial(because it has f2fs )
i'm not face any of those error
which Miui you're using??
i think any of rom and recovery just support miui6
Click to expand...
Click to collapse
tried the latest in the twrp folder. I was using just the previous of the latest version and got the same result when tried "Format Data" as it said it will also remove the encryption.
I also tried to flash the latest mokee build below are the screen snaps of the logs
Reboot to recovery is also not working and it loads to fastboot screen.
Edit: Previously when i tried flash_all in miflash it gave me error:
0x80004005: FAILED (remote: failed to write partition) at the line where it invokes flash partition command.
warlord060816 said:
tried the latest in the twrp folder. I was using just the previous of the latest version and got the same result when tried "Format Data" as it said it will also remove the encryption.
I also tried to flash the latest mokee build below are the screen snaps of the logs
Reboot to recovery is also not working and it loads to fastboot screen.
Click to expand...
Click to collapse
okay, now i see you're using otg (case 1)(i never used OTG for flash any files)
how about format data from fastboot ?
which miui you're using?
faizauthar12 said:
okay, now i see you're using otg (case 1)(i never used OTG for flash any files)
how about format data from fastboot ?
which miui you're using?
Click to expand...
Click to collapse
Fastboot MIUI version - ferrari_global_images_V7.5.1.0
I tried the format data command from fastboot. If you are referring to "fastboot format userdata" , then it was successful. I tried again and below is the log.
warlord060816 said:
Fastboot MIUI version - ferrari_global_images_V7.5.1.0
I tried the format data command from fastboot. If you are referring to "fastboot format userdata" , then it was successful. I tried again and below is the log.
Click to expand...
Click to collapse
somebody(i forget who is he)
said to me that when using miui 7,you will got a lots of trouble when using TWRP
use any of miui 6 firmware
faizauthar12 said:
somebody(i forget who is he)
said to me that when using miui 7,you will got a lots of trouble when using TWRP
use any of miui 6 firmware
Click to expand...
Click to collapse
I was thinking of trying this unbrick-qualcomm-mobiles/. but again this phone is not entering into "Qualcomm HS-USB QDLoader 9008" mode.
Tell me which miui version other than 7 I should try? and if possible link me to that.
Edit: Now downloading this: ferrari_global_images_V6.5.6.0.LXIMICD_5.0_global hoping to fix the partitions if this has those files required like
"rawprogram0.xml"
"patch0.xml"
warlord060816 said:
I was thinking of trying this unbrick-qualcomm-mobiles/. but again this phone is not entering into "Qualcomm HS-USB QDLoader 9008" mode.
Tell me which miui version other than 7 I should try? and if possible link me to that.
Edit: Now downloading this: ferrari_global_images_V6.5.6.0.LXIMICD_5.0_global hoping to fix the partitions if this has those files required like
"rawprogram0.xml"
"patch0.xml"
Click to expand...
Click to collapse
do you mean edl?
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
go to fastboot then use that files
since we only can type reboot edl with adb not fastboot, that thread have a modified fastboot to support reboot edl
tried edl. phone is not going into edl. Well i don't know how it will look like if it goes into edl, right now it boots to fastboot. I don't know if I'm missing anything.
warlord060816 said:
tried edl. phone is not going into edl. Well i don't know how it will look like if it goes into edl, right now it boots to fastboot. I don't know if I'm missing anything.
Click to expand...
Click to collapse
Hey Warlord,
I believe I'm facing the same issue as you did. Have you made any progress?..
Phone does not boot to ROM but only recovery. Must boot bootloader, "Normal Powerup"
My Moto G (2003) has TWRP. When I switch on the phone, it only boots into recovery TWRP 3.0.2.0, no matter what ROM I install.
However, when I boot the phone into bootloader mode and then select to do "Normal Powerup", the phone boots the installed ROM.
It is really strange.
Any hints on how to figure out what is happening? And how to fix?
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Thanks, this solved the problem.
Before, this partition had the strings
Code:
$ adb shell strings /dev/block/mmcblk0p30
boot-recovery
recovery
qe 1/1
Once the partition was cleared up (and stayed zeroed out), the phone would boot to the ROM.
lost101 said:
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
I have the same problem, but I got the error message:
Code:
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
When I tried to run the suggested soultion.
Any idea how to solve this?
rrd108 said:
I have the same problem, but I got the error message:
Code:
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
When I tried to run the suggested soultion.
Any idea how to solve this?
Click to expand...
Click to collapse
Yes, ignore the error message. The infinite number of zeroes from /dev/zero doesn't fit into the limited space of a partition, but when you get the message the partition is already filled.