Database Info

Possibly bricked trying to update to CM11

A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!

Quevvy said:
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Click to expand...
Click to collapse
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.

cmendonc2 said:
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
Click to expand...
Click to collapse
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…

Quevvy said:
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Click to expand...
Click to collapse
No, you need nvflash backups to use APX mode. Since you can't get to the recovery menu, I can't think of any other solutions....?

Same here
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.

boggessb said:
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
Click to expand...
Click to collapse
You would have to open it and replace the motherboard with a new one like this:
http://forum.xda-developers.com/showthread.php?t=2368372
With a new part like this:
http://www.ebay.com/itm/like/390706401658?lpid=82

[Q] TF700 bricked...?

Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!

Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??

lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo

nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??

lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?

nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/

lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!

Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app

lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays

So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?

First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.

berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery

Hope this worked

s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???

berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?

s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.

OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.

s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?

The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it

s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?

After rooting my nexus 5 is not booting up with non stop booting animation

I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...

nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally

funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:

funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know

I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.

First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.

Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.

fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.

Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.

hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys

@[email protected], possible power button problem?

[XT1541 16Gb] - Update caused boot loop, cannot flash ROM

Hi all,
I just tried to update my XT1541 (I didn't see what version it was to, sorry), but was rewarded by an endless boot loop -- the phone wouldn't progress past the white splash screen, and lasted about 15-20 seconds per cycle.
Holding the [Volume Down] button got me to the bootloader screen, from which I was able to go into recovery. However, this only displayed an error message, 'No command found', with a red warning symbol over the android image.
I could get round this, however, by holding down [Power] then [Volume Up], and was able to both wipe the cache and do a factory reset. Neither of these helped fix the issue, however. I am unable to flash from the SD Card, either, as attempting this results in the error message, 'internal and external memory cannot be mounted'.
At this, point, I imagine I can try adb and fastboot, but does anyone have any guidance first?

Go into that bootloader screen and flash the stock rom with fastboot.

maarten2001 said:
Go into that bootloader screen and flash the stock rom with fastboot.
Click to expand...
Click to collapse
Ach, now I can't unzip the factory ROM -- sparsechunk.4 is broken and refuses to be extracted :/

rosyatrandom said:
Ach, now I can't unzip the factory ROM -- sparsechunk.4 is broken and refuses to be extracted :/
Click to expand...
Click to collapse
Make sure you have downloaded the correct version for your device or try to download it again.

[SOLVED] H60-L02 bricked beyond recovery? Plz help me!

edit: If you are just looking for the solution, plz click here: http://forum.xda-developers.com/showpost.php?p=68626049&postcount=11
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)

mike175de said:
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
Click to expand...
Click to collapse
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.

With which version?
muradulislam said:
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
Click to expand...
Click to collapse
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!

mike175de said:
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
Click to expand...
Click to collapse
You can use any firmware but the latest one should be better, and flash four images, boot, Cust, system and boot and let it boot normally.
Then put the dload folder with update.app in sd card and do an update from settings.

Thx. I will give it a try when I'm back from work.
I let you know if it is working.

mike175de said:
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
Click to expand...
Click to collapse
I meant to say flash boot, Cust, recovery and system images.
Wrote boot twice

Nothing changed
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike

mike175de said:
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
Click to expand...
Click to collapse
Of all the things you have already tried, the only thing remains to take it to a Huawei service center.
May be someone else can help you here but I have read most of honor 6 and 7 posts and I don't think there is anything there for this problem atm.

Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.

mike175de said:
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
Click to expand...
Click to collapse
I myself have an H60-L01, bought it from china, bricked and tried everything to revive it but could not, still have to try Huawei customer service in Pakistan, am not sure whether they will be able to help me or not, but will give it a try. I wish you luck buddy. Hope you find a solution.

It's alive ;o)
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike

The same can not restore brick
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.

igorxxl said:
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
Click to expand...
Click to collapse
Have you unlocked and rooted it?
When does it says that message?

error! no func. func_boot_kernel or _recovery
zinko_pt said:
Have you unlocked and rooted it?
When does it says that message?
Click to expand...
Click to collapse
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.

igorxxl said:
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
Click to expand...
Click to collapse
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.

Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..

igorxxl said:
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
Click to expand...
Click to collapse
You can also try installing custom recovery and restore a twrp backup of ROM.

zinko_pt said:
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Click to expand...
Click to collapse
goldfinv said:
You can also try installing custom recovery and restore a twrp backup of ROM.
Click to expand...
Click to collapse

i'm in the same situation with my honor 6 plus pe-ul00 i'll try this metod!

mike175de said:
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0 [emoji14]
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
Click to expand...
Click to collapse
I got a problem at 9.3 or 9.4. The recovery wont start i see only honor logo i used PE_EMUI3.1_Android5.1_6.1.1.zip (as developer edition i.e sdcard/dload/UPDATE.APP) and PE-UL00-V100R001CHNC00B200.zip to extract and flash BOOT.img and RECOVERY.img
any ideas why i can't enter in recovery? =(
EDIT: "fixed with DC-Phoenix tool"