Develop Bugs

TWRP Recovery & Possible ROM Issues

I rooted my kindle fire using kfu 9.8. As of this moment when I install roms they do not boot up and they stay at the boot logo. I dont know if it has to do with TWRP or the roms, but I have tried 2 cm10 roms and one AOSP 4.2.2 rom. I will tell you exactly what I did.
1. Rooted with kfu
2. went straight to recovery, flashed the aosp rom + google apps
3. Booted up and it stayed at the boot screen
4. Tried another rom, put it onto the device through usb mounting with twrp
5. Still stuck at boot logo
6. Tried the last rom but still stuck!!
After that I tried to flash back to stock using this
(doesnt let me post a link if requested I will pm)
But twrp gave an error and it did not install, it said somewhere an error doesnt matter and you would boot up fine but I didnt
Between installing all Roms I wiped cache, dalvik, and factory reset.
Thanks in advnce!
EDIT
Used this to try to bring to stock
theunlockr DOT com/2012/10/29/how-to-unroot-the-amazon-kindle-fire
Used these roms (all on xda)
/showthread.php?t=2100963
/showthread.php?t=2041694
cant find the third rom
EDIT
I have no problem using adb or fastboot so feel free to try and fix my problem with those.

Ilia Goro said:
But twrp gave an error and it did not install it said somewhere an error doesnt matter and you would boot up fine but I didn't
Click to expand...
Click to collapse
It would be very helpful to know exactly what error you are receiving.

soupmagnet said:
It would be very helpful to know exactly what error you are receiving.
Click to expand...
Click to collapse
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.

Ilia Goro said:
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Click to expand...
Click to collapse
Any update on this? I'm getting the same issue on mine.

Runaround said:
Any update on this? I'm getting the same issue on mine.
Click to expand...
Click to collapse
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app

philipsw said:
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.

votinh said:
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
Click to expand...
Click to collapse
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app

philipsw said:
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.

2.2.2.1 zip?
votinh said:
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
Click to expand...
Click to collapse
where did you find the zip file?

TWRP
You need TWRP 2.6.3.1 too install KitKat Roms here is the link for your first gen fires you need the otter.img
TWRP

PLEASE HELP! Kindle Fire 1st Gen. I've looked everywhere for answers
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?

Feedback
DroidLover93 said:
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Click to expand...
Click to collapse
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??

lj50036 said:
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
Click to expand...
Click to collapse
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.

DroidLover93 said:
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
Click to expand...
Click to collapse
And you are using the firefirefire utility??

lj50036 said:
And you are using the firefirefire utility??
Click to expand...
Click to collapse
Yes, I believe so.

TWRP
DroidLover93 said:
Yes, I believe so.
Click to expand...
Click to collapse
We need to get you on the latest version of twrp....http://techerrata.com/browse/twrp2/blaze
Go here and get version 2.6.3.1 make sure your get the otter.img as the blaze is for the 2nd gen fire....
Let me know if you need any help with this.. Let me know when you have it installed....Thx lj
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows....

@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7

Feedback
DroidLover93 said:
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Click to expand...
Click to collapse
Check this forum for your fastboot adb driver needs...http://forum.xda-developers.com/showthread.php?t=2588979
Hold on a sec I will make you a flashable recovery zip for easy of installation...

TWRP 2.6.3.1
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399

lj50036 said:
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
Click to expand...
Click to collapse
Thanks! Okay so TWRP update was successful. Then I followed the link for ADB and fastboot. I installed them to PC. Now, just to be clear.. Was I supposed to do that with the USB connected to my device? or was that just for my PC? I just dont want to mess anything up.

[Q] Accidently Deleted Android and Don't Know How To Reflash It!

I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!

GabuscusMason said:
I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!
Click to expand...
Click to collapse
You will need to use the ADB sideload feature of TWRP to upload a rom to install. Research ADB on how to use it as well as the sideload feature of TWRP. You will need to connect the tablet to your PC for this,.

What he said ^^
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.

And as for adb drivers, here is a link to a post by Koush with a driver install that should work without any issues.
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

DaveRichardson said:
NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.
Click to expand...
Click to collapse
I've done what the OP has done, and if I recall, getting the device into download mode will allow Wug's Toolbox to pick it up from there. I reinstalled the OEM rom, rerooted and reinstalled TWRP. You can download the OEM rom from the toolbox.

[Q] [VK810] Stuck in Fastboot. Need Boot Image

Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark

dadof10 said:
Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark
Click to expand...
Click to collapse
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.

sleekmason said:
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.
Click to expand...
Click to collapse
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app

dadof10 said:
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
sleekmason said:
double check and make sure it is for your device. Link to Recovery
Click to expand...
Click to collapse
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!

sleekmason said:
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!
Click to expand...
Click to collapse
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app

dadof10 said:
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....

mcerk02 said:
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....
Click to expand...
Click to collapse
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app

dadof10 said:
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img

sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
Ok, I got it. Duhhh...I re-read it and it makes sense now. Somehow I had it in my mind that I had to open terminal emulator on my GPad, which I can't do. I'll try it tonight when I get home from work and let you know how it goes. Thanks again.
Sent from my SM-G900V using XDA Free mobile app

sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?

dadof10 said:
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?
Click to expand...
Click to collapse
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?

sleekmason said:
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?
Click to expand...
Click to collapse
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.

dadof10 said:
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.
Click to expand...
Click to collapse
not saying you should, but you could always try to flash the recovery just to see if it would work.

same problem, but how I fixed it
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.

Downgrade aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.

pakron said:
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.
Click to expand...
Click to collapse
Sir or m'am, in the future, you shouldn't post the same thing in two different threads.

FynxSyndct said:
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.
Click to expand...
Click to collapse
i was having the same issue, get the boot.img file and typed "fastboot flash boot boot.img" after moving the boot.img file into the same folder as adb/fastboot and it worked, thanks bro!

Lg g3 700 fastboot mode started when going to recovery

Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.

Any updates? Im having the same exact problem (d851)

In which computer you are trying the process. Which windows is installed on computer that you are using for installing stock rom.
Which guide you are following to install stock rom. Have you unlocked your device for bump, if not follow the guide.
http://forum.xda-developers.com/lg-g3/orig-development/bump-unlock-lg-g3-twrp-d852-d852g-f400-t2900614

I am dead sure that your board is not d855.open your phone to confirm this.that is the reason your twrp is not compatible with your board.

droidrzr1610 said:
Any updates? Im having the same exact problem (d851)
Click to expand...
Click to collapse
Same problem for me.
I was using TWRP for weekly update of LineageOS 16.1 on D855 with no problem.
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App.
Then I tried to boot in Recovery mode and I got black screen with the message:
[700] fastboot mode started
I tried older version with no success installing them with ADB or TWRP App.
---------- Post added at 06:55 AM ---------- Previous post was at 06:32 AM ----------
Polex73 said:
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App..
Click to expand...
Click to collapse
I noticed the twrp-3.4.0-0-d855.img file was corrupted.
I downloaded from the https://eu.dl.twrp.me/d855/ directly to the phonr.
Problem solved

Recovery doesnt boot on D851. Goes into fastboot mode instead.

So I recently bought an Lg G3 D851 and the phone was already Rooted and bootloader unlocked. So i downloaded some root checkers to verify and then installed SuperSU. Since after doing some research I knew that the T-Mobile variant comes with a factory unlocked bootloader. I tried flashing the latest twrp from their own website using flashify, it would flash successfully but instead of going into twrp when rebooting into recovery, it just says: Fastboot mode started. It is the same case for all the other recoveries i could find for the d851. Im on Kitkat 4.4.2.

droidrzr1610 said:
So I recently bought an Lg G3 D851 and the phone was already Rooted and bootloader unlocked. So i downloaded some root checkers to verify and then installed SuperSU. Since after doing some research I knew that the T-Mobile variant comes with a factory unlocked bootloader. I tried flashing the latest twrp from their own website using flashify, it would flash successfully but instead of going into twrp when rebooting into recovery, it just says: Fastboot mode started. It is the same case for all the other recoveries i could find for the d851. Im on Kitkat 4.4.2.
Click to expand...
Click to collapse
Go to https://dl.twrp.me/d851/
Download the 3.0.2.0
Install Rashr from the playstore. Try flashing it through rashr and let me know what it does. I had problems with flashify and never had a problem with rashr.

Gytole said:
Go to https://dl.twrp.me/d851/
Download the 3.0.2.0
Install Rashr from the playstore. Try flashing it through rashr and let me know what it does. I had problems with flashify and never had a problem with rashr.
Click to expand...
Click to collapse
Tried rashr. Same thing happens.

droidrzr1610 said:
Tried rashr. Same thing happens.
Click to expand...
Click to collapse
Hook it up to the pc in fastboot mode, open a command prompt, and type adb devices, and once it shows the phone type fastboot erase recovery
Then boot the phone and rashr twrp again.
I'll be waitin
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
droidrzr1610 said:
Tried rashr. Same thing happens.
Click to expand...
Click to collapse
Hook it up to the pc in fastboot mode, open a command prompt, and type adb devices, and once it shows the phone type fastboot erase recovery
Then boot the phone and rashr twrp again.
I'll be waitin

Sorry for not replying earlier.. Was busy in exams. Just tried what you said but still got the same results. I even tried flashing the recovery through fastboot but still its the same problem. I have dealt with a lot of android phones in the past, but this is just weird.