Database Develop

[TOOL]Flasher for the Kindle Fire HD 8.9

Disclaimer: I am not responsible in any way if using anything I've made causes hard bricks,bootloops,alien abductions or any other problems.
Hey guys!
It's been some time that I've been seeing people having problems flashing the 2nd Bootloader and TWRP recovery to the 2012 Kindle Fire HD 8.9". So,I decided to create this tool. May I present to you,
8.9 Flasher
By SafinWasi​
This is a batch file which can flash the 2nd Bootloader and TWRP recovery to the 2012 Kindle Fire HD 8.9",complete with ADB and Fast boot executables,stack override,disable auto-recovery update script as well as the 8.1.4 Bootloader downgrade to prevent red screens.
Working features:
Device verification through fastboot.
Flashing Freedom boot and TWRP
Downgrading the Bootloader to 8.1.4
Stack override
Disabling auto-update recovery script
Reboot into TWRP(optional)
Backing up boot,recovery and system partitions.
Restoring previously made backup
Click to expand...
Click to collapse
Steps to use:
Download the zip and extract it.
Read the ReadMe.txt carefully.
Install the Kindle Fire ADB drivers(if needed)
Run Flasher.bat as Administrator.
Follow the on-screen instructions.
Click to expand...
Click to collapse
Changelog:
[30/03/2014]Initial Release
Click to expand...
Click to collapse
Download link:
Looks like a new version is to be released.
Click to expand...
Click to collapse
Notes:
This tool is designed to work for Amazon OS version 8.4.6. So,using it on any other software might get you into a bootloop,but TWRP recovery and Freedom-boot will work.Because of this,it is recommended to do the following things before using this tool:
Rooting the device.
Backing up any important data.
Placing the ROM and GApps zips on the sdcard in case you get a bootloop,so that you can just flash those in recovery after doing a complete wipe.
Preparing to lose the Amazon OS
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/8.9-Flasher.git
Click to expand...
Click to collapse
Credits go to Hashcode,seokhun,BuQQzz,fattire,very green and anyone else whose work helped me.
​Please hit the Thanks button if this tool helped you. Feel free to comment below to suggest any modifications,report any issues or for any help.
Thanks.
Please ignore the following lines that tell you that this tool is for the Kindle Fire HD 7". It's not. It's for the 8.9" tablet.
XDA:DevDB Information
8.9 Flasher, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Anonymous.123, SafinWasi
Version Information
Status: Beta
Beta Release Date: 2014-03-30
Created 2014-03-30
Last Updated 2014-07-07

Reserved

Not a single reply? Thanks for the tool.

So, the option to flash Freedom boot and TWRP can only be done from within the OS, huh? Is there a way to do it in fastboot?

captainreynolds said:
So, the option to flash Freedom boot and TWRP can only be done from within the OS, huh? Is there a way to do it in fastboot?
Click to expand...
Click to collapse
Well,the flashing IS done in fastboot by my tool. If you want to flash in the OS,you'll have to use either FireFlash (search for it) or the terminal emulator.
For the TE:
Code:
flash boot kfhd8-u-boot-prod-8.1.4.bin
flash bootloader <filename>.img
flash recovery <filename>.img
reboot
The 8.1.4 bootloader downgrade is to prevent red screens.

Can't get the ADB drivers to install. I'm running Windows 8.1 x64

donalgodon said:
Can't get the ADB drivers to install. I'm running Windows 8.1 x64
Click to expand...
Click to collapse
You have to disable the driver signature enforcement. Google it. I don't use Windows 8,so I don't know the details.

Windows 8 Help
donalgodon said:
Can't get the ADB drivers to install. I'm running Windows 8.1 x64
Click to expand...
Click to collapse
This may help anyone who needs it, I have it bookmarked.The link below will walk you through installing the drivers on Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2093296

bat ended by saying it was successful. but now i boot into redscreen. any help would be appreciated.

dopepope said:
bat ended by saying it was successful. but now i boot into redscreen. any help would be appreciated.
Click to expand...
Click to collapse
I think it avoided flashing the 8.2.3 bootloader. I'll take down the download links and have a look. You'll need a fastboot cable.
Sent from my device running CyanogenMod 11

Safin thanks for your reply. Trying to figure out the issue I manually loaded uboot 8.1.4, twrp 2.7 and freedom 8.4.6 while in fastboot. now I get the kindle fire logo, but it appears to be stuck in a bootloop (let it sit for 6 or 7 minutes with no change). After reading other posts, I'm concerned that when I rooted my KF because I had the latest OTA that the root actually didn't work, so whatever was loaded with the stack didn't take place.
I'll keep messing around today and let you know if anything changes. Also please let me know if you have any ideas.

just to keep you updated:
used fastboot to push the stock boot and recovery found in hashcodes tutorial.
kindle now boots up, and isn't sluggish (like it was after trying the root method on this website).
used the onemelia system.img file he includes in his recovery tool for the image.
checking now to see if his system.img did indeed included superuser access. i'll update.
---------- Post added 9th July 2014 at 12:33 AM ---------- Previous post was 8th July 2014 at 11:58 PM ----------
OK.
I'm on CM11 now.
the system.img of onemeila is indeed pre-rooted and its 8.1.4
First step for the newest firmware is to revert back to 8.1.4 (with that system img its pre-rooted) and then proceed with the rest of your script.
so:
boot into fastboot> flash onemeila system.img (system1.img in his files)
check root
(turn off wifi, freaking thing updated while i was pushing files, so i had to start from scratch as it killed root)
and then the process as described by hashcode in his tutorial.
hope this helps.

dopepope said:
just to keep you updated:
used fastboot to push the stock boot and recovery found in hashcodes tutorial.
kindle now boots up, and isn't sluggish (like it was after trying the root method on this website).
used the onemelia system.img file he includes in his recovery tool for the image.
checking now to see if his system.img did indeed included superuser access. i'll update.
---------- Post added 9th July 2014 at 12:33 AM ---------- Previous post was 8th July 2014 at 11:58 PM ----------
OK.
I'm on CM11 now.
the system.img of onemeila is indeed pre-rooted and its 8.1.4
First step for the newest firmware is to revert back to 8.1.4 (with that system img its pre-rooted) and then proceed with the rest of your script.
so:
boot into fastboot> flash onemeila system.img (system1.img in his files)
check root
(turn off wifi, freaking thing updated while i was pushing files, so i had to start from scratch as it killed root)
and then the process as described by hashcode in his tutorial.
hope this helps.
Click to expand...
Click to collapse
If it was sluggish after rooting,the problem was in the root,not my tool.

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

TWRP not working: D405

Dear all,
got a LG D405 with Android 5.0.2 and Version V20b here. Wanted to install LineageOS. First I enabled USB Debugging and rooted the device. Then I used ADB to flash the newest Version of TWRP (twrp-3.1.1-0-w7.img). I typed:
adb push twrp-3.1.1-0-w7.img /sdcard/twrp-w7.img
*then*
su (+granting rights on the phone)
dd if=/sdcard/twrp-w7.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Then I shut down the phone and reboot using the key combinations (vol down + power).
After rebooting into recovery mode, nothing happens. I see a blue screen for a fraction of a second, then it goes black and off. Then I can restart the phone normally. How can I get a working TWRP? Thanks for any help!!!

tracko123 said:
Dear all,
got a LG D405 with Android 5.0.2 and Version V20b here. Wanted to install LineageOS. First I enabled USB Debugging and rooted the device. Then I used ADB to flash the newest Version of TWRP (twrp-3.1.1-0-w7.img). I typed:
adb push twrp-3.1.1-0-w7.img /sdcard/twrp-w7.img
*then*
su (+granting rights on the phone)
dd if=/sdcard/twrp-w7.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Then I shut down the phone and reboot using the key combinations (vol down + power).
After rebooting into recovery mode, nothing happens. I see a blue screen for a fraction of a second, then it goes black and off. Then I can restart the phone normally. How can I get a working TWRP? Thanks for any help!!!
Click to expand...
Click to collapse
Did you unlock bootloader?

0000.0000.00 said:
Did you unlock bootloader?
Click to expand...
Click to collapse
No. Basically I follow this guide here:
lineageos.org/devices/w7/install
Now I read a lot here in the forum and think the guide there is very misleading and forgetting a lot of steps. I am very confused because the issue seems to be very complicated and there are so many different versions and solutions. Can someone please tell me which is *the* guide to follow for my phone (LG D405 with Android 5.0.2 and Version V20b)?

tracko123 said:
No. Basically I follow this guide here:
lineageos.org/devices/w7/install
Now I read a lot here in the forum and think the guide there is very misleading and forgetting a lot of steps. I am very confused because the issue seems to be very complicated and there are so many different versions and solutions. Can someone please tell me which is *the* guide to follow for my phone (LG D405 with Android 5.0.2 and Version V20b)?
Click to expand...
Click to collapse
So there is no guide for this and the lineageos one is terrible. So what you have to do basically is get root. Unlock bootloader look around on xda and you have to get patched aboot for your device and stock rom version and flash it. Then flash twrp. With twrp wipe system cache and data partitions. Then flash lineageos and if you want root flash root zip. And if you want gapps flash that too then reboot and setup lineageos.

So, since my device is already rooted... Can I now just flash with a new aboot or do I have to install another stock? As my Version is V20b, this post here says I just can use V20a.
https://forum.xda-developers.com/lg-l90/help/aboot-zip-lg-d405-v20b-t3533401
Is this correct? Or do I have to get a totally different version first? If so, which one? My IMEI tells me this:
Model:LGD405
Suffix:ADEUOP
Latest Firmware40520B_00
I really appreciate any hints. Thank you.
EDIT:
Now I used this file here (https://forum.xda-developers.com/showpost.php?p=54358527&postcount=2), Version 405_v20a with my v20b and it worked perfectly. After I followed this guide here (https://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917) and could install LineageOS 14! Works!!!

tracko123 said:
So, since my device is already rooted... Can I now just flash with a new aboot or do I have to install another stock? As my Version is V20b, this post here says I just can use V20a.
https://forum.xda-developers.com/lg-l90/help/aboot-zip-lg-d405-v20b-t3533401
Is this correct? Or do I have to get a totally different version first? If so, which one? My IMEI tells me this:
Model:LGD405
Suffix:ADEUOP
Latest Firmware40520B_00
I really appreciate any hints. Thank you.
EDIT:
Now I used this file here (https://forum.xda-developers.com/showpost.php?p=54358527&postcount=2), Version 405_v20a with my v20b and it worked perfectly. After I followed this guide here (https://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917) and could install LineageOS 14! Works!!!
Click to expand...
Click to collapse
Good you figured it out but since you didnt quote my post I didnt get notification so I did not see this.

[Recovery] TWRP LG H872 (Unofficial)

Download
v3.2.1-0
Sauce: Github
Fixed /system mounting issues
let me know if you have any issues and I will do what I can to fix them.
Credit: @Josh1x for having the h870 device tree put together for me to clone and update. I will fix the original author on my master branch as soon as I get some time

Thank you!

Works like a charm. No issues here, thanks bro.
---------- Post added at 02:27 PM ---------- Previous post was at 01:42 PM ----------
Also this recovery also fixes the error messages apon flashing mods and what not

How can we apply it if no fastboot commands work

Trippyy Doee said:
How can we apply it if no fastboot commands work
Click to expand...
Click to collapse
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery

MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
So this is all we've been waiting for ?! Finally can haz root ? ?

MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
when i go into recovery mode all i get is no command. what should i do?

purplekushDGK said:
when i go into recovery mode all i get is no command. what should i do?
Click to expand...
Click to collapse
I think you might have to reflash recovery but idk I'm not the best with this

MudaTrucka said:
I think you might have to reflash recovery but idk I'm not the best with this
Click to expand...
Click to collapse
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man

purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
No problem, I thought I'd at least try to help

@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian

MudaTrucka said:
No problem, I thought I'd at least try to help
Click to expand...
Click to collapse
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)

agmyers76259 said:
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
Click to expand...
Click to collapse
Flash the image to recovery, use the steps in the root thread to get it to stick and make sure you're actually booting into recovery and not laf

runningnak3d said:
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
Click to expand...
Click to collapse
Any idea when this might be ready good sir? I am not in a good place right now with my G6, could really use these commands---stuck in TWRP and can boot a rom, but somehow didnt follow your Step 3 in the Root guide, and my misc.img didnt get moved over, thus I have a rom that cannot connect to Wifi due to lack of MAC--this update would be huge, as I would go back to stock and restart this mess.
TIA

That won't help you now. Hopefully you still have the backup of your misc partition that was made in step 2. If so, boot to TWRP, and run:
adb push misc.img /sdcard/
adb shell dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc
-- Brian

how do you flash the update
how do you flash the update? its not a option in the system app

purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
I used flashify and was promted for a decryption password upon booting recovery. Am I doing something wrong?
(Note that I can still access storage on the original download mode twrp, but not on this one)

Like everyone else I'm also confused as to how I can get the h872 recovery to work without breaking anything since I have the h870 recovery on laf

Stupid question I think, but I get a "Traceback (most recent call last):" after entering ./partitions.py --restoremisc twrp-3.2.1-0-h870.img .
Is there a specific place to put the TWRP ing file ? I think when I run the command its not finding the img.

MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
Hey so I already followed this tut last week and have been on root but having issues that this recovery fixes, how can I flash to this TWRP?

[RECOVERY][UNOFFICIAL] TWRP 3.5.2_10 for Moto G 5G (kiev)

DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.
What has been tested and works:
- Touchscreen
- Installing flashable zips
- Flashing images
- Flashing the recovery itself
- Creating backups (to internal storage, sdcard or OTG)
- Restoring from backups
- Terminal
- adb
- Rebooting to system, recovery, bootloader, ...
That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.
Usage (without flashing)
Bash:
# boot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
If you want to flash you have 2 options
Bash:
# boot to bootloader
adb reboot bootloader
# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img
# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.
Download: google drive
Sources will be posted in due time and this post will be updated accordingly.
Built for: Motorola Moto G 5G (Motorla One 5G Ace)
My model: XT2113-3 (kiev)
Credits
To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.

reserved

reserved

Great!

Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.

It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??

clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
It won't brick. I used it. (only once)

clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.

h3xmind said:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
Click to expand...
Click to collapse
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.

PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.

Tomspector said:
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Click to expand...
Click to collapse
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.

I will do it now,
I would help
h3xmind said:
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me
Click to expand...
Click to collapse
I will do it now

Tomspector said:
I will do it now,
I would help
I will do it now
Click to expand...
Click to collapse
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace

Tomspector said:
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Click to expand...
Click to collapse
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.

h3xmind said:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
Click to expand...
Click to collapse
I did not clear my data, I did not feel like redoing my phone today,
It may be that

Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet

Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family

Tomspector said:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Click to expand...
Click to collapse
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/

Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Anyway, I flashed it by doing the following:
Bash:
# boot to bootloader
adb reboot bootloader
# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img
# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)
Then I rebooted to recovery and it took me directly to twrp. The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work But it'll be fun. I can't wait to put my hands on it.
Did you manage to find the rom for your phone?

PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.