Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Kooky_Lukey said:
Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Click to expand...
Click to collapse
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Thepooch said:
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Click to expand...
Click to collapse
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Kooky_Lukey said:
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Click to expand...
Click to collapse
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Thepooch said:
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Click to expand...
Click to collapse
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Kooky_Lukey said:
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Click to expand...
Click to collapse
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Thepooch said:
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Click to expand...
Click to collapse
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Kooky_Lukey said:
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Click to expand...
Click to collapse
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thepooch said:
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Click to expand...
Click to collapse
Thank you so much you do not know how much I appreciate it. If anything youre writing has anything to do with java i would love to help but if not then i wouldnt be of much help
stunts513 said:
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I wouldn`t even bother opening it let Amazon do their job. Case openers, case damage it would be pretty hard to pin the issue on them if you were to open the device.
Actually because of the present condition of the device I would go this route http://forum.xda-developers.com/showthread.php?t=2096888 . Just pick the latest version of the 8.9 to restore to you should also be prompted with an option to wipe cache and data please do so. All the partitions will be restored to stock and the device will be ready for return. Say nothing about modifying the device just leave those details out. If you want help catch me online and we will set something up. Some of this does depend on the state of your warranty. Be courteous with customer service and brief as to what caused the issue you simply just found it that way Good luck.
Good point, wasn't really thinking about "what if the problem wasn't that".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Related
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
I remember the instructions for the skorpn factory cable says to plug it into your computer first and then your device. Make sure you hold the power button for 20 seconds to shut it down first.
I just read through more information. I don't think this factory cable is even getting me into fastboot mode. What's my screen supposed to look like if it is in fastboot? I can't find any info on what that looks like.
Looked at your video you need to fix your bootloader its somehow broken your not getting to the fff screen I could be wrong but best from what I observed in your video this is the closest to your issue. Someone correct me if Im wrong but this is a job for firekit.
Thepooch said:
Looked at your video you need to fix your bootloader its somehow broken your not getting to the fff screen I could be wrong but best from what I observed in your video this is the closest to your issue. Someone correct me if Im wrong but this is a job for firekit.
Click to expand...
Click to collapse
Is firekit the one where I need to crack open the back case? I really hope not...
jeffjoleen said:
Is firekit the one where I need to crack open the back case? I really hope not...
Click to expand...
Click to collapse
You're fine. I watched your video. The first time you plug it in, I think you hit the power button with your forefinger before you plugged it into your computer and the KF booted normally. When you turned it off, back on again, and then it got "stuck" on the "kindle fire" logo... that's what's supposed to happen with the factory cable. Your KF should now be in fastboot mode. Now you have to get your drivers working so that the computer sees the device properly and you'll be able to issue fastboot commands.
Look at this link...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
compare what you get in the device manager with the table in the middle of that post. You should be seeing "Android Phone -> Android Composite ADB Interface" in the list. Then it's a matter of opening up the Windows command prompt program and sending the KF some fastboot commands to have it boot into recovery. That's in one of the posts you already mentioned in the OP.
EDIT: My bad... that should be "Android Phone -> Android ADB Interface"... no "Composite" in there.
This is new...I now go to the Device Manager and it shows under the main "Martin-PC" I now have "Android Phone" with the "Android ADB Interface" nested underneath it. I don't think it's going into fastboot mode like the factory cable is supposed to do. What is it supposed to look like?
Unfortunately Jeff it is but I really wonder about your situation because your not getting to the fff bootloader but you may be getting to the stock one . So get it where your just looking at the kindle fire logo not the pissed of unicorn go to kfu shift+right click on the tools folder choose open command window here then type fastboot devices post the results here if any
Try using the fire utility and click I think #1 or boot options make sure it says the device is online. Then hit the normal boot option I think your stuck in fast boot that is what happened with me. Use a regular cable make sure you have the drivers.
jeffjoleen said:
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
Click to expand...
Click to collapse
Did you try to wipe it?
Code:
fastboot -i 0x1949 -w
I don't want to discourage you guys from trying to help people here who find themselves in trouble, but please try to understand the problem before offering guidance. How can you fix something without understanding the situation?
Hyperrunner said:
Try using the fire utility and click I think #1 or boot options make sure it says the device is online. Then hit the normal boot option I think your stuck in fast boot that is what happened with me. Use a regular cable make sure you have the drivers.
Click to expand...
Click to collapse
The system software on his device is broken and will not boot. Setting the bootmode to normal with KFU or otherwise doesn't fix anything. That would just put him right back into the situation he's trying to get out of in the first place. He doesn't want to get out of fastboot mode the way you're suggesting, he's trying to get into fastboot as the first step in flashing a new ROM.
xiaohewu said:
Did you try to wipe it?
Code:
fastboot -i 0x1949 -w
Click to expand...
Click to collapse
The OP and his followup posts show that he doesn't know if he's even in fastboot mode. Your question doesn't even make sense in this context.
Guys, this post isn't meant to chastise you for trying to help. Just don't throw out random things to people who are already flustered and confused as it is.
jeffjoleen said:
Hello everyone,
Here's a video I created to walk through my problems.
http://www.youtube.com/watch?v=OyTFmDCAa3w&feature=youtu.be
I'm stuck. No idea where to turn from here. I would LOVE to be able to talk to someone. I have a factory cable, but still not able to get into fastboot. I have TWRP installed and made a backup of my original Kindle software.
I"ve already tried EVERYTHING suggested and nothing has worked. I've gone to the following links:
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?t=1638452
I've read every word and understand it to a point. I think I'd be able to work it all out of I could get to the fastboot. I'm not completely clear on all of the vocabulary and that's what's probably screwing me up.
My email address is [email protected]. If somebody could email me and I'll send my cell number and we can talk, I think I can get this up and running. I'm more than happy to pay for the service or donate to a developer of your choice. I'm just completely screwed at this point and I'm beyond frustrated now. Thanks for looking and hopefully somebody can help. -Jeff
Click to expand...
Click to collapse
Did you fix your KF?
Was trying to root kf . started "Install Permanent Boot, etc." all seamed to be going OK. Went as far as TWRP was installed. At that point the OS for the fire was GONE. Fire is hung at TWRP. No operating system for anything. Plz HELP
If TWRP is still functional, then you can just "mount USB," put a rom and gapps into the folder, flash them, then boom! You'll have an OS again; just basic protocol haha.
I would also wipe data/cache, dalvik, etc. just in case...
...But if you want stock Amazon Gingerbread then you're going to have to look way back in time in the forums for the stock rom.
What happens when you reboot system? Does it go right back to TWRP?
Me Too
I have no OS on my kindle fire. I wiped the memory and now I lost my roms and backups. I heard you can try ADB, but I couldn't get it to work. Mine just boots to the kindle fire logo but nothing else happens. It's basically collecting dust.
Take a breath, relax, and take comfort in the fact that there is nothing wrong with your Kindle. It is doing exactly what it was told to do. Your problem is easy to fix, but you need to know what's going on first.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it. Then read it again. And while you're at it, go ahead and read it a third time. Do this before anything else.
[Edit:] Oh yeah, and read this too.
http://forum.xda-developers.com/showthread.php?p=25730650
Ahh, what the hell, read this one as well.
http://forum.xda-developers.com/showthread.php?p=26435498
soupmagnet said:
What happens when you reboot system? Does it go right back to TWRP?
Click to expand...
Click to collapse
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
"
Click to expand...
Click to collapse
jerryhndy said:
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
Click to expand...
Click to collapse
Wow, very interesting, and welcome back.
Weird. It's almost as if you have TWRP installed to the system partition. Selecting "reset boot" on FFF1.4 changes the idme value to 4000, so your device should boot to the system partition no matter what. But you said the boot logo changes from blue to red. What's actually happening, is the bootloader finishes doing it's thing and then boots to the system. The red and white Kindle Fire logo you see then is the stock boot animation, which makes everything really strange. "Recovery" boot shouldn't show the boot animation at all. And if you have recovery installed to the system partition, you shouldn't see the boot animation there either. WTF did you do to your Kindle?
My best advice would be to get into fastboot and reinstall TWRP to the correct partition so you can reinstall your ROM. From the sounds of it, you will likely have no access to the adb shell, in which case you would need to get a factory cable.
So, boot into recovery and enter the following command to see if you even have a working shell:
Code:
adb shell idme bootmode 4002
no os
jerryhndy said:
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
Sorry, above is the correct info that I sent in. #2 is "recovery. Sorry for the confusion.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
soupmagnet said:
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
Click to expand...
Click to collapse
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
jerryhndy said:
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
Click to expand...
Click to collapse
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
soupmagnet said:
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
Click to expand...
Click to collapse
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
jerryhndy said:
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
Click to expand...
Click to collapse
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
soupmagnet said:
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
Click to expand...
Click to collapse
I found a keyboard in TWRP in the KF, however it would only let me type #'s. I think I am lost here. Do you accept KF's (sent to you), for
repair or what ever to get it to root ?? If so, I could sent it to you etc. [email protected]
Soupmagnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Thepooch said:
Soup magnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Click to expand...
Click to collapse
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
jerryhndy said:
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
Click to expand...
Click to collapse
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Thepooch said:
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Click to expand...
Click to collapse
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
to
jerryhndy said:
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
Click to expand...
Click to collapse
I sent you a pm Jerry. I would not charge you. Lets take a look and see if we can`t fix it without you even having to ship it.
Help.... A100 was running fine last night, but hung.... I rebooted it and just got the acer logo and nothing else....
I was running ICS, (not sure which version)....
I've tried quite a few roms as 'update.zip' but all i get is the 'droid' picture, then it lies down with a big red '!'.
Now, all I can do is get into 'bootloader v0.0.13-ICS: Starting Fastboot USB download protocol'
If i connect to pc, doing adb devices shows no devices..
any ideas? :crying:
Yeah eMMc is a goner.
Sent from my Galaxy Nexus using xda app-developers app
filking said:
Help.... A100 was running fine last night, but hung.... I rebooted it and just got the acer logo and nothing else....
I was running ICS, (not sure which version)....
I've tried quite a few roms as 'update.zip' but all i get is the 'droid' picture, then it lies down with a big red '!'.
Now, all I can do is get into 'bootloader v0.0.13-ICS: Starting Fastboot USB download protocol'
If i connect to pc, doing adb devices shows no devices..
any ideas? :crying:
Click to expand...
Click to collapse
Adb commands don't work in fastboot mode, you need fastboot devices instead, so adb devices not working doesn't mean anything. If it did work that's odd though lol. Also, booting in fastboot is the wrong mode anyways, use the other volume key for recovery, for now remove the external sd then boot recovery and report back what happens there.
Tapatalked from my HTC DNA
Ok, removed the usb and external SD.
Do the other boot I get a quick message saying 'erasing cache before sd-update'
Hold on...
While typing this, it's changed..
Before I had the 'droid' then he fell over when '!'... it's done that again, but straight away it's got loads of messages.
E:Can't open /dev/block/mmcblk0p5
(no such file or directory)
that is repeated several time for dif files/directories...
Then it displays the recovery menu.....
reboot,
apply update
wipe data
wipe cache
apply update
1st time it's shown that....
Next step??
Anyone help??
I have the Android system recovery utility...
What now?
filking said:
Anyone help??
I have the Android system recovery utility...
What now?
Click to expand...
Click to collapse
You can try wiping but that error is usually a dead or dying emmc.
Also, have some patience, we have lives to live we answer when we can.
Tapatalked from my HTC DNA
lol, sorry... 2nd post wasn't meant as a 'hurry up and fix mine, because i'm more important'.....
I was typing something else in, then i decided that was stupid, so i deleted and put that instead....
my bad...
:angel:
just as an update, this may seem silly to some but if I don't tell you i'll never know...
The recovery does nothing, so I put it in bootloader mode...
connect up the usb,
then typing 'fastboot reboot' does reboot the device... so maybe other commands will work??
how do i wipe?
and i'm clutching at straws....
filking said:
just as an update, this may seem silly to some but if I don't tell you i'll never know...
The recovery does nothing, so I put it in bootloader mode...
connect up the usb,
then typing 'fastboot reboot' does reboot the device... so maybe other commands will work??
how do i wipe?
and i'm clutching at straws....
Click to expand...
Click to collapse
Fastboot commands will always work provided drivers are installed and it can boot into fastboot, it doesn't mean you aren't in the process of bricking, just hasn't gone all the way yet. When its final you won't even get a screen that lights up or vibration.
Since you asked though in recovery you can wipe cache but that will likely give errors again. The nuclear option is fastboot erase userdata but that's like massive data destruction, even internal sd I think.
As you're stock, stop now, and get in touch with acer and see if they'll cover it for warranty repair under their 1 year BS coverage.
Tapatalked from my HTC DNA
Please excuse my ignorance to some things.
The tab isn't under warranty, it's 15 months old
It wasn't stock, i had one of the modded roms installed... (but i can't remember which one, I did it last year sometime to swap internal disk for external one to give me more space)..
I'm not worried about anything on the tablet at all as luckily I did a complete system backup on titanium 2 days ago on my external sd.
Cheers
filking said:
Please excuse my ignorance to some things.
The tab isn't under warranty, it's 15 months old
It wasn't stock, i had one of the modded roms installed... (but i can't remember which one, I did it last year sometime to swap internal disk for external one to give me more space)..
I'm not worried about anything on the tablet at all as luckily I did a complete system backup on titanium 2 days ago on my external sd.
Cheers
Click to expand...
Click to collapse
I said stock because you have a stock recovery, though fastboot mode says you rooted and all that at some point. Probably ran a stock based Rom and ended up overwriting recovery which makes this harder to figure out. But its 99% likely its dying.
You can manually flash a recovery in fastboot and try to factory reset there or just do the fastboot command in my last post.
Tapatalked from my HTC DNA
Thanks for all the replies... I'll look round the forums to work out how to flash recovery in fastboot mode, then i'll try the wipe userdata.
If that fails,i'll just wait.... I noticed that the genius's are currently looking at ways to fix the numerous brick problems so maybe in the future there will be a simple solution..
Has there been an actual reason for the brickage... Is is motherboard related?
filking said:
Thanks for all the replies... I'll look round the forums to work out how to flash recovery in fastboot mode, then i'll try the wipe userdata.
If that fails,i'll just wait.... I noticed that the genius's are currently looking at ways to fix the numerous brick problems so maybe in the future there will be a simple solution..
Has there been an actual reason for the brickage... Is is motherboard related?
Click to expand...
Click to collapse
Read the brick thread for info on it, but short answer is emmc died.
Tapatalked from my HTC DNA
Well, acer support want £55.15 just to post it back to them, then they will call with cost of repair... lol I don't think so somehow..
Luckily I am in a good position at the mo, so i've just purchased a nexus n7...
I'll monitor this site until 1 day maybe one of the genius's on here will find a cheaper cure..
Good luck all...
(i'll be moving to the nexus section now then.. look out overthere.... :silly
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
I have a bricked kindle (8.9). i have followed ALL guide but still get red screen and then fast boot screen.
i have pushed boot and recovery and still get the same . i used first aid package and kfhd, but still boot to fastboot screen.
I would appropriate any help or guidance.
gs4n said:
I have a bricked kindle (8.9). i have followed ALL guide but still get red screen and then fast boot screen.
i have pushed boot and recovery and still get the same . i used first aid package and kfhd, but still boot to fastboot screen.
I would appropriate any help or guidance.
Click to expand...
Click to collapse
you ever get this straight? i had the very same issue and after several DAYS of reading/flashing/swearing i finally got it straight back to factory, let me know if you still need help and i will try to find the thread that ultimately helped me bring mine back to life
Thanks
Mike
11fan said:
you ever get this straight? i had the very same issue and after several DAYS of reading/flashing/swearing i finally got it straight back to factory, let me know if you still need help and i will try to find the thread that ultimately helped me bring mine back to life
Thanks
Mike
Click to expand...
Click to collapse
Hi,
i am still down. how did you get it to boot up. ? How did you fix it ? Mine is completely blank now. Thanks,
OK..let me find the thread that should get u going..I have it bookmarked on my PC but using mobile ATM, I will try to find it
this here should get you going! just follow EXACTLY! (with the exception of using KFFirstAide) just use regular command prompt run as admin) probably will not have to go past 8 in most cases, usually after you flash that recovery image and erase cache and user data it will reboot in it's OWN recovery on next reboot, and also when erasing user data, it could take up to 45 mins maybe depending on how long you had been using it before it got corrupted so don't panic when it sits there forever after you issue erase user data command. IF it reboots back into it's own recovery it will give you two options on the Kindle screen to either boot into OS or RESET to factory, in my experience I would definitely choose to RESET TO FACTORY DEFAULTS, but thats your choice, and if you need help I will try to walk you through it on some type of IM or google hangout or something. keep me posted as im curious to here the outcome. I know this has fixed two Kindles with the same problem as yours http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193
can you still access fastboot?
my KFHD 8.9 was stuck in fastboot mode also a few days ago (http://forum.xda-developers.com/kin...lp/help-stuck-kindlefire-boot-screen-t2971768), and @11fan helped me. (Thanks a lot!). That thread that he posted was the one that helped me revive my kindle. I also tried the KFHD SRT where i tried the option to restore with the SU app. I actually didnt know if that helped but when i was finally able to get my kindle going, it was on version 8.1.4 (i was on 8.5.1 before). Then i used that thread, the thing is, it took me 37 minutes to erase the userdata (as was mentioned by @11fan), and when i rebooted to system, i didnt go the restore factory settings (probably because i erased all the userdata already).
I hope you get to fix your kindle. i know the feeling of being in that situation.
? ?. ? ?