Related
DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14
Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.
bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.
keep up the great work now we just gotta get custom rom installed
Can Flashify be used to boot into the recovery?
niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk
Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.
Any Tom development started yet?
Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
added video to post #2
Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.
sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device
sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.
So I have, after some work and experimentation, got encryption to work with CM 13. However I have run into a problem, TWRP will not accept my password and decrypt my phone. My phone will boot fine, I have CM 13 working correctly, make calls, surf the web and so on. It also accepts my password to unlock the phone no issues. But TWRP will not, so I cannot flash Xposed or any other ROMs without going through the process of wiping, encrypting and reflashing. That is the other oddity, TWRP DID accept the password at first and let me flash the CM 13 mod originally. After that I got a message saying the phones info was corrupted, the password was correct but my phone could not unlock. I restarted it and the phone started like normal but now we have this issue. Any advice would be very much appreciated.
Sent from my DROID Turbo using XDA-Developers mobile app
You must be running TWRP 3.0.1.0
Flash TWRP 3.0.2.0 and your problem should he fixed
Actually I am on TWRP 3.0.2.0
Sent from my DROID Turbo using XDA-Developers mobile app
Any other suggestions for this situation?
Sent from my DROID Turbo using XDA-Developers mobile app
BEDickey said:
Any other suggestions for this situation?
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
Re-flash TWRP 3.0.2.0? That update was specifically a fix for encryption issues. If reflashing doesn't work, then don't know.
I just tried to get encryption going on my Turbo with RR, and I got the same issue. I don't think it's a TWRP problem. I'll work on it some tonight and see if I can get it to work.
Yeah, it's some issue with RR. The latest TWRP decrypts the stock rom just fine. Weird.
I was not on RR, I was on CM 13. RR is a mod off of CM correct?
Sent from my DROID Turbo using XDA-Developers mobile app
BEDickey said:
I was not on RR, I was on CM 13. RR is a mod off of CM correct?
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
Correct. So to be more precise, it's an issue with CM.
I read somewhere that with CM12.1 (and maybe CM13), it's necessary to set selinux to permissive before encrypting, but once you do that, you can just encrypt through the settings menu while running CM (no stock rom trickery required). My battery is too low to test this, but I'll definitely test it when I get home tonight.
Edit: Nope. Didn't work.
I'm determined to get this to work. I actually figured out how to get RR to encrypt on its own without having to go back to stock first, but TWRP still won't decrypt it. I've tried all TWRP versions available for quark. I'm going to try using CM recovery. If that doesn't work, I dunno what will. For what it's worth, google says that we're not the only ones having trouble decrypting CM13.
For those who are curious, you can get RR (and presumably CM13) to encrypt by first flashing the stock recovery menu and doing a factory reset. The reason this is necessary is that encryption requires the data partition to reserve about 16kb of data to be used during encryption. However, when TWRP formats the data partition, it includes all of the available space in the partition and leave nothing unallocated. The stock recovery menu knows better.
EDIT: CM recovery is totally useless. It doesn't even touch /data unless you're factory resetting. Welp, I'm out of ideas for now.
Well this sucks! Thanks for your work The St33v. It looks like this has to be edited at the top so it leaves that extra space needed. The TWRP code needs to be fixed imho.
BEDickey said:
Well this sucks! Thanks for your work The St33v. It looks like this has to be edited at the top so it leaves that extra space needed. The TWRP code needs to be fixed imho.
Click to expand...
Click to collapse
Yeah, I'm not really sure what the issue is at this point. According to my Googling, some devices running CM13 can decrypt with TWRP just fine, but many can't. That tells me that it's a device-specific issue, which means the TWRP maintainer for our device would need to fix it. Who knows though. I could be wrong.
I don't really feel like bothering him about it, but in case anyone else does, the TWRP guy for our device is none other than the legendary baybutcher27.
I tried to get a copy of the TWRP log, but it tries to save the log to /data/media. I don't imagine that actually happened since /data is still encrypted.
EDIT: Nevermind. The log file doesn't have any information that is different from what TWRP displays on the screen, and TWRP doesn't display anything that is helpful.
Different device (Zenfone 2/z00t), but I've been bouncing around forums looking for the same solution. Currently using Flashify to update CyanogenMod Recovery, then using the ADB sideload menu to flash the nightlies. Switching to TWRP every few nightlies to see if it's fixed. It's not an elegant solution, but encryption is pretty much a must.
NewDayRising said:
Different device (Zenfone 2/z00t), but I've been bouncing around forums looking for the same solution. Currently using Flashify to update CyanogenMod Recovery, then using the ADB sideload menu to flash the nightlies. Switching to TWRP every few nightlies to see if it's fixed. It's not an elegant solution, but encryption is pretty much a must.
Click to expand...
Click to collapse
I talked to the maintainer of our TWRP build, and he said that it would be something that he would have to figure out how to add, but he is working on it. Apparently, methods of encryption/decryption are specific to each device.
Right. And since I'm still running nightlies with no snapshot as of yet for my device, I'll deal with the workaround till it's sorted, or file a bug report when a stable release/snapshot is available. Thankfully ADB sideload is an option till then. Thanks for the info about the issue being specific to each device.
Hi everyone,
I literally just got the Chinese version of the oneplus 3T (A3010) and I want to move from Hydrogen OS 2.5.1 to Oxygen OS 3.5 official with OTA. Does anyone have the file or instructions how to do this? I found instructions for the oneplus 3 but not sure with this model. I'm sure any help would help out a lot of people who are gonna ask this question.
Also will this unlock the bootloader? Just curious about it affecting android pay.
Thank you!:laugh:
logansrun24 said:
Hi everyone,
I literally just got the Chinese version of the oneplus 3T (A3010) and I want to move from Hydrogen OS 2.5.1 to Oxygen OS 3.5 official with OTA. Does anyone have the file or instructions how to do this? I found instructions for the oneplus 3 but not sure with this model. I'm sure any help would help out a lot of people who are gonna ask this question.
Also will this unlock the bootloader? Just curious about it affecting android pay.
Thank you!:laugh:
Click to expand...
Click to collapse
Wanna do me a favor and grab a nandroid backup of your rom before you kill it? I actually want h2os
Aside from that, you should theoretically be able to: ("Official" guide https://forums.oneplus.net/threads/...oid-efs-backup-and-more.475142/#post-15431571)
Unlock the bootloader
Flash TWRP
Flash dm-verity
Flash OOS 3.5.3 from the ROM page, I have a mirror too (http://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015) mirror on pg 2.
and you'll be set, you can flash the original recovery if it's available on the OnePlus page as well and relock to go back to full stock just English version
PS: Since there is no stock recovery image available yet, maybe will have to run TWRP temporarily, rip the recovery off and then proceed? I dunno
Thanks for your quick reply! I was hoping more along the lines of the adb Sideload method and keep the bootloader locked for now though. If I go the root method sure I can share the nandroid backup.
PS the rom looks really similar to the oxygen rom, so far it looks like only the launcher is different. I guess this is part of the plan to merge the two.
Well you can try flashing the image straight. It's a stock image anyways so it could work.
logansrun24 said:
Thanks for your quick reply! I was hoping more along the lines of the adb Sideload method and keep the bootloader locked for now though. If I go the root method sure I can share the nandroid backup.
PS the rom looks really similar to the oxygen rom, so far it looks like only the launcher is different. I guess this is part of the plan to merge the two.
Click to expand...
Click to collapse
Basically what I meant was to do the opposite of what is suggested here http://forum.xda-developers.com/oneplus-3t/how-to/rom-h2os-2-5-oneplus-3t-released-t3511443 but with the 3.5.3 ROM
Help needed with android pay and OOS clean install
I'm in a similar situation with a chinese bought OnePlus 3G from Lazada.sg that came with Hydrogen OS. I've managed to install TWRP but because I'm completely new, got stuck and instead managed to install OOS 3.5 (now 4.## from the official website) using adb sideload.
I do have 2 questions:
1) My internet connection drops occasionally even though my WiFi is still connected, is that an issue because I might not have installed it correctly? Would a clean flash solve it?
2) I understand android pay is disabled when you unlock bootloader but even after that, will it be possible to wipe the phone clean and do a fresh install of the lastest OOS and the phone will pretty much be like the international version, with android pay re-enabled?
I believe you can use Sultanxda's patch as another way around, but it sounds complicated as hell for a new person, so I'll continue digging around while waiting for a reply.
Thank you, and any advice will be greatly appreciated.
Hi all,
I just got my Mi MIX today (6gb version). I have been trying to get TWRP and SuperSU working on it, then flash the EU rom. During this process, my TWRP has become unresponsive. At the same time, my Wifi cannot be enabled. (I am installing EU rom because my Google Play Store download speed was throttled, and I could not find the option in Mi App Store to disable)
I am hoping that someone has a stock recovery I can flash, or knows how I can revert to stock. I have ADB and Fastboot installed.
I have tried re-flashing TWRP, and it does not work. I have also tried Fastboot -w to see if it helps. It instead shows me the screen asking to write to system again, instead of the main menu like before.
Any help is very appreciated! :crying:
go read the entire detailing how to install xposed, twrp, etc others have had similar things happen and there are instructions on what to type in fastboot to fix. just read the thread.
http://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592/page1
The OP in this thread has a comprehensive run through of how to install TWRP, EU ROM and root with Su. I suggest using the EU TWRP from the beginning as we found that it works best with the CN Stable ROM (8.0.11.0) .
Don't forget to root
Cheers
J
Sent from my MIX using XDA Labs
Hello,
I encountered the same problem (TWRP not responsible)
Solved with flashing this version of TWRP that work with latest EU ROM .
https://mega.nz/#!A91zFZqQ!AB1AB6HMaAtVS-2GQlUNgVXDtn-ZJej22rjEwJgVQlU
Try and tell me if it's OK ?
Thanks all! This is solved now Happy to be using my new Mi MIX!
4DM said:
Thanks all! This is solved now Happy to be using my new Mi MIX!
Click to expand...
Click to collapse
Glad to hear you have it working
Enjoy your Mix
Best
J
Sent from my MIX using XDA Labs
Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.