Database Users

Android 4.3 image errors

Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Issue fixed, see below!
************************************************************************************************
Ok guys, the problem was solved in an odd way!
I got annoyed with the flashing errors, and flashed the old kernel and radio I was using with my Illusion rom which thankfully got me back to that even though I had lost all of my data (backed up though).
For anyone having this problem and wants to unroot to go back to 4.3 or is trying to flash the legit 4.3 rom from Google and then maybe unroot or just use the 4.3 rom direct from Google...
DOWNLOAD THE LEAKED 4.3 ROM AND FLASH USING STANDARD CWM METHOD.
DOWNLOAD THE .84/.83 KERNEL AND FLASH THIS AS WELL.
After this I got the legitimate OTA update which was only 3.4mb and it even fixed root so I am now back to complete stock, locked bootloader and no root!
Hope this helps
Click to expand...
Click to collapse

Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode. Personally, I do the following:
1. Extract the entire TGZ (including the update.zip)
2. Move all the IMG files into one folder
3. Rename them to easy names, e.g. bootloader, radio, system, userdata, boot, recovery, etc.
4. Flash them all in turn, rebooting the bootloader each time
5. Once all done, erase/format the cache (fastboot erase cache and fastboot format cache)
6. Boot into recovery and clear cache again and then do a factory reset (this makes sure the unit see all the internal memory)
7. Reboot the phone
Should all work now

siravarice said:
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Click to expand...
Click to collapse
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
4.3 (JWR66V)
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
7zip
http://www.7-zip.de/
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312

EddyOS said:
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode
Click to expand...
Click to collapse
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?

info.brandenburg said:
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
Click to expand...
Click to collapse
Did that, same thing happened. I tried flashing the entire .zip and then I tried separately and it still didn't work.

Ok so I know it is just the system.img file that doesn't work, as all the other files have just flashed fine! Going to re-download and see if that helps.

siravarice said:
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
Click to expand...
Click to collapse
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows

EddyOS said:
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
Click to expand...
Click to collapse
Still doesn't work.
I used: bash flash-al.sh
And it just said fastboot not found in certain lines for the command and did nothing. I thought it fixed itself when I swapped USB ports but when it got to the system.img it just gave me the same error again. It flashes everything else ok but not this file, it's the third time I have downloaded it and now I have no way to get it back to being useable as when I press start it just gives me a black screen
HELP PLEASE!

I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again

EddyOS said:
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
Click to expand...
Click to collapse
Im trying to install some Samsung Android Drivers on my old laptop but the thing is so slow it's basically impossible to work from now
I've redownloaded the files, I don't know how to check the MD5Sum though. Still nothing doing. I get this error:
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6166 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6664 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
edue3e4:4.2unrootnexus4 Simon$
It really doesn't want to write the system.img file, or maybe it doesn't want to write to system?

What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
efrant said:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this
Click to expand...
Click to collapse

EddyOS said:
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
Click to expand...
Click to collapse
That's exactly what I have been doing, I prefer doing it manually as I don't like using Toolkits and finding a good one for mac is hard enough.
It just says that it cannot send it because the file or directory does not exist, yet if I unplug the phone it does go back into my old rom I was using before that, even though I flashed a new radio and recovery.img, boot.img, user data.img, everything except system.img as it doesn't work

Something clearly wrong with the partition but no idea what...

I know right, I've gone back to the ROM I had previously and downloaded the leaked 4.3 rom and flashed it through flashify. If it works I will simply lock the bootloader again and it should be good to go!

i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again

Hmmy 4444 said:
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Click to expand...
Click to collapse
Let me know if you get anywhere with it!

it worked.. jst copy the image n dont rename it n go to google nexus 4 toolkit folder n there u would see a folder named *put googlr factory image here* paste it there n before starting ur bootloader must be unlocked.. so thats that.. after that that open the nexus 4 toolkit n then click on number 9 whch says download extract + flash google factore stock rom n then after that type 2 whch says flash google factory image... n thats it. it will automatically flash it.... gv me thanks too
Sent from my Nexus 4 using xda app-developers app

Hi there, same issue with me on a mac
Plus can you tell me how you went back to the previous rom, my phone is unusable right now and i do have a nandroid backup so.

Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium

EddyOS said:
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I dont mind, can you direct me towards a post where they show how to, i m not sure of all this and dont want to mess around with wrong files.
UPDATE: I tried and that works just fine. Rebooted to 4.2.1

[GUIDE]Nexus 9 back to stock guide - Unbrick - Restore factory firmware

The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition

Great. Is it possible to make a batch file to run all the commands at once?

albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.

i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?

Cool, thanks for the information.

Thanks for creating this! Will come in handy. Saving this for later

This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.

scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app

remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1

cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.

doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.

I also used Linux but I executed the commands individually rather than using the script. It worked.

remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s

nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.

These instructions also worked with 5.1.1

im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode

maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?

[XT1022] 5.1 Stock Firmware

Need to be flashed via fastboot
Doesn't matter which ROM you are using !
Just flash it !
You will be on stock 5.1​
Steps :
Download and install Moto E drivers on your pc. Link : https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/99012/p/30,6720,9146
Download mfastboot files and extract the files in a folder. Link :https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Download Stock firmware for XT1022 and extract the files to the same folder. Link :https://drive.google.com/file/d/0B05Crz57q4zgbFQ5b0dDck5yWGc/view?usp=sharing
Now, reboot your phone into bootloader by pressing volume down + power for a few seconds. You will see the bootloader screen.
Go to the folder where you have extracted Stock Firmware and mfastboot files and open command prompt there (Press shift + right mouse button and click on open command prompt)
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
Hit thanks, if helped

It don't stuck in recovery logo flicking ?

which commands?

Which command to be used

Shaikh Arbaaz said:
Which command to be used
Click to expand...
Click to collapse
Use this command bat Retail.bat in zip file.

prince.d.emperor said:
Need to be flashed via fastboot
Doesn't matter which ROM you are using !
Just flash it !
You will be on stock 5.1​
Steps :
Download and install Moto E drivers on your pc. Link : https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/99012/p/30,6720,9146
Download mfastboot files and extract the files in a folder. Link :https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Download Stock firmware for XT1022 and extract the files to the same folder. Link :https://drive.google.com/file/d/0B05Crz57q4zgbFQ5b0dDck5yWGc/view?usp=sharing
Now, reboot your phone into bootloader by pressing volume down + power for a few seconds. You will see the bootloader screen.
Go to the folder where you have extracted Stock Firmware and mfastboot files and open command prompt there (Press shift + right mouse button and click on open command prompt)
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
Hit thanks, if helped
Click to expand...
Click to collapse
Already posted on XDA for all versions. Why you duplicate the post.http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111

Have you tried it??
Will it cause bootloop as it occurs it many cases.

chaithanya0207 said:
Already posted on XDA for all versions. Why you duplicate the post.http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Click to expand...
Click to collapse
I didn't duplicate.
I respect that post but that has been edited and the stock ROM for XT1022 has been added later to that post.

thanx

Is this working?
Which are the fastboot/adb commands?
All of them are to be executed when flashing?
My Phone isn't booting, how to flash Stock ROM?

chaithanya0207 said:
Already posted on XDA for all versions. Why you duplicate the post.http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Click to expand...
Click to collapse
Those are OTA, not Fastboot Files,Broo.
Thnx to this Broo for the Fastboot files,

lul
thank you

Can the rom zip file be flashed from the stock recovery?, i dont have twrp and my pc wont detect my phone when i its connected via usb cable. My moto e is bootloader unlocked, and its stuck at the bootloader unlocked warning message and i can boot to recovery, so i was thinking mabe i could flash the stock rom zip file from the stock recovery

Soooo, theoretically if one were to follow these same steps on a XT803C (Straight talk Moto E CDMA variant), would this boot or brick? Haha, sorry I know how tough that is to answer, but this phone is $26 on NewEgg & I'd love to break it, I don't care about modem working, it will never have service just wifi only, so I figured id ask xD

Thanks

i have stucked at bootloader while iam flashing it says preflash verification failed and i didn't even root my device,please help me

I can't thank you enough for this OP. You're a live saver.

hey guys i am stuck.......
this screenshot would explain it all.......
please help......
https://drive.google.com/open?id=1Qaim6BJPdXRc97G0nXYz6dhleNoU9FYc

unable to load from fastboot

I am trying to flash the kernal for 5.1.1 after a restore to stock and get my wifi going again. I placed the kernal zip in the adb folder
where I have the adb and fastboot exe files. I opened the command prompt in that folder after I unziped the kernal to get the img.
I can fastboot reboot bootloader, and fastboot devices, which shows the s.n for the phone. When I used the, fastboot flash boot v4tk-kernel-uber-alias.img, command I get an "unable to load"? Whats going on and how do I fix this. Same thing happened when I tried to flash non-hlos.bin. Help please....I am using windows 10.

Garyalp said:
I am trying to flash the kernal for 5.1.1 after a restore to stock and get my wifi going again. I placed the kernal zip in the adb folder
where I have the adb and fastboot exe files. I opened the command prompt in that folder after I unziped the kernal to get the img.
I can fastboot reboot bootloader, and fastboot devices, which shows the s.n for the phone. When I used the, fastboot flash boot v4tk-kernel-uber-alias.img, command I get an "unable to load"? Whats going on and how do I fix this. Same thing happened when I tried to flash non-hlos.bin. Help please....I am using windows 10.
Click to expand...
Click to collapse
Somebody? Im sure Im not the only one with this problem.....

Flashing boot and modem are pretty straight forward. Not sure what your issue is.

Garyalp said:
I am trying to flash the kernal for 5.1.1 after a restore to stock and get my wifi going again. I placed the kernal zip in the adb folder
where I have the adb and fastboot exe files. I opened the command prompt in that folder after I unziped the kernal to get the img.
I can fastboot reboot bootloader, and fastboot devices, which shows the s.n for the phone. When I used the, fastboot flash boot v4tk-kernel-uber-alias.img, command I get an "unable to load"? Whats going on and how do I fix this. Same thing happened when I tried to flash non-hlos.bin. Help please....I am using windows 10.
Click to expand...
Click to collapse
The only things I can think of that would cause that would be either the file is not in that directory or it's not spelled correctly. For the modem are you typing non-hlos or NON-HLOS? It should be all caps. As for the boot image, try renaming it. That's about all I can think of.
Sent from my XT1575 using XDA-Developers mobile app

Help with rooting P8-lite Ale L21 dual-sim C432B564

I have a relatively new P8-lite L21 dual sim phone and I am quite happy with it. It came with C432B170 which is Lollipop I think 5.01. After a few days it updated to B172. I have unlocked the bootloader after registering with Huawei and waiting 2 weeks. Then I have successfuly rooted the phone with Kingroot phone version. Two or three weeks ago I have updated the phone to MM (6) and Emui 4 with local update (B560) that I have gotten from this forum. 2 days ago I recieved the notification of OTA B564 which went smoothly beside the fact that it reset the phone but i have succesfully restored (contacts, data etc.) All of this time since I upgraded to MM i have tried to root the phone but I was unsuccesful either with any software solution ( Kingroot, Kingoroot or others). After reading most if not all discussions on this forum and several blogs and how -tos, I tried the so called fastboot method others have recommended but here is now the gist of my problem. My phone is seen by my PC - OK so USB drivers are properly installed (by the way my PC is Win 10) and I have installed Android SDK as well as minimal ADB. When i try to flash TWRP 3.00.2 I can not do it (the message says something about not able to access or i think remote command not allowed. So since I cannot flash TWRP i am unable to put SU on the phone and root it. I hope someone more experienced and skillfull in Android world can point me in the right direction and help me. Thank you

Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.

VladHD said:
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
Click to expand...
Click to collapse
Downloaded minimal adb fastboot and installed it. Tried the procedure. Copied TWRP recovery to the minimal folder. Shift right clicked in the folder of minimal and opened command window. Adb rebooted to bootloader. Phone shows it is unlocked. The device is seen in fastboot window but flashing recovery doesn't work (same message) I am really confused. How do I give adb full permissions ?
Any way thanks in advance.

Did you activate usb debugging ?

VladHD said:
Did you activate usb debugging ?
Click to expand...
Click to collapse
Yes of course !

Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.

VladHD said:
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
Click to expand...
Click to collapse
The drivers were reinstalled. My bootloader shows unlocked on bootloader (bottom of fastboot screen). Fastboot devices does nothing. Adb devices shows my phone serial number correctly (I have it written down). But then when i try to flash recovery it is unsuccessfull. It says "FAILED (remote: Command not allowed)"

What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img

doomking_99 said:
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
Click to expand...
Click to collapse
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)

amageek said:
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
Click to expand...
Click to collapse
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.

doomking_99 said:
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
Click to expand...
Click to collapse
ahhh... sorry mate, dont know the solution.. but try re-installing adb drivers again ...

Are you logged as adminstrator on pc?
Try to plug usb into different slots.

VladHD said:
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
Click to expand...
Click to collapse
I am and I have. I am stumped. Obviously something is wrong with windows permissions I think. Is it possible to put recovery. img on sd card or on phone and flash recovery from the phone ?

This is the output every time no matter which usb port
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
W3D7N15C08019820 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.624s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
C:\Program Files (x86)\Minimal ADB and Fastboot>
The thing i don't understand is why fastboot command doesn't show device while adb command does.

You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.

doomking_99 said:
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
Click to expand...
Click to collapse
Sorry for the zombiethreading here, but... what whas the solution? I'm curious

For the time being there is no solution. Can not flash TWRP - phone not rooted

doomking_99 said:
For the time being there is no solution. Can not flash TWRP - phone not rooted
Click to expand...
Click to collapse
Weird... i can't think of anything else myself that hasn't been said. Perhaps... redownloading twrp? Maybe the image is corrupted by something... ot's a long shot because ot should flash everytging that comes its way. But it's the only thing you hven't tried.