[Q] Rooting KJ4 with zergrush doesn't work - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hey there,
i had LB2 (german version) on the n7000 before i bought it, so i flashed back to KJ4. But when i run the zergrush it's stuck at "--- WAITING FOR DEVICE".
In the device manager i have the gtn7000 as mtp device, the usb-debugging is turned on and unknown sources too. So what could be the problem now?
I had installed kies, but now i have deinstalled it and installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86 but its still not working. Odin can see the device.
I am glad about any helpful comment !
Greetings
Okay odin doesn't see the device anymore :-/, so it could still be a problem with the driver?! Which driver should it be if i would like to select the driver manually? There are so many folders with inf files in it...

zentaury said:
Hey there,
i had LB2 (german version) on the n7000 before i bought it, so i flashed back to KJ4. But when i run the zergrush it's stuck at "--- WAITING FOR DEVICE".
In the device manager i have the gtn7000 as mtp device, the usb-debugging is turned on and unknown sources too. So what could be the problem now?
I had installed kies, but now i have deinstalled it and installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86 but its still not working. Odin can see the device.
I am glad about any helpful comment !
Greetings
Okay odin doesn't see the device anymore :-/, so it could still be a problem with the driver?! Which driver should it be if i would like to select the driver manually? There are so many folders with inf files in it...
Click to expand...
Click to collapse
It is definitely a driver problem. Try to uninstall any drivers you have and reboot. Then download one of the drivers at the top of this page (Choose a 32- or 64-bit Windows drivers, I don't know which one you've got). Reboot again after installation. Connect your Note to one of the USB slots at the back of your PC - not at the front or at the side - wait for Windows to install additional drivers (5 or 6 of them) and try again.

Now i am getting till:
* daemon not running. starting it now *
* daemon started successfully *
And again stuck :/.
I have Win7 32bit, turned the antivirus software off, doenst do anything, installed/uninstalled/rebooted several times, disconnected/connected device...

It works?! "ADB.exe devices" didnt show the n7000 but now it do so everything was working fine now. Thx!

Related

[Q] Usb not Recognised SGS HELP?

I have seen posts on here regarding this error for the sgs althought none of the solutions that have came up are working on my sgs.
i have tried multiple os and every driver you can think of also i have used usb debug mode and altered between what usb port i am using..
My main os is windows 7 64bit the error i get on screen is:
usb device not recognised...so drivers wont install. skip to device manager and then there is and unknown device when i view this windows gives the error :
Windows has stopped this device because it has reported problems. (Code 43)
its really starting to destroy my soul...none of the methods previously posted are working..
Please help
You dont mention Kies installed .
Install Kies on phone go to settings and select mass storage mode .
Connect USB cable wait for pc to find phone and install drivers .
jje
yeah sorry kies is installed i tried different versions of that aswell.
There is an install driver option in Kees, try to re-install driver. Be aware that in kies it takes too long to install driver(don't know why), for long time it will show 100% in progress bar but wait until you get driver successfully installed driver message in Kies, it tool more than 10 mins.
Just fixed the similar problem today only, on Windows 7 64 bit, was struggling to but re-installation worked. Earlier I also tried reinstall driver but I thought it stuck on installation so I canceled but not today I gave it full time hence I said wait till you get success message. I didn't connected the device till driver installed.
May be your problem will also get fixed by this, nothing wrong in trying.

Soft-Bricked Galaxy S - Device Not Recognized

Hi, looking for some help with a soft-bricked SGS i9000.
It is bricked to the point that it only shows the 'Phone--!--Computer' when switched on, or when attempting to access Recovery Mode.
I can access Download mode absolutely fine, but Windows refuses to recognise the device when it is plugged in, therefore it doesn't show up in Odin, therefore I can't flash a new ROM.
Is there anything I can try to get Windows/Odin recognising it?
(Someone on another thread suggested just unplugging and replugging the phone until Windows recognises it - should I give this a try?)
Thanks.
I assume you have tried reinstalling the drivers?
Yeah, I've removed the device from device manager, reinstalled the drivers and re-plugged it.
Then I've tried updating the drivers via Device Manager - the message I get is that the best drivers are already installed.
Keys767 said:
Yeah, I've removed the device from device manager, reinstalled the drivers and re-plugged it.
Then I've tried updating the drivers via Device Manager - the message I get is that the best drivers are already installed.
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed at the moment and read this thread:
http://forum.xda-developers.com/sho...an always uninstall and install Samsung Kies.
try a different usb port, sometimes you can actually fool windows with that, i have had the same a couple of times, rebooting your pc or using a other pc sometimes works...
can you enter to download mode? It should be recognised by odin. If not you need an usb jig.
I had the same thing, so i looked around and someonle suggested installinog nexus S drivers and Odin recognizes your phone!!
It really works.
Nexus S Driver Link: androiddrivers.net/samsung-android-drivers/download-nexus-s-drivers/
>>can't post links yet

Windows will not connect to P7310

Happy new year all,
I have a 8.9 wifi only 32gb amazon.com version 7310.
I can’t get it to connect to my windows PCs (multiple PCs) ANYMORE…I have the drivers installed, but when I plug it in, windows will ask me for the driver and when it tries to install it I get an error (device not installed properly).
Some history:
I have the usb driver (“GT-p7510_USB_Driver_v1_3_2360_0-Escape.exe”) installed from the thread: “[GUIDE]Root, Bootloader Mode, ODIN, Recoveries & NANDROID Backup [7300/7310]”
Fresh off the box I hooked the tab up to my windows XP PC using the above driver and my PC recognized it. Also ODIN connected too.
I installed CWM (“Overcome_CWM_Recovery_v5.1.2.6_P73xx.zip”) from the above thread and rooted the tab using the root file (“Root.zip”) also from the above thread.
After that I couldn’t get the tab to be recognized from my PCs. But ODIN still works.
BTW, I’ve also tried Samsung Kies but it did not work (couldn’t connect to the tab).
I did a hard reset but I still have the same problem!!!
I need to be able to move files from my PC to the tablet as fast as possible. Wifi works but it is slower than usb 2.0!!!
Any help?
Thank you,
Have you tried uninstalling the drivers, restarting, then installing again? Sometimes Windows is a bit iffy. Also, the drivers from Kies are kinda different and tend to conflict (happened to me once). Another tip I'll give you: certain ROMs tend to hate having USB Debugging set to ON at Settings > Applications > Development. They just won't connect through USB while having that set to ON. I found this behavior on Android 3.1 ROMs, haven't had it in the KJ5 firmware and it's been almost two months with it. Best of lucks solving this!
issue solved by re installing the kies
Thank you for your suggestion.
Re installing kies and the latest kies update solved the issue.

CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP

CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP
HI - I've been fighting this captivate for over 48 hours. Being very familiar with all this, and not doing this for the first time either, the fact that I can't get this resolved drives me insane as I have never been so mentally exhausted in being incapable of resolving a problem, thus seeking professional guidance from the Gods on mobile technology!
HERE IS THE SPIEL:
Device: Samsung Captivate i897 (Device is rooted)
Software: AOKP build.38
Kernel: IcyGlitch v14
CWM: Installed v.5-----
The Problem
Device stuck at AT&T Logo - Not Looping (just stuck)
Windows XP Professional SP3 (x86) with all recommended USB drivers will not detect device. Device Manager displays the phone as unknown, regardless of drivers & upon inputting it into a USB (2.0) windows displays a message "USB Device is not recognized".
Windows 7 Ultimate SP1 (x64) brings up identical message as that of Windows XP with all proper & recommended drivers with the phone recognized as "unknown"
Device boots into download mode via holding Vol.+/- and plugin in USB cable. Both Heimdall & Odin can't recognized the device when it's in UNKNOWN state by windows. Although all drivers are installed.
Purchased new Micro USB cable - NOTHING - that's testing all USB ports on all my systems.
The Story:
The device was working flawlessly being able to mount as mass storage on both my Windows 7 Ultimate SP1 (x64) & Windows XP Professional SP3 (x86) until i've upgraded to AOKP build #38. The upgrade was successful (2 months ago). 2 days ago, i decided to upgrade to AOKP build #40. The device was not recognized as mass storage but rather "Unknown Device" or "USB Device not Recognized" - although the phone was in full working condition (USB Debugging was enabled). After some reading, I realized that the AOKP build #38 has a bug where there was a problem with mounting & the camera was not functioning since it had no access to external_sd (a problem that was very irritating since the update, but i had no time to look into it until recently). I followed a similar tutorial (http://forum.xda-developers.com/showthread.php?t=1545801) which required the editing of the vold.fstab file with Root Explorer, resolving the issue of external_sd becoming accessible on the phone with camera working, however unable to mount and copy the new AOKP Build 40 ROM through Windows to flash via CWM.
At this point I booted into CWM via holding volume +/- & power button. Wiped everything, and loaded a backup I've done a # of months ago where everything was working perfectly. There was an error when it was "...loading data image" which is normal, so I did it again and the error persisted. On the second attempt, it again re-sent me primary CWM menu where i was intending to now load another backup. I accidentally clicked the restart button, having already cleaned the devlick cache, etc, including user data which brought me this NIGHTMARE of problems.
I will be forever grateful the the kind soul which will help me resolve this, as I am at a phase of taking this samsung captivate and throwing it against a wall.
I assume you can still access recovery? Try putting CM9 on the external SD with a card reader, and flashing that...
EDIT: Just saw you can't access CWM... Try recovery again... all three until ATT comes up, immediately let off power... Try multiple times... Leave the battery out, hold all three, have someone else insert it, and let off power at ATT... When going into download mode, leave the battery out, hook it up, hold boths vols, and insert the battery...
The Unknown device issue....
Uninstall your drivers... Here are drivers to manually install, they are 64bit... so try right clicking the Unknown device in device manager and doing a manual driver update...
OP,
See this thread... Captivate Connection Issues...
Sent from my SAMSUNG-SGH-I777 using xda premium
B-Naughty: Thank you. I have tried this & that no luck. Even loaded Linux Mint 13, however heimdall is being a !*&#@ in loading the firmware...Perhaps if you would know any (proper) packages for a Samsung Captivate i897 via heimdall id be grateful. I used heimdall-suite-1.3.2 command line & frontend. Will try again tomorrow. Although still haven't figured out whether or not it read the phone in Linux (it's a different world for me)
4-2ndtwin: My friend, thank you for the detailed link. I have been doing this for over 48 hours ... nothing. I'll give it another shot via Linux, if not i'll try Ubuntu. Truly am just confused out of my mind, never had this before.
PS: The phone's data is wiped & it's stuck at AT&T when loaded via power button. Booting into DOWNLOAD MODE isn't a problem. All combination to load into recovery, did not work. I mean...there must be a way! There always is...Any further ideas or should i simply through it out and buy a Galaxy SIII?
I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click
And try all of your USB cords, I don't know what you bought, but a bad one, or a lot of times an aftermarket one won't work...
Edit:
I saw you can get into download mode. So my original post doesn't help much.
Have you tried installing the Andoid SDK and downloading the nexus drivers from there? Perhaps your device now thinks it is a nexus. It might be worth a shot.
^
+ 1
Yes... I second this ^
Sent from my SAMSUNG-SGH-I777 using xda premium
This happened to me and I just reflash the boot loader and reinstalled the same from to keep my data
Decrapitated Samsung
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
Seems as though you have a hardware problem with the phone, or a s/w problem so messed up you're down to Unbrickable Mod
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
Red_81 said:
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
Click to expand...
Click to collapse
He had a fresh Windows install and install drivers...
Unbrickable MOD - wont be able to do this my self, would need an electric to look into it. I mean the phone isn't bricked, it accesses download mode i just have to get it to connect via usb to be read as a "samsung composite device" to flash the bootloader. As now, it would be stuck at the AT&T screen without giving access to CWM.
I have installed Ubuntu 12.04 - set up java 7 - loaded Heimdall One-Click stock rom provided above via java...tried all USB's phone not detected via DOWNLOAD MODE. Phone not detected at all!
This is just insane...If it's in DOWNLOAD MODE, it should be accessible, not the contrary. Ubuntu doesn't need usb drivers, should be plug&play...Both XP & Win7Ultimate at least recognized the phone as an unknown device. On Ubuntu it does nothing at all, as if it never was plugged in.
The microusb slot on the phone is not damaged / cable is stock, also have another one from Staples. The system w/XP is reading all devices on a plug&play basis and read the captivate before flawlessly. Same applies to the Asus P43 laptop, which read the device without hesitation on Win7 Ultimate x64. The Ubuntu is now on the laptop...tried connecting the Galaxy Tab 10.1 (Samsung) it recognized it immediately...with full access to files etc.
Last plea for Ideas...before i'll send this captivate to hell, to where the journey isn't captivating at all!
It sounds like you have a bad flash. You need jtag to fix this issue. Contact mobiletechvideos and Josh should be able to repair it for you. I think at this point you've tried every other option.
Sent from my SAMSUNG-SGH-I897 using xda premium
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
did u try reverting back to stock using ODIN 1 Click Stock Firmware Installer? there's a tutorial on youtube by mobiletechvideos original post by connexion2005.
Samsung Captivate (ODIN 1 Click Stock Firmware Installer)
youtube.com/watch?v=UDtxnH4lFuk
I would like to have that free captivate thou :good:
Same Problem
i have the same prob and if i try to recovery mode (i.e. by pressing volume buttons and power button simultaneously)
i get following type of errors
"E:failed to mount /cache (Invalid argument)
E:Can't mount/cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log"
kindly sugeest some way out
I have done everything possible to get it connected and recognized by the PC & all is failing. I have tried to "manually" install the Samsung composite Device driver via "have disk method in Device Manager.
In XP:
I load device manager and than do the following:
Click Universal Serial Bus Controllers
Right click "unknown device" which is the captivate
Select Update Driver
Select Install from a list or specific location (Advanced)
Select Don't Search. I will choose the driver to install. (Click Next)
Select "Have Disk" with the (show compatible devices) checked
Browse to the directory of extracted 32bit Windows XP Drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
Select "ssadadb2.inf" & click open
And than i get the msg saying:The specified location does not contain information about your hardware
...WTF... I mean really...
Windows 7 Ultimate:
Same procedure as above until you select have disk, pick a proper x64 driver provided by XDA - also tried the Universal_Naked_Driver_Beta_0.6 ...there was progress that got me very excited - the Phone was detected as: Samsung Android Composite Device. Was I happy...until i clicked next and got this msg:Samsung Android USB Composite Device - This device cannot start. (Code10)...
There must be a solution: I had the phone bricked when i first tried to change from stock rom, managed to load it in download mode, and it was detected fine on all systems via USB with the same accessories, worked like a charm...so when this happened i wasn't concerned, as i thought id follow standard procedure, accept it did not work.
Anyone?
Let's try this since you seem to be stuck in a boot loop.
Code:
adb wait-for-device reboot recovery
Make sure your phone is plugged in and reboot it. If your machine recognizes the phone at any point in the boot process it will kick it into recovery.
Once there you can try to restore the backup again.
If this doesn't work, you will most likely need JTAG service. Because of the bad image flash your device might not "think" it is a Captivate any longer and that's why the drivers aren't working.
Red_81 :Thank You. Would you please be more specific & put into a 1,2,3...process?
1. Power off device
2. Plug in to computer
3. Open a command prompt
4. Navigate to adb.exe (android sdk or inside my kk4 root utility)
5. Enter command above
6. Boot up phone.
7. Hopefully go into recovery
Sent from my SGH-I777 using xda premium
Thank you. I've been endlessly fighting the achievement of the PC systems to detect the captivate & no results. Thank you all for you help...when i have time i'll JTAG this device, or probably not even going to bother and pick up a SGIII. By the way Red_81:http://forum.xda-developers.com/showthread.php?t=1680048 is an amazing app, if only my phone was detected as it's recognized as unknown device, so there isn't much it can do. Although i highly recommend it to anyone else whose phone is detected.

[Q] Trouble with Samsung USB Drivers version 1.5.18.0 + KIES

Hello.
I recently tried to root my phone with the S3 Mini Toolkit. I have the GT-I8190 international version.
It said that I needed to Install the device drivers first (which is the v1.5.18.0).
So I did it as instructed in the command prompt. When it finished installing the driver, and I plugged my device as instructed, suddenly came an error message "Samsung Hardware ID is missing error", and my Mini became unrecognized all of a sudden. I couldn't access my device storage.
There was an error message too popped up in my device saying that It cannot find a driver in my PC for my device.
I tried to install KIES afterward, hoping that it can solve the problem. Thing is, it didn't. My device was still not recognized, and KIES couldn't recognize it either (Connecting.....for, like forever).
I then tried to Google the problem, and came by a forum, saying that it was the 1.5 USB Drivers that caused the problem (but the case being talked in the forum is for Galaxy S3). Said that my PC need to uninstall the 1.5 drivers, uninstall KIES, deactivate the automatic device installation by Windows, and install the 1.4 version.
Well, what I can find in the internet is the 1.3 USB Drivers, so I tried the instructions, and installed the version 1.3 USB Drivers, and my PC recognized my device again, and able to access the storage.
(also, the 1.3 drivers made Odin unable to recognize my phone too in download mode).
Does anybody here have ever experienced the same problem as mine? Or did I do something wrong?
I managed to root my Mini, being not recognized by the PC (but registered at the toolkit) in the whole process, and then did the whole uninstalling and re-install the USB drivers so that I can access my storage again.
Because it's rather a painful process if in the future I want to use the toolkit again with the newest drivers.
Note:
- before rooting, I did the latest OTA update.
My current device info is
Android version 4.1.2
Baseband version I8190DXAMA2
Build vnumber JZO54K.I8190DXAMA2
Region Indonesia
Thank you very much
Bumped. Can anybody gives me some enlightenment about this issue? Thanks

Categories

Resources