Database Info

[Q] Semibricked Desire S, possible to fix?

Hi guys! I think I need your massive help...
What I did:
S-OFFed my Desire S with alpharevx - no problem
Rooted with Gingerbreak - no problem
Flashed ClockWorkMod Recovery with RomManager - no problem
Flashed Virtuos Unity ROM with ClockWorkMod - no problem
Tried to boot phone after flashing Virtuos Unity ROM - PROBLEM!
Phone stayed at VU bootscreen for about 30 minutes, not responding to anything.
Only thing to do was to remove battery. After that, it hung at HTC Bootlogo (green on white background), nothing happens.
So, I tried to enter CWM to flash my nandroid backup - wouldn´t accept it.
Tried to flash all other ROMs that I found - always error.
Entered CWM to try to wipe partitions.
First screen shows the menu and below that following message:
ClockworkMod Recovery v3.0.2.6
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
I can still use the menu however.
Wipe data/factory reset is no problem
Wipe cache partition is ok, but makes the environment REALLY slow!
Always show errormessage when trying to install ROM, when it is trying to format /system, doesn´t matter if it is custom or my nandroid backup.
Errormessage is: Error formatting /system!
Sometime I had an (Status 1) message when trying to install a custom rom. It says that it is an error in the zip file. However, I tried several with the same result.
So, I thought, "Wrong CWM?". Let´s try 4EXTRecovery instead.
Beginning to flash:
assert failed: write_raw_image(“/tmp/recovery.img, “recovery”)
E:Error in /sdcard/4EXTRecovery_v2.0.2_RC2-saga.zip
(Status 7)
Installation aborted.
There´s no error in the file, I tried to download it from several sources.
I can reach the phone thru ADB and Fastboot. I tried a couple of commands I found on the net to wipe cache but only got an error. Don´t know what to type...
When trying to flash a newer Clockwork Mod Recovery with fastbootcommand, sending the file is OK, but when writing ´recovery´ it hangs, nothing happens for 20 minutes. When unplugging the USB cord I get an error (status read failed (Too many links)).
I also tried to flash my .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img from my nandroidbackup (ex. fastboot flash boot boot.img) with the same results: sending file is ok, when writing the file the phone stops responding until I pull the USB cable, then I get the "Too many links error".
So: Is there anything I can do?
I have all the files .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img on my computer if that is any good.
I can mount and access the sdcard thru ClockworkMod Recovery.
Both HBOOT (Bootloader?), FASTBOOT and CWMrecovery is responding on phone, there is a working link between computer (ADB and FASTBOOT command), however something seems to be broken as it stops responding.
Is there any command I can use? I really don´t know more than the FLASH and WIPE command so maybe i´m missing something?
I appreciate all your input!
Thanks!

kinda looks familiar...
compare your problem to this:
http://forum.xda-developers.com/showthread.php?t=1150917

F**k... Stupid me, I read that post when it was new. However, I didn´t have that problem myself then...
So, is there a command I can execute to see that the eMMC chip is really broken?
As in that thread, point 8, second infoscreen (DS Brick shows). Just to make sure, I think I have a friend that can replace it for me then...

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] My Nexus 5 die????

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)

Asus TF700T boot loop

Some time ago I successfully unlocked my TF700 and installed one of the Cromi-X roms. The machine wasn't improved that much and was still very slow with frequent messages asking if I wanted to wait for apps to respond or to close the app. I thought I would try the "Revisited CROMi-X-ET_v3.0-RC2" rom as that allowed the f2fs file system and I wondered if that would be faster. I installed TWRP version twrp-3.0.0-0-tf700t and did the install of the above rom using TWRP and choosing all the default options which reformatted some of the partitions to f2fs.
On reboot I got the start screen and then after a while a reboot again repeatedly. I tried booting to recovery and just got the Teamwin screen.
I then reinstalled TWRP using fastboot and a USB connection. I have tried twrp-2.8.7.0-tf700t, twrp_tf700t_kang_2.8.7.4, and twrp-3.0.0-0-tf700t and all give error messages when I do a wipe, try to restore a previous backup or try to install a new ROM.
On 2.8.7.0 the log I get from a wipe is:-
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/staging'
Erimary block device '/dev/block/mmcbblk0p8' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Kernel does not have support for reading SELinux contents.
E:Unable to mount '/cache'
E:Unable to set bootloader message
E:Unable to mount '/cache'
E:Unable to mount '/data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
E:Unable to mount '/data'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
The twrp_tf700t_kang_2.8.7.4 version gives similar messages except it says failed to unmount system cache and data. The log from twrp-3.0.0-0-tf700t is the same as the kang version except this one says failed to mount the three partitions.
After reading another thread with similar symptom, I tried to format a partition using adb with the shell command:
make_ext4fs /dev/block/mmcblk0p8
this returns Need size of filesystem.
I would be grateful if anyone could help (or is my tablet irretrevably bricked).

What's the version of your bootloader?
Boot to TWRP and run "adb shell dmesg > dmesg.txt" and post the resulting file.

_that said:
What's the version of your bootloader?
Boot to TWRP and run "adb shell dmesg > dmesg.txt" and post the resulting file.
Click to expand...
Click to collapse
I did this some time last week but got no text file for some reason. Repeated it without the redirect to file and copied from the cmd window. It's a very long file however. Do I paste it in here or is there some way of attaching it so you can see it (I'm new to posting in forums)
How do I get the boot loader version?
Thanks for trying to help.

kenhanley said:
Do I paste it in here or is there some way of attaching it so you can see it (I'm new to posting in forums)
Click to expand...
Click to collapse
This forum has a feature to attach files (use the paper clip icon). I'm not sure if new users are allowed to attach files - if not, put your log on pastebin and add the relevant part of the URL to your answer.
kenhanley said:
How do I get the boot loader version?
Click to expand...
Click to collapse
Boot to the bootloader (Power+Volume down), read the small text in the upper left corner.

_that said:
This forum has a feature to attach files (use the paper clip icon). I'm not sure if new users are allowed to attach files - if not, put your log on pastebin and add the relevant part of the URL to your answer.
Boot to the bootloader (Power+Volume down), read the small text in the upper left corner.
Click to expand...
Click to collapse
As far as I can tell with two pairs of reading glasses on (its an age thing), the second line reads
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
I don't see the paperclip and - sorry to be so ignorant but - how do I logon to pastebin
Regards
Ken

kenhanley said:
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Click to expand...
Click to collapse
OK, that's the correct version.
kenhanley said:
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
Click to expand...
Click to collapse
You need to fully reboot after installing TWRP via fastboot (however you can go directly to the bootloader menu and select RCK, no need to start Android), otherwise it can't access your partitions.

kenhanley said:
As far as I can tell with two pairs of reading glasses on (its an age thing), the second line reads
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" R03
Insidentally I just descovered that TWRP only runs once after installing with fastboot. If I power down I have to use fastboot again each time and re-install twrp.
I don't see the paperclip and - sorry to be so ignorant but - how do I logon to pastebin
Regards
Ken
Click to expand...
Click to collapse
I think I manage to paste into pastebin under title KenHanley demsg. Not sure how you get to see it.
Regards
Ken

Not sure I understand about the reboot after TWRP install. When I install TWR the tablet is sitting with the three icons RCK Android and Wipe Data. After install completes if I press Vol up with the RCK flashing TWRP works. If I reboot straight away TWRP hangs on the start screen or tries to reboot after a time depending on which version I installed. Same thing happens after powering down from running TWRP without the reboot.
Regards
Ken

just realised youasked for pastebin url. It's
pastebin/4Bh8zdXa
regards
Ken

kenhanley said:
Not sure I understand about the reboot after TWRP install. When I install TWR the tablet is sitting with the three icons RCK Android and Wipe Data. After install completes if I press Vol up with the RCK flashing TWRP works. If I reboot straight away TWRP hangs on the start screen or tries to reboot after a time depending on which version I installed. Same thing happens after powering down from running TWRP without the reboot.
Regards
Ken
Click to expand...
Click to collapse
There's your problem, as _that said: You need to reboot after flashing TWRP before you can use it:
Flash TWRP
Reboot into bootloader
Enter TWRP by selecting the RCK icon.
I know you said TWRP hung if you reboot straight away, but that is strange. Describe step by step how you flash TWRP.

OK.
I boot TF700 with vol down pressed. Connect USB to computer running windows 10. Open cmd window. (copy from cmd window below):
C:\adb>fastboot flash recovery twrp-2.8.7.0-tf700t.img
sending 'recovery' (7372 KB)...
OKAY [ 3.418s]
writing 'recovery'...
OKAY [ 6.528s]
finished. total time: 9.951s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb>
Holding vol down when typing fastboot reboot. Press Vol up when RCK is flashing. Teamwin screen comes on then briefly flashes off and comes on again and that is as far as it gets.
Same thing happens if instead of typing fastboot reboot I press and hold the TF700 power button to reboot.
If I skip the reboot and press Vol up after the flash has finished TWRP starts up and after a delay I get all the various buttons to Install, Backup, Restore etc.. Then I get the storage not mounted problems

Do not touch any button on the tablet after the recovery flash. Just type fastboot reboot, then hit enter.
After you've seen the Asus logo with a blue bar underneath filling up you can reboot into the bootloader and enter recovery.

Just done that. I get a blue bar when I flash.
After fastboot reboot the screen blanks then the Asus Logo comes up but no bluebar. Eventually after displaying the Asus screen for about 35 seconds the tablet reboots itself in the bootloop I originally mentioned. Booting to recovery gives me the teamwin screen hangup I described above.
I repeated and this time instead of waiting on the Asus screen I rebooted from the Asus screen by pressing and holding power and vol down. Same happens TWRP hangs on Teamwin screen
Sorry I'm causing all this trouble.
Regards
Ken

Never seen that before and I don't have an explanation for it either....
What kind of wipes did you do before flashing the new rom?
Don't know.. maybe @_that has a better idea, but at this point I would flash the Asus firmware in fastboot and start from scratch.....
Hang in there for word from @_that, otherwise I can hook you up with instructions for the fastboot firmware flash
Sent from my ASUS Transformer Pad TF700T using Tapatalk

kenhanley said:
C:\adb>fastboot flash recovery twrp-2.8.7.0-tf700t.img
sending 'recovery' (7372 KB)...
OKAY [ 3.418s]
writing 'recovery'...
OKAY [ 6.528s]
finished. total time: 9.951s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb>
Holding vol down when typing fastboot reboot. Press Vol up when RCK is flashing. Teamwin screen comes on then briefly flashes off and comes on again and that is as far as it gets.
Click to expand...
Click to collapse
I think it's crashing due to a corrupted filesystem. Reboot to TWRP, and with the splash screen flashing, run this:
Code:
adb pull /tmp/recovery.log
Post the resulting file.
To reformat /data as f2fs (be careful with this command and press Enter only after double-checking that you got the "p8" right):
Code:
adb shell mkfs.f2fs /dev/block/mmcblk0p8

_that
I posted the recovery log http://pastebin.com/PdZVbEsC title KenHanleyrecoverylog.
Just did the format of /data then installed TWRP again. Reboot still didn't give a blue bar but Yipee The bootloop is gone and I'm into the setup screens for the ROM I flashed that caused all the bother. Thank You
berndblb
I looked on the Asus site for firmware but they don't list the TF700T anymore. I would be grateful if you can point me to the files and instructions for the Asus firmware in case I do need to do a restore to original.
Thanks again to you all for the help

It's not the rom that did it - I'm running it without trouble for months! It was what you did.
http://www.transformerforums.com/fo...e-firmware-tf101-tf201-tf300-tf700-tf701.html
Check out post 2 and download a copy. Who knows when Asus takes it down entirely....

I didn't mean to imply it was the ROM. It seems to be running OK now. I think somehow the formatting of \data went wrong during the install but I can't identify anything I did that could have caused it. Anyway I'm just grateful to you guys for digging me out of the hole I dug for myself. Thanks for the link, I got to the firmware download page OK from that. I'll grab everything I can now while the going is good.

I realize this is an old post, but hopefully ....
I have the same problem except that it will only boot to the splash screen of TWRP3.1.x.
I had KatKiss 7.1 on it and rebooted it and into a loop. I re-flashed TWRP V3 via fastboot and the much discussed blue line was there, a "fastboot reboot" just sent me into the boot loop again. Pwr/Voldn gave me the 3 flashing icons, but selecting recovery just gives me the TWRP loading screen for about 10 seconds or so, then reboots.
I'm assuming I have to start from scratch as well but am a bit confused as to which firmware from asus' site and how to do this.

Strange - I wonder what it is that prevents TWRP from booting....
Did you try the command from above to reformat data to f2fs?
If nothing resolves this you can always flash the stock blob in fastboot.
The firmware is here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Download the SKU for your region (most likely WW or US).
Unzip it twice and copy only the blob into your fastboot folder.
Then try this:
Code:
fastboot erase userdata
Now try to boot into TWRP via the buttons
If that did not do it, continue with:
Code:
fastboot erase misc
fastboot erase cache
Again boot into TWRP and see if that did it.
If not continue with this:
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot flash system blob
fastboot reboot
The commands will finish fairly quickly except for erasing data and flashing the blob. Be patient.
If you're not the inquisitive type who wants to find out what the problem is and more the roundhouse-punch-radical type you can also run all the above commands one after the other in one go to get you back to stock. The order is not important as long as you flash the blob last. Before rebooting that is.
That should return you to a stock JB 4.2 system.
Then flash TWRP, format data, convert it to f2fs and finally flash the rom or restore your last nandroid.
Good luck

coolpad f1 not opening

Hello guys . After a restart of my coolpad f1 8297w my phone was in bootloop . I entered in recovery mode and this message appeared :E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
I tried to use Sp flashtools and even that it was successful the phone does not open at all anymore .. Any ideas ? Thank you .

peej2014 said:
Hello guys . After a restart of my coolpad f1 8297w my phone was in bootloop . I entered in recovery mode and this message appeared :E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
I tried to use Sp flashtools and even that it was successful the phone does not open at all anymore .. Any ideas ? Thank you .
Click to expand...
Click to collapse
I have that phone and had the same problem. Re-format the cache partition to fix the recovery. And then reflash a stable rom.
---------- Post added at 12:42 ---------- Previous post was at 11:44 ----------
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

How can you un brick if it wont powrr on? I'm letting mine charge, it was gave by a friend. Id like to get it running..