Well. when twrp 3.0 comes for this device how do i upgrade to it?
Pix12 said:
Well. when twrp 3.0 comes for this device how do i upgrade to it?
Click to expand...
Click to collapse
First off (and most importantly), do not download builds from the TWRP website. This device (tate) isn't officially supported, and it's highly likely that an incompatible build will brick the kindle.
That being said, a TWRP 3.0 port isn't completely impossible. I'll see what I can do in a couple days once I have access to a working build computer.
As for upgrading TWRP, there should be a recovery .zip that you can flash directly in TWRP. If there isn't one, there will more than likely be a recovery image that you can flash via fastboot (or even via TWRP itself, in recent versions!).
monster1612 said:
First off (and most importantly), do not download builds from the TWRP website. This device (tate) isn't officially supported, and it's highly likely that an incompatible build will brick the kindle.
That being said, a TWRP 3.0 port isn't completely impossible. I'll see what I can do in a couple days once I have access to a working build computer.
As for upgrading TWRP, there should be a recovery .zip that you can flash directly in TWRP. If there isn't one, there will more than likely be a recovery image that you can flash via fastboot (or even via TWRP itself, in recent versions!).
Click to expand...
Click to collapse
Okay. I know that. It has been recently released. Well let's see what happens...
2.8.7.0 is perfect, there is no real reason to improve to version 3.0.
But, yes I want twrp 3.0 for Tate, because why not?
TWRP update
alexander_32 said:
2.8.7.0 is perfect, there is no real reason to improve to version 3.0.
But, yes I want twrp 3.0 for Tate, because why not?
Click to expand...
Click to collapse
Hi,
I did try to update to version 3.0 with flashify but...for some reason, it didn't work, and now my tablet don't boot, it is stuck on kindle fire logo and flash every 5 seconds.
Any idea what to do? (my pc don't react at all when i plug the tablet with the usb cable)
thanks
Al3xi$ said:
Hi,
I did try to update to version 3.0 with flashify but...for some reason, it didn't work, and now my tablet don't boot, it is stuck on kindle fire logo and flash every 5 seconds.
Any idea what to do? (my pc don't react at all when i plug the tablet with the usb cable)
thanks
Click to expand...
Click to collapse
You're going to need a fastboot cable (or make one). I just had the same bootloop, but for a different reason. I found a fastboot cable on ebay for about $4. Totally worth it. Once you get into fastboot, you can push the boot.img for your rom and get back to where you were.
http://www.ebay.com/itm/like/271276553980?ul_noapp=true&chn=ps&lpid=82
fastboot cable
Are you sure this would help?
What do I have to do with the cable when i get it?
Thanks for your answer
Al3xi$ said:
Are you sure this would help?
What do I have to do with the cable when i get it?
Thanks for your answer
Click to expand...
Click to collapse
Here's how @r3t3ch helped me. It may get you moving in the right direction. Just substitute the CM13 for whatever rom you are currently running.
""The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs.""
He'll definitely need a fastboot cable, but those instructions are to reflash boot. If he tried flashing an incompatible twrp to recovery, he'll want to do what I mentioned here. Followed by "fastboot -i 0x1949 reboot oem recovery" and power cycle he should end up in twrp and be able to recover anything from there.
r3t3ch said:
He'll definitely need a fastboot cable, but those instructions are to reflash boot. If he tried flashing an incompatible twrp to recovery, he'll want to do what I mentioned here. Followed by "fastboot -i 0x1949 reboot oem recovery" and power cycle he should end up in twrp and be able to recover anything from there.
Click to expand...
Click to collapse
You da man!
Related
hey sorry I'm sure this has been covered but I've been trying to root my new phone for the past 15+ hours and after installing Android revolution HD one 92.04a9 through Team Win Recovery project v2.6.3.0 it now keeps restarting in recovery and then takes me to Recovery project after a htc logo screen.
This is the first time I have attempted to root a phone and I'm a noob evidently so please go easy on me. (all I wanted was to hook up my bluetooth controller so I can play FF7 with more ease) any help would be greatly appreciated as I've just moved from London to the middle of nowhere and I'm bored out of my mind without my beloved HTC
Thanks a lot Mr. Tickles
I am so frustrated with general support of HTC. I am trying to get in touch with service for two months and no luck. My next phone won't be HTC for sure, I know.
ticklemelee said:
hey sorry I'm sure this has been covered but I've been trying to root my new phone for the past 15+ hours and after installing Android revolution HD one 92.04a9 through Team Win Recovery project v2.6.3.0 it now keeps restarting in recovery and then takes me to Recovery project after a htc logo screen.
This is the first time I have attempted to root a phone and I'm a noob evidently so please go easy on me. (all I wanted was to hook up my bluetooth controller so I can play FF7 with more ease) any help would be greatly appreciated as I've just moved from London to the middle of nowhere and I'm bored out of my mind without my beloved HTC
Thanks a lot Mr. Tickles
Click to expand...
Click to collapse
Try factory reset from twrp recovery and the flash again. Also you can try to download the zip of the ROM again to be sure it is downloaded correctly and try change the twrp version.
You are using an older version of twrp. Try updating it first to the latest version and try flashing your rom again
Get the latest one here
https://dl.twrp.me/m7/
But how do I do that if my phone wont appear in my computer any more?
Its 100% connected to my computer though because its appearing in devices printers but under the name android 1.0
You cannot enter in fastboot mode? If you can, then you flash recovery via fastboot
ticklemelee said:
But how do I do that if my phone wont appear in my computer any more?
Its 100% connected to my computer though because its appearing in devices printers but under the name android 1.0
Click to expand...
Click to collapse
@istribo is right, to flash arhd you need at least twrp 2.6.3.3 or newer (latest version is 2.8.7.0) To update your recovery, make sure you have HTC drivers installed on your computer and also uninstall htc sync if its installed (but do not uninstall the drivers). Download your new twrp .img file from the link istribo posted above, save it in the same folder where you have adb and fastboot installed on your computer. Reboot your phone in bootloader / fastboot usb mode. Open a terminal window from your adb/fastboot folder and use these commands to flash the recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Then reboot in recovery and flash arhd.
Note that you should also have a 7.xx.xxx.x firmware installed on your phone if flashing Android 5.0.2 Sense roms. You can know your firmware version with the command "fastboot getvar version-main"
My phone wont appear in my computer so how am I supposed to copy over the files...
sorry guys I'm going to need a step by step guide made for an idiot lol
ticklemelee said:
sorry guys I'm going to need a step by step guide made for an idiot lol
Click to expand...
Click to collapse
If you press power button and volume down button it gets you into recovery. Then u choose fastboot and the you do what alray said.
right so the fact my phone wont appear in my computer doesn't matter then?
Okay sorry for being silly I've just read that properly. Problem is when I got to install adb/fast boot it says something like incorrect parameter 'sheppard'
ticklemelee said:
Okay sorry for being silly I've just read that properly. Problem is when I got to install adb/fast boot it says something like incorrect parameter 'sheppard'
Click to expand...
Click to collapse
Download the sdk tools here (fastboot and adb): https://developer.android.com/sdk/index.html#Other
Download and install HTC drivers: http://www.mediafire.com/download/k7trah995whrw0d/HTC-Mobile-Driver_v4.16.0.001.exe
Connect your phone to a USB 2 port directly from your computer (no external usb hub, better to use back ports, not front ports)
Reboot your phone in bootloader mode by holding power and volume down. When in bootloader, make sure you see the red "fastboot usb" caption, if not select the "fastboot" option using the vol up/down and power key to enter. Once "fastboot" option is selected, make sure you now see the red "fastboot usb" caption.
Open a terminal window from your sdk tools folder
Type "fastboot getvar all" without the quotes en hit enter
copy paste the output here so we can see it (but do not post your IMEI/Serialno)
Then update your twrp:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Sorry I forgot to say I got my phone all working and rooted! Thank you all so much for your help! wouldn't of done it without you guys.
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Gospelalex said:
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Click to expand...
Click to collapse
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
vasolini said:
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
Click to expand...
Click to collapse
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Gospelalex said:
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Click to expand...
Click to collapse
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
vasolini said:
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
Click to expand...
Click to collapse
Can`t install them - install failed.
Gospelalex said:
Can`t install them - install failed.
Click to expand...
Click to collapse
Got another cable. Was able to get to fastboot. But couldn`t get past it. Device was shown as tate unrecognized. Pushed to install driver and made it recognized by pc. Tried kindle fire utility v099 to run recovery. The kindle gone into reboot. So now it reboots into main loge, then changes into fastboot loge and then going into continuous reboot again. Windows in the same time stop recognize it. Shows it in usb unidentified for a second because it switches on and off again.
Update:
Managed to return it into fastboot. But in cmd when i run adb.exe devices there is nothing.
I know how to fix this problem. I ran into this 10 times before Android Studio suddenly went through my head.
In order to install the Kindle Fire ADB Drivers, you need to download and install the Android SDK Manager from Google Inc. Then when you install those drivers I mentioned earlier, you won't get errors. It's so weird.
You can try using the Ultimate Unbrick Tool, but I forgot the download link for it. There should be a thread about it here on XDA.
Lots of advanced technical stuff. I suck at explaining without making it a very long explanation because then people stop reading after 10 seconds.
So ok first i was running cyanomod 13 on it with twrp installed then i tried to root by getting a super user from a site they told me to just go into twrp and flash the zip with the super user to my kindle and ill be rooted thats what i did and after that i pressed reboot system and thats where the bootloop problem started. So it just shows kindlefire logo for about 20-25 sec then it goes black and comes back up again and this just keeps on repeating and so i cant access twrp to load my backup and my pc dosent recognize it when i plug it in. I also tried to do a hard reset that didnt work either.
Any suggestions on how to get this fixed?????? help needed....
i was told that i could buy a fastboot cable and that will bring it to fastboot then i could use a program to wipe and restore it but havent order it yet so any other ideas in the meanwhile?????
Hi, I think you might have to side load stock firmware and start over, it's the only method I found out there, Boot into bootloader, download the stock firmware and use Android development tool to install your stock, and start your same rooting process all over, hope this helps it's my first post.
LexoLinux said:
Hi, I think you might have to side load stock firmware and start over, it's the only method I found out there, Boot into bootloader, download the stock firmware and use Android development tool to install your stock, and start your same rooting process all over, hope this helps it's my first post.
Click to expand...
Click to collapse
Thanks that's what i had in mind just waiting on the fastboot cable :good:
troythefader said:
Thanks that's what i had in mind just waiting on the fastboot cable :good:
Click to expand...
Click to collapse
You don't need to wipe your data or reinstall Amazon's OS. Do you have the CM13 ROM somewhere on your hard drive?
monster1612 said:
You don't need to wipe your data or reinstall Amazon's OS. Do you have the CM13 ROM somewhere on your hard drive?
Click to expand...
Click to collapse
like on my pc if yes i do.
troythefader said:
like on my pc if yes i do.
Click to expand...
Click to collapse
Apologies for the late reply - I've been busy with schoolwork lately. Anyway, all you need to do is copy the boot.img file within the ROM zip to an accessible folder on your machine (the desktop works, too), boot the kindle into fastboot with fastboot -i 0x1949 getvar product, and then run fastboot -i 0x1949 flash boot path/to/boot.img to flash the image. Then just run fastboot -i 0x1949 reboot to reboot the device afterwards, and it should work after that.
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".
It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img
Rename file
Did you rename the file? You need to rename it before flashing.
IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.
cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.
Try the last TWRP release, should work!
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.
Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...
cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...
adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon