Database Info

[Q] TWRP Install Fail

I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:

Seahorse said:
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Click to expand...
Click to collapse
Are you installing the jb compatible twrp? what happens when you try and boot recovery?
Sent from my SGH-I727 using xda app-developers app

I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.

Seahorse said:
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Click to expand...
Click to collapse
When you used twrp to flash stock it includes recovery which overwrites twrp. Go back to the instructions to fastboot twrp, do so and you should be good.
Good Luck!
Try a new download of twrp!
Reboot your pc, only plugin your asus and no other device, retry fastboot.
Forgot, if on dock remove from dock reboot pc and asus and try again.

Clearing cache maybe? Just a shot in the dark, never seen this one. I can tell you I flashed ota v13 and it blew away my recovery but I was able to get it back easily.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

After following numerous google links - too many links fastboot, I found one resolution. Another device used on pc and usb drivers installed since last use of unit giving links error. Resolution was remove offending drivers, reboot pc and profit.
Good Luck!

I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
Click to expand...
Click to collapse
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.

Blew away cache, used fastboot again on twrp.blob and got same install fail error message. However, on power on + vol down RCK now works with TWRP, which is kind of odd, but there you go. Thanks for all the suggestions...

glad you got it fixed

SITH16 said:
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
Quote:
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Click to expand...
Click to collapse
Three things come to mind.
1. Try to flash as twrp directions show; without adb reboot bootloader.
2. Verify you are trying to flash the proper version for your bootloader; ics or jb.
3. If the above two items fail redownload proper version for your boot loader and try again.
Note: The twrp page also shows how to flash with adb!
Good Luck!

Terminal Emulator is an easier way to flash TWRP imo. But hey.

babymatteo said:
Terminal Emulator is an easier way to flash TWRP imo. But hey.
Click to expand...
Click to collapse
Terminal method worked. Thanks everyone for helping me out.

TWRP Install Fail
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?

BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
this is the tf300t forum. Make sure you are installing a tf700t TWRP

cmendonc2 said:
this is the tf300t forum. Make sure you are installing a tf700t TWRP
Click to expand...
Click to collapse
I noticed that after I hit reply. I was using all of the correct TF700t TWRP and whatnot. I found this in a google search because it was similar to my issue. It turned out that even though I thought I had unlocked my device, it did not unlock. I fixed that and now I am all set.

BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
The warning invalid state normally applies to the bootloader being locked make sure your bootloader is unlocked.
Sent from my Nexus 5 using Tapatalk

I need your help........

I tried to flash a new rom last night and it's all gone wrong. I'll list below what I did and what is happening below.
1. I managed to get s-off no problem.
2. Installed cwm recovery no problem.
3. Super cid went fine.
4. Wanted to flash Android Revolution HD 6.8.0
5. Flashed 3.33.401 firmware, no problem.
6. This is where it has gone wrong.......I ran superwipe. This has done the damage. It said instaltion aborted after that when I try to go to recovery it just goes straight to HTC screen and hangs. If I take the battery out it does the same. I t was getting late so I left it till the morning. All it is doing now is when I plug it in the yellow light flashes then goes solid, the cwm flashes very briefly and goes off. It does this a couple of times then the phones goes dead, no light or anything. If I take battery out it just does the same cycle.
Please help.....is this any way recoverable?

Charlie3999 said:
I tried to flash a new rom last night and it's all gone wrong. I'll list below what I did and what is happening below.
1. I managed to get s-off no problem.
2. Installed cwm recovery no problem.
3. Super cid went fine.
4. Wanted to flash Android Revolution HD 6.8.0
5. Flashed 3.33.401 firmware, no problem.
6. This is where it has gone wrong.......I ran superwipe. This has done the damage. It said instaltion aborted after that when I try to go to recovery it just goes straight to HTC screen and hangs. If I take the battery out it does the same. I t was getting late so I left it till the morning. All it is doing now is when I plug it in the yellow light flashes then goes solid, the cwm flashes very briefly and goes off. It does this a couple of times then the phones goes dead, no light or anything. If I take battery out it just does the same cycle.
Please help.....is this any way recoverable?
Click to expand...
Click to collapse
hi,
i suggest you to flash 4ext recovery
then from recovery choose format all partitions except sdcard
after that flash the rom
you will be fine

4ext
rzr86 said:
hi,
i suggest you to flash 4ext recovery
then from recovery choose format all partitions except sdcard
after that flash the rom
you will be fine
Click to expand...
Click to collapse
How do I do this if my phone isn't responding now?

Charlie3999 said:
How do I do this if my phone isn't responding now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1631861
step 2 on how to flash 4ext recovery

Ok I've managed to get it back to bootloader but it won't allow me to flash. It starts and says
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (6116 KB)...
OKAY [ 1.493s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.823s
Maybe the de-bugging is turned off

Charlie3999 said:
Ok I've managed to get it back to bootloader but it won't allow me to flash. It starts and says
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (6116 KB)...
OKAY [ 1.493s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.823s
Maybe the de-bugging is turned off
Click to expand...
Click to collapse
Hi,
Look HERE
Use third method.

Wait I've managed to re-unlock my bootloader again and flashed the 4ext. These have both worked, flashing rom now let you know.

I've fixed it, thank you very much for help. You have made my Christmas.

Glad it all worked out for you! Had some very helpful members with those suggestions. Merry Christmas!

I got a new problem. I have s_off two phones already and my friend asked me to do his. I did the dev unlock and then tried to s_off with juopunutbear. It didn't work I keep trying it and it keeps rebooting after I touch it with the wire once. It won't even boot to android anymore it just sits there with the juopunutbear screen showing and that's it. I can't understand as I'm doing the same as I did with my other two phones.

[Q] bricked? not sure

Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?

Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?

Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app

Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?

Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app

installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.

any suggestions on trying something else?

waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk

unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?

waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk

Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?

waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there

Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.

abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.

What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.

abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?

waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6

abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s

Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.

[Q] Can't boot into TWRP after updating to 4.4.3

Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.

maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything.
Any help is appreciated.
Click to expand...
Click to collapse
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?

dottat said:
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
Click to expand...
Click to collapse
Worked like a charm. Thanks!

maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.

santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
Brain fart on my part. Such an obvious mistake. Thanks!

santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?

cntryby429 said:
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
Click to expand...
Click to collapse
Yeah I know that was possible in the past, to flash a rom using a recovery one time, without overwriting the current one.
As I've never seen any real need or purpose to doing that, I've never done it that way.
I do know that the other command is what should be used to actually overwrite and flash a new recovery for further use.
So I can't really answer as to whether that method still works or not.
Didn't sound like it did for him though.

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk