Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before using it! YOU are choosing to make these modifications.
Notes
- The recovery cannot boot if flashed to the recovery partition instead it must be booted via fastboot using:
Code:
fastboot boot recovery.img
- The reason it cannot be flashed is that the bootloader is signature checking the flashed image against Amazon's RSA keys.
- External sdcard is not accessible from the recovery at the moment - will fix
- The touchscreen panel is not usable at the moment - instead use the volume up/down keys to navigate and power button to select
- The volume up/down keys are swapped - will fix this
- Apply update from internal memory and sideload are working.
- This is a basic recovery - it has no backup or restore function
- This does the job until TWRP is available
Download
- Amazon Fire Cyanogen Recovery
XDA:DevDB Information
Cyanogenmod Recovery, Tool/Utility for the Amazon Fire
Contributors
ggow
Version Information
Status: Beta
Created 2015-11-04
Last Updated 2015-11-06
So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.
Awesomeslayerg said:
So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.
Click to expand...
Click to collapse
- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
ggow said:
- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
Click to expand...
Click to collapse
Oh ok. So we can try sideload in or flashing a custom image now?
Awesomeslayerg said:
Oh ok. So we can try sideload in or flashing a custom image now?
Click to expand...
Click to collapse
Yes, we can flash a custom rom
ggow said:
Yes, we can flash a custom rom
Click to expand...
Click to collapse
And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.
Sent from my XT912 using Tapatalk
Vlasp said:
And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
- The bootloader has no knowledge of the Android ROM AFAIK
- We have to bear in mind that we are limited to the stock boot.img therefore
- Any rom we produce should be based off the stock boot.img
- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.
- On the HDX, when it was a locked device I was able to boot AOSP in this manner
ggow said:
- The bootloader has no knowledge of the Android ROM AFAIK
- We have to bear in mind that we are limited to the stock boot.img therefore
- Any rom we produce should be based off the stock boot.img
- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.
- On the HDX, when it was a locked device I was able to boot AOSP in this manner
Click to expand...
Click to collapse
We should be able to use custom boot.img when we get safestrap, right?
Sent from my KFFOWI using Tapatalk
ggow said:
- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
Click to expand...
Click to collapse
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.
Do you mind sharing which gapps package did you use and what modification you did?
this works on t he 50$ fire tab?
patt2k said:
this works on t he 50$ fire tab?
Click to expand...
Click to collapse
This is FOR it dummy
stkpxl said:
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
Click to expand...
Click to collapse
inscythe said:
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.
Do you mind sharing which gapps package did you use and what modification you did?
Click to expand...
Click to collapse
- Yes, I'll post it shortly
- I have only flashed it so far with no testing
- My Fire hasn't been online yet because I haven't blocked OTA updates yet
- Will test and provide a link for download
EDIT: Good news the Gapps package works with full play store functionality
I'll upload it and post a link in the General Section
Vlasp said:
We should be able to use custom boot.img when we get safestrap, right?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
- I started investigating this and Safestrap may not be possible
- Safestrap is usually for locked devices granted, however...
- Even if it were possible our kernel doesn't have kexec capabilities
- As with other amazon devices we really need a way to unlock the bootloader.
Modified Open Gapps Package
inscythe said:
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.
Do you mind sharing which gapps package did you use and what modification you did?
Click to expand...
Click to collapse
stkpxl said:
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
Click to expand...
Click to collapse
- I have posted the Modified Open Gapps package here.
- Tested and seems to be working fine.
ggow said:
- I have posted the Modified Open Gapps package here.
- Tested and seems to be working fine.
Click to expand...
Click to collapse
Very nice will have to play around with this later have this tablet for my grandma so at least with root and custom launcher I can make it easier to use at least
ggow is the ****ing bomb!
Between all your work on the FirePhone and this tablet, tell me what I owe you!
Moogagot said:
ggow is the ****ing bomb!
Between all your work on the FirePhone and this tablet, tell me what I owe you!
Click to expand...
Click to collapse
Your first born maybe?
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
sandman512 said:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
Click to expand...
Click to collapse
No problem. You can find instructions here.
sandman512 said:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
Click to expand...
Click to collapse
you need adb and fastboot files
several options there are some basic information in my Amazon Fire Index
Fire Index: Which Amazon (Kindle) Fire Do I have?
once you have adb setup
boot Fire into fastboot mode: power off, Hold volume down, power on
if it boots to recovery select bootloader
once in fastboot mode check device manager Fire should be listed as Android adb interface
If so you should test fastboot commands with
Code:
fastboot -i 0x1949 getvar product
should get this back
Code:
ford
if so
place recovery.img in the same location as listed in command prompt
then boot recovery.img with
Code:
fastboot boot 2015-11-04-cm-12-recovery.img
Sent from my KFFOWI using Tapatalk
Related
As there is now an official version of CWM Recovery I updated this thread now. Thanks to everyone who used my version and helped me. I will keep on what I'm doing and maybe there will be other interesting things I will release.
The official CWM Recovery by Koush can be downloaded here:
Images to flash via fastboot
touch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-mako.img
nontouch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-mako.img
Flashable zips
touch-version: https://www.mediafire.com/?nx826v1jo0bdqdj
nontouch-version: https://www.mediafire.com/?69kmvtcvgooc0gv
For the fastboot images:
You can try this out and boot it via
Code:
fastboot boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(only Android 4.2.X)
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(Android 4.3 and above)
If you want to flash it you can use
Code:
fastboot flash recovery recovery-clockwork(-touch)-6.0.4.7-mako.img
If you have the touch-version use this commands without '(' and ')' but with its content.
If you have the nontouch-version use this commands without '(' and ')' and its content-
Outdated as all new recoveries already provide this function.
I also want to present you my revert recovery disabler.
As you know if you flash CWM on Nexus 4 it reverts back to the stock recovery. This patch prevents this. This is not needed at the moment for CWM as CWM offers the possibly to disable the revert by itself.
You can download my revert recovery disabler here: http://www.mediafire.com/?78fkhdh5icz3zdg
This disabler is compatible with mskip's toolkit (uses the same methode).
To use it boot in CWM recovery and flash this as a zip.
If you want to restore the default option and make your Nexus 4 reverting back to the stock recovery you can flash the enabler: http://www.mediafire.com/?19enww985e2gpnc
Thanks to:
Stryder5 providing some information
Kstarz for some testing and providing information
mskip for his toolkit and giving me the idea to do this
pankaj88 for his sample update zip
Old thread said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (UPDATED 11/16/2012)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to:
Stryder5 for testing and providing some information
Kstarz for testing and providing some information
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
To clarify, I can confirm the boot method will allow you to boot the recovery and flash a zip file. I did not attempt to flash this as my recovery yet.
---------- Post added at 12:53 AM ---------- Previous post was at 12:21 AM ----------
I tried to flash the recovery instead of booting from it, but that doesn't work. I ran the command:
Code:
fastboot flash recovery cwm-recovery-mako.img
When I try to boot into recovery after that, it'll show the Google logo twice, then proceed with the regular boot.
I think this is because Secure Boot is still enabled.
Same thing here..recovery will not stick if flashed
Sent from my Nexus 4
good news! https://plus.google.com/u/0/103583939320326217147/posts/CzstapsDpYf
fkrone said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (more mirrors will be added soon)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to my tester Stryder5.
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
What RAMDISK load address are you using? 0x81200000?
Thanks to the tip by Stryder5, I have updated my rooting guide with instructions for rooting via CWM, linking to this thread for the recovery and providing the due credit. =)
g33k3r said:
What RAMDISK load address are you using? 0x81200000?
Click to expand...
Click to collapse
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
fkrone said:
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
Click to expand...
Click to collapse
Looking forward to it!
Sent from my Nexus 4 using xda app-developers app
does anyone actually build cwm these days?
Sweet!! So our Nexus 4 is codenamed "MAKO?"
DaX05 said:
Sweet!! So our Nexus 4 is codenamed "MAKO?"
Click to expand...
Click to collapse
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
fkrone said:
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
Click to expand...
Click to collapse
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
mskip said:
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
Click to expand...
Click to collapse
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
fkrone said:
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
Click to expand...
Click to collapse
Thanks and of course
What version is it? V6.0.1.5?
Mark.
mskip said:
Thanks and of course
What version is it? V6.0.1.5?
Mark.
Click to expand...
Click to collapse
As I built it this afternoon (GMT+1) it is V6.0.1.5 with the latest bugfix which was released today.
Man I can't wait to see some custom ROM's outta here. The phone is sweet and snappy but I've had a few problems that I'm not sure if they're hardware or software related. Quadrant scores are around 4400-4900, the phone rings hot and I'm getting the worst speed test results. Like I get 11-18 MBS on my gs2 and I'm getting like 2-3mbs now. I got two weeks before I can return it so I hope it just needs to stettle. Anyhoo. Good luck guys!
Sent from my Nexus 4 using XDA Premium HD app
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Arasthel said:
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Click to expand...
Click to collapse
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
fkrone said:
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
Click to expand...
Click to collapse
Sorry, I misunderstood you. I thought this bugfix would allow us to flash the recovery in our devices, then I realized that the bugfix was what let us boot it, as you said a few messages back. Anyway, there you have the official build link.
Can somebody please explain, in simple terms, why we can't flash this permanently yet? What do we need to enable us to flash it permanently?
OUYA Safe Recovery v1.0.0
Because the OUYA lacks a hardware recovery button combination.Purpose
To create a safe environment where the end user can flash their OUYA with confidence.
How This is Achieved
By switching the roles of the boot image and the recovery image, the user is presented with a customized recovery before entering the actual ROM. This gives the user a failsafe before they start to flash their OUYA. This way if something were to go wrong in the flashing process, the recovery image is still in tact and the system can be restored to a working state.
Features
Custom font size that looks better on HDTV's.
Custom color scheme that matches that of the OUYA theming.
Custom reboot options.
Installation Methods
Method 1 - Computer
Simply download the archieve containing a script that will flash your OUYA. Follow the on-screen directions based on the OS your computer is running.
Method 2 - Recovery
This method is a little more dangerous, but if you already have Clockworkmod Recovery installed on your OUYA you can flash the specified zip to install OUYA Safe Recovery.
Downloads
Computer Method: Ouya Safe Recovery Installer v1.0.0.zip - 16.08 MB
Recovery Method: update_v1.0.0.zip - 6.93 MB
Source and GPL
The source for this project is quite simple, but will continue to evolve over time. If you are interested in taking a look at the required source code or compiling your own Safe Recovery binary, you can find the requested material here.
Credits
Credit to koush for maintaining ClockworkMod Recovery which this recovery is built and compiled from, and to mybook4 for the original CWM port to the OUYA.
Donations and Thanks
If you like the work that I am doing and would like to send a donation my way, please feel free to do so, even though it is not required. Every dollar is appreciated, and will go towards future development costs.
Changelog
Will we be able to install Cyanogenmod 10 with this recovery? Or will we need to replace the boot.Img in the zip so it will gflash correctly without having to use fastboot?
Edit: Where are my manners, AWESOME! Thanks for the recovery! I remember you talking about it in the Cyanogenmod Thread and I didn't expect it to be made so fast!
qwasz123 said:
Will we be able to install Cyanogenmod 10 with this recovery? Or will we need to replace the boot.Img in the zip so it will gflash correctly without having to use fastboot?
Edit: Where are my manners, AWESOME! Thanks for the recovery! I remember you talking about it in the Cyanogenmod Thread and I didn't expect it to be made so fast!
Click to expand...
Click to collapse
To install Cyanogenmod 10 you will need to manually flash the boot.img to the recovery partition.
Code:
fastboot flash recovery 20130702-boot.img
Thanks for the nice comment!
ProfessorAnomaly said:
To install Cyanogenmod 10 you will need to manually flash the boot.img to the recovery partition.
Code:
fastboot flash recovery 20130702-boot.img
Thanks for the nice comment!
Click to expand...
Click to collapse
You're welcome!
So I'm guessing all of the roms need to be updated to install to the recovery partition instead of the boot partition?
Hi, you have done A Great Job, i flashed (via CWM) the recovery and Its working, i also flashed boot image (via Fastboot) and its booting.. Everything is working, we are safe Now!!! Finally!!!! Thanks to you!!!
This should be in Xda Portal!!!!
Only one thing remains what should we choose when we are asked to disable recovery flash... ?
Tried the installer from windows and it reset the ouya and booted back into the ouya launcher? Am I doing something wrong? So far im rooted and adb is working as its sending the files to my internal SD Card. Driver is installed correctly on the pc. Im running Windows 7 (x86).
Sent from my A210 using Tapatalk 4
Does this have any passthrough mode? I mean, is there any functionality to make it automatically boot into the rom by default, and only show the recovery screen if you are holding the power button or some key on the usb keyboard?
qwasz123 said:
You're welcome!
So I'm guessing all of the roms need to be updated to install to the recovery partition instead of the boot partition?
Click to expand...
Click to collapse
The updated fstab should allow for the existing ROMs to flash the boot image to the recovery partition granted developers are writing the image the correct way.
suruceanu.nick said:
Hi, you have done A Great Job, i flashed (via CWM) the recovery and Its working, i also flashed boot image (via Fastboot) and its booting.. Everything is working, we are safe Now!!! Finally!!!! Thanks to you!!!
This should be in Xda Portal!!!!
Only one thing remains what should we choose when we are asked to disable recovery flash... ?
Click to expand...
Click to collapse
I've been choosing no, but I doubt it makes much of a difference.
martinbrettphilo said:
Tried the installer from windows and it reset the ouya and booted back into the ouya launcher? Am I doing something wrong? So far im rooted and adb is working as its sending the files to my internal SD Card. Driver is installed correctly on the pc. Im running Windows 7 (x86).
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
It should work. I don't see why it wouldn't if adb is working correctly.
Maybe a bad download is to blame?
gianptune said:
Does this have any passthrough mode? I mean, is there any functionality to make it automatically boot into the rom by default, and only show the recovery screen if you are holding the power button or some key on the usb keyboard?
Click to expand...
Click to collapse
This is what I have planned for the next update. Shouldn't be too long before I get it worked out.
ProfessorAnomaly said:
It should work. I don't see why it wouldn't. Maybe try rebooting?
Click to expand...
Click to collapse
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
ProfessorAnomaly said:
This is what I have planned for the next update. Shouldn't be too long before I get it worked out.
Click to expand...
Click to collapse
I believe that for koush bootstrap recovery what it does is puts a certain file /system/etc on successful shut down and when it restarts the recovery checks first if the file is there and it moves into normal boot and after that it destroys the file to be rebuilt on successful shutdown.
But if the file is not found it goes into recovery mode
martinbrettphilo said:
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
Could you please screenshot the errors you are seeing?
I installed this but I'm confused on how to get into recovery. When trying to boot into recovery, it boots into a screen with a Ouya logo and an exclamation mark right under it (Ouya !")
martinbrettphilo said:
I did and nothing also the batch file is reporting unknown id for some of the commands. :S
Sent from my A210 using Tapatalk 4
Click to expand...
Click to collapse
Sam3gX said:
I installed this but I'm confused on how to get into recovery. When trying to boot into recovery, it boots into a screen with a Ouya logo and an exclamation mark right under it (Ouya !")
Click to expand...
Click to collapse
The installation was not successful. Please try again.
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.
Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.
I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!
Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk
Thanks ggow. Could we expect CM roms soon from your new release?
Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.
dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0
ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-rav-sofia.img
drive.google.com
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G8
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-31
Hello, I'm trying to port TWRP to the motorola edge plus and right now I'm running into an issue where my touchscreen and adb do not work. Could you publish the device tree you used here so I can take a look at it and potentially get it working on my phone?
Thanks.
pixlone said:
Hello, I'm trying to port TWRP to the motorola edge plus and right now I'm running into an issue where my touchscreen and adb do not work. Could you publish the device tree you used here so I can take a look at it and potentially get it working on my phone?
Thanks.
Click to expand...
Click to collapse
You'd better check the moto edge tree : https://github.com/boulzordev/android_device_motorola_racer/tree/twrp
Unified one for trinket devices is here : https://github.com/moto-sm6xxx/android_device_motorola_sofiar/tree/twrp
Where to look at :
recovery/root/vendor/firmware - firmwares for touchscreen and vibrator
recovery/root/sbin/modules - drivers for touchscreen/battery/vibrator
recovery/root/sbin/load_ts_firmware.sh - in charge to load modules and tell touchscreen driver which firmware to load
Just like to confirm that this is working great either booted or installed. Thanks for the hard work vache :good::good:
There is no system partition to install to in TWRP. Super is listed twice. It may be nice to know what partitions listed actually mean.
No checkbox activation:
System
Vendor
product
USB storage
swear000 said:
There is no system partition to install to in TWRP. Super is listed twice. It may be nice to know what partitions listed actually mean.
Click to expand...
Click to collapse
It would be nice to see users searching by themself.
Google for "dynamic partitions" and "fastbootd". That could also help you to understand why omni is shipped as images for now instead of flashable zip.
vache said:
You'd better check the moto edge tree : https://github.com/boulzordev/android_device_motorola_racer/tree/twrp
Unified one for trinket devices is here : https://github.com/moto-sm6xxx/android_device_motorola_sofiar/tree/twrp
Where to look at :
recovery/root/vendor/firmware - firmwares for touchscreen and vibrator
recovery/root/sbin/modules - drivers for touchscreen/battery/vibrator
recovery/root/sbin/load_ts_firmware.sh - in charge to load modules and tell touchscreen driver which firmware to load
Click to expand...
Click to collapse
Oh thanks, I didn't even know you had a moto edge tree. I'll take a look at it and see what I can do with it.
OMNI
vache said:
It would be nice to see users searching by themself.
Google for "dynamic partitions" and "fastbootd". That could also help you to understand why omni is shipped as images for now instead of flashable zip.
Click to expand...
Click to collapse
Most people agree OMNI is a great ROM. System, Vendor, and product are critical partitions for ROM flashing so I am surprised TWRP does not toggle them correctly.
Update : https://drive.google.com/file/d/17QLv1Pzq9x1FCzAYKULfUTwn3R0akMXI/view?usp=sharing
Changelog :
-Fixed Novatech touchscreen
vache said:
Update : https://drive.google.com/file/d/17QLv1Pzq9x1FCzAYKULfUTwn3R0akMXI/view?usp=sharing
Changelog :
-Fixed Novatech touchscreen
Click to expand...
Click to collapse
I can confirm that it is fixed. I used Magisk's adb/fastboot module to unlock my Moto G Fast with my rooted G7 Play with a USB C to C cable, boot twrp, and make a back up. This is epic!
It took some digging to figure this out, so I'm going to outline the steps for getting this installed without a boot loop.
1. Unlock your device. (I'm not holding your hand here.)
2. Reboot into fastboot.
3. Temporarily boot twrp.
4. Install magisk by flashing the latest zip from twrp. Then flash the copy partitions zip so you don't hard brick.
5. Reboot to system, and you're now rooted.
6. Reboot into recovery.
7. From stock recovery select "enter fastboot" this takes you to "fastboot d" mode.
8. Flash twrp while you're in fastbootd mode.
9. Enjoy! Everything is working perfectly. Rebooting to recovery takes you to TWRP. Rebooting to system gives you root. We also have full decryption support.
Great work
Spaceminer said:
I can confirm that it is fixed. I used Magisk's adb/fastboot module to unlock my Moto G Fast with my rooted G7 Play with a USB C to C cable, boot twrp, and make a back up. This is epic![/QUOTE @Spaceminer View attachment g8fast-nexus7.zip
([emoji88]Omni Rom[emoji88])
Click to expand...
Click to collapse
asineth said:
Great work
Click to expand...
Click to collapse
Great work fixing the Bluetooth audio [emoji817]
([emoji88]Omni Rom[emoji88])
is it to much to ask for a more through explanation on how to flash twrp and magisk on this phone?.....
ninjakira said:
is it to much to ask for a more through explanation on how to flash twrp and magisk on this phone?.....
Click to expand...
Click to collapse
If you have telegram I walk you threw it PoochyX
([emoji88]Omni Rom[emoji88])
PoochyX said:
If you have telegram I walk you threw it PoochyX
([emoji88]Omni Rom[emoji88])
Click to expand...
Click to collapse
just send the invite to whatever telegram group then i suppose.....
Spaceminer said:
It took some digging to figure this out, so I'm going to outline the steps for getting this installed without a boot loop.
1. Unlock your device. (I'm not holding your hand here.)
2. Reboot into fastboot.
3. Temporarily boot twrp.
4. Install magisk by flashing the latest zip from twrp. Then flash the copy partitions zip so you don't hard brick.
5. Reboot to system, and you're now rooted.
6. Reboot into recovery.
7. From stock recovery select "enter fastboot" this takes you to "fastboot d" mode.
8. Flash twrp while you're in fastbootd mode.
9. Enjoy! Everything is working perfectly. Rebooting to recovery takes you to TWRP. Rebooting to system gives you root. We also have full decryption support.
Click to expand...
Click to collapse
I'm rather new to the scene, everything you're saying here makes sense except the copypartions.zip. Is this something that is the same for all phones or is there a special file i should have for the g fast?
and still bootloop lmao, im doing the exact steps provided exactly as i see them on this thread, christ ill send 20 bucks through paypal to whoever makes a actual detailed guide with explanations on what to do like for example what is the copy partitions zip? whats it for? do i make a patched boot image first if im coming from full stock? do i do any of this to the other partition? treat it like your making it for noobs like christ is it that hard to help out now lmao
ninjakira said:
and still bootloop lmao, im doing the exact steps provided exactly as i see them on this thread, christ ill send 20 bucks through paypal to whoever makes a actual detailed guide with explanations on what to do like for example what is the copy partitions zip? whats it for? do i make a patched boot image first if im coming from full stock? do i do any of this to the other partition? treat it like your making it for noobs like christ is it that hard to help out now lmao
Click to expand...
Click to collapse
If you have done an OTA update on the phone, AFAIK you don't need the copy-partitions.zip. The zip copies needed partitions from the used slot to the unused slot. So if it does change from one to another, you aren't left with a completely blank slot with nothing on it. (As i said, if you have done a OTA update, both slots will be populated, so it isn't necessary to flash the zip..)
SOMEONE SMARTER THAN ME CORRECT ME IF IM WRONG ON THE ABOVE STATEMENT PLEASE
So.. assuming you are on clean stock and you have done an OTA update... In fastboot:
(make sure you have a magisk.zip on your phone or sd card)
Code:
fastboot flash recovery <twrpfilename>.img
Then enter recovery mode from the bootloader menu you are still in.
Wait for twrp to load, install magisk, reboot.
Profit.
Now you are rooted, with twrp permanently installed.
p.s: Keep the 20 bucks and send it to vache :silly: