Related
I'm so mad right now. I had Gingerbread VeggieTab RC1 installed and it was working fine. I selected the reboot option since it was acting kind of wonky what with the market crashing constantly. Upon Startup, I got those 3 frickin' birds looking at me. I've been in this situation before, where I can't access the birds. So I instantly turn to this tutorial here: http://viewsonic-gtablet-for-dummies><.webs><.com/nvflash.htm (remove '><'s)
I've already installed APX drivers so I thought, no big deal, right? Wrong. You see, when I plugin the gTablet, in "devices and printers", it's under 'unspecified' at the bottom, looking like an idiot labeled "APX." Clearly I'm infuriated here. When I try and access nothing happens. You cannot see the gTablet as a storage device.
Then, I thought, "Well, what if I installed the APX Drivers again?" So I opened up device manager, uninstalled 'NVIDIA USB Boot-recovery driver for mobile devices', and then restarted. Good, so now APX is showing up as unsuccessful and looks like it should in the guide. Was I in the clear? Noooo. I installed the USB driver software, ez pz etcetera. It basically got me in a full loop. "NVIDIA USB Boot-recovery driver for mobile devices" shows up again, and it's still displayed as APX.
I'm sorry if I'm acting REALLY distressed but it's very urgent that I fix this in the next 3 hours. I am also aware that it could probably work if I used another computer but this is the only one I got. SO PLEASE, PLEASE, XDA, HELP ME!
I take no responsibility for people deviating from my the procedures I listed. I'll explore some options and will get back to you later.
Have you powered down completely? Sometimes it in apx mode and the tab looks like its off. Hold power for 20 seconds and then plug into computer and then hold power volume down(-). This will insure your PC is reading apx as it becomes available. Good luck
goodintentions said:
I take no responsibility for people deviating from my the procedures I listed. I'll explore some options and will get back to you later.
Click to expand...
Click to collapse
I never said your procedure didn't work, it did. What I am saying is that in your procedure the driver only works the first time you use it and not any time after that. The same driver didn't allow me to use it a second time and the resulting times after that.
Uh...common sense dictates that you only need to install the driver once.
Actually, let me edit my website.
Here is a quick fix for you.
Download virtualbox and run a linux virtual machine on your system. Nvflash actually works better in linux.
Added by edit.
Oh, I see what's wrong. That driver is for apx mode, not the storage device. Goodness. The page even said for nvflash.
If you want your pc to recognize your gtab's internal storage device, you need to have the right kernel. Again, this is all explained on my website.
goodintentions said:
Uh...common sense dictates that you only need to install the driver once.
Actually, let me edit my website.
Here is a quick fix for you.
Download virtualbox and run a linux virtual machine on your system. Nvflash actually works better in linux.
Added by edit.
Oh, I see what's wrong. That driver is for apx mode, not the storage device. Goodness. The page even said for nvflash.
If you want your pc to recognize your gtab's internal storage device, you need to have the right kernel. Again, this is all explained on my website.
Click to expand...
Click to collapse
Oh my god, I was like "what the hell does he mean "you only need to install it once...it's already installed and--" and then I realized it...****. Wow, I feel stupid.
Can I say a few things?
1. Instead of flashing "You only need to update driver once!" can you say "If this is the 2nd time you are doing this, skip to step 3 and then skip to Part II".
2. I realize this is the 2nd time you've corrected me with this, but still. It makes me really frustrated when you talk so condescendingly. I would be happy if you talked to me person to person, thank you. If there weren't dummies like me, your site wouldn't get any traffic
Now then. I ran everything the same. When I boot up, though, the screen gets stuck at the "N" part of tapntap where its loading. Then it just runs for a while, repeats the TAPNTAP screen, and does this several times before it just turns off. Does this mean I really have to repartition
(1) I'll change my website to your words. Thanks for the advice.
(2) This is the way I talk in real life all the time. I've been described as the king of sarcasm. My "girl friend" is a therapist. She's working with me on this issue.
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Added by edit.
You should have seen the original version of my site. It sounded exactly like me in real life. After some emails suggesting I change a few things before I face a class action lawsuit for upsetting a whole class of people (mainly dummies) I started doing some major overhauls based on their suggestions.
3 birds only; NO cwm, NO nvflash!
This is the closest forum I have found to my "issue"
I recently used nvflash to "update" to 1.2 branch with cwm. Worked fine and I installed cyanogenmod 7.0.3 (yes, the one that is meant for 1.2 branch). THAT started up seemingly fine.
Then I did a complete shut down and now I only get to the 3 bird screen. Won't acknowledge anything when I hold the Power and volume + button; when I try to connect to the PC it recognizes the device, but as soon as I try to do the nvflash to either 1.1 or 1.2 builds (I have successfully done both builds with this device; soft bricked before I understood what version I had, I'm a noob) it opens momentarily on the computer screen and shuts down. I have tried this on two different computers. I haven't seen anything that quite addresses this issue; it seems like most people can get into cwm. So... Help?
Couple sidenotes: the 1.1 and 1.2 nvflash folders I have had on my computer DO have cwm included. Also, I am currently following the recommendation to leave the tablet on until the battery is completely dead (and until it won't even begin to start up anymore) if all else fails, then start it up again. It didn't specifically say what that would accomplish... I'm giving it a shot though. Thanks for your help in advance!
drigg07 said:
This is the closest forum I have found to my "issue"
I recently used nvflash to "update" to 1.2 branch with cwm. Worked fine and I installed cyanogenmod 7.0.3 (yes, the one that is meant for 1.2 branch). THAT started up seemingly fine.
Then I did a complete shut down and now I only get to the 3 bird screen. Won't acknowledge anything when I hold the Power and volume + button; when I try to connect to the PC it recognizes the device, but as soon as I try to do the nvflash to either 1.1 or 1.2 builds (I have successfully done both builds with this device; soft bricked before I understood what version I had, I'm a noob) it opens momentarily on the computer screen and shuts down. I have tried this on two different computers. I haven't seen anything that quite addresses this issue; it seems like most people can get into cwm. So... Help?
Couple sidenotes: the 1.1 and 1.2 nvflash folders I have had on my computer DO have cwm included. Also, I am currently following the recommendation to leave the tablet on until the battery is completely dead (and until it won't even begin to start up anymore) if all else fails, then start it up again. It didn't specifically say what that would accomplish... I'm giving it a shot though. Thanks for your help in advance!
Click to expand...
Click to collapse
I have flashed my Gtab more times then I can think of, and also installed many custom mods. The only best solution that I can give you is if you can get into CWM you need to partition the drive (2048-0). Then after that is complete Fix Permissions and mount USB. Connect USB to computer and transfer the mod you are trying to install. Remember that when using a 1.2 mod you have to be using CWM v.3.0.2.8. That's the only one that I would trust in. You can download it off the web.
I hate humble pie... thank you for your hard work, your site helped an old man stop his hair from getting grayer...
Thanks for the "for Dummies" site!
goodintentions said:
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Click to expand...
Click to collapse
I bricked my gtab good, but [code red] pulled me thru. GRACIAS!
"OMG THIS IS SO GREAT!"
"WOW! YOU ROCK AND I WANT TO HAVE YOUR BABIES!"
"THIS IS THE BEST THING EVER!"
"THANKS FOR THIS!"
You saved my a$$.
Thank you SO much
goodintentions said:
(1) I'll change my website to your words. Thanks for the advice.
(2) This is the way I talk in real life all the time. I've been described as the king of sarcasm. My "girl friend" is a therapist. She's working with me on this issue.
(3) You have brickage. You've bricked your gtab. You need to follow my code red to get out of brickary.
Added by edit.
You should have seen the original version of my site. It sounded exactly like me in real life. After some emails suggesting I change a few things before I face a class action lawsuit for upsetting a whole class of people (mainly dummies) I started doing some major overhauls based on their suggestions.
Click to expand...
Click to collapse
THANK YOU!
Thank you thank you thank you thank you.
I can't say thank you enough for your awesome work.
I've created many step-by-step tutorials for dummies on other subjects, so I know it's very time consuming, etc.
Thank you SO much.
my boss bought us new g tablets to use for work, and i brick it the same day i got it!
your code red procedure just saved my butt.
(now, going to try flashing cyanogenMod again! lol)
*edit*
*edit2*
i guess i wasnt holding down the volume button long enough.
once i held it down longer, recovery mode started ok.
Is anyone working on a way to use nvflash to go back to an original firmware (like what was available for many tegra 2 devices)?
The reason I ask is I have a prime that won't boot but is apparently stuck in APX mode. It shows up in my windows device manager as APX. No matter what button combination / time press combination I try, I can't get it to boot. It came this way out of the box, it never once has booted. The charge LED's in the power button work and I can feel it vibe when I hold the power button for a few sec. I also get a long vibe after holding the power button for 10 or 15 sec. Sometimes it shows up in the device manager as MTP device, but I can't get it to take the asus drivers. I always get an error saying the device could not be started.
It looks like there is a nvflash that supports tegra 3 floating around (but only for linux) and the official firmwares are available on the asus website. I have never used nvflash and don't have linux installed, but I'm going to try booting off an ubuntu live CD and see what I can figure out.
look in the Prime Android developement section. answers to your questions are in there as people working on that right now. there's a thread on what u mentioned.
unxconformed said:
Is anyone working on a way to use nvflash to go back to an original firmware (like what was available for many tegra 2 devices)?
The reason I ask is I have a prime that won't boot but is apparently stuck in APX mode. It shows up in my windows device manager as APX. No matter what button combination / time press combination I try, I can't get it to boot. It came this way out of the box, it never once has booted. The charge LED's in the power button work and I can feel it vibe when I hold the power button for a few sec. I also get a long vibe after holding the power button for 10 or 15 sec. Sometimes it shows up in the device manager as MTP device, but I can't get it to take the asus drivers. I always get an error saying the device could not be started.
It looks like there is a nvflash that supports tegra 3 floating around (but only for linux) and the official firmwares are available on the asus website. I have never used nvflash and don't have linux installed, but I'm going to try booting off an ubuntu live CD and see what I can figure out.
Click to expand...
Click to collapse
my advice to you, dont even TOUCH NVFLASH.
if you don't know how to use the search button, dear god, you don't know how to use nvflash. its difficult, and i finally have a solid grip on it.. and i AM a dev
biggem001 said:
my advice to you, dont even TOUCH NVFLASH.
if you don't know how to use the search button, dear god, you don't know how to use nvflash. its difficult, and i finally have a solid grip on it.. and i AM a dev
Click to expand...
Click to collapse
You don't need to be so hostile, this is a friendly forum.
I've seen the thread in the dev section on nvflash. After page 2 the whole thread devolved into people rambling about trying to brute force the encryption key for the bootloader. The only person who had the linux build of nvflash that had tegra 3 support was already pm'd before posting here. Since that thread fell apart into people trying to figure out a way around the encryption key, I figured I'd ask if anyone was looking into flashing original firmware and not modified or rootable firmware. Since I had nothing to contribute yet, I put it in general and not in development.
The part I didn't understand is if flashing an original ASUS firmware was not possible with bootloader encryption.
unxconformed said:
You don't need to be so hostile, this is a friendly forum.
I've seen the thread in the dev section on nvflash. After page 2 the whole thread devolved into people rambling about trying to brute force the encryption key for the bootloader. The only person who had the linux build of nvflash that had tegra 3 support was already pm'd before posting here. Since that thread fell apart into people trying to figure out a way around the encryption key, I figured I'd ask if anyone was looking into flashing original firmware and not modified or rootable firmware. Since I had nothing to contribute yet, I put it in general and not in development.
Click to expand...
Click to collapse
Um maybe that's because you can't use the nvflash without the unlocked bootloader
Sent from my Inspire 4G with ICS!
dsmitty166 said:
Um maybe that's because you can't use the nvflash without the unlocked bootloader
Sent from my Inspire 4G with ICS!
Click to expand...
Click to collapse
Ok, well that is part I wasn't aware of. I wasn't sure if the it was similar to my HTC devices that had locked bootloaders but could be flashed with official firmwares using a zip on the SD. I realized the nvflash method was entirely different but I didn't know if the firmwares that asus provides on their site had the key in them and were possibly usable. But it sounds like that isn't the case.
unxconformed said:
Ok, well that is part I wasn't aware of. I wasn't sure if the it was similar to my HTC devices that had locked bootloaders but could be flashed with official firmwares using a zip on the SD. I realized the nvflash method was entirely different but I didn't know if the firmwares that asus provides on their site had the key in them and were possibly usable. But it sounds like that isn't the case.
Click to expand...
Click to collapse
Unfortunatly, we are at the mercy of Asus right now...
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
Dear All,
I am a newbie on this so please bear with me. I did take the time out to read up on some of the basics before I posted this but I am not familiar with most of the acronyms.
I bought a HTC One X+ with no power button. The seller claimed he bought the phone as is and didnt know if the phone worked or not.
When I received it, I placed a power button and put it on charge. Within minutes the phone loaded with the 3 logo (UK) but to the bootloader screen. I tried all the various options from Hboot, Restart, Restart with Bootloader and Power Down. When I choose HBoot, I get the following error:
sd checking....
Failed to open USB master mode
(preload) Failed to open USB master mode
loading image....
Failed to open USB master mode
Plug off device.
When I try to power down, it simply restarts. When I choose Recovery, nothing works. I just keep coming back to the bootloader screen no matter what I do.
I read the following thread but I didnt understand some of it, eg RUU. I assume this is the type of ROM that is flashed to the phone.
http://forum.xda-developers.com/showthread.php?t=1940194
I have tried connecting phone to the laptop to see if I can see the drive in windows explorer. Laptop recognises the HTC phone in System Device (loaded HTC Sync Manager from HTC website) but it wont recognise the phone's drive. When I try to use the CMD box, i get same issue. It cannot find the phone's storage, therefore I cannot write anything to the phone.
It seems like whoever tried to flash this phone which is on the 3 network made a hash of it, as from reading the above thread, it looks like 3 networked HTC One X cannot be unlocked.
Therefore is it possible to get this phone back to working mode as it was, given the issues I am having.
Any help will be mightily appreciated! :good:
Thanks
Shanni
you got those "errors" because you have the usb cable plugged in too soon.
Lloir said:
you got those "errors" because you have the usb cable plugged in too soon.
Click to expand...
Click to collapse
I have tried it with cable in early and late. It is the same issue
I just realised it is NOT on the 3 network, that is my HTC One X! Cant believe I got that mixed up!
Actually I dont know what network this is on as I cant get out of bootloader!
I have been informed by a friend that the phone needs to be s-off before it can be flashed. How can I do this?
this device DOES NOT need s-off so your friend is talking out of his ass,
the guide to flash ruu's is in the general section
also there is NO WAY to s-off the X+
Lloir said:
this device DOES NOT need s-off so your friend is talking out of his ass,
the guide to flash ruu's is in the general section
also there is NO WAY to s-off the X+
Click to expand...
Click to collapse
Ok cool, I will have a look at flashing ruu's. Will that fix my phone?
shanni10 said:
Ok cool, I will have a look at flashing ruu's. Will that fix my phone?
Click to expand...
Click to collapse
I keep getting signature errors everytime I try a different UK network RUU! I dont even know what this signature error means!
Also how do I know which RUU to use as there are so many different types. Any help will be gladly appreciated
I have followed Hasoon's directions using his utility tool. I have managed to unlock the phone but cant get beyond that.
Every single viable HTC One X+ RUU I use simply doesnt work. I cant access the USB drive to my phone (prob because the person previously never ticked USB Debugging when he/she attempted to root the phone) so cannot transfer the RUU files to my phone.
I have tried to run the original RUU for this phone but it keeps giving me an error. I have no idea what to do next. I have read all the posts on the General Forum for instructions on ADB, rooting, unlocking, RUUs etc.
I would truly be thankful if I can get some assistance here please.
shanni10 said:
I have followed Hasoon's directions using his utility tool. I have managed to unlock the phone but cant get beyond that.
Every single viable HTC One X+ RUU I use simply doesnt work. I cant access the USB drive to my phone (prob because the person previously never ticked USB Debugging when he/she attempted to root the phone) so cannot transfer the RUU files to my phone.
I have tried to run the original RUU for this phone but it keeps giving me an error. I have no idea what to do next. I have read all the posts on the General Forum for instructions on ADB, rooting, unlocking, RUUs etc.
I would truly be thankful if I can get some assistance here please.
Click to expand...
Click to collapse
where in the UK are you? if you are close to me i can sort it out for you. Also you need to relock the bootloader put the device into bootloader > fastboot usb and THEN run the correct RUU
Lloir said:
where in the UK are you? if you are close to me i can sort it out for you. Also you need to relock the bootloader put the device into bootloader > fastboot usb and THEN run the correct RUU
Click to expand...
Click to collapse
I am in Manchester. I have relocked the bootloader but now the phone wont charge. I have seen a post here how to fix that, so I will try that.
I have done the above but I simply do not know what the correct RUU is. How do I even know which is right? I have tried around 10 so far and none have worked.
Fixed It!!!!
I cant believe it! I fixed it!!!!
I accidentally came up on a post here on this forum looking for something else and a member discussed the same problem as me. The reason why he was getting the signature error etc because he had the wrong recovery loaded.
I therefore loaded the latest TWRP version from here (link provided from General Settings) - http://techerrata.com/browse/twrp2/enrc2b
I didnt use Hasoon's recovery as TWRP is user friendly. I relocked the phone, loaded the correct RUU and it worked!
So to summarise this is how I fixed my phone
1. Downloaded Hasoon2000's toolkit from here - http://forum.xda-developers.com/showthread.php?t=2066390
2. Rooted the phone
3. Unlocked the phone
4. Flashed latest recovery file using his toolkit (Your Own Recovery)
5. Loaded the correct RUU - RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed.exe from http://androidfiles.org/ruu/?dir=ENRC2B
NB to know which RUU to use, go into bootloader and you will see the RUU details at the top part of the screen - in my case it was Radio_3.1204.168.32. Also when I tried to run any RUU.exe file it told me the version I had was 1.17.401.1. I searched for it on the android files and found the above RUU to match my RUU. This I guess is the stock RUU.
As a newbie, it can be very tough trying to understand this, but this forum is just awesome!! I am an accountant by profession, and I cant believe I figured how to fix an HTC One X+ by going through this forum! The FAQ has it all - http://forum.xda-developers.com/showthread.php?t=2179337
Thanks to everyone who gave their advice here!
I am now going to try performance tweaks next as I am feeling confident
http://forum.xda-developers.com/showpost.php?p=34021248&postcount=2
Shanni
I followed the instructions provided at the MEGA UNBRICK something thread situated here http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
Anyway, when I hold the volume-up button for 10 seconds, followed by plugging the Onyx with the PC, the system does't detect the device. What can I do now? And is there any alternative method to unbrick a hardbricked phone? I urgently need help
If you installed the drivers and the computer is not reckognizing the device, that's bad news. How did you manage to accomplish that?
aredpanda said:
If you installed the drivers and the computer is nota reckognizing the device, that's bad news. How did you manage to accomplish that?
Click to expand...
Click to collapse
I don't know. And ijust in case if you were being sarcastic, I used the same computer to replace the recovery of this phone.
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
aredpanda said:
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
Click to expand...
Click to collapse
I was using Bliss ROM with BluSpark kernel. Anyway, I downloaded 2 ROMS today, Sailfish OS and the stock H2OS for OPX. I wiped the phone and first flashed the Sailfish OS, but the phone was stuck in a bootloop which only was showing the oneplus logo and the text "Powered by Anrdoid". After that, I entered recovery, and did the normal pre-flash wipe again. This time I flashed the H2OS, but after I gave "Reboot to System", my phone just wont do nor display anything. Hardbricked, dead
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
aredpanda said:
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
Click to expand...
Click to collapse
Yeah, it didn't boot into recovery
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
No, it doesn't
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
I turned off the signature check, W8
If your led doesnt light when your phone is plugged to the wall, this is behind the hard unbricking procedure and your phone is indeed, dead.
Sent from my ONE E1003 using Tapatalk
This issue has been resolved via PM,
Can a mod please close this thread?
No idea what it could be besides corrupt firmware which I've never heard of happening before. The Qualcomm utility should work just fine. Leave it plugged in for an hour or two and see if anything happens
Did you install the qualcomm drivers? If not do it again carefully with driver enforcement off. It works like a charm. Have bricked my device twice as of now and it worked.