Hi everyone,
the reason I'm starting this thread is because after two days of trying to solve my issue by reading threads and trying various things, I'm still stuck. The scenario is this, my Kindle Fire HD is stuck at teamwin screen and I cannot access TWRP. I have no idea if this is soft-bricked or corrupted or whatever. What happens when I switch on the tablet is that I get the orange Kindle Fire logo, then the blue Kindle Fire logo and then teamwin screen which flashes every 5 seconds and is stuck there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
During this process, the Device Manager from Windows 8.1 successfully recognizes the tablet as 'Android Composite ADB Interface'
If I start CMD as Admin mode and key in 'adb kill-server' and then 'adb devices' I can see the device listed as '0123456789ABCDEF recovery'
Another issue is that when I go into 'adb shell', all the commands I type, I get '/sbin/sh: command not found'. I also tried 'KindleUnbrickV1.1.jar', but every option I select I get <waiting for device> and stays like that. I left it overnight.
I also tried Kindle Fire Utility, but was unsuccessful as well.
At this point I don't think there's anything else I could do and I guess it's time to say goodbye to my little fella. At least managed to finish univ with it.
If anyone has some opinions or suggestion, you're more than welcome to do so and they will be highly appreciated. By the way, I don't have any important data on the tablet so it's ok if I need to format it without taking backups.
Kind regards,
/pH-
Related
I've done some searching, but can't seem to find this particular situation.
Stats: Original droid, running clockwork, cyanogen 6.x, everything worked well this weekend. It's not activated currently, but the phone behaved as it should all weekend, as I prepped it for sale yesterday.
Yesterday, I rebooted the phone. Well, sort of. It rebooted, and my motorola logo is centered in the left third of the screen, rather than in the center third. It will not move past the moto logo when powered on.
I've tried X+power, and assorted other combos, and the only one that will allow me access to anything is holding down+camera when booting, which gives me a bootloader 2c.6c screen, showing that the battery is okay, and that it's okay to program.
I can connect in this mode to RSD lite, and attempt a reflash, but when the phone reboots, it goes back to the crooked motorola logo screen, and stays there.
Initially, before I attempted to reflash with rsd, I could find the device with adb, but it wouldn't reboot or reboot-bootloader, hanging instead on the crooked logo.
Am I missing anything? If it's bricked, it's bricked, it hasn't been my primary phone since I bought my X, but Ideally I'd like to restore it and either keep it as a backup, or sell it and make a buck or two.
Sorry for writing a book, just figured I'd convey as much info as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my cool new boot page. The bottom right side is just some white nonsense, no legible text or anything.
Really? No thoughts at all? Not even a "dude, you're so screwed".
Hello,
I posted this on cyanogenMod forum few days ago, but no one was able to help me so far, so maybe I will have more luck here...
Recently I found my old dev phone 1 with stock image and decided to make it more useful by installing cyanogenMod on it. I tried to follow instructions on http://wiki.cyanogenmod.com/index.php?title=Android_Dev_Phone_1:_Full_Update_Guide page. I downloaded Amon_Ra's Recovery, adb and fastboot tools, added all-htc udev rules and followed instructions on fastboot page http://wiki.cyanogenmod.com/index.php?title=Fastboot#Access_bootloader to access the bootloader.
Unfortunately fastboot devices returned empty list of devices even more, lsusb did not list any new device.
When connecting the phone in debug mode adb sees my phone without problems and lsusb shows my phone as well so it's not connectivity problem.
I found this section about SPL S-OFF on fastboot page http://wiki.cyanogenmod.com/index.php?title=Fastboot#Verify_SPL_S-OFF and it seems it applies to my case as my fastboot screen looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The section continues that in such case I have to use different SPL, so I went to http://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_DangerSPL page to install DangerSPL, but it requires Amon_Ra recovery which again requires fastboot to install so there's a cycle here
I would be grateful for any hints what I should do in this situation
Thanks!
ok, never mind: I used standard dream procedure with rooting and it worked ok, I'm on cyanogenMod now
Cheers
Morg
Hi, after rooted my kindle and installed ADW launcher by kindle first aide.. I was installing the "Stunts_Wallpaper_Fix" but kindle after installation shut down.. now is stucked on the "Kindle Fire System Recovery".. it isn't recognised by pc (I got factory cable) and if i choose "Reset to factory Defaults" The device try to recover but it reboot again and return at the "Kindle Fire System Recovery"... :crying::crying::crying:
Can I do something???? Help me please :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Up.. Help me please :'(
Nothing to do then... ty Stunts.
Up..
RhysTheExiled said:
Up..
Click to expand...
Click to collapse
Sorry to hear it bricked while using my utility, it has a number of safeties but occasionally this will happen. You are probably going to need to reflash it from fastboot to fix it, im guessing the framework-res.apk didn’t transfer correctly and corrupted, so the system can't boot without that file correctly. This usually happens when the system partition runs out of disk space when the file is transferred over. I have a check in place so that that shouldnt happen though so its a bit odd that it would. Also so sorry for the late reply, im not near as active on here as i used to be, that might change soon though...
I used it at my risks.. I didn't see on the forum a same problem like that..
Now i hope i can fix that.. but my device isn't recognized by my pc.. How can i do that for recognise it and get fastboot mode?
So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!
Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!
Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk
Hi all,
So, I was running fine with CROMi-X KitKat, but wanted to upgrade to Marshmallow (to install sw not supported in KitKat), so decided to try KatKiss 6.0. It's been years since I've played with flashing ROMs, but I did a little reading to refresh my memory. Then I rebooted into recovery (ClockworkMod), backed everything up, then wiped everything, formatted /data, and tried flashing the KatKiss zip file. At that point, it just sat there forever at the ASUS logo screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried several times to boot back into recovery by holding the Vol+ and Power buttons, but it either doesn't boot, or boots to the above screen. I've connected it to my Mac w/ the Android SDK Platform Tools, but adb doesn't see any device listed. [I've got an old Windows laptop (XP?)] I could use if it will do something the Mac can't.]
Any advice on how I can save this tablet?
Have you found a solution finally?
Well, I haven't found a solution, but after letting it sit unplugged for months, I came across it today as I was straightening up. I plugged it in, waited maybe half an hour, and was able to boot it into recovery mode. I was then able to restore from a backup, and damned if it didn't reboot and come up just fine. No idea why it wouldn't boot into recovery before, but I'm happy camper!