[Q] Kindle fire was in loop, now in "brick" i suppose - General Questions and Answers

so, i have read just about everything i can on these forums, and have tried everything. I want to say i rooted the fire, with burrito root3, and installed fff recovery. It was all working fine, then i added golauncher, and it worked amazing. I went on vacvation, tried to hook up to wifi to watch a movie on netflix, then it turned off and went into a boot loop where the fff logo came on for 5 seconds or so then it would turn off. I tried everything i could that i read on these forums, and still not loading. I have it stuck in "fastboot" now i suppose, where the yelow firefirefire logo is just there, the only good thing with this that i have noticed, that since it stays on, the computer sees the device, but that is where i am at, i would be happy with getting back to the oem os.

Related

Coby Kyros 1042 bricked with no reason

Hellow buddehs, this is Frank Garrett.
So my brand new tablet got bricked with no reason (just for fun dammit) and i have googled absolutely everything that could possibly help me but with no results. So it brought me to making this thread - the last thing i am trying to do before throwing out the tablet.
Well my tablet just got really laggy once and i tried to delete some applications that i've installed there, and after i did reboot it as usual. But it didn't launch as it should. Instead it gives me the "COBY" logo and that it - it just stays with this freaking logo all the time till it gets turned off. So i've tried to get it into the Recovery mode - but with no result either. It either does not doing anything but showing "COBY" logo, or just gives me black screen.
So i have absolutely no idea what to do (adb?) or is it even possible To Do anything, because i'm not sure if its totally broken or else...
Help please.

[Q] Kindle Fire System ro.product.board issue

Okay I have a Kindle Fire that has been rooted with the Kindle Fire Utility and until recently everything was fine and worked great.
A few days ago I attempted to install an app from the Google Play store that was incompatible, and searched the internet for possible solutions of how to circumvent this incompatibility problem and came to a site that said to change the build.prop file on the kindle with the ES file explorer app.
From what I read it said that what I was going to do was "trick" the kindle into thinking it is a different device, like a Samsung Galaxy S2 that will run the app fine.
All said and done I changed a few lines in the build.prop file and reset the device, and notice there is a difference in how it looks, but the app still says incompatible. I take it upon myself to go back into the mentioned file and change a few more lines, and again reset the device.
This time it does not boot normally, but loops the kindle logo and ends with having a dimly lit background with nothing on it. I hold the power button only to have this repeat, and eventually make it to the fastboot screen and finally TWRP logo and screen.
I spent some time messing around with it only to get nowhere, when plugged into my computer that I used to root it, it will not recognize it as an ADB device.
I had my brother come mess with it because he tutors computer science from time to time and he did not seem to make much progress either.
The only difference from when I messed around with it and when he did is that now I cannot get to the TWRP screen like before my brother had it. I asked him if he was able to change anything, and he said the only thing he did was when resetting it with the power button, instead of choosing recovery to go to the TWRP screen he just let it boot normally, which before never interfered with getting to the TWRP screen.
If anyone knows what I have done or can do to reverse this or even restore it to factory settings or back to when it was rooted, I would appreciate it greatly.
And if I left any details out, I can try to fill in any blanks.
Thanks!

Moto G Stuck In Bootloop

Now I'm posting this because my issue isn't like the ones I'm seeing here. I've done absolutely nothing to my device as far as tweaking goes, the device isn't even rooted. Randomly on a drive when I pulled up my map for directions, my phone's audio began skipping, the phone froze, & then crashed. Now I can't get past boot.
When I try to get into recovery mode via Fastboot, it just goes to a black screen.
I've allowed the device to die fully & then charge, but no dice. The status of the battery is showing as OK. My PC will not recognize the device in Fastboot either.
Any advice?

Need assistance/info with bricked shield tablet

Received a shield tablet through a promotion my company was doing with nvidia, decided to try it out. (pointing this out ahead of time to let the 'just return it' people know that I cant and am stuck with it.) upon finally deciding to boot it up a couple months later, it booted into the bootloader menu instead of booting like normal. then when choosing to boot would boot into a very stripped version of android with few apps, tegra services repeatadly crashing, no app store/play/etc . I wanted to have the proper out of the box experience nvidia intended, so decided to hunt down a stock factory image to flash to it to just resolve the issue and start from scratch with my new tablet. was able to flash recovery/boot/system/userdata/etc via fastboot. upon restarting, screen went black and wouldnt start. plugged in to computer, device manager says "APX" and that's it. with unknown device/driver icon. if I power it off all the way and plug it back in it just goes back to saying "APX" with a "?" in device manager.
how can I get it out of this mode and booting so I can finally try this thing out? have tried diff combos including bootloader/recovery mode button presses at boot time and nothing works, goes back to the same thing. I've also seen mention about nvflash and some other things when looking into this, but nothing solid on where I get the program, how im supposed to use it to fix my device.
Thanks

Please Help! Stuck at boot screen...

Hello. Sorry in advance if this is the wrong thread. I own a pretty old 1 year old tablet that currently has a problem.
Important info: Android 5, No access to a computer for 2 weeks (vacation), slightly cracked screen (still works), I had to install a Play Store apk as the one I had previously was corrupt. Tablet was functioning fine until the moment of the incident (except for the play store apk, which I later fixed).
Minor detail: Once the screen turns on after a restart the pixels near the top of the screen seem to turn purple for a second when I tilt the tablet.
Here is the story:
I was watching a YouTube video and suddenly my tablet froze. I thought: "Uhh, another freeze how annoying," and waited for it to load. I did not unfreeze. I thought: "Well, I guess I'll be fine if I turn my tablet off and on. This is where I got worried. My Power key was not responding. I tried the volume keys. Nothing. I tried connecting a mouse and moving it around. Still nothing. I thought "Ok, lets try restarting it" I did that by holding the Power key down for 10 seconds. To my relief, it turned off. But when it was turning back on again, it was at the loading screen for a little to long. It usually takes 5 seconds to get past the loading screen and enter the boot screen. I decided to wait. 1 minute: nothing. 5 minutes: nothing. I got worried. I tried restarting the tablet again. I restarted successfully but was stuck at the loading screen again. The was no movement on the screen. Only the loading screen. I decided to try the restart backup button which I could activate by putting a pin in a small hole at the back. It had the same effect holding down the power key had. I decided to ue my backup plan: recovery mode. I successfully entered recovery mode. I chose the option "clear cache" and tried to boot again. No changes. I did a scan for any root errors. it said that there were 5 errors, but there was nothing I could do about that. I tried doing a factory reset, then booting up. The reset was successful, but I got the same effect as always. No changes. I gave up and tried to google a solution on my phone. Most of them told me to install a PC program, but one told me to do the same thing I already did: reset, restart. So I decided to let the tablet sit with the boot screen for 2 hours. When I came back, there was no change at all. I tried searching again for a solution. A YouTube video said that the boot time after factory resets may be long, so I decided to reset and let it sit for a bit. 20 mins later, no changes at all. Finally, I gave up and now try to ask for help here.
Norqw said:
Hello. Sorry in advance if this is the wrong thread. I own a pretty old 1 year old tablet that currently has a problem.
Important info: Android 5, No access to a computer for 2 weeks (vacation), slightly cracked screen (still works), I had to install a Play Store apk as the one I had previously was corrupt. Tablet was functioning fine until the moment of the incident (except for the play store apk, which I later fixed).
Minor detail: Once the screen turns on after a restart the pixels near the top of the screen seem to turn purple for a second when I tilt the tablet.
Here is the story:
I was watching a YouTube video and suddenly my tablet froze. I thought: "Uhh, another freeze how annoying," and waited for it to load. I did not unfreeze. I thought: "Well, I guess I'll be fine if I turn my tablet off and on. This is where I got worried. My Power key was not responding. I tried the volume keys. Nothing. I tried connecting a mouse and moving it around. Still nothing. I thought "Ok, lets try restarting it" I did that by holding the Power key down for 10 seconds. To my relief, it turned off. But when it was turning back on again, it was at the loading screen for a little to long. It usually takes 5 seconds to get past the loading screen and enter the boot screen. I decided to wait. 1 minute: nothing. 5 minutes: nothing. I got worried. I tried restarting the tablet again. I restarted successfully but was stuck at the loading screen again. The was no movement on the screen. Only the loading screen. I decided to try the restart backup button which I could activate by putting a pin in a small hole at the back. It had the same effect holding down the power key had. I decided to ue my backup plan: recovery mode. I successfully entered recovery mode. I chose the option "clear cache" and tried to boot again. No changes. I did a scan for any root errors. it said that there were 5 errors, but there was nothing I could do about that. I tried doing a factory reset, then booting up. The reset was successful, but I got the same effect as always. No changes. I gave up and tried to google a solution on my phone. Most of them told me to install a PC program, but one told me to do the same thing I already did: reset, restart. So I decided to let the tablet sit with the boot screen for 2 hours. When I came back, there was no change at all. I tried searching again for a solution. A YouTube video said that the boot time after factory resets may be long, so I decided to reset and let it sit for a bit. 20 mins later, no changes at all. Finally, I gave up and now try to ask for help here.
Click to expand...
Click to collapse
Was your device rooted? Did you have TWRP custom recovery installed? If you don't have either of these two things then your only option is to flash the stock firmware via PC.
Do a google for:
"Return to stock (your model number)"
If what you need is out there somewhere, that woll find the instructions, the tools and the file(s) you need.
Sent from my LGL84VL using Tapatalk

Categories

Resources