[Q] Galaxy tab 10.1v unrecognized by computer - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

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

Related

SH*T - Stuck at 3 Birds, tried NVFlash but APX Drivers not working! READ ASAP PLEASE

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.

Enable USB Debugging from Computer

It is possible to enable USB debug from computer? I need to delete some file from the internal memory that causes the problem. I can't connect through adb at all.
I'm trying to fix my secondary phone (Garminfone) that that loads into desktop, but force close launcher and everything else. The only thing that I can do is connect to the computer for file sharing with the phone.
Thank you in advance.
I'm in a bit of a conundrum, myself...
I am attempting to do this, too, but for a totally different reason.
I am a VZW agent trying to extract contacts for a customer from a Moto. RAZR with a completely non-functional touch screen (no display, no function). Phone boots up fine, no sweat. Stock ROM, no backup :crying:, all of the typical means of transfer have been exhausted.
More or less, the only chance I have at succeeding is to either:
Enable USB debugging through some kind of shortcut or trick, or
Somehow, without USB debugging, figure out the user name for the customer's G-mail account (he has two, and cannot remember/doesn't use the one with all his contacts...)
Wouldn't be surprised if it's simply not possible.... but maybe somebody with a bit more knowledge can let us know! :good:
Edit: Hmm, not possible to run adb from the bootloader, but you can run Fastboot commands. None of those seem to be of use for these purposes though...
as mentioned by PhantasmRezound, It's not possible, However. adb is enabled in most recoveries. Also If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
or
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
There's always a way.
Thanks for the input...
I appreciate the feedback, but the way I read it... it's either not going to help in this situation, or it's too technical for a noob such as myself and I'm in over my head
If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
Click to expand...
Click to collapse
Customer's phone is completely stock. Hope I'm following along correctly, but I don't think this is possible without having something like ClockworkMod and pre-existing root access?
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
Click to expand...
Click to collapse
Never really tried this... but, I suspect, this won't work... not only does the touch screen not work, but the display is black.
I suppose it could be possible in combination with HDMI-out... but since the HDMI has never been set to "mirroring," I cannot simply plug it in and go (the best and only result I've gotten in this case is the red "M" logo on the screen...)
I would have given up on this hours ago, but it really bothers me when I can't figure out how to do something that appears to be so fundamental and simple...
Thanks for the inputs :good:
jad57pitt said:
Customer's phone is completely stock. Hope I'm following along correctly, but I don't think this is
possible without having something like ClockworkMod and pre-existing root access?
Click to expand...
Click to collapse
Well, I was thinking about this, and I think you can do adb in a stock recovery, should be able to create a backup image with the right software. It all gets a little hazy and wolly on techinical details, so I'm afraid I can't help anyone there.
jad57pitt said:
appreciate the feedback, but the way I read it... it's either not going to help in this situation, or it's too technical for a noob such as myself and I'm in over my head
Click to expand...
Click to collapse
And you're a noob , I fully understand that my casual, off the cuff, do a,b,c etc reply assumes a lot of technical knowledge, If it's not your phone man, don't stress it too much ..... Just hand it back to them look blankly into the middle distance while shaking your head.....use the following phrase " Nah man you've F*ed this up good, did you not sync it up with your google account at anytime "
Sorry man, I'm drunk, probably shouldn't be at this keyboard now
trevd said:
as mentioned by PhantasmRezound, It's not possible, However. adb is enabled in most recoveries. Also If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
or
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
There's always a way.
Click to expand...
Click to collapse
Unfortunately, Garminfone is a piece of garbage, lol. There's no custom recovery for it. There is nothing I can do now, I guess. I can't get into fastboot or anything because every time I try adb or fastboot it would not recognize the device.
wolftou said:
Unfortunately, Garminfone is a piece of garbage, lol. There's no custom recovery for it. There is nothing I can do now, I guess. I can't get into fastboot or anything because every time I try adb or fastboot it would not recognize the device.
Click to expand...
Click to collapse
If nothing else, you can do a Factory Reset. You'll lose all data but it will be running again.
Make sure the phone is charged up since this will take a while.
With the phone off, hold down left on the d-pad as you power it on. It will show "Wipe User Data" and then you can let go of the buttons. Just leave it for an hour or so, it will go about wiping and restoring system files from it's own recovery partition.
Also, random Garminfone blog with interesting entries to read while waiting on your phone lol. The person started to develop a port for CWM:
http://mygarminfone.blogspot.com/
PhantasmRezound, I've done tons of wipes but no luck and I'm familiar with the website you posted. Everytime I wipe, I get force process com.android.setupwizard stopped unexpectedly on the phone.
@wolftou
Ok.... A couple more tricks to try for your specific device and then I'm all out of ideas plus it's kinda getting away the original question/topic
1 Android Safe Mode:
Android does have a safemode, exactly the same idea as windows safemode, only needed apps are loaded. This might let you remove the troublesome app.
How to get into it on your device? I have no idea and from my limted research ( google as always ), it appears to vary by manufacturer and probably device. I have booted my tablet into it a couple of times by accident but never really stopped to figure out how, that's not important anyway Just I can confirm this mode exists ( In some androids at least ).
2 Flashing an alternative rom:
Have you tried flashing a different rom? I'm not sure of your model number so I don't whether this is relevant to you but have a look at this thread it looks like you can trigger an update using a sdcard swap trick....
I'm thinking about buying one myself now... just to see what's possible with them, fortunately ( for my wallet at least ) they are not available in the UK and I've got plenty of things to fill my Android addiction for now :laugh:
all answer not similliar the question
across tablet 8"
i have 8 inc across tablet,i cannot open my tab,,i think the operating not found,,how can i install it..because i cant open the system ,,unit help me pls...
actually i got canvas doodle 2 with no external sd support nd my usb debugging mode is off nd no backup is there in my phone...
but there is adb sideload...is there any way to enable usb debugging? and my phone is rooted and it is stucked at boot logo
Alternative usb debugging...
Hey my phone is stuck in an bootloop.....is there anyway to enable usb debugging even tho i cant get into the phone
My lenovo vibe s1 is showing black screen
I tried rooting my phone by the steps given by your site and now my phone is showing black screen. i tried pressing volume buttons and power button still it is not working. so when i am connecting my phone to computer it gets connected for 1 min and disconnects and again connects after 1 min. so is there any possible way that i can send my phone to USB debugging through computer.
I need use my samsung j2 mobile on pc bcoz my mobile display is not working.
usb debugging off
Keyah Cort said:
Hey my phone is stuck in an bootloop.....is there anyway to enable usb debugging even tho i cant get into the phone
Click to expand...
Click to collapse
mine too... how to enable usb debugging? please help...
trevd said:
as mentioned by PhantasmRezound, It's not possible, However. adb is enabled in most recoveries. Also If the device is unlocked ( and you can flash custom recoveries ) in any way you can flash a custom recovery, back up the boot img. pull that off the device or simply put the sdcard in your computer with unpack that, edit the init.rc to start adb. and reflash it with fastboot not quiet what your after but might do the trick.
or
With the non functioning touch screen issue, If the device acts as a usb host, plug a mouse in and away you go
There's always a way.
Click to expand...
Click to collapse
Can you create a step-by-step tutorial? I have a LG Leon. Stock. Bluetooth/Wi-Fi disabled. My Google account won't accept. I've been trying to find ways to enable "Developer Options", "USB Debugging" just so I recover access. ADB and most of the programs I've used required USB Debugging, or wireless access.
Hello Everyone, I hope the you can help me with my request, How can I enable the USB debugging mode in android vers. 2.2.2 to 2.3.4
I really had a hard time since my Huawei Ideos s7-105 screen had been broken. I am not sure if the USB debugging was enabled. I have a really have a good reasons why I need to recover the files from my device.
Hoping for your kind response and help.
Monsterkid09
I'm sorry. I'm in doubt. I have a problem: Navon predator 10 tabs have dropped my gmail account. Adb debug off (or something you see 1-2 programs see something in adb mode but only in device info.If anything else i want always say do not connect. Very strong frp protection.What can I do?

Recover from the dread QHSUSB DLOAD

Lately my HTC One shut off while typing on it and it was dead.
Holding power for 10 seconds (and any of the combination with the volume buttons) did not help.
And when you connect it to the power does not even had the red led indicating that is charging.
If you connect it to a PC you get prompted to install the QHSUSB_DLOAD drivers.
So the phone is dead but not really completely dead.
Clearly that QHSUSB_DLOAD is a Qualcom hook that could be use to debug and probably re-flash the phone. The question is what is this tool and how do you use it?
I think there is some sort of standard way to recover across phone (maybe not all with a Qualcomm but I am sure that the protocol is the same among a few processors).
There are a few examples out there:
[UNBRICK] HTC Unbricking Project - http://forum.xda-developers.com/showthread.php?t=1627886
DLOADTool - https://github.com/posixninja/DLOADTool
http://xiaomi.eu/community/threads/ultimate-cure-to-the-qhsusb_dload-of-mi2-s.20567/
And a lot of info about HTC internal here: http://tjworld.net/wiki/Android/HTC/Vision
So I wonder if anybody here has some idea about the tools and how to use to resurrect HTC phones and in particular the HTC One (M7).
Camicia said:
If you connect it to a PC you get prompted to install the QHSUSB_DLOAD drivers.
So I wonder if anybody here has some idea about the tools and how to use to resurrect HTC phones and in particular the HTC One (M7).
Click to expand...
Click to collapse
First: Wrong thread. Mod will likely move it to Q&A. (Hopefully not before I'm done trying to post this to help you out)
This normally occurs if you have a modified hboot meant for downgrading your device via RUU or some-such.
Best solution is to plug it in to a Windows 7 (32-bit) machine, and download an RUU.
If you hold the power-button for 15 seconds or so, you should feel it "bump". Basically, it was in a broken fastboot mode and you just put it into RUU mode, but with no on-screen indication of it.
Running the RUU at this point should work but remember: Whenever the RUU utility states "Waiting for Bootloader", you will need to hold the power-button in until you feel the bump again or it moves from "Waiting for bootloader" (should be around 15 seconds, every time).
I've made multiple full conversions on my device and run into this problem periodically before I started flashing rumrunner's hboot prior to conversion.
Hope this helps.
For future reference - some helpful links:
(added to sig)
I cannot feel and "bump" on the phone even if holding the power button actually cycle the phone QHSUSB DLOAD.
No luck. It does not work.
BTW, some of the link in your signature linked to files that Chorme marks as Malware.
Camicia said:
I cannot feel and "bump" on the phone even if holding the power button actually cycle the phone QHSUSB DLOAD.
No luck. It does not work.
BTW, some of the link in your signature linked to files that Chorme marks as Malware.
Click to expand...
Click to collapse
Most of those links are XDA. The others are HTC, RumRunner and such.
By "bump" I meant a vibration. If you are not getting that and the RUU is not detecting your device, I really don't know what else to tell you. This is what has worked for me in the past with that issue (running the RUU with the device plugged in and on and when it says "waiting for bootloader" holding the power button until the RUU continues.)
Sorry I couldn't be of more help.
PhoenixPath said:
Most of those links are XDA. The others are HTC, RumRunner and such.
By "bump" I meant a vibration. If you are not getting that and the RUU is not detecting your device, I really don't know what else to tell you. This is what has worked for me in the past with that issue (running the RUU with the device plugged in and on and when it says "waiting for bootloader" holding the power button until the RUU continues.)
Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Yes, I got what you meant. It seemed worth to try anyway.
The link with the malware was one on rootzwiki. I woudl not be surprise if somebody concatenate a trojan with a RUU.
Camicia said:
Yes, I got what you meant. It seemed worth to try anyway.
The link with the malware was one on rootzwiki. I woudl not be surprise if somebody concatenate a trojan with a RUU.
Click to expand...
Click to collapse
Well, it's been used by countless people with no reports of any trojan or otherwise. I've used it several times myself (I use it every time I convert to get back to T-Mobile stock and make sure OTA's work before moving on to the next conversion). The only reason it isn't a thread here for it is due to politics I try not to get involved in. Just trying to help folks out.
As always though, I do strongly suggest that everyone use their own judgement and that they do not do *anything* with their devices that makes them uncomfortable or that they feel may have unintended consequences.
That said; I use chrome exclusively and haven't seen any warnings from it. Even Google Search isn't reporting issues with the link. If I were you I would check and make sure that you don't have any "helper objects" like toolbars or search-assist add-ons installed as those sometimes hijack page-requests.
Regardless of all of that, I am sorry I could not be of more help. The only time I've seen the DLOAD issue - the above steps fixed it. Seems my experience is not enough to solve this one. Hopefully someone else can pitch in. Best of luck!
Thread closed as duplicate/triplicate/quadruplicate of QHSUSB_DLOAD - What is the protocol?. Please continue the discussion there.

Moto X (2014) Model: XT1092, Error: Failed to validate system image

So my Moto X (2014) which is around 20 months old just up and started giving this problem. When I try to boot it, it just goes to the fastboot screen and gives the error: "Fastboot reason: Failed to validate system image". The usual fastboot options like Normal Power up, factory, recovery, etc show up, but no matter what I select it gives the error: "Failed to validate system image. Boot up failed". I tried to attach some images, but being a new user was unable to link them.
Now the thing is, I am a complete noob at this stuff. So all I did was try to use adb sideload to try and re-flash the official ROM. But the adb command window doesn't seem to detect my device. Also, I'd just like to add, when I connect my phone to the PC, the standard windows sound of a USB being connected is heard, I don't know if that means anything, but I just thought I'd put it out there.
So obviously, the next thing I did was approach the service center. After a days inspection, they said, and I quote "There is an issue with the motherboard and/or PCB". I don't know what a PCB is. To fix the issue it's gonna cost me INR 12500, which is almost as much as a new phone. When I asked if they had tried re-flashing the ROM, they didn't seem to understand what I was saying, which made me a little skeptical. So, I came home and tried with the adb again, without any luck of course. Only this time when I connect my USB, I get a new error: "Fastboot reason: UTAG 'bootmode' configured as fastboot. USB connected".
Is there any way to fix this?
Or do I use it as a door stopper?
Thank you for any help in advance.
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
es0tericcha0s said:
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
Click to expand...
Click to collapse
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
souamguha said:
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
Click to expand...
Click to collapse
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
es0tericcha0s said:
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
Click to expand...
Click to collapse
Okay, so I followed the thread exactly. But I can't get past the first step. When I type in "adb devices" on the adb command window, nothing shows up on the device list. (Note: My phone is already in the AP fastboot mode. I don't know if adb is supposed to detect it when it's in that mode).
But, Motorola device manager is able to detect my phone. When I run Motorola device manager with my phone connected, it searches for "repair software" for a while and then gives a pop-up saying "Your software is up to date" (and the name of the ROM installed).
Any further advice?
Thanks.
Use the fastboot method since you're in the bootloader. The adb is only mentioned there as an alternative way to get to the bootloader. Since you are there, skip that step.
Sorry for the late reply. But turns out the Boot IC of my motherboard was faulty. Whatever I did, it would always get stuck on the fast boot screen. Replaced my motherboard and now it's all good .
Thanks for all the help guys.

Stuck in setup with missing files and can't get stock ROM to flash

I beat my head against this for about eight hours yesterday and am at my wit's end. Thanks in advance for any help.
The short version: After rooting my Blue VIvo 5, installing a few apps and setting Nova Launcher as my launcher, I started getting some errors. Apps would fail mysteriously or not launch at all. Reinstalling the apps didn't help. I tried to take an OS update that the phone said was available, but when I tried to update it said the system was damaged and I couldn't install the update.
Well, I thought naively, I'll just remove all my user data and start over. That will restore the original ROM and I'll just start over, right?
BIG mistake.
Now when I try to start up my phone the sequence goes like this:
1. I get a popup that says "Unfortunately, Carefree Launcher has stopped."
2. After clearing that popup I can choose my language.
3. Next I go tot he screen where I choose my wireless connection. Choosing the connection works, but the next screen where I put in my password only allows me to speak - there's no keyboard option. The only time during the process I really laughed was when I saw what Google's voice recognition software tried to enter for the wifi password.
4. I managed to get the password entered by using the OTG dongle and a USB keyboard. After that, though, it goes to the "Checking for updates" screen, at which point it tells me "Unfortunately, Google Play Services has stopped." Then it loops back to the "choose your network" screen.
5. Lather, rinse, repeat.
I managed to get TWRP installed and running, but the stock ROM file I found on another thread (BLU_V0050UU_V09_REPAIR.zip) won't install. SP Flasher (which I also tried) throws a message about a mismatched baseband unit of some kind, and TWRP says there's a file called META-INF/com/google/android/update-binary missing from the archive.
So here I am, asking the community what I can do short of laying out $200 for another phone. I might be able to install the AOSP or CM12 ROMs that are in this forum, and I might do that if I have to replace the phone anyway, but if there's a way to restore the phone to its initial OOB state, I would love to know how to do it.
Again, thanks for any help you can give me.
Update, 16 hours later: I had a flash of inspiration this morning. Since it looked like at any rate I was going to have to get another phone I went ahead and ordered the replacement for same-day delivery. It arrived this afternoon, I unboxed it, set it up and backed it up with "adb backup". Then, I tried to restore the backup onto the bricked phone.
You guessed it. I never saw a notification that the backup was loading. It was the same wifi network, check for updates, broken google play loop again.
So unless someone has a brilliant idea as to how to restore the original firmware, I am going to keep the old bricked phone around and try installing aosp or cm12 on it, whichever looks like it's further along. Maybe both. Why not?
Anyway cheers.
Do you not know how to use SP Flash Tool?
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
victorvscn said:
Do you not know how to use SP Flash Tool?
Click to expand...
Click to collapse
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
victorvscn said:
Download the original rom + SP Flash Tool from elsewhere in this forums and flash it. The one for the Gionee S6 or A55 slim on the Marshmallow thread will do. I think someone has posted the original vivo 5 ROM somewhere as well.
Basic steps are open SP Flash Tool.
Load the scatter file (comes with the rom). This will fill a lot of fields in the flash screen (boot, recovery, logo, system, userdata, etc.).
Do not change anything. Click "Start"—this will wipe your phone. If you don't want it wiped, disable the "userdata" field.
Connect your phone properly turned off.
It should detect your phone right away.
Wait for the flash to end.
Disconnect your phone and turn it on.
Should boot alright.
If it doesn't detect your phone, see in Device Manager if your phone is properly recognized. If it's not, download the MediaTek PreLoader USB VCOM drivers.
Click to expand...
Click to collapse
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
NerdFire said:
Thank you for your reply. In answer to your quesiton: Maybe not. Everybody starts somewhere, and while I have quite a few years of experience in desktop computers, I'm still learning the world of Android. I've flashed quite a few Kindle Fire tablets (that's the origin of my user name, 'nerdfire') but this has been my first experience with a phone.
Click to expand...
Click to collapse
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it.
NerdFire said:
I've got SP Flash running, but it's the Linux version. which I think is the same, as Windows except that it looks like there's a "Download" button rather than a "Start" button. Unless I'm missing something, which could easily be.
I followed the directions above, not checking "userdata", and hit "Download." No response from the program for over 30 minutes. I eventually found the timeout setting, lowered it to 2 minutes, and ran the program from a console window. The console output indicated that SP Flash was finding the proper USB port, but then nothing. No communication with the phone and the program eventually timed out.
It could be a lack of drivers. Linux comes with drivers for most common USB devices baked in, but this might not be one of them. Thanks for the hint - I'll check when I get home later tonight.
Again, I appreciate the help.
Click to expand...
Click to collapse
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
victorvscn said:
Sorry about that, mate, I came out rather bluntly for some reason. Just wanted to ask whether you'd had any experience with it..
Click to expand...
Click to collapse
No worries, I didn't take offense.
victorvscn said:
I have no experience flashing with Linux, but that definitely looks like lack of the right drivers. Maybe following this tutorial will work for you: https://forum.xda-developers.com/ge...torial-how-to-setup-spflashtoollinux-t3160802
The thread says you need to know the specific way to boot up after connecting the cable, depending on the phone. On the Vivo, my experience is that you don't need to press anything, just connecting the cable with the phone powered off will do. However, if you happen to brick your phone by flashing something wrong, or interrupting a flash, you'll need to press volume down upon connecting the cable.
Click to expand...
Click to collapse
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
Good to hear!
NerdFire said:
No worries, I didn't take offense.
I did a little digging and won't go through all the gory details, but the long and short of it was, after removing a package in my Linux distribution that was interfering with accessing the serial port, I was able to flash the stock ROM onto the phone. So I am good to go. Plus, now I have a good idea of how to start over again if necessary
Thank you again so much for your help.,
Click to expand...
Click to collapse
where can I find the stock Rom ? Can you Share link please?

Categories

Resources