When i plug my note 2 into the computer running vista its not recognised and contantly asks for a CDC communication interface driver, after searching online it all seems to trace back to a S2 i9100...after my mistake of flashing a s2 rom onto my note 2 i cannot seem to get it back right...any advice would be welcome.
I have flashed new original note 2 firmware loads of time and that aint fixing the issue..cannot downgrade due to the mk4 bootloader
Phone works fine once running except seems to go into deep sleep when left and needs a battery removal
pearlpassat said:
When i plug my note 2 into the computer running vista its not recognised and contantly asks for a CDC communication interface driver, after searching online it all seems to trace back to a S2 i9100...after my mistake of flashing a s2 rom onto my note 2 i cannot seem to get it back right...any advice would be welcome.
I have flashed new original note 2 firmware loads of time and that aint fixing the issue..cannot downgrade due to the mk4 bootloader
Phone works fine once running except seems to go into deep sleep when left and needs a battery removal
Click to expand...
Click to collapse
Did you find a solution? i've exactly the same issue
Related
Hello - I urgently need help with my Samsung Galaxy Tab.
I flashed a wrong PIT/PDA & what happened is:
- my Galaxy Tab does not reboot at all
- the flashlight in the back suddenly switched ON automatically
No matter how long I press the Power Button, the device switches off just for one second, and then the flashlight switches ON again - but no reboot.
I cannot get into download mode / when I try to use commands with Odin, it only says: error: device not found.
Odin does show my device ([COM:4]), it appears as: Added // only the download mode does not work!
When I tried to start SuperOneClick, trying to Unroot, it is stuck with: "Waiting for device"
Weirdly, though, my netbook does install the drivers automatically when I plug it in. Which means, my netbook can "read" the device.
Does anyone here know how I could make the extreme Hard Reset, without having to reboot?
--------------------------
If you think this post should rather go to the Developers section, please feel free to move it // I am thankful for any help
Have you tried connecting to it with ADB to see if you can reach it at this level (apart from with SuperOneClick)? Try installing the Droid Explorer application on your Windows PC and see if it will recognise your Tab. If it will you should be able to initiate a reset from the Droid Explorer UI. If it won't I would suggest that you are hard bricked and it will have to visit Samsung. Good luck!
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
QueenAmy said:
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
Click to expand...
Click to collapse
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
rotohammer said:
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
Click to expand...
Click to collapse
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
bdl1969 said:
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
Click to expand...
Click to collapse
lol, I'll get my cheap Chinese Tab cables this week and hack one up to test.
My guess is that Odin will only see the Tab when it is in download mode. Id try flashing it in that state and find out for sure. It sure cant hurt.
You went to your retailer?I have exactly the same problem!!
First of all - THANK YOU for having started this discussion.
Yes, I went to the retailer. My Galaxy Tab is with Samsung Technical Support now; will keep you posted.
To answer some earlier questions, yes ODIN did recognize my Tab; but the screen on the Tab remained totally black. Only this strange "flash" light on the back kept glowing.
rotohammer, if you really get to test what you mentioned before, I'd be interested to hear what happened - but, personally I would not recommend it, unless you are sure you want to risk completely ruining your dear Tab.
studio54 said:
You went to your retailer?I have exactly the same problem!!
Click to expand...
Click to collapse
I did ... and less than 2 weeks later ..
Update:
13-Jan-2011
Today noon I got a call from my retailer my Galaxy Tab was ready to be picked up & I was really lucky: my retailer said the repair would normally cost EUR 650.-
.. as I had damaged the whole mainboard ..
but as the Tab was less than 1 month old, they were so kind to do it w/in my warranty - so I did not have to pay for it.
I'm very relieved, as you can imagine.
Got my Galaxy Tab back with a brand-new mainboard, everything is working well &
I sure learned my lesson.
I will not flash the Galaxy Tab again.
Only because Galaxy Tab and Galaxy i9000 are both on Froyo, it does NOT mean that you can flash the same software!
I wanted to apply the 3 button combo fix on my Galaxy Tab but apparently it does not work!
Bricked mine as well, but mine is a weird case
I bring up the weirdest case of bricking so far, i was on an official Arabic (P1000JPJK2)Firmware, and i noticed a new Arabic release on SamsungFirmware.com (P1000JPJM3) i downloaded it and downloaded the .pit file, Started Odin v1.7 and unchecked repartition, selected the PDA and the pit and started the processes, odin finished and Reseted the device and give me the green light with the word PASS, however, the my p1000 decided to reboot into download mode automatically, so i rebooted the device manually and got stock in the Samsung Logo and keeps looping. so i decided to go back to my previous Rom but it will always fail and i would have to reboot my tab and it will show the good ol' Phon-PC logos, however, odin would see it and would flash anything i want. i tried flashing various versions of rom's but they would all fail... i tried repartition checked and unchecked and nothing worked, so lastly i decided to flash the .pit file alone and that worked and got me back to where i was stuck in the Samsung logo loop and no ROM would be flashed through Odin BUT the (P1000JPJM3) but it still will not boot! and funny enough i took it to sammy's repair shop and they told me to come pick it up in a few hours but they told me that they failed to repair it and they would need to keep it till tomorrow, but they guy was not that optimistic about getting it repaired and to make things worse i couldn't get unrooted so there is a good chance that there will be no warranty... does this mean that i bricked it for good? please help me.
Hey
I Bought a Note 3. But I have some problems with it.
At the first it keeps restarting so I put a custom s6 rom on it. After that problem is still there.
Then I fully wiped the note 3 and now the phone isn't recognized at windows.
Please help me.
Fanatiek said:
Hey
I Bought a Note 3. But I have some problems with it.
At the first it keeps restarting so I put a custom s6 rom on it. After that problem is still there.
Then I fully wiped the note 3 and now the phone isn't recognized at windows.
Please help me.
Click to expand...
Click to collapse
Windows will not recognize the phone if you wiped (deleted) the OS coz. Download the latest firmware of your device via Sammobile.com and flash it via ODIN. Done.
Now it keeps rebooting, got the stock ROM on it.
Sounds like it may be a hardware problem. If the power button flaky?
So I am trying to install a custom recovery for my i9505, but Odin does not recognize the phone which was put in download mode before. Please help me! Here are some details:
I got proper USB Drivers installed (1.5.55.0), tried even with Kies/smart switch installed
Using Odin 3.09-3.10.7
Different usb-cables
Completly UNROOTED i9505 with STOCK recovery and 80% charge
In device manager the phone does not appear properly. It has two listings:
1. Other Devices\ MSM8960
2. USB-Controller \ Unknown USB Device (Error trying to get device description //translated from German
Windows 10 Home 64bit
Personally I think it should be a problem with Windows 10 but I am not sure...
To the phone itself because it could be hardware-wise broken:
The phone itself is a completly meltdown. Before I tried repairing it the speaker were broken (no sound). The phone ran an official lollipop rom. I think 5.0.1. Then I thought I could just hit a software update to fix maybe some problems. I updated to I9505XXUHOJ2 [5.0.1] DBT
And now the software experience is completly broken. The phone gets a lot of soft-reboots, the booting takes like 5 minutes and yes the phone is factory reseted. BUT HEY THE SPEAKER WORK AGAIN?!
I really dont know what is happening but there can be only 2 solutions:
1. Re-Install stock software via odin and then switch to cm and hope it works
2. or throw this piece of sh*t away because the cr*ppy hardware is brokanus sarus rekt
or is there any other solution? Tell me
Otherwise I would also ask if there is any solution to install cm12.1 or a custom recovery without root and odin access. (thinking of sideloading in recovery or something like this)
Thanks for reading and replying. I am gratefull for everything I hope the best ^.^
Try running Odin in compatibility mode, set for Windows 7.
fabsau said:
So I am trying to install a custom recovery for my i9505, but Odin does not recognize the phone which was put in download mode before. Please help me! Here are some details:
I got proper USB Drivers installed (1.5.55.0), tried even with Kies/smart switch installed
Using Odin 3.09-3.10.7
Different usb-cables
Completly UNROOTED i9505 with STOCK recovery and 80% charge
In device manager the phone does not appear properly. It has two listings:
1. Other Devices\ MSM8960
2. USB-Controller \ Unknown USB Device (Error trying to get device description //translated from German
Windows 10 Home 64bit
Personally I think it should be a problem with Windows 10 but I am not sure...
To the phone itself because it could be hardware-wise broken:
The phone itself is a completly meltdown. Before I tried repairing it the speaker were broken (no sound). The phone ran an official lollipop rom. I think 5.0.1. Then I thought I could just hit a software update to fix maybe some problems. I updated to I9505XXUHOJ2 [5.0.1] DBT
And now the software experience is completly broken. The phone gets a lot of soft-reboots, the booting takes like 5 minutes and yes the phone is factory reseted. BUT HEY THE SPEAKER WORK AGAIN?!
I really dont know what is happening but there can be only 2 solutions:
1. Re-Install stock software via odin and then switch to cm and hope it works
2. or throw this piece of sh*t away because the cr*ppy hardware is brokanus sarus rekt
or is there any other solution? Tell me
Otherwise I would also ask if there is any solution to install cm12.1 or a custom recovery without root and odin access. (thinking of sideloading in recovery or something like this)
Thanks for reading and replying. I am gratefull for everything I hope the best ^.^
Click to expand...
Click to collapse
Windows 10 x64 works fine. I used it myself.
Try all the different usb ports and reinstall the drivers. Use the drivers from here:
http://developer.samsung.com/technical-doc/view.do?v=T000000117
Hi,
As the addition, make sure Kies isn't running when Odin is executed as it could cause the device being not detected properly in Odin.
PS Note: I used Windows 10 Home x64 too and working fine as it should.
Sent from my GT-I9500
I just bought a BNIB Note 3.
Samsung Note 3: SM-N900W8
Symptoms: Won't turn on, no lights, no load screen, no recovery mode, no download mode.
When I hook the phone up to the PC via USB it does vibrate and sounds the connection ringtone
What I was doing when this happened:
I had just recently rooted using "KINGRoot" - checked root and it was successful
I installed "TWRP" and booted into recovery mode and it was a success as well(I didn't actually run here yet)
***I installed and opened "Flashfire" to Flash the LINEAGE OS to my Rom buuut I didn't actually select the Lineage pack and I accidently pressed FLash(insert expletive here) *****
So Flashfire went through it's loading and when it was done it shut off and then the symptoms started.
It's a Note3 from Bell with all of their bloatware on it and I wanted to clean it all off and run a clean/efficient Note 3 cell with Rogers. I'm not looking to keep any of the data currently on the phone as there isn't anything currently on it. I just want to be able to install Lineage and use my Note.
I've searched for 30 hours pretty solid so far and unfortunately I haven't come across a clear solution. Can anyone give me a diagnosis and a tutorial or a link to a fix.
I'm open to loading from MicroSD, USB Jig, Samsung Kies....anymore information you require from me as away and I'll get back ASAP
Dead battery would be first check .
JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
Battery - I did the "spin" test on the battery and it doesn't show any physical characteristics of an overheated(bulged) battery. I'm going to test fit my battery into another note3 and I'll respond asap.
JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
I tried the battery in another Note3 and my battery is 52% charged and had no issues booting the tester phone.
I have the phone being tested for any Hardware issues right now.
If it's not a hardware issue will I be able to force a Rom(whether OEM Firmware or other) to install via MicroSD or USB jig?
When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.
audit13 said:
When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.
Click to expand...
Click to collapse
No, the PC doesn't see the phone.
The USB jig or MicroSD force is something I'm researching to try next(feel free to provide any good links to set up a jig(I've done this with Ubuntu on my laptop but this has a more intimidating feel to it)). The Tech at the shop I took it to test the hardware says "the motherboard" is broken and he'll fix it for $60.
For future considerations I'll learn to use TWRP flashing ROMs.
If the shop is offering to fix it for $60, they may be just force-flashing the firmware with something like an Octopusbox.
The USB jig may force the phone into download. If it doesn't, I don't think you'll have a choice but to pay to have it flashed. Unfortunately, Samsung will not help as rooting would trip the knox counter.
USB jig ebay are the usual cheap source.
Edit: flashed most recent stock firmware (Android 5.0 based, dated back in early 2017) and charging/file transfer is possible again. So I'd speculate that it comes down to incompatible kernel from the later version of ROM.
I would still love to have Lineage OS 16 on this though, so any help/pointer is still appreciated.
--------- Original Situation Below ---------
I recently took a very old Galaxy Note 3 (N9002), and successfully flashed TWRP (N9005/HLTE) build, and the equivalent Lineage OS 16 build (official nightly).
I was very pleased to see that the 6-yr old device runs the Android 9 based ROM very smoothly, and had all the fun getting re-acquainted with Android in general, until the moment I plugged in the charging cable and Samsung official adapter -- nothing.
I reconfirmed this by turning on Developer Mode - ADB debugging, and connected to the computer that I used to flash in the recovery earlier, with 3 different working USB cables. No charging, no file transfer, no devices attached when doing
Code:
adb devices
.
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around camera) gets mildly heated.
Turned the phone back on in Download Mode, and confirmed that it's still detected by Odin3 (and even flashed an HLTECHN TWRP and back to HLTE one successfully). Both prove that the cable, the charging, and the transfer mechanism should work.
This becomes pretty inconvenient in terms of day-to-day use, so any help and suggestion would be greatly appreciated.
Thanks.
Exactly the same issue
woozyking said:
Edit: flashed most recent stock firmware (Android 5.0 based, dated back in early 2017) and charging/file transfer is possible again. So I'd speculate that it comes down to incompatible kernel from the later version of ROM.
I would still love to have Lineage OS 16 on this though, so any help/pointer is still appreciated.
--------- Original Situation Below ---------
I recently took a very old Galaxy Note 3 (N9002), and successfully flashed TWRP (N9005/HLTE) build, and the equivalent Lineage OS 16 build (official nightly).
I was very pleased to see that the 6-yr old device runs the Android 9 based ROM very smoothly, and had all the fun getting re-acquainted with Android in general, until the moment I plugged in the charging cable and Samsung official adapter -- nothing.
I reconfirmed this by turning on Developer Mode - ADB debugging, and connected to the computer that I used to flash in the recovery earlier, with 3 different working USB cables. No charging, no file transfer, no devices attached when doing
Code:
adb devices
.
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around camera) gets mildly heated.
Turned the phone back on in Download Mode, and confirmed that it's still detected by Odin3 (and even flashed an HLTECHN TWRP and back to HLTE one successfully). Both prove that the cable, the charging, and the transfer mechanism should work.
This becomes pretty inconvenient in terms of day-to-day use, so any help and suggestion would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
I'm facing exactly the same issue after flashing with the same Lineage OS 16 on the mobile model Galaxy Note sm-n9002 HLTECHN
No charging, no file transfer, no devices attached when doing
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around the camera) gets mildly heated.
Will greatly appreciate if someone can help
Thanks
valteg said:
I'm facing exactly the same issue after flashing with the same Lineage OS 16 on the mobile model Galaxy Note sm-n9002 HLTECHN
No charging, no file transfer, no devices attached when doing
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around the camera) gets mildly heated.
Will greatly appreciate if someone can help
Thanks
Click to expand...
Click to collapse
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
https://drive.google.com/open?id=1G1...K7y1HwQbd4LN20
sm-n9002
pigliang said:
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
Thanks, Pigliang for the quick help
But I can't open the link, I keep receiving the following ERROR message from Google.
"404. That’s an error.
The requested URL was not found on this server. That’s all we know."
Please can you check and send the script again
Thanks
Click to expand...
Click to collapse
pigliang said:
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
https://drive.google.com/open?id=1G1...K7y1HwQbd4LN20
Click to expand...
Click to collapse
The link is not working, can you uplode it again?
Recently I've been to coolapk and find a one seemed to be working right (not tested yet):
Google Drive