[Q] N7000 not recognized by windows. - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hello all,
My mother has a GT-N7000 running complete stock.
It updated something according to ehr saying and afterwards it rebooted.
After the reboot it rebooted again and now its bootlooping, it shows samsung and plays the sound.
The bleu glaze comes up and the the device reboots.
I cant get into recovery with vol up+home+power button combo.
It boots to it and it shows the droid with the sort of cubic icon spinning in its belly and after 3 sec the device reboots.
I cant do a factory reset there so i read about Odin and reflash stock image.
I downloaded the proper file and Odin 3.0.9 and installed samsung drivers.
I dont have Kies installed as i read it could give problems.
The device does go i ndownlaod mode but my PC running w7 ultimate 64bit doesnt recognize the device.
I tried 3 different USB ports from the Mobo, and i tried a couple of diferent USB cables.
One of the cables is original Samung U2 cable.
Everyt time i connect the device winodws shows the message: the USB device isnt recognized.
Odin doesnt register anything so i cant flash a thing with it to restore.
Does this mean the device is bricked?
Does the N7000 has some sort of unbrick JTAG mode or something or would linux help to rewrite all partitions?
Thx for any tips.
With best ergards,
Mister_mini
Edit: thinking back it could be possible USB debuuging has been turned on but im not sure on this part.

Related

Any Other Way To Bring My Phone Back To Life

My SGS isn't bricked. But lately after I flashed a deodexed 2.3.3 ROM, I have a hard time connecting my USB (USB not recognized). This afternoon, my phone jammed and won't boot (Stuck in Samsung Galaxy S I9000 Screen). I can't enter the recovery mode either for no reason (used to be able to).
Now I can't flash a stock ROM because my USB isn't recognized and recovery mode is unaccessible too. Trying to install the drivers for the USB now. Anyway as it's installing, any other ways to bring my phone back?
Flash a rom through odin. You could try darky's 9.2 ressurection edition.
The problem now is I could not flash with Odin because my USB isn't working
smiles.smiley said:
My SGS isn't bricked. But lately after I flashed a deodexed 2.3.3 ROM, I have a hard time connecting my USB (USB not recognized). This afternoon, my phone jammed and won't boot (Stuck in Samsung Galaxy S I9000 Screen). I can't enter the recovery mode either for no reason (used to be able to).
Now I can't flash a stock ROM because my USB isn't recognized and recovery mode is unaccessible too. Trying to install the drivers for the USB now. Anyway as it's installing, any other ways to bring my phone back?
Click to expand...
Click to collapse
seriously try using other computer or laptop.. install the required drivers on your friends computer and then try to flash a different rom via odin
tried that. on different comp. same problem. USB not recognized with the drivers installed
I guess this is the problem. When I can't boot my phone, I did a backup restore. Maybe something is messed up and drivers don't recognize my phone as Samsung Galaxy S anymore. Anyway to force it to recognize?
http://www.nirsoft.net/utils/usb_devices_view.html
REMOVE USB DEVICES .
USB connection must be a motherboard connector .
jje
I'm sorry for being a noob. I've downloaded USBDeview. I should remove USB devices and? What do i do after that?
My USB device is Not Recognized. will it show on USBDeview?
Shows old usb drivers delete the lot on that port .
jje
Deleted everything. Plugged in my SGS in Downloading Mode. Still don't get anything.
smiles.smiley said:
Deleted everything. Plugged in my SGS in Downloading Mode. Still don't get anything.
Click to expand...
Click to collapse
if you can go into download mode then you surely can get it flashed with odin ..
try downloading the drivers again and then installing again and then try again....
... if everything fails then you should send it to the service center
Try unplugging and plugging the usb repeatedly. I've had this happen before, and I was able to get the phone recognised by doing this.

[Q] Galaxy S soft brick(?) + USB failure(?) problem

Hi,
I was using F1 V6 ROM on JVK for some time (flashed it with no problems using Odin and Clockwork). After some time, it started to crash more often. I triend V7 but it was even worse so I got back to V6. The only problem was often restarts and sometimes slow operation.
Yesterday I decided to switch to Cyanogen to give it a try. I did it without flashing from scratch. I just used Cyanogen 7.1 installation through Clockwork. It seemed OK untill I tried to connect my phone to PC via USB. I couldn't get any response from PC (not even a sound indicating that something was connected to USB) or Phone (no mount USB screen).
So I was able to charge my phone through USB but not to connect it to PC (tried 2 PCs, different cables, different ports). It doesn't seem like driver problem (no sign of connecting phone to PC, nothing).
I thought that it might be some problem with Cyanogen ROM. So I tried to go back to F1 V6 (wipe) through Clockwork. After doing it, I got boot loop but still showing the logo of Cyanogen (not SGSII from F1). Having no USB connection and being unable to start the phone, I tried to do recovery (I had a backup of F1 V6 from the moment before installing Cyanogen. That didn't go well either. The process stopped and left me with Samsung Galaxy S logo (no boot loop - just hanging there). I cant get into recovery mode anymore. I can only get to download mode.
So the status right now is:
Download mode - OK
USB - can't get phone to connect with PC (no signs of connection so probably not a driver problem but maybe? I tried reinstalling kies, drivers, running Odin, no sign of connected phone, USBDeview shows no Samsung or Kies or Android drivers in my system right now).
Hanging on the Samsung Galaxy S screen.
Did anyone had similar situation?
What do you advice? Any idea on a atest checking if USB hardware is fine?
Was it possible to break USB hardware or driver in phone by installing Cyanogen 7.1 on F1 V6 SGS2?
Any help would be appreciated.
Thanks
kaminkac said:
Hi,
I was using F1 V6 ROM on JVK for some time (flashed it with no problems using Odin and Clockwork). After some time, it started to crash more often. I triend V7 but it was even worse so I got back to V6. The only problem was often restarts and sometimes slow operation.
Yesterday I decided to switch to Cyanogen to give it a try. I did it without flashing from scratch. I just used Cyanogen 7.1 installation through Clockwork. It seemed OK untill I tried to connect my phone to PC via USB. I couldn't get any response from PC (not even a sound indicating that something was connected to USB) or Phone (no mount USB screen).
So I was able to charge my phone through USB but not to connect it to PC (tried 2 PCs, different cables, different ports). It doesn't seem like driver problem (no sign of connecting phone to PC, nothing).
I thought that it might be some problem with Cyanogen ROM. So I tried to go back to F1 V6 (wipe) through Clockwork. After doing it, I got boot loop but still showing the logo of Cyanogen (not SGSII from F1). Having no USB connection and being unable to start the phone, I tried to do recovery (I had a backup of F1 V6 from the moment before installing Cyanogen. That didn't go well either. The process stopped and left me with Samsung Galaxy S logo (no boot loop - just hanging there). I cant get into recovery mode anymore. I can only get to download mode.
So the status right now is:
Download mode - OK
USB - can't get phone to connect with PC (no signs of connection so probably not a driver problem but maybe? I tried reinstalling kies, drivers, running Odin, no sign of connected phone, USBDeview shows no Samsung or Kies or Android drivers in my system right now).
Hanging on the Samsung Galaxy S screen.
Did anyone had similar situation?
What do you advice? Any idea on a atest checking if USB hardware is fine?
Was it possible to break USB hardware or driver in phone by installing Cyanogen 7.1 on F1 V6 SGS2?
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Cyanogen uses a different file system, so to get it back to a Sammy ROM you need to flash it with Odin. and cyanogen doesn't use the Sammy driver for connecting to the PC. download nexus s drivers from the Android SDK and install it.
Sent from my GT-I9000 using xda premium
OK, so how do I install these drivers when my PC can't see that I have my phone connected to USB port? There is no driver error. After connection nothing happens.
Is there a way to install these drivers on Windows 7 without actually having sgs listed on device list?
any help with that?
kaminkac said:
OK, so how do I install these drivers when my PC can't see that I have my phone connected to USB port? There is no driver error. After connection nothing happens.
Is there a way to install these drivers on Windows 7 without actually having sgs listed on device list?
any help with that?
Click to expand...
Click to collapse
Get your phone into download mode (volume down + home + power) and see if windows lists it then.
Sent from my GT-I9000 using xda premium
Thanks but it does not.
No sign of connecting phone to PC.
any ideas?
kaminkac said:
Thanks but it does not.
No sign of connecting phone to PC.
any ideas?
Click to expand...
Click to collapse
Reflash the CM7 Rom, and see if it shows up in device manager. Do you get an option on CM to share disc drives with usb plugged to the computer?
Oh, and if you have KIES installed, try remove it and remove the driver pack too (i know it affects ODIN's ability to see the phone).
Solved
Thanks for help.
I got different cable (third) and different (third) PC and somehow it worked - PC noticed connection of SGS in download mode and than it was easy.
I installed clean JVT, than CF-Root and CM 7.1 + google apps.
It seems to work fine for now.
Please close this thread.
Cheers

Galaxy TAB P1000 NOT Detecting in ODIN

Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i switchd the damn thing off completely
I have tried to go in download mode to flash but odin doesnt recognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS- i im not worried about my data , and i have not backed up the rom etc before doing any of these)
Try to reinstall or install a usb driver from samsung
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Yeah, happened to me too, nearly had a sh*t my pants when Odin didn't recognise my Tab.
I would recommend -
charge the Tab fully using wall adapter (4 hrs+)
plug it in with Odin open and using USB cable
don't expect Odin to recognise the Tab immediately
check back after 5 mins or so (I don't know, does Odin refresh?)
I was able to restore my Tab from the PC - ! - Marvin screen.
I don't want to go back there again though!
yea dude.. same here
i kept it on charge for a couple of hours and then tried.. bam it conencts..
Libon
Tab not turning on
HI Guys I have Galaxy 1000 .I was updating it by using kies in between the process my computer shut down and when I am trying to connect my tab again its not turning on .can some one help me please ?
Waiting no charge baterry 2 3 j
Run odin
Connect tab . Wait Long time 20 30min
Tab is. Détect go flashing
Sorry for my english
I m.. French
Envoyé depuis mon GT-P1000
GT P1000 Odin wont detect
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
iamkakers said:
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
Click to expand...
Click to collapse
do u have samsung kies installed in your pc? if does, kill the kies process (Ctrl+Alt+Del). close, and open odin3, put your tab into download mode, and then plug it into usb port. try to change different ports.
i always had this problems.. if all if that didn't work, i'll format my pc
Sent from my GT-P1000
odin3
hi
i also have a gt p1000 and odin3 doesnt detect the tab. i've been trying to root my tab for a while, tried odin and it doesnt detect, tried doomlord and it doesnt even get past the first step. i tried uninstalling kies on my windows 8 laptop and still no luck im not too sure what to do. is there something that i might be doing wrong because i follow all the info thati get from here.
is there another rooting app i can try that doesnt brick my device? and or is there an app that i can get that i am able to use a ps3 controller on my device that does not require a rooted device. please help
thanks
My Galaxy tab also doesn't connect to usb after cache wiped humber os flash
Thanks in advance guys!..
Earlier I was using Cyanogen mode 10 Custom ROM but has few issues like recognize SD card.
later I flashed to Humber OS caused real problem.
It was clock work recovery installed but my tab tab boots stays on screen humber OS.
It goes to recovery mode, and also to some unknown recovery mode.
Either the way not recognized by computer. I tried all options like heimtal an Odin. No help.
Friends any help, would be highly appreciated.
BUMP
Any solution to this given the fact that usb drivers have been installed?
Are you sure it is recognised by the computer before trying Odin or Heimdall?
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
farza(db)astany said:
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
Click to expand...
Click to collapse
reason 1: my phone is samsung and it's detected by ODIN, kies and I transfer files from and to my computer without problems. also tried reinstalling just in case but nothing, so I guess this is not the answer for my problem
reason 2: tried with original cable, but as I didn't use the tablet for a long time I also thought it could be the cable, so I asked a friend of mine if he could lend me one cable, but that didn't work. pity. :/
reason 3: tried 3 different versions of ODIN, and in every version my phone (mentioned above) is detected. shame. :S
reason 4: tried the 3 different USB ports in my laptop. two 2.0 USB ports and one 3.0 USB port, so again I doubt this is the reason of my problem.
extra reason: ~~~ maybe it's the OS version ~~~ // this laptop came with windows 8 preinstalled. nothing. then, I updated to win 8.1. again nothing. now I'm running windows 10 and the same, nothing is detected neither by ODIN nor the computer. also tried in 4 different computers running win xp, win 7 and other with win 8.1.
btw, thank you anyway for your apportation; this may help other people, but unfortunately, it's not my case, so can anybody else join me to think about a new reason and a way to solve it? thank you very much :good: :highfive: :fingers-crossed:
~~~~~~~~~~~~ EDIT ~~~~~~~~~~~~
I have continued researching and found a software. it didn't work for me, but maybe it works for other people.
-first, you have to make sure you have java installed on your computer.
-second, extract the oneclick.rar file on an easy-access directory.
-third, put your tab on download mode (while charging icon when tab is turned off, press power + volume down until a yellow triangle appears).
-fourth, click start unsoft-brick and let the magic begin! 8)
note: if a warning error pops up, trust the software and click on resolution center and follow the instructions of one of the three "alternative ways".
download: https://www.dropbox.com/s/8ix6yygu23a1kjn/OneClick.rar?dl=0
good luck!!
help
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
hi can you plz help me out with the processess you followed to as im suffring the same problum only CWM working and even it shows sd card mount error also not installing any rom via SD card showing error and odin not detecting it nothing happening only CWM and blank screen
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
How did you did it im having the same error???
i did the same thing with my tab exactly like yours plzzzz help me recover it

[Q] Unkown device on bricked phone

Hello, my Samsung Galaxy S GT-i9003 was working fine yesterday, but now it stays stuck on the samsung logo when booting. I'm trying to flash it, the thing is, I can't get my computer to detect my phone, it shows up as an unkown device. I tried a factory reboot etc.. didn't work, and I can't even use it as a mass storage device since it's bricked. I used all the newest drivers, the newest version of kies but it still doesn't work.
I'm on windows 7/64 bit btw.
Thank you in advance.
Are you able to enter into download mode? (hold volume down + home + power)
If not, You can try to make (or buy) a JIG which will force download mode and you can flash a new ROM with Odin
Regards
I can enter in download mode, the thing is, my computer detects my phone as an "unknown device" and it isn't recognised by Odin either, which means I can't flash it.
are you sure the drivers are installed correctly? I recently had problems with the USB cable.. try another one and if possible, other PC....
I installed many times the drivers, using kies or without kies, the result is just the same, maybe it's the cable.
Try to change the cable and the USB port. Last week I tried to update a Motorola Atrix and the same thing happened, unknown device. Then I changed the USB Cable and voila... worked !
Let me know if it works....
Regards
just wondering if you have resolved this yet ? I have same problem tried all usb drivers i can find , 5 different computers , jig , odin still not detect and windows show unknown device detected.
Sent from my Dell Streak using XDA
Guys I had the same problem. After trying many pc, drivers, cables combinations I came to a conclusion that the usb port on the phone itself must be damaged. After taking a close look, I saw some of the gold contacts damaged/missing.. That might be the case with your phone aswell. Look at the pins and if yo usee some visual damage you know what the problem is. Even if you dont see it, it still might be a problem.

Odin stuck on "system.img.ext4" Help please?

Hi All,
I tried to flash my phone from VZW firmware to unlocked firmware and my odin3b has been stuck on system.img.ext4.
I realized I hadn't installed the samsung drivers the first time around. I attempted to restart the phone as it was stuck on system.img.ext4 - following that my phone shows the screen:
"Software Update Failed Your device didn't update successfully. Use the Verizon Software Upgrade Assistant on a computer to repair your device and complete the update."
I'm unable to re-boot or do anything, when I hold power, bixby, volume down it presents me the warning screen before entering download mode. If I press Volume Up or Volume Down - I hit the same warning screen I typed up above. I am able to view the barcodes by pressing the bixby screen...
When I went back to Odin it still showed as "Added" when I plugged in the phone. I attempted the process again but it's still stuck on the same part.
Anybody have any suggestions of what I should attempt? I've been reading but have been unable to see any solutions.
Thanks for reading.
I Havnt played with the note 9 in terms of flashing or rooting as I have the SM-N960W Canadian Snapdragon version and there is no way yet. I've used Odin many times to flash and it can be fussy for a few reasons, I rooted my Galaxy S7 and nexus 5 and a few others. My tips would be....
First Uninstall Samsung driver.
Then Download "usbdeview" on your pc and Uninstall any previous USB connections labeled Android or Samsung or related, as this will allow you to start off as if it's a fresh connection.
Re-Install Samsung USB drivers, then....
Plug in Using stock OEM Samsung Note USB cord and wait for it to connect.
If no luck try a different USB port. USB 2.0 May work if your using USB 3.0 and it isn't.
Try a different version of odin, there are many, also running odin as administrator may help but not necessarily for sure.
If all this fails try on another computer or laptop. Make sure you only select the proper/necessary options in odin.
It sucks when things don't go as planned but that's the risk you take when you don't stay stock & update OTA. The steps I've written for you have fixed any issues I have ever run in to with odin & flashing but if yours was an incomplete flash and disconnected or interrupted mid way you may be stuck with an expensive paperweight I'm sad to say. Try contacting Samsung for proper odin version & odin settings, I wish you the best of luck. I am in no way a mobile phone technician but I've rooted many phones and always made it work. I hope you can too!
Best of luck!
flash back your official firmware to get back access to fone
if none of this works use smartswitch( it will reinstall drivers)
then tey again with odin 13.3 b using u1 firmware
also to get to dl mode power off the fone. if you have access to recovery ( reboot fone with vol down Bixby and power and quicly change to vol up bixy and pwr when you see it reboot)go there and choose shutdown phone. or let battery die and charge it for 10 mins and do while phone is off :
hold vol down and Bixby with one had and with the other plug the usb cable from rhe pc to fone.
The same problem happened with me. I wonder if anyone knows how to solve it?
Sukrus said:
The same problem happened with me. I wonder if anyone knows how to solve it?
Click to expand...
Click to collapse
Try your luck with different odin versions, different cable, different pc, different firmwares
As above first step Samsung USB drivers and Samsung USB cable .

Categories

Resources