Database Users

Kindle Fire Boots to Team Win Recovery Program Screen

Help! For Christmas my parents bought me a Kindle Fire but before I got it, they gave it to my sisters boyfriend who is a techy kind of guy and he put twrp and hacked the kindle. Well the other day I was trying to download something and it rebooted and went straight to the TWRP gray screen (the one with the options to install, backup, restore, wipe, etc.) I do not know what to do! I have searched through threads on the forum about using the kindle fire utility, it doesnt work. My computer recognizes the kindle as an android phone and when i run the utility, it says my boot status is unknown so i dont think that the program is detecting my kindle? Please help!

Are you having trouble getting out of TWRP, or what?
Just click on Reboot --> System and that should get you back into the normal system.
You may also want to check into this if you have further problems:
http://forum.xda-developers.com/showthread.php?t=1356257

I have tried the link that you have given me before and it didnt work as well. I've also tried the reboot -> system and the other option given. Neither of them work. My problem is, whenever i start up my Kindle, it goes straight to that screen after the yellow triangle screen. Any help?

Dakdak234 said:
I have tried the link that you have given me before and it didnt work as well. I've also tried the reboot -> system and the other option given. Neither of them work. My problem is, whenever i start up my Kindle, it goes straight to that screen after the yellow triangle screen. Any help?
Click to expand...
Click to collapse
I'm assuming you accidentally hit "reboot into recovery. If you are not a "techy" guy, you need to get in that mode and follow the link dude provided. You will need to download a couple programs to your pc, and acquire a microusb cable. Follow directions to the TEE' and you'll be ready to go in no time.
Sent from my Amazon Kindle Fire using xda premium

kfu is just good for what you need - regardless what status it reports try option1 and bootmode normal
if it does not work check your drivers - in device manager it should show up under android phones - if not update the driver - try to run install_drivers.bat in the kfu directory first - if it does'nt work try to update manually - it is in the drivers\kindle directory of kfu
regarding drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then retry kfu option 1 bootmode normal

Okay so i remembered using winRAR you need to extract the folder and I did and the kfu is working properly now except for one thing, it says the ABD status is offline... i dont know what to do about this

the adb status is offline - this is normal when the kf is in fastboot mode
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO

Sorry but i'm confused on what youre telling me to do :/

- run kfu
- select option 1 (bootmode menu)
- select option 1 (bootmode normal)
that's it

Thank you a million! I just realized that i was typing in "4000" instead of "1" and it wasnt recognizing the command!

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Okay 1 last thing and im really sorry for putting you through all this... when its booting up, it gets past the black screen with the yellow triangle but after that the screen is just black, its not shutoff because i can see that the backlight is on... Is this a problem thats fixable?> :/

hold the power button for ~20sec till it turns off - power on again

Did like you told me to... Got past the yellow triangle fire fire fire screen and just sits there with the backlight on...

what did you try to install ? it seems the kf can't boot into a system ...
and as you asked earlier - everything (besides hardware failures) is fixable
but a hardware failure seems not to be your problem

I cant exactly remember but i remember it downloaded and then the kindle randomly shut off and when i turned it back on it just went straight to the recovery... ive tried resetting the kindle several times right now and even going back into the recovery mode and nothing is working :/ i believe the problem has gotten worse

you can install a new rom now - which one did you have before ?
i can give you the download location and how it is done ...

Like i mentioned before, i didnt set it up. I cant tell you what rom was downloaded but i do remember some programs that ive seen before in guides?? There were like the golauncher and other "go" programs... if that doesnt stand out to any specific one i believe there were some cryogen (or however its spelled) stuff on it... i know it was set up just like his verizon phone

then i would think it it was cm7 - download from here: http://www.mediafire.com/download.php?hmdc0lmgvnlbg97
this is the update version - i would try this one first so you should not loose anything
- boot into twrp
- now you should see the kf on your computer
- copy the downloaded file on the kf
- tap install
- select the file and install
try this first

Okay thank you. Is it okay if i PM you if something goes wrong? You seem to know alot about this

TWRP "Your phone does not appear to be rooted"

I was recently given a phone that a friend had fooled around with. It has TWRP installed on it but when you try to reboot back to the system, or even just go to the power off option in the reboot menu it says "Your phone does not appear to be rooted" and asks if I want to install SuperSU. Whether I pick do not install or swipe to install it just reboots right back to the main TWRP menu. I have tried a couple of root programs which have told me that they successfully rooted the phone, yet after it still gives me the same "Your phone does not appear to be rooted" message. Also when i plug the phone into the computer it makes a connection noise but does not show up on windows explorer yet the root programs were able to recognize it. Any suggestions?

Upgrade your TWRP to last version 2.8.7.3. http://blastagator.ddns.net/twrp.html

Recover data from broken screen and digitizer, adb not detecting phone in recovery

I realize there are many other threads on this, bear with me please, I was not able to find a solution that works.
-display is broken, shows light but nothing else
-digitizer is 99%? broken, back and menu buttons work, there is some heptic feedback in upper part of the screen
-phone does not have a lock pattern or password, just swipe to unlock
-voice commands work
-phone was rooted a long time ago, I don't recall the mehod, I think the current OS is likely 4.4 but i'm not sure (is there a way to check)?
-I had a custom recovery on it which i think was CWM, again, not sure how to check this now
-I can install apps via web appstore
-At some point I installed a clockroot app (never worked) it's probably still on the phone
-I don't have OTG, ordered one
-I don't want to order a new digitizer
Here are somethings that kind of work and some that don't
-dr.fone shows a USB debug promt with instructions on how to accept the RSA key. I'm guessing USB debugging mode is on but it's not the same computer
-if I have the device in download mode, it is "sometimes" recognized by dr.fone, just says its in download mode and asks to reboot
-if I have the device in recovery mode (i think), it's not recognized at all, does not even show up in device manager
-when phone is just on, it's recognized by the computer, I can browse and backup files (i need to backup google auth app)
-with phone on, its recognized by windows and adb, adb says the device is not authorized.
-however adb does not recognize it if I boot into recovery
I think my best best to just to push the rsa key to the phone in recovery but I'm stuck because the phone is not recognized. I will try re-installing drivers next but I doubt this will help.
Lastly, I wasn't sure if I really do have CWM installed or its stock recovery. So I tried to flash CWM using Odin, with phone in download mode, recognized by Odin, the flash fails with an auth error, i'm reading that might mean the phone is not rooted which is 100% not the case here, maybe the rootclock app is doing something to it.
Any advice?

I'm starting to recall the rooting process a bit and I'm fairly sure I used safestrap method, as I was on 4.4.2-4 NJ something kitcat at the time. So I may not have CWM installed after all.

little bit of progress to report. I'm fairly certain i have safestrap recovery on this phone. So booting into recovery must have been bringing me to the safestrap screen that needs a screen tap to recovery or continue. If I hit power it reboots, if its only 2 options recovery or continue to normal boot, volume down move me to the other option, + power....now adb detects the phone! in sideload mode, lets see if I can do something with this, fingers crossed.

no luck, sideloading seems useless. How can i get myself into recovery!?
I think if I can push the adb rsa key I would be set to use one of the screen mirroring apps. How can I sideload it in?

My experience with FRP lock and how I solved it...

So my nephew brings me his galaxy s6 t-mobile phone... He forgot his lock pin so he factory reset it. Now he can no longer get into the phone because he doesnt know the correct email or password. I did some digging through the net watched a few videos... and found none of the methods they used to bypass the lock would work on his phone. Then I read about the Combination Rom (Factory Binary)... At this time I do not have any windows pc's and my VM will not read the usbs of the phone... (im not that experienced with vm to set this up) So i grabbed JOdin for linux and proceeded to try to flash the binary. However, JOdin did not work for me. So i found Heimdall and installed to learn that i had to find some weird way to run it as SU for it to work... Tho Heimdall worked like a charm.... With Heimdall I had to take the rom and completely extract it to a folder and find all the img files in it to install on heimdal like sboot, boot, cm, system, and quite a few others as well.I used the "PIT" file from the combination rom (which came in the download). When done installing the phone boots into Factory Binary... Interesting little rom... From here you can access settings, tho the instructions tell you to enable developer options and turn on usb debugging... in this rom they are set on by default i believe, so that was kind of a waste of time... then from the main menu you click the icon that looks like a calculator and type in "*#0808# where you are then presented with usb options. Select the last one on the list with adb at the end of it, click save and reboot. At this point I thought i was supposed to install the stock rom back (that was where i was lost) however all you have to do is let it boot back to binary. After it has reloaded... plug it into the pc and send it the proper adb instructions to disable frp lock. Techeligible has a batch file for use in windows, however if you dont have windows like me that does no good... So I went into the batch file with a text reader and extracted the information i needed ( 3 adb commands).In terminal i made sure my adb and fastboot were updated and working. I learned that when you type "adb devices" it will show the phone and if it says nothing else you are good to go. However it may give you a problem with permissions. If this is the case then unplug and make sure usb debuggin is on, you can also check that the adb is enabled again by doing the *#0808# command again and make sure the last selection is checked. When all is in order... At first I thought all commands must work for it to succeed... However this is not true at all. Only one of the adb commands will not give an error and at that time you can reboot into download mode and install the stock rom back on. After installation the phone will reboot and FRP Lock is no longer on... Now you can go into settings open up developer settings (tap build number till it unlocks) and select "OEM Unlock" and turn it on. Make sure usb debugging is on and you can boot back into download mode and install TWRP without a hitch.
I tried installing a couple of custom roms, however I have had no success with getting one to boot. (always stuck in boot loop even with wipe or factory reset) so I gave up and left him with the stock rom. If anyone has any idea of how i could get passed the bootloop maybe i can try again for him sometime and see how he likes various custom roms, but now he is happy he has his phone back working and it only took me a week of off and on frustration to figure it out... Hope this helps someone... (please dont ask for links) but if you do need help or have questions feel free to ask.

BIG PROBLEM! Moto C without solution! Throw it away? Or is there a Bad#@ there to help me?

I think I have an unsolved problem. I know it doesn't exist, but it's very hard to find it.
I know it's not the Plus, but the Model is the Moto C XT1754 (NAMATH) Android 7.0 Nogaut - NRD90M.060
And there is no specific topic for it, but they are very similar and I thought I could post it here.
It's a very complicated problem, so I'll explain in detail what happened and why I had to come here to solve it.
(translated)
- STARTING:
I installed a TWRP through the app, without unlocking the Bootloader.
Whenever I turned it on, at boot still, the message appeared:
'red state
Your device has failed verification and may not work properly
Your device will boot in 5 seconds'
But it called normally.
I installed 'Magisk Manager 24.2' by zip and app afterwards.
I activated 'Zygisk' and in DenyList I activated/hidden from Google Play Services completely. All.
I restarted the smartphone and Sitema started having numerous errors. Most of the apps that I opened, closed with error, and other apps in the background too, mainly Google Play Services.
I tried to solve this but I couldn't because the smartphone was unusable.
I decided to format by TWRP.
But when I tried to restart the device, I always entered TWRP and continued that message in Boot ('Red State Your Device...')
I decided to reinstall Stockrom from Moto C XT1754.
When I tried to install Stockrom through flash_tool, I couldn't.
It always gives error.
'BROM ERROR : S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early.
[HINT}:'
or this one is the most common:
'BROM ERROR : ?? (0x1)
[HINT];'
I even tried installing a Custom Rom via Sdcard , 'Viper-namath-20171206-Coral-v3.1.1-UNOFFICIAL' with the GAPPs, etc.
I can install the ROM. (but the GAPPS gives an error at the end of the installation) 'open_gapps-arm64-7.1-micro-20220215'
But I think this case is because it is not installing the Custom ROM correctly. (Because of the Locked Bootloader? Maybe... I'm kind of a layman on the subject)
Because when I restart the device after installation it goes back to TWRP.
I can't get into Fastboot mode with the command by the buttons on the device, only by TWRP when I access 'Reboot>Bootloader'.
Reboot and go to fastboot (Black screen, down there written '=> FASTBOOT mode...'
I've already tried to recover/rescue the device by Motorola/Lenovo's 'Rescue and Smart Assistant'. But when I try to rescue it (with it connected to TWRP) it asks to accept the message to enable USB debugging.
But I don't have access to this window through TWRP.
Here comes the big question, why I am not able to solve my problem:
I think my 'USB Debugging' was off/disabled before I erased everything (formatted).
I'll try Stockrom's Flash through TWRP to see if it solves the problem, but I don't think it will.
I think the problem may be with the 'USB Cable' as well. He's old. I tested with a non-original USB cable that I had to see and I can't either, the errors persisted.
I plan on getting another original to test as well.
Just an observation.
My device is being recognized as 'USB MTP Device' (under 'Portable Devices')
If anyone can save me, I'd really appreciate it!
Thanks in advance for all the help! Every opinion matters!

And when I give the command 'ADB Devices' my device appears 'unauthorized'
'ZW3223CGWK unauthorized'