Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!
iKaosTony said:
Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!
Click to expand...
Click to collapse
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?
wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.
wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
Thank you for your fast reply.
That is about right. When I go in CWM and try 'install zip' -> 'choose zip from sdcard', I get 2 folders. The first one is called '0/' and the other is called 'clockworkmod/' both of them are empty. So I guess there are no files on my device anymore.
I will try Wugs Toolkit. I will keep you updated.
samersh72 said:
supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?
Click to expand...
Click to collapse
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
Zepius said:
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.
Click to expand...
Click to collapse
I just tried Wugs Toolkit without success.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?
iKaosTony said:
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
I just tried Wugs Toolkit without success.
I just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?
Click to expand...
Click to collapse
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...
19Max87 said:
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...
Click to expand...
Click to collapse
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?
iKaosTony said:
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?
Click to expand...
Click to collapse
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:
19Max87 said:
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:
Click to expand...
Click to collapse
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything
iKaosTony said:
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything
Click to expand...
Click to collapse
Sorry bro, I'm out of ideas... :banghead:
Boot into an Ubuntu live USB. It doesn't require drivers. Just install the adb and fastboot tools from apt-get. There are about 50,000 tutorials on how.
Sent from my Galaxy Nexus
Try an other cable or computer or USB port.. Go to a friend if you must.. Then flash the Factory image via fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app
I have tried using Ubuntu to access my device, but no luck either. When I come to the step where I have to use the command 'lsusb' does not show up. I have tried putting my device in Download mode, Fastboot mode and Recovery mode to see if 'lsusb' will show my device.
The tutorials I followed:
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
http://www.youtube.com/watch?v=3heTSqjWcaY
http://bernaerts.dyndns.org/linux/245-ubuntu-precise-install-android-sdk
Tried 4 different cables, 3 different computers and a friends computer where all the drivers are working with his Galaxy Nexus.
I do not know what I am doing wrong. :crying:
in recovery mode execute "adb push rom.zip /sdcard/", better from Ubuntu so you don't need any driver
Then flash the rom from the recovery
Inviato dal mio Galaxy Nexus con Tapatalk 2
If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro
do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app
beekay201 said:
If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro
Click to expand...
Click to collapse
I am also thinking my USB port is broken...
unmystic said:
do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have CWM. How do I do that?
In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.
stevemw said:
In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.
Click to expand...
Click to collapse
I tried that too, but no luck.
Related
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.
I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.
Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.
BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:
BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.
Situation
My SGH-T989 boots to the cyanogenmod circular animation screen, and stays there. If I hold volume up + volume down, I am able to boot to clockworkmod recovery 6.0.3.1. Some functions in CMR (format /cache, Go Back) lock up CMR and I have to reboot.
My PC doesn't seem to find the USB device using adb devices nor Odin. After searching xda, I bought this USB jig, which allows me to boot to download mode. Still no dice on USB though, doesn't even show up in Device Manager. I have tried both ports and three different cables, at least one of which worked on my Motorola Atrix2.
Background
I was running great using cyanogenmod 9 and clockworkmod recovery 5.0.2.7, which I originally set up using Odin on Windows 7 within VMWare Fusion on my Mac.
Through ROM Manager notifications, I downloaded clockworkmod recovery 6.0.3.1 and cyanogenmod 10.0.0 and later, cyanogenmod 10.1RC1. I upgraded to CMR6 and CM10.0 (not sure which order) successfully, after making a backup using CMR5. I decided to try out CM10.1, and downloaded it using ROM Manager. I made another backup and installed CM10.1. For some reason I decided to go back, and restored that backup.
I have Samsung drivers v1.5.14.0 installed. Here's what Odin looks like. Since I am new, please copy and paste the link below to see it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Goal
Get back to a working phone, with any ROM and any recovery.
Get cyanogenmod 10.0 working with any recovery and make sure I have a good backup.
Try Jedi Mind Trick with TWRP
I really appreciate any help or xda pointers. I honestly searched my butt off before posting, and watched the noob video.
rhoegg said:
Situation
My SGH-T989 boots to the cyanogenmod circular animation screen, and stays there. If I hold volume up + volume down, I am able to boot to clockworkmod recovery 6.0.3.1. Some functions in CMR (format /cache, Go Back) lock up CMR and I have to reboot.
My PC doesn't seem to find the USB device using adb devices nor Odin. After searching xda, I bought this USB jig, which allows me to boot to download mode. Still no dice on USB though, doesn't even show up in Device Manager. I have tried both ports and three different cables, at least one of which worked on my Motorola Atrix2.
Background
I was running great using cyanogenmod 9 and clockworkmod recovery 5.0.2.7, which I originally set up using Odin on Windows 7 within VMWare Fusion on my Mac.
Through ROM Manager notifications, I downloaded clockworkmod recovery 6.0.3.1 and cyanogenmod 10.0.0 and later, cyanogenmod 10.1RC1. I upgraded to CMR6 and CM10.0 (not sure which order) successfully, after making a backup using CMR5. I decided to try out CM10.1, and downloaded it using ROM Manager. I made another backup and installed CM10.1. For some reason I decided to go back, and restored that backup.
I have the Samsung drivers installed. Here's what Odin looks like. Since I am new, please copy and paste the link below to see it.
My Goal
Get back to a working phone, with any ROM and any recovery.
Get cyanogenmod 10.0 working with any recovery and make sure I have a good backup.
Try Jedi Mind Trick with TWRP
I really appreciate any help or xda pointers. I honestly searched my butt off before posting, and watched the noob video.
Click to expand...
Click to collapse
Try downloading a new recovery to your sd card using a sd card reader on your computer or monitor if you have one. If not try one click unbrick. kies ( emergency firmware) , or reinstalling drivers. As long as you have a boot screen usually your phone can be fixed so there is hope.
You've over done this a bit I think, no purchases should be necessary, just boot into recovery, mount your SD card or internal storage, copy over a ROM of your choice (check t989 development section), copy it to your phone, and another recommendation would be to use the infamous wipe scripts, but always make sure to flash a new ROM after using any wipe function (except for cache) otherwise phone won't have anything to boot from. Basically, just format and reflash
Sent from my SGH-T989 using Tapatalk 2
maybe CMR is broken?
nashy10 said:
You've over done this a bit I think, no purchases should be necessary, just boot into recovery, mount your SD card or internal storage, copy over a ROM of your choice (check t989 development section), copy it to your phone, and another recommendation would be to use the infamous wipe scripts, but always make sure to flash a new ROM after using any wipe function (except for cache) otherwise phone won't have anything to boot from. Basically, just format and reflash
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your quick answer... I guess my problem is with clockworkmod recovery. Your reply reminded me that I can just put the SD into my other phone to put ROMs on it, which I did. I copied both INFAMOUS scripts to the SD and tried to install them using CMR6.0.3.1, but the phone seems to freeze when I try to install each of them, then the phone reboots after a short while (around 2-3 minutes).
Is it possible to install a different recovery without being able to see the phone in Odin?
rhoegg said:
Thanks for your quick answer... I guess my problem is with clockworkmod recovery. Your reply reminded me that I can just put the SD into my other phone to put ROMs on it, which I did. I copied both INFAMOUS scripts to the SD and tried to install them using CMR6.0.3.1, but the phone seems to freeze when I try to install each of them, then the phone reboots after a short while (around 2-3 minutes).
Is it possible to install a different recovery without being able to see the phone in Odin?
Click to expand...
Click to collapse
If your phone can be recognized on the computer for at least 3 minutes than you can use different programs to install it straight to your phone.
Sent from my SGH-T989 using Tapatalk 2
Trying these suggestions...
richardlibeau said:
Try downloading a new recovery to your sd card using a sd card reader on your computer or monitor if you have one. If not try one click unbrick. kies ( emergency firmware) , or reinstalling drivers. As long as you have a boot screen usually your phone can be fixed so there is hope.
Click to expand...
Click to collapse
Thanks I am working my way through these suggestions; so far, clockworkmod recovery 6.0.3.1 doesn't seem to be able to flash anything without freezing and rebooting after 2-3 minutes. I will update once I try all the options you listed. I am on a fresh install of the drivers (I think) and the phone doesn't appear under USB in Device Manager, so I think that option is out
Will update once I get through a recovery update, one click, and kies. Thanks again.
My problem might be USB...
richardlibeau said:
Try downloading a new recovery to your sd card using a sd card reader on your computer or monitor if you have one. If not try one click unbrick. kies ( emergency firmware) , or reinstalling drivers. As long as you have a boot screen usually your phone can be fixed so there is hope.
Click to expand...
Click to collapse
I tried all of these except one click unbrick, because what I read tells me Odin has to be able to see the device in order for one-click-unbrick to work.
First I tried booting to CMR 6.0.3.1 and installing recovery-clockwork-touch-5.8.1.3-hercules.zip. One line printed saying it was flashing, the phone sat there a short while then rebooted.
Neither Kies, nor Odin can see my device when I connect it either booted to CMR, or in download mode via the USB Jig. I noticed that when in Download Mode, I see "Factory Mode" at the top in red, not "Odin Mode".
I uninstalled the USB drivers from my PC (I was on 1.5.20.0) and installed the ones I got from the Samsung site (1.5.14.0). Same response, nothing under ID:COM in Odin.
I suspected a bad USB cable or port, so I tested my Motorola Atrix2 with the exact same cable and port. It works.
Maybe I have a bad USB connection on my phone? I think it still charges the battery as of this morning.... how could I test this idea? Or, how else can I install a new recovery?
rhoegg said:
I tried all of these except one click unbrick, because what I read tells me Odin has to be able to see the device in order for one-click-unbrick to work.
First I tried booting to CMR 6.0.3.1 and installing recovery-clockwork-touch-5.8.1.3-hercules.zip. One line printed saying it was flashing, the phone sat there a short while then rebooted.
Neither Kies, nor Odin can see my device when I connect it either booted to CMR, or in download mode via the USB Jig. I noticed that when in Download Mode, I see "Factory Mode" at the top in red, not "Odin Mode".
I uninstalled the USB drivers from my PC (I was on 1.5.20.0) and installed the ones I got from the Samsung site (1.5.14.0). Same response, nothing under ID:COM in Odin.
I suspected a bad USB cable or port, so I tested my Motorola Atrix2 with the exact same cable and port. It works.
Maybe I have a bad USB connection on my phone? I think it still charges the battery as of this morning.... how could I test this idea? Or, how else can I install a new recovery?
Click to expand...
Click to collapse
what exactly does your computer say when your phone is connected? USB, MT
P DEVICE, ADB, QHS_USB_DOWNLOAD MODE, UNRECOGNIZED DEVICE, ETC?
richardlibeau said:
what exactly does your computer say when your phone is connected? USB, MT
P DEVICE, ADB, QHS_USB_DOWNLOAD MODE, UNRECOGNIZED DEVICE, ETC?
Click to expand...
Click to collapse
Nothing, it behaves like there is nothing connected. I have reinstalled the drivers twice, and Kies reinstalled them again I think. This is the same whether the phone is booted with the USB Jig to "Factory Mode" or ClockworkMod Recovery.
Dumb question... but did you restart your pc when you installed the drivers?
Sent from Evils Cradle of Filth T999
alloycowboy said:
Dumb question... but did you restart your pc when you installed the drivers?
Sent from Evils Cradle of Filth T999
Click to expand...
Click to collapse
No I didn't
I just did, though, and I got the same results. It's like nothing is plugged in at all.
rhoegg said:
No I didn't
I just did, though, and I got the same results. It's like nothing is plugged in at all.
Click to expand...
Click to collapse
Can you try installing over the system within the CWM you currently have now, or will it just freeze on you? If you have a SD card, you could put the CM9 ROM back on there, and try reflashing to see if you can at least get into your phone...
smokinjoe2122 said:
Can you try installing over the system within the CWM you currently have now, or will it just freeze on you? If you have a SD card, you could put the CM9 ROM back on there, and try reflashing to see if you can at least get into your phone...
Click to expand...
Click to collapse
I have tried several versions of CM that I already had on my external SD (9.0.0, 9.1.0, 10.0.0) and now it boots to a black screen rather than the infinite CM10 boot animation. I think that's due to a successful format /system and format /data I did yesterday.
When I try to install any of these zips, it prints a single line "Installing <whatever>..." then sits there for several minutes, then reboots.
rhoegg said:
I have tried several versions of CM that I already had on my external SD (9.0.0, 9.1.0, 10.0.0) and now it boots to a black screen rather than the infinite CM10 boot animation. I think that's due to a successful format /system and format /data I did yesterday.
When I try to install any of these zips, it prints a single line "Installing <whatever>..." then sits there for several minutes, then reboots.
Click to expand...
Click to collapse
Hmmm. I do think ODIN may be the only way to go. I know you said you can't get your PC to see your phone, have you tried a different computer? Just to make sure it's not a comm problem with your particular computer or driver corruption?
[Q] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?
THREAD CLOSED:Final update made
Solution: JTAG. I have updated the main page for anyone who comes across this in their troubles. Try the advice in this thread. It's good advice. I just couldn't be helped. These guys are smart as ****. Take their advice. Good luck, and good night.
Original post
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
Recap
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
What I tried
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 2 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Info
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Conclusion:
Windows GS3Toolkit fails to see it
Windows Kies fails to see it
Windows 7 OS fails to recognize it
Windows adb fails to see it
Linux adb fails to see it
Mac OS X heimdall fails to see it
Mac OS X adb fails to see it
My conclusion: For some reason, my phone is reporting itself incorrectly, with a potentially damaged usb port on the phone.
Solution A: Try to JTAG myself. (NOT RECOMMENDED) Pros: Learning. Cons: Too much to buy and ugh. F that noise.
Solution B: (Chosen path) Send to someone to JTAG it for me. Pros: Fast, easy (for me) Cons: $60
Solution C: Sell the phone. Pros: Potentially less cost (through loss) Cons: Time to sell and buy, jockey for prices, potentially lose my ass.
Solution D: Do nothing. Pros: No more loss, no more work, maybe something will come through. Cons: bricked phone
Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
I'll talk with you no doubt.
Kilo__ said:
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
I'll talk with you no doubt.
Click to expand...
Click to collapse
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
Well that's the thing. It does not show up in devices. ADB will not recognize the device. I'm fairly knowledgeable with using adb and I have 3 versions on my computer. None of the three (adb.exe adb-toolkit.exe or SOCadb.exe) will view it.
{
"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"
}
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
Kilo__ said:
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
Click to expand...
Click to collapse
Tried it. Unrecognized still. I think I may just be f***ed
Kilo__ said:
Tried it. Unrecognized still. I think I may just be f***ed
Click to expand...
Click to collapse
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
No, I don't get any options. "Teamwin" for about 30 seconds. Then black... 5 seconds. Then vibrate twice and then reboot. I think I wiped system, and then TWRP borked as you say. I have used many cords for this.
And yes, the phone goes into Odin mode, but the Odin program doesn't pick it up, neither will ADB and windows says "USB not recognized"
DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
I just wanted to say thank you all for the help on this situation. Nothing has turned up with the phone but I'm 99% sure this isn't a driver thing now. I'm gonna face the music and try to find either a Jtag kit somewhere or possibly someone to buy it from me. If anyone has any ideas on this and wants to weigh in, I'll of course attempt their solution, but I am going to try other solutions now. Once the device has been either sold or fixed, I will close this thread and edit my first thread with the solution for others to see. Again, each and every one of you, thank you. Hopefully, I can return the favor some day
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
mrhaley30705 said:
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
Click to expand...
Click to collapse
Yea, yea it is but I don't know what else to try. I've browsed forum after forum after forum. Of all the people that have received help this problem (Odin is the only choice and isn't recognized), a total of 0 have had something work for them and most threads die unsuccessful. I partially blame the OPs for their lack of through information and replies, but also to the fact that I believe this is just a case of Bad Luck Brian. To have me mess up with the ROM, TWRP take a nose dive, and ODIN play enigma all at the same time seems like a very unlucky scenario.
It has been 8 days now that I've had no phone. Now, I'm not an important person, but I'd at least like to have the phone number I'm paying for, be usable to me. I am really grateful for all of the help and I don't feel slighted or let down in any way, it's just plain and simple that I want a working phone back. If something comes up here before I remedy the situation myself, I'll be sure to let y'all know how it goes, but I'm at the point where I want a usable phone. Again, thank you all for help you have provided and the time you've put into my issue.
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
mrhaley30705 said:
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
Click to expand...
Click to collapse
Ah, yes. Actually, one of my posts (probably the main one) I bring up 2 laptops and 1 desktop being used, one of the laptops was his. He has an S3 (he's actually the one that pushed me towards getting one). It was the first one with this problem, as I was at his house when it all happened.
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
mrhaley30705 said:
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
Click to expand...
Click to collapse
I haven't. Is there an easy guide on how to do this or how to get adb on linux?
Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"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"
}
Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it
I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Tried it on a full battery, still no luck.
tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here
Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.
Have you tried adb/fastboot?
Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.
DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4
The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.
Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?
{
"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"
}
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.
MaRkuS_538 said:
Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?View attachment 3659595
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.
Click to expand...
Click to collapse
I have that same line running down mine, looks like twrp.
hope someone chimes in...
It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.
r3t3ch said:
It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.
Click to expand...
Click to collapse
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...
You have a driver problem. If it gets listed under anything, uninstall the drivers for it from device manager. It should show up as something like "jem-pvt-prod-04" under other devices with a yellow triangle. You can then try to install its driver as adb composite interface or try using the driver from this thread. If you don't see "Android Composite ADB Interface" when you try manually installing the driver, reinstall adb/fastboot.
MaRkuS_538 said:
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...
Click to expand...
Click to collapse
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry
sullytrny said:
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry
Click to expand...
Click to collapse
Hey hope all went well with the storm for you, now can u do a write up on how to fix the issue please.
Yeah, hopefully. But it would be very nice to tell what you've done exactly (especially driver setup)
Gesendet von meinem Nexus 6P mit Tapatalk
Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?
MaRkuS_538 said:
Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?
Click to expand...
Click to collapse
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs
It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk
monster1612 said:
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Can you tell me how you did this? I disabled driver signature enforcement (running windows 10), but I have no clue where to go from here.
---------- Post added at 02:30 PM ---------- Previous post was at 02:20 PM ----------
MaRkuS_538 said:
It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Can you by chance explain what you did? I've got mine stuck at that screen (no recovery or anything) and can't go anywhere.
I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk
MaRkuS_538 said:
I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?
kslonkey said:
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?
Click to expand...
Click to collapse
YES, i can help.
you need EITHER:
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA
OR
Minimal ADB and Fastboot (a few megs) from here @ X-DA
launch the app, and when it says "waiting on device" plug the usb cable into the ALREADY OFF tablet.
this is the only way i could get fastboot to work (and be "installed" in windows) on my 32 gig model. i have the "red screen of death" and these 2 apps are the only ones i could get to work. i WANT to try "kindle fire first aid" but ALL the links here for that app are DEAD.