ok so i firgure i root my tablet with superoneclick 1.9 after that i restarted my tablet and everything was fine i then downloaded CWM for the tablet and was doing pretty much everything i did with the one for the DX i went to create a backup and everything seem fine until i restarted my galaxy tablet and it would stay stuck on the samsung logo, i then tried to do the power and volume down and all i get is the downloading and do not turn off i think i have tried everything and with no luck so please if someone knows anything please let me know before i throw it across the room. please and thanks
edit: if you know please dont just read and help me out thanks...
elitecmdr666 said:
ok so i firgure i root my tablet with superoneclick 1.9 after that i restarted my tablet and everything was fine i then downloaded CWM for the tablet and was doing pretty much everything i did with the one for the DX i went to create a backup and everything seem fine until i restarted my galaxy tablet and it would stay stuck on the samsung logo, i then tried to do the power and volume down and all i get is the downloading and do not turn off i think i have tried everything and with no luck so please if someone knows anything please let me know before i throw it across the room. please and thanks
edit: if you know please dont just read and help me out thanks...
Click to expand...
Click to collapse
You want power and UP to get into recovery again.
i already tried that as well and no luck this is the second time this happens to me on the galaxy tablet i never had an issue with any other android device [email protected]#$%^&*(
If your tab can still go into download mode then I believe you want this guide:
hxxp://forum.xda-developers.com/showthread.php?t=1133590
(Sorry, can't post links yet)
I think the instructions on recovering a soft bricked device are what you're after...
drezman said:
If your tab can still go into download mode then I believe you want this guide:
hxxp://forum.xda-developers.com/showthread.php?t=1133590
(Sorry, can't post links yet)
I think the instructions on recovering a soft bricked device are what you're after...
Click to expand...
Click to collapse
im trying to do that but when im on heimdall and i connect my tablet it wont even recognize it so i can install the drivers and proceed to the next step here is what i been trying. http://forum.xda-developers.com/showthread.php?t=967175 so every time i connect my tablet to the pc its saying that the device was not recognized...im to the point of giving up twice i have done everything by the book and always something goes wrong
I see. So does it give an error when you try to install the drivers with zadig.exe, or have you completed that step and the device is still not recognized by heimdall? It's probably unrelated, but heimdall only recognizes my tab on one of the two usb ports on my crappy old laptop. (They both work for mass storage) it's a long shot, but maybe try another port?
Sent from right behind you...
ok this is what i get once i plugged it on my pc it did not reconize it then i did zadig and this is what i get:
ini file 'zadig.ini' not found - default parameters will be used
0 devices found.
libwdi:info [detect_version] Windows 7
0 devices found.
Driver Installation: FAILED (No such device)
1 device found.
Using inf name: Unknown_Device.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created C:\usb_driver\Unknown_Device.inf
Driver Installation: FAILED (Resource already exists)
1 device found.
Settings, applications, development, usb debugging checked.
Okay so i did something i shouldn't of.
After buying a T-mobile dell streak 7 online, i found out it had been rooted with clockwork recovery mod by dj steve v4.0.1.4. When i tried working with it i found out i couldn't use the phone functions of the tablet so i decided to do a factory reset in the settings. To my dismay the problem only got worse and now when the tablet boots up normally it asks me for a password that wasn't on there before. I read on a thread somewhere that this is because the device is trying to decrypt something but that it's because there's no OS on it. I can still boot up in recovery mode and perform all the options in there.
So i bought a usb cable for it hoping that i would be able to flash it back to factory settings, but now i am unable to get it to work with usb.
I have a win 7 64 bit and i have tried downloading divers from all kinds of places which seem to be the right ones but windows will not allow me to install them and insists that the best ones are installed.
I've downloaded android sdk tools and installed all the components that are pertinent to this version and make (at least i think)
I've tried downloading PDAnet, the pc sync tool that is available on the dell site and that didn't work either. Under fastboot mode on the tablet the driver is installed correctly but still appears as a unknow device and i don't see the fastboot window show up when i plug it in so...
I've literally read hundreds of threads to see if maybe i could do it by placing update.zip files on the sd card and then installing them under CWM, some have worked, some haven't but when i reboot it's still the same.
Please help!!!
timaloud said:
Okay so i did something i shouldn't of.
After buying a T-mobile dell streak 7 online, i found out it had been rooted with clockwork recovery mod by dj steve v4.0.1.4. When i tried working with it i found out i couldn't use the phone functions of the tablet so i decided to do a factory reset in the settings. To my dismay the problem only got worse and now when the tablet boots up normally it asks me for a password that wasn't on there before. I read on a thread somewhere that this is because the device is trying to decrypt something but that it's because there's no OS on it. I can still boot up in recovery mode and perform all the options in there.
So i bought a usb cable for it hoping that i would be able to flash it back to factory settings, but now i am unable to get it to work with usb.
I have a win 7 64 bit and i have tried downloading divers from all kinds of places which seem to be the right ones but windows will not allow me to install them and insists that the best ones are installed.
I've downloaded android sdk tools and installed all the components that are pertinent to this version and make (at least i think)
I've tried downloading PDAnet, the pc sync tool that is available on the dell site and that didn't work either. Under fastboot mode on the tablet the driver is installed correctly but still appears as a unknow device and i don't see the fastboot window show up when i plug it in so...
I've literally read hundreds of threads to see if maybe i could do it by placing update.zip files on the sd card and then installing them under CWM, some have worked, some haven't but when i reboot it's still the same.
Please help!!!
Click to expand...
Click to collapse
You need to grab a NVFLash pack, put device in APX mode, install the APX drivers, and install a complete full restore.
reply
giveen said:
You need to grab a NVFLash pack, put device in APX mode, install the APX drivers, and install a complete full restore.
Click to expand...
Click to collapse
Thank you so much for taking your time to help.
Ok so i downloaded NVFlash, that i have found to be able to put my device in APX mode i need to hold down the power button and the volume - button at the same time when booting up but that sends me to fastboot. Is this the same as APX ? Sorry i don't know much about this.
Also when you say install the APX drivers, i have not been able to find these, could you send me a link ?
I don't mean to be rude or mean, but this is a question that has been answered a hundred times here, please look around and read a bit, we are getting tired of holding baby hands.
Thanks for your imput
giveen said:
I don't mean to be rude or mean, but this is a question that has been answered a hundred times here, please look around and read a bit, we are getting tired of holding baby hands.
Click to expand...
Click to collapse
Hey! Thank you for answering. Please don't be too quick to pass judgement, I have read hundreds of threads and i have downloaded all kinds of different drivers, roms, and recovery images. I've followed all the instructions of the related posts but the Tablet's OS wont boot up. I cannot install any .pkg updates because any option i select when i boot it up holding down power and volume + buttons sends me to CWM recovery mod and all the update.zip roms that i have installed this way have made no difference.
I have come to the conclusion that i need to flash a recovery image from the computer but i cannot because all the drivers i have found for it have not worked. My device does not appear as a drive therefore i can't see it in nvflash or even windows for that matter. yesterday i called dell support to see if they had any drivers available that weren't already posted on their site but with no luck.
The reason i'm writing this is because i was hoping someone had a similar problem and could help me, i know you deal with people that don't even take the trouble to look into the other threads every day, but believe me i have.
If you can help i would greatly appreciate it, or point me to what i'm doing wrong Tks.
In NVflash or APX mode the S7 doesn't appear as a drive. With your S7 on plugged into your PC, you don't see it as a drive? This should work right out of the box. Although some have reported the manual mentioned Driver. Zip folder is missing.
If hold the Volume + and - button in a plug into your PC, do your hear a beep? If so, you would then go into the device manager, select the APX device and install the drivars from the NVflash download package.
These videos posted by "giveen" may help as well: http://www.youtube.com/playlist?list=PLB99FAE280F618B12
awesome
wptski said:
In NVflash or APX mode the S7 doesn't appear as a drive. With your S7 on plugged into your PC, you don't see it as a drive? This should work right out of the box. Although some have reported the manual mentioned Driver. Zip folder is missing.
If hold the Volume + and - button in a plug into your PC, do your hear a beep? If so, you would then go into the device manager, select the APX device and install the drivars from the NVflash download package.
These videos posted by "giveen" may help as well:
Thank you so much, i was finally able to install the drivers in APX mode. Flashing it from here shouldn't be too much of a hassle. Very grateful for your help. Cheers
Click to expand...
Click to collapse
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Crossvxm said:
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Click to expand...
Click to collapse
Many Android devices, once depleted of battery, will not boot properly until the battery is anywhere from 20% or above. Try letting it charge longer. To speed up the process, use a wall adapter from your other devices. it will pump more voltages. As you said, there aren't any mods I can see that would cause bootloops or bricks.
Try charging it for a good hour, not booted up. To make sure it has charge. Then try to turn it on. This is very weird though, first time I heard a Android device acting up like that.
Sent from my air conditioner unit running CyanogenMod
I left it charging from 5am to now and it hasn't charged a thing because when I disconnected it and tried to turn it on it turned off after 7 minutes of the Kindle Fire logo. I also noticed that the reflection animation on the logo moves faster than it usually does. It just stays there. I'm guessing my only option would be a factory cable of some sort. No matter how many 20 second power button thing I use, it just stays stuck on the logo, as if something had damaged the firmware somewhere, but how? I will try to charge it once more for a while and see.
EDIT : I made my own "factory cable" and got it to fastboot. Now what can I do to restore it???
Hopeless???
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
{
"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"
}
Crossvxm said:
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
View attachment 2012991
View attachment 2012994
Click to expand...
Click to collapse
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
seokhun said:
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
Click to expand...
Click to collapse
I tried and the System Recovery Tool does not detect the device. It stays at "waiting for device"
One step forward and two steps back
Okay each time I advance, I am stuck with a new obstacle. I got ADB working (can use its commands) but my device isn't detected when I use the command "adb devices." As mentioned before, in Device Manager > Other Devices, Kindle appears as Tate-PVT-08, updating that "driver" is no use, and here I am Kindle-less once again. This is like a nightmare. Had I caused this issue by flashing a rom, or second bootloader, I'd probably give up and say "oh well I read the warnings, went along and I messed it up." But the case is that I did nothing to cause this, it only ran out of battery which happened once before and that time there were no issues starting up. I've searched left and right, high and low but cant find a way to now get this thing detected so I can see what I can do next. Can anyone please give me a list of what to do to get out of this Kindle Fire logo?
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
dugoy13 said:
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
http://translate.google.com/translate?hl=en&sl=ja&u=http://ameblo.jp/conpe/entry-11437514328.html&prev=/search%3Fq%3DTate-PVT-08%26biw%3D1366%26bih%3D673
Is there any specific place/thread with the drivers to the fastboot?
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Possibly Solved
Crossvxm said:
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
Is there any specific place/thread with the drivers to the fastboot?
Click to expand...
Click to collapse
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
CVanB said:
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
Click to expand...
Click to collapse
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
An other option
Crossvxm said:
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
Click to expand...
Click to collapse
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
CVanB said:
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
Click to expand...
Click to collapse
It updated randomly from 7.3.1 to 7.4.1 on May 30th (aprox 5 days ago) that same day I rooted it after it erased my root with the same guide I used for 7.3.1 that was based on 7.4.1. It worked perfectly, but around that time I never let the battery die during those few days. In record, I've only let the battery die once before, this time makes it 2 times total. The cable I made is from a Samsung, I made it using instructions on making it for the Kindle Fire HD 7 specifically, although as I've heard, you may be right. But when I research that "device" (Tate-PVT-08) on google, the Kindle Fire pops up in search results, but none are really helpful. Example, the bottom of this thread I'm posting below, people have similar issues and the "Tate" thing:
http://forum.xda-developers.com/showthread.php?t=1930656
Same problem
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
dugoy13 said:
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari said:
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
Click to expand...
Click to collapse
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
DroidIt! said:
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
Click to expand...
Click to collapse
Yeah I tried that and even my own little invention. But I give up. I'm just scrapping the whole project. Its useless, I'll just have to get me a Nexus 7, I don't want to get stuck with another brick. Amazon is pretty ridiculous. Their system is unstable, their device is crap. I have read about problems like this on these things everywhere. Whether its the charging refusal, 0% battery, not starting up, not having Google Play, root headaches and nearly impossible restore scheme, these things are well worth their cheap price.
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
stunts513 said:
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for trying. But if you'd see what I did to the poor thing out of frustration you'd call me nuts. Its really not coming back now...
So I woke up this morning (after going to bed listening to audiobooks on sleep mode) to find my brand new flex would not power on, did not respond to charging, and I even tried to use paper clips on the two small holes in case it was a soft reset ability.
I had to leave on a business trip for a few hours, but before I left I USBd to the laptop, and it found about twelve drive partitions all asking me to format. My questions are numerous, but primarily I want to beg slash ask ;
1. Any advice on what to do?
2. Were those drives all related to the efs partitions in another thread?
hubrisnxs said:
So I woke up this morning (after going to bed listening to audiobooks on sleep mode) to find my brand new flex would not power on, did not respond to charging, and I even tried to use paper clips on the two small holes in case it was a soft reset ability.
I had to leave on a business trip for a few hours, but before I left I USBd to the laptop, and it found about twelve drive partitions all asking me to format. My questions are numerous, but primarily I want to beg slash ask ;
1. Any advice on what to do?
2. Were those drives all related to the efs partitions in another thread?
Click to expand...
Click to collapse
What's the device listed in device manager? Sounds like your phone is hosed...Partition tables got messed up.
You might be able to restore it in Linux using dd. Can you get into download mode?
return it; if its brand new, dont mess with it, just get it replaced..
EDIT: I see you rooted it; what exact method/steps did you do?
I hosed my G2 a month ago. Tried 3 or 4 ways to bring it back but nothing helped. Lesson learned to back up EFS on laptop and phone before anything. I had mine swapped out but took a few days. Good luck.
Sent from my LG-D959 using Tapatalk
AndroidUser00110001 said:
What's the device listed in device manager? Sounds like your phone is hosed...Partition tables got messed up.
You might be able to restore it in Linux using dd. Can you get into download mode?
Click to expand...
Click to collapse
Have exact problem...I can get in download mode but dont know what to do from there. I tried adb and fastboot commands but it cant find device. Anyway to get it into fastboot mode or how do I use download mode so it will boot again. If powered on it tries to boot like it is updating (the blue line under android) then he falls over dead with the triangle. If I could get it to connect to my pc via usb I can do the fastboot flash of the .img files. Thanks in advance
mjcintexas said:
Have exact problem...I can get in download mode but dont know what to do from there. I tried adb and fastboot commands but it cant find device. Anyway to get it into fastboot mode or how do I use download mode so it will boot again. If powered on it tries to boot like it is updating (the blue line under android) then he falls over dead with the triangle. If I could get it to connect to my pc via usb I can do the fastboot flash of the .img files. Thanks in advance
Click to expand...
Click to collapse
Check here:
Code:
http://forum.xda-developers.com/showthread.php?t=2644083&page=10
We already tried some of the ideas of the Ubuntu VM dd commands as well as some other stuff.
If someone can continue this work to get G Flex into download or fastboot mode like others did LG G2, than share there or here...
I'll be more then happy...
cheers m8s
Triad79 said:
Check here:
Code:
http://forum.xda-developers.com/showthread.php?t=2644083&page=10
We already tried some of the ideas of the Ubuntu VM dd commands as well as some other stuff.
If someone can continue this work to get G Flex into download or fastboot mode like others did LG G2, than share there or here...
I'll be more then happy...
cheers m8s
Click to expand...
Click to collapse
I can get in download mode but dont know what to do from there. My biggest problem is trying to get my computer to talk to the phone via usb.