Related
hello, greetings to all, I have a X10i, and it will install universalroot change the original numbering system for the Norse to upgrade to 2.1 when the numbers change and reset the phone tells me it should be closed forcibly Timescape, I try to upgrade to 2.1 pc companion error and tells me never recognizes the phone, and SEUS says I have the latest software, trarto of restauralor from the phone and I get error, open the market and I get error any program I run. restore it to factory settings and I get the same error, I went to the model information and tells me I have the firmware 1.6 but the model number which came out before I get one now X10i unkonwn is as if he had model now tell me I hope your help to do, ah another thing I can not install any program from mobile
When you editted the numbers when you were trying to upgrade you didn't enter the right numbers or you changed something else which you weren't meant to.
There is some amounst the may threads a solution to this which bin4ary made. I'll see if I can find it and point you in the right direction....
Sent from my X10i using XDA App
I'm sorry I can't seem to find it. My advice is send bin4ry a PM and hopefully he can find the right info for you.
Sent from my X10i using XDA App
thanks friends
nuncar21 said:
thanks friends
Click to expand...
Click to collapse
No worries. The problem is where some of the threads get so long tryng to find proper news and useful stuff gets mixed in with all the other stuff too.
Sent from my X10i using XDA App
Run this which will update you to 2.1 - http://forum.xda-developers.com/showthread.php?t=825675
XperiaX10iUser said:
Run this which will update you to 2.1 - http://forum.xda-developers.com/showthread.php?t=825675
Click to expand...
Click to collapse
and tell us how you go with it!
hello friends probe through the tutorial and download the program but when I run the program x10flashbat and asks me to connect the phone in flash mode and press any key to continue when I make that step completely closes the program that I can do
nuncar21 said:
hello friends probe through the tutorial and download the program but when I run the program x10flashbat and asks me to connect the phone in flash mode and press any key to continue when I make that step completely closes the program that I can do
Click to expand...
Click to collapse
Reread the guide carefully, and try again.
hello friends I have read all topics and I have tried everything, when I run the regedit in windows and put "Vid_0fce & Pid_adde" I do not see the DeviceInstance try putting "USB \ VID_0FCE & PID_ADDE" and I do not see anything I have Windows 7 32bit everything I've done with the phone plugged into debug mode but nothing that I get something, and when I run the file if you put nothing opens and when I plug in flash that I close the program
You have to have SEUS installed and PC Companion.. run it through PC companion once. Then do the regiedit thing.
To put your phone into flash mode, turn off the phone completely, then hold the back button and connect the phone through USB to the computer.
(when you do this, make sure PC companion is NOT running)
-please read the whole thread-
:The point of this thread.
Find a way to get flash mode to stay active longer, Gives you more time to work and experiment"
The point of basing it on on the newer driver is that there may be something in them that will give us access to Fastboot"
Hopefully use that to get to the boot loader.
:--
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be useful.
It ejects when flash mode isn't used i think.
Sent from my X10i
jockep said:
It ejects when flash mode isn't used i think.
Sent from my X10i
Click to expand...
Click to collapse
No.
please just listen to me.
If any developer is interested in this PM me and i will explain.
Just a note but you may want to mention which version of the flash tool you are having issues with.
exsulis said:
Just a note but you may want to mention which version of the flash tool you are having issues with.
Click to expand...
Click to collapse
Please.. as i said DEVELOPERS ONLY.
PLEASE DON'T spam.
I'm not talking about the flash tool.
i don't think it has anything to do with the driver, as much as the phone's flashmode behavior itself.
ie the computer recognises the device device differently whether its in regular usb mode, debugging, mounted, flashmode, etc.
i think what it's experiencing is flashmode turns off if there's a delay, and changes usb mode. the computer sees the change as "device A" no longer there and "device B" now there. the computer will see the different usb modes as separate devices since there will be separate ID's for the mode.
if there was a way to keep the phone in flashmode, this would fix the problem. but there's no way of doing that without changing and reflashing fastboot/bootloader.
Then perhaps a driver that acts more like the drivers for the newer phones.
I think.. Fast boot could easily be accessed this way.
And all we need is for it to load that driver and to test using this command.
fastboot.exe -i 0x0fce getvar version
This is all speculation.. but call it a lucky hunch.
If i am wrong then the mods may delete this thread and XDA may ridicule me.
If anyone does manage to do this.
The credit is all yours.
No.. now i am sure the X10's driver may be buggy.
Hold the flash button and insert your charging lead using the wall charger.
You will notice it stays in flash mode for much longer.
I may be wrong.. but test it.
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
but don't get me wrong, if you or any devs know of a way to exploit it, by all means go to it!
svtfmook said:
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
Click to expand...
Click to collapse
I know this.. But i would like to get a few more developer opinions on this.
OmegaRED^ said:
I know this.. But i would like to get a few more developer opinions on this.
Click to expand...
Click to collapse
no doubt. would be cool if it could be exploited.
svtfmook said:
no doubt. would be cool if it could be exploited.
Click to expand...
Click to collapse
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
OmegaRED^ said:
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
Click to expand...
Click to collapse
Never head that on the x10 forums
Sent from my X10i using XDA App
rtblittlebrown said:
Never head that on the x10 forums
Sent from my X10i using XDA App
Click to expand...
Click to collapse
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
OmegaRED^ said:
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Click to expand...
Click to collapse
If other devs had that attitude they may already have picked this thread up
Seems you may have fallen foul of someones temper tantrum
Sorry for the spam
OmegaRED^ said:
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
Click to expand...
Click to collapse
If your plugged into your charger that happens on older rom's with charge when off problems
Sent from my X10 using XDA App
OmegaRED^ said:
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be usefull.
Click to expand...
Click to collapse
Not to throw a spanner in the works BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Edit: also some more research it indicates the its the android generic open driver inf
asmanthebell said:
Not to throw a spanner in the work BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Click to expand...
Click to collapse
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
This is why i asked for developers only to reply.
OmegaRED^ said:
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
Click to expand...
Click to collapse
Sigh!
1. Do you know and understand what an .inf file is?
2. Do you know how interacts with an operation system?
3. Can you post the rest of driver i.e the .cat file and .sys to go with the inf?
hey all! great forum... former se x10 mini user... getting my atrix today!
my main question is: i want to install greyblur after rooting but there are always warnings about not installing it on the BELL version... yet i see, via their signatures, that many bell users have it installed... the guide for greyblur does not have specific instructions for bell, just has big warning in red saying not to install it on bell!
so how do i get it working?? what do i need? i'm pretty handy with android, so no need to have crazy detailed help...
thanks everyone! looking forward to learning more and more about this great device!!
ryan
watchyourbreath said:
hey all! great forum... former se x10 mini user... getting my atrix today!
my main question is: i want to install greyblur after rooting but there are always warnings about not installing it on the BELL version... yet i see, via their signatures, that many bell users have it installed... the guide for greyblur does not have specific instructions for bell, just has big warning in red saying not to install it on bell!
so how do i get it working?? what do i need? i'm pretty handy with android, so no need to have crazy detailed help...
thanks everyone! looking forward to learning more and more about this great device!!
ryan
Click to expand...
Click to collapse
See the thread called "SBF/root/deodex 2.1.1 SBF" or something along those lines (in this forum). In order to get greyblur/GingerBlur working on a bell phone you have to flash an international SBF file. Right now the most current is 2.1.1, a generic SBF (leaked from France). Just be warned that flashing this will void your warranty. However, it hasn't caused any issues itself and wont CAUSE anything on your device to fail at all, if you get into trouble its most likely just bad luck with hardware and if you REALLY need to return your phone there is a general way to make it seem like you've gone back to stock, that you can do with the help of forum members here if needed.
Not trying to scare you off, I've done this myself. I'm just making sure you understand the risks. Hope this post helps you understand what you're getting into and where to go for further info.
Also, this should be in Q&A section, not dev.
Sent from my MB860 using XDA Premium App
not scared at all! thanks for the PERFECT response!
Moved to proper forum.
ok, i'm going through the steps but for some reason the x64 drivers won't install (yes i have 64-bit windows.). says this:
"The system administrator has set policies to prevent this installation."
i assumed they weren't required.
nothing happens when i run rds before plugging in phone. when i reboot the phone, i see the rds protocol message, i run rds on my pc, plug in the phone and nothing happens....
thoughts?
I know nothing about windows sorry bruvva
I do know that once you are running a p rom pretty much everything becomes compatible
Sent from my Googletron
watchyourbreath said:
ok, i'm going through the steps but for some reason the x64 drivers won't install (yes i have 64-bit windows.). says this:
"The system administrator has set policies to prevent this installation."
i assumed they weren't required.
nothing happens when i run rds before plugging in phone. when i reboot the phone, i see the rds protocol message, i run rds on my pc, plug in the phone and nothing happens....
thoughts?
Click to expand...
Click to collapse
well the drivers do need to be installed, you can find the necessary drivers in an executable package here although i can't tell you whether admin restrictions will block that too. might be easiest to find a PC where you can do stuff as an admin depending on your current system's configs.
once drivers are installed your PC will recognize device when in RSD mode.
I would assume that the login on your comp is not set as an administrator. You have to be logged on as an administrator to modify system files or drivers in windows.
You could also try right clicking the usb driver installation exe and choose "run as administrator".
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
Hey
Regarding the Win 64 driver, I had the same issue, until I realised the link given in the thread about 2.1.1/Greyblur for the driver lead to a corrupted file (~ 500 kb) even using a download manager. I downloaded them from elsewhere (Motorola Website) and the error message disappeared without having anything else to do.
Hope that helps!
Guillaume
Actually got the whole thing going a while back... sorry for not checking back!
I am officially enamoured by this phone......... the start of a beautiful and complex relationship ...
And yeah, I suspected that it had something to do with corrupt file... tried a few diff sites but all seemed the same... eventually tried a diff usb port and it worked...
Sent from my MB860 using XDA App
Hi all, I have problem with nokia care suite,
i follow the tutorial for debranding lumia 800 (I have Tmobile DE) but when it comes to step "click programming and choose refurbrish" i can't do that =( because if i click the programming tab it doesn't do anything =(
i think i did everything correct, i downloaded the fw version changed the product code, the grey cube button turned to green, also the program recognize my phone and shows "USB1-RM801" but i can't flash it....
also i tried every usb ports on my computer
p.s. I use windows 7 64bit and original usb cable.
I hope someone can help me
eccomania said:
Hi all, I have problem with nokia care suite,
i follow the tutorial for debranding lumia 800 (I have Tmobile DE) but when it comes to step "click programming and choose refurbrish" i can't do that =( because if i click the programming tab it doesn't do anything =(
i think i did everything correct, i downloaded the fw version changed the product code, the grey cube button turned to green, also the program recognize my phone and shows "USB1-RM801" but i can't flash it....
also i tried every usb ports on my computer
p.s. I use windows 7 64bit and original usb cable.
I hope someone can help me
Click to expand...
Click to collapse
What error are you getting?
Have you tried using Recover instead of Refurbish?
anseio said:
What error are you getting?
Have you tried using Recover instead of Refurbish?
Click to expand...
Click to collapse
the problem is i don't get any errors or anything, the programming button doesn't work at all, when i click nothing happens, not even opening the refurbrish or recover droplist...
eccomania said:
the problem is i don't get any errors or anything, the programming button doesn't work at all, when i click nothing happens, not even opening the refurbrish or recover droplist...
Click to expand...
Click to collapse
Are you following this process?
http://forum.xda-developers.com/showthread.php?t=1457341
anseio said:
Are you following this process?
http://forum.xda-developers.com/showthread.php?t=1457341
Click to expand...
Click to collapse
yes i tried that method too.. but no luck =(
i can't click programming button thats the problem... it's kinda deactivated I think
Are you opening product code RM-801 or have you moved the firmware to a different folder? Not much can be done from the RM-801 folder.
I'm just having problems installing Nokia Care Suite. It gets so far and I get a 1220 error.
Any ideas?
Sent from my iPad using Tapatalk HD
It's some odd registry error, right? I think you just click through it. You'll have to navigate to the program folder to open the launcher. IIRC, that's what I had to do.
eccomania said:
yes i tried that method too.. but no luck =(
i can't click programming button thats the problem... it's kinda deactivated I think
Click to expand...
Click to collapse
so, how did you solve this problem? Ive got exactly same trouble wasting my time for days...
Do You ha e a screenlock code on the device. I had to remove my Outlook account, which requires a screenlock code, remove the code and then I was good to go.
Sent from my Lumia 800 using Board Express
anseio said:
Are you opening product code RM-801 or have you moved the firmware to a different folder? Not much can be done from the RM-801 folder.
Click to expand...
Click to collapse
This. In order for the Programming menu to be available, you need to select "Open Product" from the File menu and choose the correct product code (RM-819, RM-801, etc.).
My problem is I can never get passed the "Checking Mode" or "Starting" stage. I keep pressing the volume up button + insert USB cable until I feel a short vibration. After that, Windows will recognise my device as DLOAD and after a short while, the device restarts. Nokia Case Suite will then prompt me to unplug the USB cable, shutdown the device and do the volume up + insert USB cable routine again. Rinse and repeat. What did I do wrong? I am using Windows 7 64-bit.
EDIT: I solved my problems by going to the C:\Program Files (x86)\Nokia\Nokia Care Suite\Drivers\ directory and manually installing all the x64 drivers.
Im also having a few problems with NCS... i just figured I would piggy back off this thread rather than start a whole new one....
When installing I get a error that says.... "ERROR 1904.Module C:\Program Files (x86)\CommonFiles\nokia\Service Layer \C\Service Modules\ServiceModule_00003\msml4.dll failed to register" I hit ignore but now when i connect my phone to my PC... it isnt being recognized as DLOAD or QC or anything. I am at a loss... i went through and installed the drivers that were in the Nokia folder manually, except one it wouldnt install for some reason. Any help would be greatly appreciated.
I am having the same problem on my lumia 920. I didn't find a solution yet. This thread is the only thing I found so far.
Edit: I tried ncs on x64 w7 and x86 w8
Not starting
my phone is not sarting after installing nopkia evolve
eccomania said:
Hi all, I have problem with nokia care suite,
i follow the tutorial for debranding lumia 800 (I have Tmobile DE) but when it comes to step "click programming and choose refurbrish" i can't do that =( because if i click the programming tab it doesn't do anything =(
i think i did everything correct, i downloaded the fw version changed the product code, the grey cube button turned to green, also the program recognize my phone and shows "USB1-RM801" but i can't flash it....
also i tried every usb ports on my computer
p.s. I use windows 7 64bit and original usb cable.
I hope someone can help me
Click to expand...
Click to collapse
I had same stupid problem. You have to change your o.s.country and region from control panel. Try UK or USA. Both will work..
Hope this will help.
Hello everyone,
I recently bought a "second hand" GT 10.1v, for which the previous owner tried to root it and install a custom firmware. He told me he had a problem during the processus and now the Tab is runs in an infinite bootloop.
I though I would be able to fix it (I have a GSII which I customed a lot so...), but I guess I was wrong... I've been looking for some answers for the last 2 days but can't do nothing. Here's the problem :
* I tried to do the method to root the device one more time. I make the button procedure to arrive to the screen with the usb plug and the android working in a triangle.
*When I choose the usb plug, I have these informations written :
fastboot usb download protocol
bootloader version : p7100BUKC8
baseband version : P7100BUKDF
serial number : the serial is written
lock state : unlocked
*When I choose the triangle, I have these :
reason : force key
secure mode : secure
check signature : check
oem lock : unlock
waiting usb cable...
Regardless of my choice, I can't have any communication with my computers (running under windows 7 x64 or windows vista x86)
*I tried with Odin (after choosing the triangle), the device is not recognized in odin.
*I tried with fastboot mode, following step by step different tutorials (this one was the first) with installing usb drivers via google sdk, modifying the android_winusb, moving adb to "tool" folder, adding the fastboot nvidia to this folder.
When I type fastboot devices in cmd, nothing is written. When I try fastboot oem unlock, it shows "waiting for device".
When I type adb devices, I have a blank list of devices.
The problem is that when I plug the usb cable to the computer, windows doesn't try to install drivers and I don't see Android phone nor ADB device or something like that in the device manager of win7???
I'm totally desperated, could someone help me to fix my problem??
Sorry for the length of the post but I prefer write as many informations as I can so you don't waste time by trying to help me on something already done.
Many thanks to you all!!
Using windows7 I'd reinstall the usb drivers as a first step. If it says the drivers are already installed, install them anyways, and see if that gets you any further. Hopefully it will.
Plus hopefully someone with more experience with 10.1v will come help also.
If you see this it was sent using my GT-P7510.
Hi Benzoman,
Thank you for your prompt reply, but as I said, the problem is that windows doesn't even detect it. How can I install the driver if I have no device in the windows device manager?
download the driver from Samsung or wherever you want and run the download. I'll post a link in a minute.
If you see this it was sent using my GT-P7510.
EDIT: Just noticed your posting for the 10.1v No experience with this version myself personally but try the following links.
Post for unlocking which includes USB Drivers http://forum.xda-developers.com/showthread.php?t=1064793
Thread referred to in first post for Windows Users http://forum.xda-developers.com/showthread.php?t=1083517
Like I said I haven't messed with the 10.1v myself so I would follow the original thread instruction first and see what they do for you. Else ask for help with the problem somewhere appropriate for the 10.1v there unless you already did.
Thank you for your help, but I still don't understand, and this is for every type of device, how can I install driver if the device is undetected by windows?? In the device manager, I don't see any unknown device or something equivalent...
You have the same issue as i do, The COM ports won't be able to be read until the device itself has loaded/opened it's COM ports to be able to communicate. Your best bet would be attempting to get it to detect via APX mode. Once that works, your only solution to getting it to boot/flash firmware normally? would be to drain the thing dry
PS- I posted a guide on here on how to get it out of the "Endless boot" or Sleep of death. I won't say your case is unique, but no reason not to give it a go, right?
I had a similar issue with my 10.1v and the 10.1 3G , I ended up bricking my 3G and getting the 10.1v at a second hand price due to the very same reason. After draining them completely I had flashed both of them successfully and now like cancer free patients, they're both alive and kicking.
Edit: I forgot to add, this is normal, the device won't even pop up on Device Manager or the "Installing drivers" list until and unless you drop it to APX mode. If you did it right, You'll hear the USB sound.
Thank you for your post Misledz, it seems that someone has a new method which might work (I hoooooope so lol).
But could you explain me what you mean by APX mode and how to get into it? I don't really understand.
Plus I don't understand what you mean about drying the thing dry. Could you explain me that too?
Many many thanks ;-)
Edit : Ok, I finally found your tutorial and will test it, hoping this will work ;-) I keep informed.
juxci said:
Thank you for your post Misledz, it seems that someone has a new method which might work (I hoooooope so lol).
But could you explain me what you mean by APX mode and how to get into it? I don't really understand.
Plus I don't understand what you mean about drying the thing dry. Could you explain me that too?
Many many thanks ;-)
Edit : Ok, I finally found your tutorial and will test it, hoping this will work ;-) I keep informed.
Click to expand...
Click to collapse
Well glad you found your way to it :] The guide talks about how to drain it dry and get it to work :] In hopes it works!
??? I don't understand why but now I'm unable to turn on the Tab unless I plug the usb in??? (maybe she's feeling i'm about to fix it?lol)
It will be hard to drain it if I can't turn on and off without plugin' it. Any idea??
Edit : important thing : when I plug the usb, I have the battery charged to 100% and the Tab vibrates, so no, it's not because the battery is empty lol
Edit II : I'm not sure I fully understood the tutorial. My though is the following:
1, I drain the tab by holding the power button down.
2, I hold the power and vol+ buttons, plug the USB and maintain both buttons for 15s (could it be more?).
After that normally I should have a loop of pop up in the device manager for APX device, I release the vol+ button but keep power button hold and wait the end of the loop to install the nvflash driver?
Correct? 'cause if it is, it don't work for me :-S I can't have the pop up loop (I remember I had this loop once, but I released the power button and the loop cut and the "unknown device" disappeared from device manager. But since, I can't get this again)
juxci said:
??? I don't understand why but now I'm unable to turn on the Tab unless I plug the usb in??? (maybe she's feeling i'm about to fix it?lol)
It will be hard to drain it if I can't turn on and off without plugin' it. Any idea??
Edit : important thing : when I plug the usb, I have the battery charged to 100% and the Tab vibrates, so no, it's not because the battery is empty lol
Click to expand...
Click to collapse
I don't think your actually getting it The whole idea is to drain it or find an alternative way to get it to fastboot mode to bring it to Download Mode where you can flash an HC rom of choice to save it 140%. 100%..Wow that's not going to be easy to drain..
In fact, I don't know why, it seems it was kind of a bug because after that I unplugged and plugged the socket charger again and I had a battery icon why a exclamation mark and charging.
However, it seems you answered when I was posting "edit II" in my previous message. Did you read it?
Anyone having an idea?
Good luck with helping this one Misledz.
They don't know how to reinstall drivers in a windows machine if the device the drivers are for are not found
So this is might just be a fun endeavor. :screwy:
I think there are other issues needed resolved before this person roots or mods anything. Like understanding their Windows machine and how to install/reinstall drivers.
Always has just been running the install from the drivers file and accepting yes I want to install the drivers even though the are already installed. I could be missing something about this part as it pertains to this problem. But sure I'm not mistaken about how to install/reinstall drivers on a windows machine. Windows can't be expected to recognize every thing first, and then download and install the drivers for it. Maybe its me but that's what I'd call a fantasy world. I know thats what plug and play says it does. I also know that it often fails. So, needing to learn, I even know how to completely uninstall the possibly offending drivers before reinstalling said drivers, sorry I don't have the patience to help with this one, but when you goto the10.1v I can use that as my excuse since I don't own one.
Plus I don't want to follow you into the rabbit hole.
A sincere Best of luck to both of you. Misledz and the person with the problem. :thumbup:
If you can read this it was sent using my GT-P7510.
Benzoman said:
Good luck with helping this one Misledz.
They don't know how to reinstall drivers in a windows machine if the device the driver are for are not found
So this is might just be a fun endeavor. :screwy:
I think there are other issues needed resolved before this person roots or mods anything. Like understanding their Windows machine and how to install/reinstall drivers. Always has just been running the install from the drivers file and accepting yes I want to install the drivers even though the are already installed. I could be missing something about this part as it pertains to this problem. But sure I'm not mistaken about how to install/reinstall drivers on a windows machine. I even know how to completely uninstall the possibly offending drivers before reinstalling the drivers, sorry I don't have the patience to help with this one, but when you goto the10.1v I can use that as my excuse since I don't own one.
Best of luck to both of you. Misledz and the person with the problem. :thumbup:
If you can read this it was sent using my GT-P7510.
Click to expand...
Click to collapse
sure, Just abandon me Q.Q
But anyways the driver for the device is in the samsung website, it's device specific.
In order for the device to be recognized you need to have the appropriate driver for it.
Another would be making sure that the tablet get's read on the computer via fastboot mode/adb. You need to use the Volume Down+Power option till the logo boots up.
Then again, what do you see when you boot up the tablet? / Can you even boot it? That would be a good start and more detailed info would be appreciated
PS- I just read your Edit II, turns out to get unknown device it's Power+Volume Down, which is the left button on the volume keys. You hold it down when it's plugged via USB to the PC for 15 secs, 20 seconds doesn't matter just it needs to cross the 15sec benchmark. Once you get past it forces itself into APX mode. This is where you need the APX driver for it. Seeing as to your tablet is unlocked you may be able to save it.
I edited my post after you quoted to try to explain my potition and reasoning reasons a little better. Good luck mate!
If you can read this it was sent using my GT-P7510.
Misledz :
The problem is that I don't find (after several researches) the drivers on samsung site, but I found another one.
The tablet is not recognized in ADB nor in fastboot (as told in my first message)
When I boot the tablet, I see the samsung logo with open padlock and then the boot animation with the android bot and then I'm stuck there.
When I hold power and left volume button, the device turns on and I see a screen with the usb and the droid in the triangle (downloading mode)
I think (by reading the very interesting post of benzoman) that it might have a confusion about "the device isn't recognized by the computer". What I mean is :
When i plug it via usb, turn it on normally, or put it in downloading mode or fastboot mode, the computer doesn't even react (any sound like when i plug a usb key nor pop up saying "new device detected" in the right bottom corner of the screen)
I hope these informations added to my first post are enough for you to have a clear vision of my problem.
Benzoman :
You don't have time to give the informations you "know", but enough to waste by writing this type of s**t?!
Can you tell me how does a cyclotron works? How we modulate the power of the exiting ray of particles? When you will be, just come back to waste your time here and show that you think you're smarter than others. Everyone has his own job, I'm not into computer science so yes, I recognize I'm far to know every thing, and I think that's the purpose of this type of forum : share knowledge and help others when needed.
I think you should open a new type of forum, if your entertainment is to waste your time by laughing at other's problem.
You wrote about 10 lines to say nothing...but don't have time to give a hand? How many lines would have been necessary to give a useful information? By seeing how strong you're saying you are, surely less!
At least, if you don't want to help, don't foul the topic, it will be easier for the ones who really want to help to follow!
juxci said:
Misledz :
The problem is that I don't find (after several researches) the drivers on samsung site, but I found another one.
The tablet is not recognized in ADB nor in fastboot (as told in my first message)
When I boot the tablet, I see the samsung logo with open padlock and then the boot animation with the android bot and then I'm stuck there.
When I hold power and left volume button, the device turns on and I see a screen with the usb and the droid in the triangle (downloading mode)
I think (by reading the very interesting post of benzoman) that it might have a confusion about "the device isn't recognized by the computer". What I mean is :
When i plug it via usb, turn it on normally, or put it in downloading mode or fastboot mode, the computer doesn't even react (any sound like when i plug a usb key nor pop up saying "new device detected" in the right bottom corner of the screen)
I hope these informations added to my first post are enough for you to have a clear vision of my problem.
Benzoman :
You don't have time to give the informations you "know", but enough to waste by writing this type of s**t?!
Can you tell me how does a cyclotron works? How we modulate the power of the exiting ray of particles? When you will be, just come back to waste your time here and show that you think you're smarter than others. Everyone has his own job, I'm not into computer science so yes, I recognize I'm far to know every thing, and I think that's the purpose of this type of forum : share knowledge and help others when needed.
I think you should open a new type of forum, if your entertainment is to waste your time by laughing at other's problem.
You wrote about 10 lines to say nothing...but don't have time to give a hand? How many lines would have been necessary to give a useful information? By seeing how strong you're saying you are, surely less!
At least, if you don't want to help, don't foul the topic, it will be easier for the ones who really want to help to follow!
Click to expand...
Click to collapse
Please do not quote this post as it is being edited constantly to futher help juxci and explain any misunderstandings and quoting it before completion will only cause more issues. Thanks for understanding.
First, I was trying to be polite by stepping back and letting Misledz help you. Having both of us suggesting conflicting ideas would have of been little help.
Second, if I did't understand the very basics of say, oh idk, maybe a cyclotron why would I mess with something that relies upon on it? I still would because there are others that can help, should something go wrong. Albeit, I would not DEMAND their help and would even understand if they chose not to help if I acted an a$$.
Then b!tch because someone tries to help me, and my response comes across like I know what I'm doing, but is really only being a rude reply of, "Can't do that." When the person trying to help knows it can be done, confirming I know not even the basics of the cyclotron and should be open to any and all help. Not act an a$$ by just saying, "That can't be done." When it can be done, and easily, if the person who knows about the cyclotron would tell me. But, since I want to be an a$$ and act like I know what can and can't be done on the cyclotron. The person who could have helped with it says, if I'm not going to listen, then they'd rather not be directly rude themselves, and get aggravated, notices another who has the knowledge is present, wishes them both an HONEST WISH OF LUCK and leaves.
This is basically what I myself was trying to do. I know the drivers can be completely be removed and reinstalled on the PC, but you acted an a$$ and said, that can't be done, sounding like you knew, what you were doing, and wasn't going to be open to accepting my help, without causing me great frustration in the process. So knowing that the very knowledgeable Misledz, was here to help, I thought it best to leave it up to him. My wish of luck was sincere, even if it was indirectly sarcastic.
I should stop here and not look back at the thread, but I have always tried to help where I can.
If you really would like my help personally. Here you go, I'll start again. Although it's repeating things Misledz has already said.
You need to get legitimate Samsung drivers which are specifically for YOUR device to install. Ones found elsewhere may cause more problems than they fix.
If installing the drivers over the top of the others doesn't help you need to uninstall the old drivers fully. Then install the official drivers. This has helped others and even myself once or twice. Widows is a finicky little [email protected] sometimes.
Uninstalling the old drivers completely may be considered complicated and without having another reference handy to help me guide you to a program, I can't do it correctly. I will have to get to my PC where I have access to use references for me to look at so I can help you best. I will be back to to check on the progress of your issue. ASAP
I think some of the problem may have initially been from my personal misunderstanding of your grammar. Believing you were stating things in a way you did not mean. If that is the case, I apologize.
Edit: http://www.nirsoft.net has a program called USBDeview. It is what I use to completely uninstall all Samsung drivers. I use it to find and remove all the drivers found referencing Samsung. CAUTION...this could cause even more issues than it solves if you remove the wrong drivers or you don't have the drivers specific to your device. I cannot say any specific driver is safe to remove without being able to see and know what they are there for.
Being that you're using a 10.1v Device and I only have personal experience with the 10.1 (no v after 10.1) I may lead you in the wrong direction. One of the reasons I was not going to help, as I stated in a previous post you took as offensive.
But if you wish to continue with my personal advice just post your progress and I'll post help when I can.
I honestly think Misledz would be of more help to you and I'm only going to get in the way trying to help. We're both saying basically the same things using different words.
Whatever the case, keep us updated.
D:...I was wondering what the fuss was about...and then the mega paragraph came Let's relax on this firstly, Jux , Benzo is just trying to help I do agree I end up suggesting the less problematic solution to drain but ofcourse there are other methods to "tame" this wild beast of a tablet. I've only been on the Galaxy Tab scene for less than a week so I'm just giving information based on experience , I hope you don't take to heart what he said, as this is a Q&A thread and almost 70~80% of the threads go unanswered that people purposely post in the development area for quick attention..only to be booted here by the mods (Which I agree they are doing a good job, Kudos), atleast on the positive side, there has been interaction in this.
Moving on to the main deal.
I know you have mentioned the droid and the triangle, but it confuses me as to do you stay in that screen or do you select an option. If memory serves me right, the left, being the droid logo (You select it with the (+) key, which is the right volume key, and navigate with the (-) and select the droid logo) I know you haven't been into download mode because you didn't mention the warning that it gives before you actually get into download mode.
Warning goes somewhere along the lines of proceeding at your own risk with a huge ass triangle telling you the following. In which you need to press the plus key again to confirm. If you did this right, no matter what, lack of driver or such, the PC will recognize the newly open port. Normally Odin won't recognize the tablet despite being in the fastboot menu, but adb will.
I would however suggest trying a different USB port? or another laptop? Normally this RARELY happens but some HP based desktops come with a built in MMC reader which consumes a port of it's own and conflicts with the port Odin requests. You don't really need a high end PC to get this done, just the required files.
And just for reference could you kindly state what OS are you on, Windows __? Seeing as to how you said you aren't that tech savy I would assume it's either Vista (Which has some HORRIBLE USB port management) , If it's XP , XP tends to reserve USB port's for previously plugged devices to avoid the recache or reinstallation of drivers.
I know the vast questions may sound silly, but trust me on this, the least expected situations are what causes the most frustrations
Note: I haven't worked in any Service Center's if ever you're wondering -.- so I do apologise if I sound like one of those Dell service reps.
My sentence was :
"Thank you for your help, but I still don't understand, and this is for every type of device, how can I install driver if the device is undetected by windows?? In the device manager, I don't see any unknown device or something equivalent"
I don't see what's not clear or what let you think that I meant "that can't be done"... Whatever, you made apologizes, I make mine too for the eventual misunderstanding between you and me and yes of course, your help is still welcome if you want to.
So, back to the main problem, I used usbdeview to uninstall all samsung drivers.
After that, I followed this tutorial to enter in fastboot : http://forum.xda-developers.com/showthread.php?t=1064793
That means I :
- Downloaded and install the JAVA SDK
- Downloaded the Android SDK
- Downloaded the USB drivers
- Edited the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf”
And then :
1) Power off your tablet
2) Hold the VOLUME DOWN button and press the POWER button (your tablet will power on and you will see the BACKUP and USB icons)
3) Use VOLUME DOWN to select the USB icon, and then press VOLUME UP to confirm the selection.
4) You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
5) If Windows doesn’t automatically detect the device, go to device manager and find the ‘Fastboot’ device. Right-click and select update driver, choose to manually install and browse to the “<PATH TO ANDROID SDK>\extras\google\usb_driver\” folder.
And there is the problem : any sound when I plug the tablet, windows doesn't detect automatically, so I go to the device manager to look for the "fastboot device" (or another type of device that is not from the computer) and I don't see nothing...so I can't update drivers.
So that is why I asked the question : How can i install drivers if the computer doesn't see the device?
After that, I tried all the things you can read in my first post because I wanted to be as complete as I could in my description so you can have all in your hand to give your advice.
*Cough* before It goes un-noticed my suggestion got blocked by your reply