[Q] My Nexus 5 die???? - Nexus 5 Q&A, Help & Troubleshooting

Hi all the expert
I having some problem with my phone/screen.
Been using this phone for 6 month. Last night my phone will auto went dark. I have to restart it in order ot turn it on. Today after i press the power button to off the screen, it went dark when i try to make it up. I have to use hard reboot by pressing the power button down for long time in order to restart the phone.
After that, I'm able to go into the android. However, if I turn off the screen again, it went dark again.
The problem now is, after few times of trying that (I mean hard restart the phone), now I cannot log into my android system. After the Google Logo and the 4 colour logo, it just went dark.
I try to plugi in my phone with USB to connect it to my PC, but it show nothing.
I try to wipe all the data by using the factory reset when i press down the volume key and power button, after wiping it, it doesn't work.
What should I do now ?
=============================================
When I do factory reset, it will either stuck here, or gone black. here is the picture:
tinypic.com/r/15higcn/8
=============================================
Thanks in advance.
Regards,
Nix

Download the factory images then use the following command: fastboot flash cache.img
If needed flash the whole factory images.

Primokorn said:
Download the factory images then use the following command: fastboot flash cache.img
If needed flash the whole factory images.
Click to expand...
Click to collapse
Hi Primokorn,
Thanks for the reply. I believe I will need to follow this instruction, am I right? http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Same as above
nixleong said:
Hi Primokorn,
Thanks for the reply. I believe I will need to follow this instruction, am I right? http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
yup... thats the way to go...

nixleong said:
Hi Primokorn,
Thanks for the reply. I believe I will need to follow this instruction, am I right? http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
fastboot flash cache.img first then follow this tutorial.

Primokorn said:
fastboot flash cache.img first then follow this tutorial.
Click to expand...
Click to collapse
Hi, sorry I'm newbie here, may I know how to do fastboot flash cache.img please? Thanks!!!

nixleong said:
Hi, sorry I'm newbie here, may I know how to do fastboot flash cache.img please? Thanks!!!
Click to expand...
Click to collapse
First off, you have to install and set up adb & fastboot on your PC.
Donwload and extract factory images until you find the cache.img file. Put this file into your platform-tools folder (SDK directory).
Open a cmd from this folder and enter the command. Your phone must be into fastboot mode (hold on Vol down + Power) and plug in to your PC.
You should find more details on the sticky threads.

Primokorn said:
First off, you have to install and set up adb & fastboot on your PC.
Donwload and extract factory images until you find the cache.img file. Put this file into your platform-tools folder (SDK directory).
Open a cmd from this folder and enter the command. Your phone must be into fastboot mode (hold on Vol down + Power) and plug in to your PC.
You should find more details on the sticky threads.
Click to expand...
Click to collapse
Hi sir, I'm getting this error message when I execute the "flash-all.bat" file.
Here is the picture:
tinypic.com/r/oid9hf/8
I run it ad administrator from Windows Operating System. I'm using the "4.4.3 (KTU84M)" file. Maybe I should use "4.4.2 (KOT49H)"?

If I right click and choose Open the "flash-all.bat" file it show this message"
tinypic.com/r/292sgma/8

nixleong said:
Hi sir, I'm getting this error message when I execute the "flash-all.bat" file.
Here is the picture:
tinypic.com/r/oid9hf/8
I run it ad administrator from Windows Operating System. I'm using the "4.4.3 (KTU84M)" file. Maybe I should use "4.4.2 (KOT49H)"?
Click to expand...
Click to collapse
as you can see, fastboot does not find the image-hammerhead-ktu84m.zip file and the bootloader image. Are the zip an bootloader image in the same folder as the flash-all.bat?
Tapatalk-kal küldve az én Nexus 5-el

nixleong said:
Hi sir, I'm getting this error message when I execute the "flash-all.bat" file.
Here is the picture:
tinypic.com/r/oid9hf/8
I run it ad administrator from Windows Operating System. I'm using the "4.4.3 (KTU84M)" file. Maybe I should use "4.4.2 (KOT49H)"?
Click to expand...
Click to collapse
Is you phone into fastboot mode? Did you already set up Fastboot on your PC? Is your bootloader unlocked? etc...
Check all pre-requisites from your above link: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

bitdomo said:
as you can see, fastboot does not find the image-hammerhead-ktu84m.zip file and the bootloader image. Are the zip an bootloader image in the same folder as the flash-all.bat?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
radio is missing too
Tapatalk-kal küldve az én Nexus 5-el

I have unlock the bootloder and able to do all these step, however once after I turn the phone on, passed the Google and 4 colour logo, I stuck at the Language screen, the screen cannot be touch, i can only power volume up and down and press the power button. Something wrong with my phone ?
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock.

So you didn't use fastboot flash cache.img?
BTW after using the factory images the phone reboots itself so it's weird that you reboot manually...

Primokorn said:
So you didn't use fastboot flash cache.img?
BTW after using the factory images the phone reboots itself so it's weird that you reboot manually...
Click to expand...
Click to collapse
I'm still dont know how to do the fastboot flash cache.img.
Between, I did clear the cache. does it matter to caused my phone bricked ?

nixleong said:
I'm still dont know how to do the fastboot flash cache.img.
Between, I did clear the cache. does it matter to caused my phone bricked ?
Click to expand...
Click to collapse
I explained you how to do that:
Download and extract factory images until you find the cache.img file. Put this file into your platform-tools folder (SDK directory).
Open a cmd from this folder and enter the following commands:
fastboot devices (you should see your serial number)
fastboot flash cache.img
Your phone must be into fastboot mode (hold on Vol down + Power) and plug in to your PC.

Primokorn said:
I explained you how to do that:
Download and extract factory images until you find the cache.img file. Put this file into your platform-tools folder (SDK directory).
Open a cmd from this folder and enter the following commands:
fastboot devices (you should see your serial number)
fastboot flash cache.img
Your phone must be into fastboot mode (hold on Vol down + Power) and plug in to your PC.
Click to expand...
Click to collapse
Thanks for the reply, appreciate it.
Ok I did what you said.
1. I downloaded the 4.4.2 (KOT49H) from: developers.google.com/android/nexus/images#hammerhead
2. I extract the file and copy the "cache.img" and pasted it into C:\Users\NixLeong\AppData\Local\Android\android-sdk\platform-tools. So the directory looks like this: tinypic.com/r/2bvcw7/8
3. I shift+ Right Click to open the CMD from the "platform-tools" directory. I typed the command: fastboot flash cache.img
4. This is the error message I got: tinypic.com/r/2ur6ln9/8

nixleong said:
Thanks for the reply, appreciate it.
Ok I did what you said.
1. I downloaded the 4.4.2 (KOT49H) from: developers.google.com/android/nexus/images#hammerhead
2. I extract the file and copy the "cache.img" and pasted it into C:\Users\NixLeong\AppData\Local\Android\android-sdk\platform-tools. So the directory looks like this: tinypic.com/r/2bvcw7/8
3. I shift+ Right Click to open the CMD from the "platform-tools" directory. I typed the command: fastboot flash cache.img
4. This is the error message I got: tinypic.com/r/2ur6ln9/8
Click to expand...
Click to collapse
The correct command for flashing cache is..
fastboot flash cache cache.img
Try this and report back.
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
If the problem still persists, flash all the .img files manually like this:
Go to bootloader and fire these commands via cmd opened from the fastboot folder. (All .img files needs to be in the folder as well!)
Code:
fastboot flash bootloader bootloader.img (File name may be different)
fastboot reboot-bootloader
fastboot flash radio radio.img (File name may be different)
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img (This will wipe the entire /sdcard)
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After following this, reboot your phone to the stock recovery and perform a factory reset and finally reboot! Everything should hopefully be fixed by now. If the problem still persists, RMA it.

vin4yak said:
The correct command for flashing cache is..
fastboot flash cache cache.img
Try this and report back.
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
If the problem still persists, flash all the .img files manually like this:
Go to bootloader and fire these commands via cmd opened from the fastboot folder. (All .img files needs to be in the folder as well!)
Code:
fastboot flash bootloader bootloader.img (File name may be different)
fastboot reboot-bootloader
fastboot flash radio radio.img (File name may be different)
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img (This will wipe the entire /sdcard)
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After following this, reboot your phone to the stock recovery and perform a factory reset and finally reboot! Everything should hopefully be fixed by now. If the problem still persists, RMA it.
Click to expand...
Click to collapse
Thanks, the command works, I followed every step till last. When I try to do the factory reset, I saw this error message:
E:failed to mount / cache (Invalid argument)
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E:failed to mount / cache (Invalid argument)
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E:failed to mount / cache (Invalid argument)
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install
E:failed to mount / cache (Invalid argument)
What does it mean ?

nixleong said:
Thanks, the command works, I followed every step till last. When I try to do the factory reset, I saw this error message:
E:failed to mount / cache (Invalid argument)
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E:failed to mount / cache (Invalid argument)
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E:failed to mount / cache (Invalid argument)
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install
E:failed to mount / cache (Invalid argument)
What does it mean ?
Click to expand...
Click to collapse
This means that the /cache partition is messed up.. Head over to the stock recovery again and format cache a couple of times and I'm sure the messages will go away. (No need to factory reset again)

Related

Encryption unsuccessful help

Hello,
I turned on my Xoom to see "Encryption Unsuccessful" tonight. If i boot into stock recovery and try to factory reset, it cannot mount Cache. If I plug the device into my computer, fastboot can find it but ADB cannot. I have the proper drivers installed. I can't get into my tablet to turn on USB debugging. I just bought an OTG cable to try to fix it, but cannot find the update.zip file that I need. If i try to fastboot oem unlock, it fails. I've tried everything I can find, I've done hours worth of playing/trial and error to no avail. Any help would be fantastic. Truly at a stand still. Please ask with any specifics needed to assist me.
Is it possible to flash to CWM recovery without being able to boot/find it in ADB?
Thank you,
Bradon
>.<
Nearly to the point of offering some sort of payment for assisting me. I'd rather not ship it out, but more than glad to work something out paypal or giftcard wise. This tablet is the only thing keeping my wife entertained, and another tablet is not in the budget.
But u can connect with fastboot to device ?
if yes this should help you
http://forum.xda-developers.com/showthread.php?t=1451655&page=7
http://forum.xda-developers.com/showthread.php?t=1049485
Probably you will lose all data on it ... Why u wanted to encrypt u device ...
I did it too but it was missunderstanding specialy when flashing a lot .
Alright so...
I've used fast boot flash user data, system, recovery and boot. Those are all successful, but if I reboot.. Nothing changes.
I've loaded many zips onto a flash drive with an otg cable, boot into the stock recovery and try to update, unable to verify signature.
Adv will not find the device, reinstalled drivers many times
Rsd will not find the device
Factory reset fails, cannot mount cache and about 10 other cache/recovery errors
Fast boot OEM unlock fails, unable to write a certain 3 letter file
I'm at work right now, so I can post specifics/pics later.
I didn't try to encrypt it, it seemed like a virus that my wife got. She clicks on advertisements, downloads sketchy files/apps.
It is unrooted, stock recovery.
20+ hours of research and trial.. No success.
Can u use this ?
http://forum.xda-developers.com/showthread.php?t=1074979
Use 2 method.
Write response what happend and it does flash recovery .
You have to unlock bootloader
look here simillar problem :
http://forum.xda-developers.com/showthread.php?t=1571827
http://forum.xda-developers.com/showthread.php?t=1952628
And u do not need any special otg cabel - use stock xoom from package. OTG is for host-usb.
Anyway u will have to do it with fastboot , probably /cache partialy encrypted.
Alright, I just followed the CWM recovery guide.
First off, ADB does not find my device, meaning I cannot reboot into the bootloader. I can flash the recovery only after flashing userdata for some reason. After flashing, it says complete though when I reboot nothing changes. The other 2 links, first one I can't use because adb doesn't find my device, and the 2nd one.. I don't think xoom has a "download mode".
Thanks
Ok, so when u push down button in booting u have only recovery ?
U should have fastboot too ... try to press up vol 1 s after booting, then connect to pc, and check in device manager rmb on "My pc"
And ? .... This must working ... Use fastboot.exe in cmd ( in windows 7 ) on Administrator User.
Also, when I first boot up recovery I get
E: failed to mount /cache (invalid argument.)
E: Can't mount /cache/recovery/command
E: Failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E: Failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E: Failed to mount /cache (invalid argument)
If i try to factory reset or clear the cache, I get the same message.
U do not understand what u reading, u cant do this from recovery ...
U have partialy crypted storage ... its normal!
1. download fastboot on windows
2. install drivers from
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
Click to expand...
Click to collapse
3. run fastboot protocol on xoom press down vol "find fastboot" if not press top vol in booting - should fastboot protocol ... in output
4. Use fastboot.exe from android sdk - run in in cmd ( Run ad Administrator , right click on cmd)
4. unlock bootloader
5. flash rom boot recovery in *.img format!
This must working...
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
bcwest said:
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
Click to expand...
Click to collapse
Is it bad ? - now when u show up "fastboot protocol ... " on xoom run fastboot from android sdk .
Fastboot ran from cmd with admin privileges.
fastboot oem unlock
used volume controls to select yes/i accept
Device unlock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:324 NvStorMgrFileOpen("UDA"):196624
ERROR: Failed to format UDA.
Error while unlocking device.
unplug mmc card from xoom and try again, where did u get files ... system.img ,recovery.img,boot.img ?
I've tried with both the mSD card in, and out. I got the boot/system/recovery/userdata from the stock image post from XDA.
ok, I didnt tryed this with stock rom, try to change recovery with http://forum.xda-developers.com/showthread.php?t=1074979
reboot and try to get to new recovery.
do this:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img <- from http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )
mx600 is the model that I have.
All of the flashing goes through fine
fastboot erase cache fails instantly (Failed to format PDB)
fastboot erase userdata fails instantly (Failed to format PDB)
fastboot reboot
volume down for recovery to see if CWM changes went through
stock android recovery
If I put my mSD card back into the unit, and try to do it all over again..
Flashes go through fine
Cache fails instantly, same error
Erase userdata causes my cmd to hang up, and the xoom sits at "StorMgr Formatting UDA STATUS: | | |"
5 minutes later, still sitting at that message.
Mx600, I restarted the device after flashing everything, If I let it go past the Dual Core Technology big red M, it boots into android but all that I get is the Encryption Unsuccessful screen. It says push restart, but it does nothing.
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )[/QUOTE]
Damn, that mean bootloader is locked or he have problem with gpt ?
ok... I'm not sure what will hapend but u can try to lock it again
fastboot oem lock
then reboot
fastboot oem unlock
output ?
Device Lock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:350 NvStorMgrFileWrite(ff, 0x00004000:00000000):196608
ERROR: Failed to format UDA
Device lock operation FAILED.

Help, Moto g won't boot up any rom

I unlock the g bootloader got it to root I have the latest cwm recovery been trying different ones also, but some how when I try to install any rom that's out there it won't boot up it only stays on the boot screen . Any ideas
Me too
I have this problem too.
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
forgotter said:
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
Click to expand...
Click to collapse
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
chente323 said:
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
Click to expand...
Click to collapse
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
This is the same thing a friend told me to do we did it had no luck Did it 2 times just in case I dint do it right the first time
Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC rename it to "CM.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\CM.zip /data/media/0/"(to push the CM11rom to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push CM.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11.zip or you can flash stock firmware through mfastboot.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Thanks I will give it a try tomorrow since it's wife phone I don't have it w me now. I'll get back at u let u know if it work
forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
Hi forgotter! I have the same problem... won't boot with any ROM. I've followed your instructions but stil stucked on the boot logo. I will try the second method you provided now, hope that works :crying:
@notnowjohn
Didn't know why first method didn't worked for you but the second one would definitely work. If you get any error then reply to me, and yes in my second method post by mistake there are some extra space added after full stop (.) e.g. in boot. img (it is boot.img ) do please avoid that.
forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
notnowjohn said:
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
Click to expand...
Click to collapse
Don't worry your phone is fine.
Whenever adb shows m mismatched partition it's fine and usual.
I understand your problem now, I just think if I your device now , I would have repaired it within minutes. Never mind, follow the below steps .
Download the philz recovery to your PC, flash it through fastboot on your phone. Then go to recovery on your phone immediately and choose wipe-wipe data and sdcard. And then flash the stock firmware through mfastboot or install any ROM through recovery.
Anyone report which step what must i do to solve this prob
sinkadorable said:
Anyone report which step what must i do to solve this prob
Click to expand...
Click to collapse
Read post #7 on page 1.
I cant push system to device. What tools must be i have?
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
pluiz halp!
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
jamiethomaswhite said:
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
Click to expand...
Click to collapse
Plug the phone to wall charger and leave it to charge for the whole night, the next when you'd restart the phone it should boot up. Sometimes the phone discharged itself to such a level that it didn't have enough juice left to show the battery charging status even.
After that follow instructions from post #7 on page 1 and paste all output commands you see. Well, the phone should boot up.
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
sinkadorable said:
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
Click to expand...
Click to collapse
Mismatched partition size is usual , no need to worry about that. What do you mean by UBL warning message? And yes, after you flash recovery, enter in recovery mode and wipe data and sdcard and then flash any ROM from fastboot.
And if you get into an error or solution doesn't work then post your problem but detailed so I can get to the main cause of the problem.

[Q] Asus stuck on TWRP Recovery

Hello,
Here is my problem,
I unlocked my tablet. Apk
After I installed the TWRP recovery with this technique
http://forum.xda-developers.com/showpost.php?p=33117920&postcount=2
Every time I got this message wanting to do the backup
E: can not mount / cache / recovery / command
E: can not mount / cache / recovery / log
E: can not open / cache / recovery / log
E: can not mount / cache recovery / last_log
E: can not open / cache recovery / last_log
I did a wipe and a re-installation
Now it will only start on recovery
that is unusable since it detects any file or folder
can not install zip
Is there a chance to reinstall
I bought it at darty I just pass by warranty?
thank you very much
titeloo said:
Hello,
Here is my problem,
I unlocked my tablet. Apk
After I installed the TWRP recovery with this technique
http://forum.xda-developers.com/showpost.php?p=33117920&postcount=2
Every time I got this message wanting to do the backup
E: can not mount / cache / recovery / command
E: can not mount / cache / recovery / log
E: can not open / cache / recovery / log
E: can not mount / cache recovery / last_log
E: can not open / cache recovery / last_log
I did a wipe and a re-installation
Now it will only start on recovery
that is unusable since it detects any file or folder
can not install zip
Is there a chance to reinstall
I bought it at darty I just pass by warranty?
thank you very much
Click to expand...
Click to collapse
Did you use the TWRP version from that guide as well? That is the TWRP for Android 4.1, not Android 4.2 bootloader, which is probably what you have.
You should look up Buster's recovery script and perform that. Then flash a -4.2 version of TWRP.
cmendonc2 said:
Did you use the TWRP version from that guide as well? That is the TWRP for Android 4.1, not Android 4.2 bootloader, which is probably what you have.
You should look up Buster's recovery script and perform that. Then flash a -4.2 version of TWRP.
Click to expand...
Click to collapse
Thank You very mutch for your answer can You explain me how to do ?
titeloo said:
Thank You very mutch for your answer can You explain me how to do ?
Click to expand...
Click to collapse
Follow this post: http://forum.xda-developers.com/showpost.php?p=45120193&postcount=1
cmendonc2 said:
Follow this post: http://forum.xda-developers.com/showpost.php?p=45120193&postcount=1
Click to expand...
Click to collapse
thanks a lot
I try to reset but the pad reboot on recovery
Do you know how can i do ?
titeloo said:
thanks a lot
I try to reset but the pad reboot on recovery
Do you know how can i do ?
Click to expand...
Click to collapse
connect it to your computer when it is starting and use
Code:
fastboot reboot bootloader
when it is in TWRP.
cmendonc2 said:
connect it to your computer when it is starting and use
Code:
fastboot reboot bootloader
when it is in TWRP.
Click to expand...
Click to collapse
Thank you very much for your help.
This is surely stupid question, but where I type the command ?
I mean if I have open cmd windows somewhere special
Or tap something befor ?
titeloo said:
Thank you very much for your help.
This is surely stupid question, but where I type the command ?
I mean if I have open cmd windows somewhere special
Or tap something befor ?
Click to expand...
Click to collapse
You need to have ADB installed: http://forum.xda-developers.com/showthread.php?p=42407269
Then type that into CMD in the directory where you installed it.
cmendonc2 said:
You need to have ADB installed: http://forum.xda-developers.com/showthread.php?p=42407269
Then type that into CMD in the directory where you installed it.
Click to expand...
Click to collapse
thank you again
Unfortunately it is not working
cmd remains <waiting for device>
This mean it is fully bricked, right?
titeloo said:
thank you again
Unfortunately it is not working
cmd remains <waiting for device>
This mean it is fully bricked, right?
Click to expand...
Click to collapse
you send me a email the other day and we were going to use Team Viewer....
Im sure If you still have fastboot, we can fix this issue...
Here is my email again [email protected]
Thx Josh
lj50036 said:
you send me a email the other day and we were going to use Team Viewer....
Im sure If you still have fastboot, we can fix this issue...
Here is my email again [email protected]
Thx Josh
Click to expand...
Click to collapse
But I haven't Fastboot ?
Install "Minimal ADB and Fastboot": http://forum.xda-developers.com/showthread.php?t=2317790
Then download the latest TWRP: http://forum.xda-developers.com/showthread.php?t=2691886
Extract the ZIP file and copy the recovery.img into the installation folder of "Minimal ADB and Fastboot". Then run the program and type in the command window:
fastboot devices (a serial number must be returned, see screenshot; ist shows that your TF300 is connected)
fastboot flash recovery recovery.img
fastboot reboot
Let Android start, shut it down and go into the recovery to flash a new ROM.
Btw: I installed CWM for testing and it did find nothing because it wasn't able to mount anything - so I switched back to TWRP...
titeloo said:
But I haven't Fastboot ?
Click to expand...
Click to collapse
O its still there.. no worries, I am here if you would like to fix your tablet.....
UncleManuel said:
Install "Minimal ADB and Fastboot": http://forum.xda-developers.com/showthread.php?t=2317790
Then download the latest TWRP: http://forum.xda-developers.com/showthread.php?t=2691886
Extract the ZIP file and copy the recovery.img into the installation folder of "Minimal ADB and Fastboot". Then run the program and type in the command window:
fastboot devices (a serial number must be returned, see screenshot; ist shows that your TF300 is connected)
fastboot flash recovery recovery.img
fastboot reboot
Let Android start, shut it down and go into the recovery to flash a new ROM.
Btw: I installed CWM for testing and it did find nothing because it wasn't able to mount anything - so I switched back to TWRP...
Click to expand...
Click to collapse
thanks for you help
Nothing happen
titeloo said:
thanks for you help
Nothing happen
Click to expand...
Click to collapse
Hmmm, that's the problem I got with the standalone version of Fastboot and the version from the Android SDK. As I said "fastboot devices" must return a serial number. It shows that your device is connected with your computer. If it shows nothing there is simply no connection...

Stuck on Boot Animation

Hi,
I was following this rooting guide...
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
And after I completed Step 2 my phone would no longer boot up. It just hangs while the cyanogenmod bolt logo spins.
I can however now boot into TWRP.
I don't know what to do... I don't think I can copy Super User or Rom Files over to my device currently. I do have an OTG cable with a thumb drive and I plugged it in and I can't seem to access that from within TWRP.
Any help would be appreciated!
Also FYI I'm using Windows 7 for my desktop.
Well, if you have access to twrp, you can do into the advanced setup and select adb sideload. Place the rom in the adb folder and typer: adb sideload 'file'.
Example: adb sideload myrom.zip ; this will flash the rom, which you can then reboot the phone and hopefulyl boot.
teh roxxorz said:
Well, if you have access to twrp, you can do into the advanced setup and select adb sideload. Place the rom in the adb folder and typer: adb sideload 'file'.
Example: adb sideload myrom.zip ; this will flash the rom, which you can then reboot the phone and hopefulyl boot.
Click to expand...
Click to collapse
Ok so I sideloaded UPDATE-SuperSU-v2.02.zip. Thanks so much for your help!
Should I sideload the stock rom the same way? Will that even work? Should I do some sort of a wipe first?
Sorry if I'm asking too many questions... I just want to be careful.
I also notice if I go into the text pane of TWRP it says
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
jkentj said:
Ok so I sideloaded UPDATE-SuperSU-v2.02.zip. Thanks so much for your help!
Should I sideload the stock rom the same way? Will that even work? Should I do some sort of a wipe first?
Sorry if I'm asking too many questions... I just want to be careful.
Click to expand...
Click to collapse
General rule of thumb, if you want to flash a flashable zip but it isn't on your phone then do adb sideload. All adb sideload does is just put the file onto your phone to flash it.
If you drag and drop the zip onto your phone then u can flash it without adb sideload.
If you're switching from 1 ROM to the next, always wipe. If its the same ROM but you're upgrading to a newer version of the ROM, then just flash without wiping.
I also notice if I go into the text pane of TWRP it says
Click to expand...
Click to collapse
Go into TWRP -> mount -> check cache.
jkentj said:
Ok so I sideloaded UPDATE-SuperSU-v2.02.zip. Thanks so much for your help!
Should I sideload the stock rom the same way? Will that even work? Should I do some sort of a wipe first?
Sorry if I'm asking too many questions... I just want to be careful.
Click to expand...
Click to collapse
Well asking questions is how we learn, so no worries.
You can flash the stock rom / any file in the same manner. When you start with the sideload you can choose to wipe the dalvik / cache.
I would sideload your rom only at this point [stock or custom] and then attempt to boot into the os.
If that fails: from twrp wipe: everything except internal storage, then sideload the rom again; this way you'll be flashing on a clean install.
Ahh success!
Ok if anyone is having this issue here is the solution:
1. Put your phone in fastboot mode (volume up + power)
2. Plug your usb cable in. Go to your PC and open the cmd prompt from the folder on your pc that has fastboot.exe (shift+right click in folder, select open command window here)
3. Type fastboot format cache
4. Then type fastboot reboot
Solved the hanging/boot loop.
jkentj said:
Ahh success!
Ok if anyone is having this issue here is the solution:
1. Put your phone in fastboot mode (volume up + power)
2. Plug your usb cable in. Go to your PC and open the cmd prompt from the folder on your pc that has fastboot.exe (shift+right click in folder, select open command window here)
3. Type fastboot format cache
4. Then type fastboot reboot
Solved the hanging/boot loop.
Click to expand...
Click to collapse
I like this guy. He helps future viewers of this thread who will have similar problems the solution. :good:
zephiK said:
I like this guy. He helps future viewers of this thread who will have similar problems the solution. :good:
Click to expand...
Click to collapse
We've created a monster that helps other monsters. Our work here is done.
teh roxxorz said:
We've created a monster that helps other monsters. Our work here is done.
Click to expand...
Click to collapse
Time for retirement? :victory:
jkentj said:
Ahh success!
Ok if anyone is having this issue here is the solution:
1. Put your phone in fastboot mode (volume up + power)
2. Plug your usb cable in. Go to your PC and open the cmd prompt from the folder on your pc that has fastboot.exe (shift+right click in folder, select open command window here)
3. Type fastboot format cache
4. Then type fastboot reboot
Solved the hanging/boot loop.
Click to expand...
Click to collapse
had the same problem, thx man!
silly me, i was always using:
Code:
fastboot erase cache
no wonder, it didnt work :silly:
jkentj said:
Ahh success!
Ok if anyone is having this issue here is the solution:
1. Put your phone in fastboot mode (volume up + power)
2. Plug your usb cable in. Go to your PC and open the cmd prompt from the folder on your pc that has fastboot.exe (shift+right click in folder, select open command window here)
3. Type fastboot format cache
4. Then type fastboot reboot
Solved the hanging/boot loop.
Click to expand...
Click to collapse
Your amazing thanks bud, worked for me just now
jkentj said:
Ahh success!
Ok if anyone is having this issue here is the solution:
1. Put your phone in fastboot mode (volume up + power)
2. Plug your usb cable in. Go to your PC and open the cmd prompt from the folder on your pc that has fastboot.exe (shift+right click in folder, select open command window here)
3. Type fastboot format cache
4. Then type fastboot reboot
Solved the hanging/boot loop.
Click to expand...
Click to collapse
I am still stuck at the boot animation screen! Any other possible solution??! thanks!!!

unsupported file system error "raw"

Hey, i messed up my phone by installing something via magisk. Now im trying to install a new rom.
When i open the phone (lenovo p2a42), i get encryption error. For able to fix that problem i have to use "fastboot format userdata" command but i get raw file system error. How can i fix this? Disk manager doesn't see the phone.
Code:
adb reboot bootloader
error: no devices/emulators found
fastboot devices
ZY223TNMLC fastboot
fastboot format userdata
(bootloader) has-slot:userdata: not found
fastboot: error: Formatting is not supported for file system with type 'raw'.
edit ok i figure it out. power button, adv setting, recovery than continued to next step, there is no need to format
Jhumsmt said:
continued to next step
Click to expand...
Click to collapse
You mean continue to regular boot or continue to recovery?

Categories

Resources