Hello!)
such a problem, the phone freezes on the logo
Recovery is not loaded (also freezes on the logo)
computer does not see the phone
what could be wrong?
Related
Help me please!
I try to do a full wipe/factory reset on my DHD...when i did so my phone just won't boot, just black screen with blue "android" sign. Cannot turn the phone down, cannot come in to the recovery mode...nothing. What can i do, to restore my phone back to normal.
What ROM were you using? I've only ever seen the "ANDROID" bootscreen on SDK builds.
Somehow I solve the problem. I had to connect phone to PC and than reboot phone via adb bootloader and install new ROM from recovery menu.
I have posted already on the Omnia section...hoping others can help me with this problem as well...
After a power surge, my Omnia hanged then when I rebooted, its now stuck at that Logo Screen. Did everything possible (hard reset, flash rom, go into recovery mode which gets stuck after zune reboots the phone....)
Used the windows support tool and I get this message: The phone is not in the 'Connect to PC' state. Please, make sure that you follow the instructions and your phone shows the 'Connect To PC' image
But I am on that Connect to pc state, but once I click on recover, I get a flash of codes then shows this message on top.
Attached is a pic of that flash message before the error above comes out.
Any help would be greatly appreciated
i have exactly the same problem. my omnia used to boot loop or logo stuck randomly before mango update, flashed a new rom, connected with zune to update but it freezes again in step 8/10 (restarting your phone).
the download mode works fine and the t-mobile logo dissapeared after flashing the new rom (at last), but the problem still persists
Essentially, whenever I try to turn on the phone, it tries to boot, gets to the LG logo, and then goes blank, returns to the LG logo, goes blank... and so on.
What I've tried: Booting into download mode gives me a firmware update menu that stays at 0% (Edit: Computer cannot read the phone during this). Cannot boot into anything else but a reset because it reboots too quickly. But, I cannot reset anyway because of very necessary data on the device.
I recently rooted and installed a custom rom on my 2011 (gen1) kindle fire.
I followed directions (https://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955) to root.
Then I installed twrp latest version (older version did not accept my rom) https://twrp.me/amazon/amazonkindlefire.html
Then I installed the Infriction speed rom https://forum.xda-developers.com/showthread.php?t=2580232
I installed some apps... about 134 MB left in app install partition.
In developer settings I enabled ART, thinking, maybe this will make it faster...
Then it rebooted.
It was then stuck at a screen (not the android logo w/ words "kindle fire", but the bubbles screen of the os).
I decided, maybe I can fix with my pc.
Unplugged it - it then immediately shut off (loss of power??).
Then tried to use kindle unbrick utility, the various commands.
Now it is out of battery, but when I plug into PC or wall, it's in a boot loop, where it shows about 3 sec of the boot logo (android robot and words) and shuts off, before doing that again.
It is now undetectable by Kindle Fire Utility (just says "waiting" while the kfire reboots over and over), fastboot probably cannot detect either... (?) (worked one time but it just shut off again... and now doesn't work??), and can't boot into recovery.
Help.:crying:
So I'm assuming the partition ran out of storage?? but then what happened...
So I had a little luck trying to reset: ht tp s:// it stillworks.com/fix-kindle-fire-boot-loop-30462 .h tml
Then I got to the OS booting screen.
EDIT:
well that worked once... I tried to do adb reboot recovery after it got to OS boot screen (bubbles).
adb tells me:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Then it just fell into boot loop again. ?
So then I plug in, try again, it's just the boot loop. I'm going to try again after 30 min, but maybe need to do something different.
Cause of boot loop found
So it turns out it was just out of battery... I let it charge, did the reset thing, then was able to reboot into recovery.
\^o^/
Hi
I have borrowed this one with unknown condition, maybe someone played with it on JTAG to get back data....
When arrived, it was a HARD BRICK, no sign of light at all, only qualcom flash loader recognition (9008).
No vibrating, no poweron, no battery charging, , only a black screen.
I have played a lot with it, resurrected with an SD card, reflashed with ODIN....
Now the phone can poweron alone (without a boot-sd), but bootlooping in ~10sec, only samsung logo and one vibration / period.
On recovery it says "nincs parancs." (no command) and immediately reboots again into normal bootloop.
I have re-flashed the recovery as well to stock one, but nothing changed.
I have successfully get into recovery by key combination on the right second (bypassing the no command), but ONLY ONCE, and i am unable to do again.
When i was in recovery, reformatted cache/data, reboot, but no change.
Now in fastboot mode it shows read only mode.
If i am right, i can re-flash it with SD card again, but WHAT TO DO to get out from bootloop or to get a working recovery or at least TWRP?
Unfortunately the full build number is unknown.
Any suggestion?
Somebody have any ROM image with ALL of the partitions inside for 9195 hungary version?