Database Info

[Q] Please help - ASUS Transformer Infinity TF700 Brick

Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?

GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
I am having the same issue. Just rooted today. Please help!

dpadaddict said:
I am having the same issue. Just rooted today. Please help!
Click to expand...
Click to collapse
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
http://teamw.in/project/twrp2/105
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!

fordwolden said:
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
Click to expand...
Click to collapse
I wish I could... The message I receive is as follows when I do that:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image
And nothing ever shows up. Just the ASUS logo.

Did you solve your problem? I'm having the same issue and tried to install custom ROMs without solving the problem

reboot the device! (power and vol down for 5 sec)
hold vol down at the ASUS screen, but don't go to recovery, just wait until you see a 3 different logos on your screen.
An Android, a Wipe and a USB Icon
go between theese logos with vol down choose USB Icon with vol up!
Now you are in Fastboot mode and with your PC you can flash another recovery image.
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!

kabauterman said:
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
Click to expand...
Click to collapse
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I never said I was new to Android. I was new to the ASUS stock tablet recovery orientation (its landscape as I found out). Hence, hit up twice, wiped data. I am by no means new in general. I did not fix the problem. I requested an RMA with Newegg and it was approved I said the issue with it was bad screen bleeding (no lie but it is normal for this tablet but bad was exaggerated) In any case! RMA approved should be getting my new unit Tuesday!

unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?

fix
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
Just follow this method and you will be fine
http://forum.xda-developers.com/showthread.php?t=1755576

kabauterman said:
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
Click to expand...
Click to collapse
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).

GRIM1337 said:
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
Click to expand...
Click to collapse
Any resolution to this other than the RMA?

HelgesenJ said:
Any resolution to this other than the RMA?
Click to expand...
Click to collapse
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.

MartyHulskemper said:
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
Click to expand...
Click to collapse
One more who used ROM manager recently and now I have a nice tray for serving beers :crying:
I'm having the same issue with APX available by powering on the transformer holding volume+up but with no nvflash backup.

I don't understand why people keep using ROM manager to install recovery, this is a death wish to your device. If they read all the "How to" posts, none of them instructed to use rom manager to install recovery, so I don't know where they got this idea from???? beat me!!!
GRIM1337, you need RMA to send out for repair. Sorry but there's no hope to recovery this.

Didn't use ROM Manager
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s

3c said:
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
Click to expand...
Click to collapse
How did you get into fastboot mode for your device??

buhohitr said:
How did you get into fastboot mode for your device??
Click to expand...
Click to collapse
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.

3c said:
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
Click to expand...
Click to collapse
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.

Re: Help needed i will try
OK WHAT YOU HAVE DONE IS WIPED THE OS FROM THE UNIT...AND LEFT THE BOOTLOADER FILES...SO THERE ISNT
ANYTHING TO BOOT TO AT THE MOMENT... I DID THIS LAST WEEK... IT WAS A BIT SCARY AND FRUSTRATING UNTIL
I FIGURED OUT HOW TO FIX IT.. ITS NOT HARD. ILL PUT DOWN HERE WHAT I DID...
1. DOWNLOAD THE GOOGLE NEXUS 7 TOOL KIT... ( this is a very good rescue tool )
2. RUN IT... INSTALL THE DRIVERS... REBOOT IT ALL AND START THE TOOL KIT AGIAN WITH YOUR TRANSFORMER
CONNECTED TO USB...
3. YOU SHOULD SEE THE SERIAL NUMBER OF YOUR TABLET AT THE TOP OF THE PAGE IN THE TOOLKIT...
IF SO..YOUR ALMOST DONE !
4. THERE ARE MANY CHOICES..SOME WORK SOME DONT ON THE TRANSFORMER...
5. I CHOOSE THE ROOT OPTION...
6. NOW..WHEN IT GETS TO THE PART WHERE IT SAYS ARE U IN FASTBOOT MODE.. SAY NO !!! THAT WILL ACTUALLY
PUT IT IN FASTBOOT AND THEN PROCEED AS DIRECTED ON THE SCREEN TO ROOT...
THATS WHAT I DID...CAUSE I NEEDED ROOT AND I HAD A STUCK BOOT LOOP JUST LIKE YOU.....
BASICALLY YOU NEED TO ROOT IT AGIAN AN THEN REBOOT AND TRY TO GET INTO CWM..OR HAVE IT REINSTALL CWM...TO FLASH A ROM...THAT WORKS..

[Q] Flashed Recovery for Another Device

I was in the process of upgrading TWRP on my phone when I wasn't paying attention and accidentally flashed the wrong zip (This one to be exact).
Now the phone shows no signs of life. Doesn't respond to any button combination presses, or when connecting it to a computer. Doing some searching, I came across this thread. Is that applicable for my situation, or should I just get a JTAG service on it? Thanks, and let me know if I'm not providing enough details. I appreciate the help.

CommieSalami said:
I was in the process of upgrading TWRP on my phone when I wasn't paying attention and accidentally flashed the wrong zip (This one to be exact).
Now the phone shows no signs of life. Doesn't respond to any button combination presses, or when connecting it to a computer. Doing some searching, I came across this thread. Is that applicable for my situation, or should I just get a JTAG service on it? Thanks, and let me know if I'm not providing enough details. I appreciate the help.
Click to expand...
Click to collapse
Yes try that, if partitions do not enumerate properly, only choice is jtagg.

exad said:
Yes try that, if partitions do not enumerate properly, only choice is jtagg.
Click to expand...
Click to collapse
How about leaving the phone consuming the battery, then plugging it to AC, charging it a little, letting it booting normally then using adb reboot bootloader to make the phone enter the bootloader mode and flashing the right recovery with fastboot flash .... The whole point is to make the phone reach the bootloader state, isn't it?
Later edit: I thought you have flashed only the wrong recovery. The above method might help only in that case. When the partition table and the bootloader partition are overwritten, only a jtag may help. And expect your phone not to look the same!
Another edit: Isn't the OTA script supposed to check the phone platform before starting to write the files? Then, when flashing an OTA zip, the recovery decompresses its contents and if it doesn't have enough space, it ends the process with an error. What am I missing here?

AlxMAX said:
How about leaving the phone consuming the battery, then plugging it to AC, charging it a little, letting it booting normally then using adb reboot bootloader to make the phone enter the bootloader mode and flashing the right recovery with fastboot flash .... The whole point is to make the phone reach the bootloader state, isn't it?
Later edit: I thought you have flashed only the wrong recovery. The above method might help only in that case. When the partition table and the bootloader partition are overwritten, only a jtag may help. And expect your phone not to look the same!
Another edit: Isn't the OTA script supposed to check the phone platform before starting to write the files? Then, when flashing an OTA zip, the recovery decompresses its contents and if it doesn't have enough space, it ends the process with an error. What am I missing here?
Click to expand...
Click to collapse
It isn't an OTA script. When flashing something through fastboot there isn't really any check. Numerous people have made this mistake:
fastboot flash boot recovery.img
They're attempting to flash a recovery but they've accidentally flashed a recovery to the boot partition which will obviously mean the device can't boot. This is just an example I'm using to highlight the fact that you are your own safety barrier when flashing via fastboot, if you get it wrong, there's a high chance of bricking.
This particular user has flashed a recovery to the recovery partition but because the recovery is for another device it has corrupted the recovery partition and probably the other partitions too.
Sent from my Evita

I got a Jtagg on my phone and it was saved.

Not ever remotely relevant.
Sent from my Evita

Bootloader Flash from TWRP (anything flash?)?

I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not:
Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there. Stupid problem to have right here, lol.
Any thoughts/help is appreciated. TIA.

Okay, so I got around the issue. I'm not sure if TWRP is supposed to be able to fastboot or ADB but mine would not, I was under the impression that I could fastboot or ADB in recovery. Maybe that was just a mistake on my part thinking that.
My workaround:
- Reboot into the bootloader (not TWRP recovery), 3 finger reset, power off, then power button + vol up + vol down until you get the OEM Android bootloader screen (unplug if plugged in, it didn't seem to want to go into bootloader when it was plugged in - maybe I just didn't wait long enough, but unplug if it doesn't want to go into the bootloader).
- From here I was able to fastboot, "fastboot devices" listed it
- I then flashed the bootloader: "fastboot flash bootloader bootloader-hammerhead-hhz12h.img" (may differ if you wan to flash different bootloader)
- I then rebooted into bootloader: "fastboot reboot-bootloader"
- I then flashed recovery: "fastboot flash recovery openrecovery-twrp-2.8.5.2-hammerhead.img" (may differ for different version of recovery)
- I then used vol up/vol down to select "reboot recovery", and hit the power button
- TWRP booted and from there, now that I have the hhz12h.img bootloader flashed I could install the ROM, so I wiped data/dalvik/cache/system again, installed the ROM, installed Gapps, and rebooted, good to go.

FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.

Primokorn said:
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Click to expand...
Click to collapse
Got it. For whatever reason I could not get ADB to see the device while I was in TWRP. I tried the ADB sideload feature in 'advanced' but it just waited and waited and waited forever. I believe ADB is set up properly on my system because it works fine on ROM. Not sure what the deal is with that, but I don't have much reason to go into ADB in recovery anyway aside from this issue, so it's [hopefully] not a big deal.
As for flashing the recovery, yeah, bad habit I guess. On my old phone (Fascinate Galaxy S 1), if you had custom recovery and had to 3-finger reset to bootloader because your phone wouldn't turn on or was bootlooping or whatever the recovery was boned, had to re-odin flash it. So it's stuck in my memory now that if I had to 3 finger it I better flash recovery. I'll try to knock myself out of that habit .
Thanks!

Syndacate said:
Is there a TWRP zip-install hhz12h bootloader I can use?
Click to expand...
Click to collapse
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)

Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk

Wakamatsu said:
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Click to expand...
Click to collapse
Thanks, I'll snag that just in case I ever have a fastboot outage or I'm on a system w/o ADB/fastboot or something.
ldubs said:
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Haha, I didn't even look at the dates, I just went to the "Tools/Utilities" page for the Nexus 5 and it was the top link....I didn't think too much on it, just figured top link = most recent = latest.
http://forum.xda-developers.com/showthread.php?t=2511507
I'll dig around for a thread which has latest and flash that on there, can't expect old versions to work flawlessly, now can we?
EDIT:
That actually might have just been a copy/paste error on my part, as I had the old TWRP lying around for fastboot and copy/pasted the name from that. I used TWRP (ROOT) app to install and I chose latest (or so I thought). Now I have literally NO idea which one I was using -_-.

No worries glad you got it sorted. You can flash an image file in twrp now BTW.
Sent from my Nexus 5 using Tapatalk

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

[HELP] Nexus 5 stuck on bootloop + bootloader locked + can't access recovery

Hi,
I have come here seeking help for repairing my Nexus 5 which is stuck in bootloop. The phone wasn't rooted with possibly no custom recovery and it's bootloader is locked. And I am not sure which firmware was on it. And I also don't know what was done to it for it to become "bricked" as it was given to me in that state.
I can access the Bootloader Mode (a.k.a. Fastboot) but when I try to enter the Recovery Menu it gives me an Android logo with the red triangle with "No Command." written underneath it. And since the bootloader is locked, I am unable to flash a Stock ROM on the phone.
I have somehow managed to "temporarily" unlock the bootloader by entering the following command.
Code:
fastboot oem unlock
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
So I tried entering that command then I immediately entered the following commands to flash the stock 6.0.1 recovery.img
Code:
fastboot erase flash
fastboot flash recovery recovery.img
But in vain, as it still gives me the "No Command." Android logo when I run the Recovery Mode. I have also tried the same procedure with the TWRP recovery.img but with the same results.
I have also tried launching the flash-all.bat from the stock 6.0.1 right after running the bootloader unlock command mentionned previously. But it fails as i guess the flash-all.bat is programmed to reboot the bootloader before flashing. Thus re-locking the bootloader right before attempting to flash it.
I have come here seeking for help as I believe XDA is the most active Android community online.
If my post is somehow against any forum rules here, please be indulgent as this is my first time posting on XDA.
Thanks in advance.

At first, fastboot erase flash is not a working fastboot command. It is used to erase a partition: boot, cache, data...
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".

NexusUser5 said:
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
Click to expand...
Click to collapse
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.

Primokorn said:
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
Click to expand...
Click to collapse
Yes the bootloader gets re-locked. And pressing Volume Up doesn't work either.
JonesL said:
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Click to expand...
Click to collapse
I've tried the tool and I can't get it to work properly as it gives me an error saying "partition.txt does not exist. Please extract the file from the total binary image."
UPDATE: I just got it to work. The SDRAM test passed but EMMC test failed. So that means it's hard-bricked right? And is changing the motherboard the only way to fix it?

I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.

audit13 said:
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
Click to expand...
Click to collapse
I suspect a hard-brick, so I am strongly considering it. Would you know if motherboards are carrier specific? Meaning if I get a motherboard from another carrier's Nexus, would it end up changing the carrier of my phone?

Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.

audit13 said:
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
Click to expand...
Click to collapse
Thanks a lot for your help, very much appreciated.