Hey whats up guys everything has been going well using qdl tool . Up until the driver installation
It keeps Saying
Windows found software for your device but encountered a error while attempting to install it and under it . just wanted to know if anyone is having this problem .
Qualcomm Hs- Usb Modem 9002
Running windows7 64 bit . I also followed the 64 bit guide and everything so im not sure why i get this message
I didn't have any problems with it. I followed the 64 bit guide to a T, then I installed the dell drivers before I used the QDL tool. I tried it before I installed the Dell Drivers and all I got was errors. After install of the drivers it went off without a hitch.
Dell Streak 2.2 w/DJ Steve 1.5.3
Moving to Q&A Section
Give this a try.
If you followed the instructions on streakdroid, and still having an issue try this:
Open the CMD window as administrator (shift+ctrl+enter)
then enter: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS (NOTICE there are 2 "D's" this is not an error, and is what is required for Windows 7)
after successful completion enter: bcdedit.exe -set TESTSIGNING ON (not case sensitive)
after successful completion close the window, and reboot. This should clarify your issue with the driver problem. Windows 7 sometimes has an attitude, this worked for me If not, please let me know.
demonchild1786 said:
Hey whats up guys everything has been going well using qdl tool . Up until the driver installation
It keeps Saying
Windows found software for your device but encountered a error while attempting to install it and under it . just wanted to know if anyone is having this problem .
Qualcomm Hs- Usb Modem 9002
Running windows7 64 bit . I also followed the 64 bit guide and everything so im not sure why i get this message
Click to expand...
Click to collapse
One more thing, make sure the driver you select reads: Qualcomm HS-USB Diagnostic 9002 There is also a non diagnostic version that will cause errors as well.
Srry about that still tring to figure this forum stuff out, please excuse my noobish behvaior
ARHMogul said:
If you followed the instructions on streakdroid, and still having an issue try this:
Open the CMD window as administrator (shift+ctrl+enter)
then enter: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS (NOTICE there are 2 "D's" this is not an error, and is what is required for Windows 7)
after successful completion enter: bcdedit.exe -set TESTSIGNING ON (not case sensitive)
after successful completion close the window, and reboot. This should clarify your issue with the driver problem. Windows 7 sometimes has an attitude, this worked for me If not, please let me know.
Click to expand...
Click to collapse
Yeah it worked really well actually Thanks a million . No im stuck trying to qdl to recongize its there. Im trying all the usb ports and it keeps saying no "connection"
demonchild1786 said:
Yeah it worked really well actually Thanks a million . No im stuck trying to qdl to recongize its there. Im trying all the usb ports and it keeps saying no "connection"
Click to expand...
Click to collapse
just to verify: are you removing the battery from your device, waiting one min, opening up QDL Tool, pres and hold the volume up button and plugging in your device in. Then it should find your device.
If thats what you are doing then I dont know what else to tell you well.... other than good luck!
You were right i didnt pay attention to actually selection Qualcomm HS-USB Diagnostic 9002. i firsty selected Just 9002. By the way the froyo i have is pre release right ? So its my best interest to update with dell right?
demonchild1786 said:
You were right i didnt pay attention to actually selection Qualcomm HS-USB Diagnostic 9002. i firsty selected Just 9002. By the way the froyo i have is pre release right ? So its my best interest to update with dell right?
Click to expand...
Click to collapse
It is the pre-release version yes. In terms of which version you choose is up to you. If you are looking for mo user customization then I would suggest Steves ROM's but if your looking for a simple froyo device the Dell 318 ROM works great as far as i can tell. Ive been using the Dell ROM for about three days now and have ad no issues to report. You just have to decide what suits you best.
ARHMogul said:
It is the pre-release version yes. In terms of which version you choose is up to you. If you are looking for mo user customization then I would suggest Steves ROM's but if your looking for a simple froyo device the Dell 318 ROM works great as far as i can tell. Ive been using the Dell ROM for about three days now and have ad no issues to report. You just have to decide what suits you best.
Click to expand...
Click to collapse
Cool makes sense. im only having one last problem . My device no longer has the 3g display signal and i cannot check or connect to the internet besides wifi. I have enabled data connection within the phone settings to no avail
demonchild1786 said:
Cool makes sense. im only having one last problem . My device no longer has the 3g display signal and i cannot check or connect to the internet besides wifi. I have enabled data connection within the phone settings to no avail
Click to expand...
Click to collapse
Thats odd, I had no issue with data.. It displayed the "H" vs 3G, but thats AT&T's new network.. I would try to do a factory reset and see if that helps. If not let me know, ill do some lookin for you
ARHMogul said:
Thats odd, I had no issue with data.. It displayed the "H" vs 3G, but thats AT&T's new network.. I would try to do a factory reset and see if that helps. If not let me know, ill do some lookin for you
Click to expand...
Click to collapse
Yeah that worked. Thanks ! loving the built in flash lol , its a huge step from dino 1.6
demonchild1786 said:
Yeah that worked. Thanks ! loving the built in flash lol , its a huge step from dino 1.6
Click to expand...
Click to collapse
Glad to hear you got it working! Enjoy your "all new" Streak
Adb fastboot time out
I AM HAVING TROUBLE WITH THE ADB...it starts to run and by the time it gets to about 47.35 seconds well it just has the error timeout ADB..how do i fix this
i am trying to up grade to the 2.2
i am using a windows vista 32bit please help as soon as possible...thank you
email me your walk through and information on how you all got this to work i would be so very thankful...
i can't even watch a Movie on my DELL STREAK....still caveman 1.6
help plz
ricanpone said:
I AM HAVING TROUBLE WITH THE ADB...it starts to run and by the time it gets to about 47.35 seconds well it just has the error timeout ADB..how do i fix this
i am trying to up grade to the 2.2
i am using a windows vista 32bit please help as soon as possible...thank you
email me your walk through and information on how you all got this to work i would be so very thankful...
i can't even watch a Movie on my DELL STREAK....still caveman 1.6
help plz
Click to expand...
Click to collapse
Try a different USB Port on your computer.. The tutorial as Streakdroid.com explains this and even has a bulletin just for that time frame There walk through is as good as it gets I assure you. Just take a look at the tutorial and the FAQ section. Good Luck!
Trouble with voice comands and blue tooth
I used the QDL and upgraded to 2.2 AT&T and I can't get my voice commands to work. What happened to nuance? after I try my voice commands it also locks up and I have to reboot. Should I try to reinstall my drivers and 2.2? Any help would be appreciated. Thanks
ARHMogul said:
If you followed the instructions on streakdroid, and still having an issue try this:
Open the CMD window as administrator (shift+ctrl+enter)
then enter: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS (NOTICE there are 2 "D's" this is not an error, and is what is required for Windows 7)
after successful completion enter: bcdedit.exe -set TESTSIGNING ON (not case sensitive)
after successful completion close the window, and reboot. This should clarify your issue with the driver problem. Windows 7 sometimes has an attitude, this worked for me If not, please let me know.
Click to expand...
Click to collapse
Hey i just wanted to know if you know the command to enable driver verification aagin ?
Totally rediculous question here but what the hell is the qdl tool and where is it? I find all kinds of stuff on how to use it but nothing on what or where it is... thanx.
I am now a proud owner of an AT&T Streak w/2.2. OH Happy Day!!!
Once I got the proper drivers installed it was quite seemless and easy to do. the video like tutorial was well laid out. and very simple to follow. I sure hope those Geico Cavemen aren't on this forum 'cause it was so easy one of them could do it!!!
Related
ok i have been all over the place trying to figure this process out. i found everything that i believe that i need and have saved all info. well i did not get far.
here is what i have done so far. i have dl 1.9.0 from dj steve i have created my install .txt file. i tried the fast boot and thats as far as i get. i try the find driver and there is not even a google, inc folder to choose. if possible i would like to get someone on some sort of chat be it yahoo or whatever that could take the time to walk me through this from start to finish. i know that this is a rather large task but if i could get it i would be greatful.
here is what i am working with.
at&t dell streak 5
android version 2.2
build number 14844
i have taken everything back to off of sd card like the rcoverey and install and 1.9.0 files.
that is all that i know so far and sorry if i am not on the right track but with all of the write ups online it is almost impossible to figure out which is best and easiest ect... well thanks to everyone for the help whether i get any or not.
Start here
Quickest way to ROOT access is to
Hold your streak above your head with both hands
Close your eyes
Shout out loudly " OPEN SESAME " (must be yelled out loudly or will not work)
Then with all the energy summoned
SMASH YOUR PHONE INTO THE GROUND
CONGRATS NOW YOU SHOULD BE ROOTED WITH SUPER USER
thanks marvin for the link i already have been all over that and no luck. i cant even get into fastboot. when i try to bring up the add driver and go to select from list google inc is not there. i have gone over every step a hundred times and dont know what it is. if anyone knows where i can dl the driver file that would be awesome. but i have read other places with guys having the same issue and they dont get any help either so, i will just hold off.
also i am trying to do this on windows 7 with x86 i dont know if this could be the issue. if so i have a vista laptop also if that would be more useful. just looking for info,
and yes i have vista in test mode
jeeper26 said:
thanks marvin for the link i already have been all over that and no luck. i cant even get into fastboot. when i try to bring up the add driver and go to select from list google inc is not there. i have gone over every step a hundred times and dont know what it is. if anyone knows where i can dl the driver file that would be awesome. but i have read other places with guys having the same issue and they dont get any help either so, i will just hold off.
also i am trying to do this on windows 7 with x86 i dont know if this could be the issue. if so i have a vista laptop also if that would be more useful. just looking for info,
and yes i have vista in test mode
Click to expand...
Click to collapse
I also use windows 7 x86, follow the instruction on streskdroid in how to setup qdltool, when you get to installing certificates do not worry if you can nnot install it just follow the next instruction. Dont forget to do that in test mode.
Sent from my Dell Streak using XDA Premium App
ok i think that i am finally on the right track. i have down loaded and run so many new programs that it is hard to recall which did what but i do know that one downloaded the google, inc folder so i am sure that i will be able to put in the drivers to allow fastboot. i am currently waiting on repairtool to dl so that i can finshish following the qdl tutorial and will post with update.. thanks guy
jeeper26 said:
. . . . i am currently waiting on repairtool to dl so that i can finshish following the qdl tutorial and will post with update.. thanks guy
Click to expand...
Click to collapse
There is no reason to actually run the QDLTool on your phone because the ROM you have is later than the one it will install. But the download will include the drivers, unzip it and look in the driver folder for what you need.
just finished with the streak droid 1.9 upgrade and first power up is coming up now mu phone just opened with a nice looking streakdroid logo by djsteve. thanks again to everyone that helped me out it is most appreciated.
how can i be sure that my install.txt file took? want to make sure i got my volume boost and density
ok scratch that ^^^^^ it took
lets say i wanted to modify that txt file on the root to make changes do i have to go back and upgrade through clockwork or will it take automatically with a reboot?? thanks guys
ok well to answer my question lol post whoreing.
i just pwrd on with the vol keys held went to update via .zip again. this was after changing the txt file and the changes took it also saved all my info and setting so i didnt have to worry about setting up all my email and stuff like that again. starting to get the hang of this.
hey all! great forum... former se x10 mini user... getting my atrix today!
my main question is: i want to install greyblur after rooting but there are always warnings about not installing it on the BELL version... yet i see, via their signatures, that many bell users have it installed... the guide for greyblur does not have specific instructions for bell, just has big warning in red saying not to install it on bell!
so how do i get it working?? what do i need? i'm pretty handy with android, so no need to have crazy detailed help...
thanks everyone! looking forward to learning more and more about this great device!!
ryan
watchyourbreath said:
hey all! great forum... former se x10 mini user... getting my atrix today!
my main question is: i want to install greyblur after rooting but there are always warnings about not installing it on the BELL version... yet i see, via their signatures, that many bell users have it installed... the guide for greyblur does not have specific instructions for bell, just has big warning in red saying not to install it on bell!
so how do i get it working?? what do i need? i'm pretty handy with android, so no need to have crazy detailed help...
thanks everyone! looking forward to learning more and more about this great device!!
ryan
Click to expand...
Click to collapse
See the thread called "SBF/root/deodex 2.1.1 SBF" or something along those lines (in this forum). In order to get greyblur/GingerBlur working on a bell phone you have to flash an international SBF file. Right now the most current is 2.1.1, a generic SBF (leaked from France). Just be warned that flashing this will void your warranty. However, it hasn't caused any issues itself and wont CAUSE anything on your device to fail at all, if you get into trouble its most likely just bad luck with hardware and if you REALLY need to return your phone there is a general way to make it seem like you've gone back to stock, that you can do with the help of forum members here if needed.
Not trying to scare you off, I've done this myself. I'm just making sure you understand the risks. Hope this post helps you understand what you're getting into and where to go for further info.
Also, this should be in Q&A section, not dev.
Sent from my MB860 using XDA Premium App
not scared at all! thanks for the PERFECT response!
Moved to proper forum.
ok, i'm going through the steps but for some reason the x64 drivers won't install (yes i have 64-bit windows.). says this:
"The system administrator has set policies to prevent this installation."
i assumed they weren't required.
nothing happens when i run rds before plugging in phone. when i reboot the phone, i see the rds protocol message, i run rds on my pc, plug in the phone and nothing happens....
thoughts?
I know nothing about windows sorry bruvva
I do know that once you are running a p rom pretty much everything becomes compatible
Sent from my Googletron
watchyourbreath said:
ok, i'm going through the steps but for some reason the x64 drivers won't install (yes i have 64-bit windows.). says this:
"The system administrator has set policies to prevent this installation."
i assumed they weren't required.
nothing happens when i run rds before plugging in phone. when i reboot the phone, i see the rds protocol message, i run rds on my pc, plug in the phone and nothing happens....
thoughts?
Click to expand...
Click to collapse
well the drivers do need to be installed, you can find the necessary drivers in an executable package here although i can't tell you whether admin restrictions will block that too. might be easiest to find a PC where you can do stuff as an admin depending on your current system's configs.
once drivers are installed your PC will recognize device when in RSD mode.
I would assume that the login on your comp is not set as an administrator. You have to be logged on as an administrator to modify system files or drivers in windows.
You could also try right clicking the usb driver installation exe and choose "run as administrator".
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
Hey
Regarding the Win 64 driver, I had the same issue, until I realised the link given in the thread about 2.1.1/Greyblur for the driver lead to a corrupted file (~ 500 kb) even using a download manager. I downloaded them from elsewhere (Motorola Website) and the error message disappeared without having anything else to do.
Hope that helps!
Guillaume
Actually got the whole thing going a while back... sorry for not checking back!
I am officially enamoured by this phone......... the start of a beautiful and complex relationship ...
And yeah, I suspected that it had something to do with corrupt file... tried a few diff sites but all seemed the same... eventually tried a diff usb port and it worked...
Sent from my MB860 using XDA App
Hi all, I have problem with nokia care suite,
i follow the tutorial for debranding lumia 800 (I have Tmobile DE) but when it comes to step "click programming and choose refurbrish" i can't do that =( because if i click the programming tab it doesn't do anything =(
i think i did everything correct, i downloaded the fw version changed the product code, the grey cube button turned to green, also the program recognize my phone and shows "USB1-RM801" but i can't flash it....
also i tried every usb ports on my computer
p.s. I use windows 7 64bit and original usb cable.
I hope someone can help me
eccomania said:
Hi all, I have problem with nokia care suite,
i follow the tutorial for debranding lumia 800 (I have Tmobile DE) but when it comes to step "click programming and choose refurbrish" i can't do that =( because if i click the programming tab it doesn't do anything =(
i think i did everything correct, i downloaded the fw version changed the product code, the grey cube button turned to green, also the program recognize my phone and shows "USB1-RM801" but i can't flash it....
also i tried every usb ports on my computer
p.s. I use windows 7 64bit and original usb cable.
I hope someone can help me
Click to expand...
Click to collapse
What error are you getting?
Have you tried using Recover instead of Refurbish?
anseio said:
What error are you getting?
Have you tried using Recover instead of Refurbish?
Click to expand...
Click to collapse
the problem is i don't get any errors or anything, the programming button doesn't work at all, when i click nothing happens, not even opening the refurbrish or recover droplist...
eccomania said:
the problem is i don't get any errors or anything, the programming button doesn't work at all, when i click nothing happens, not even opening the refurbrish or recover droplist...
Click to expand...
Click to collapse
Are you following this process?
http://forum.xda-developers.com/showthread.php?t=1457341
anseio said:
Are you following this process?
http://forum.xda-developers.com/showthread.php?t=1457341
Click to expand...
Click to collapse
yes i tried that method too.. but no luck =(
i can't click programming button thats the problem... it's kinda deactivated I think
Are you opening product code RM-801 or have you moved the firmware to a different folder? Not much can be done from the RM-801 folder.
I'm just having problems installing Nokia Care Suite. It gets so far and I get a 1220 error.
Any ideas?
Sent from my iPad using Tapatalk HD
It's some odd registry error, right? I think you just click through it. You'll have to navigate to the program folder to open the launcher. IIRC, that's what I had to do.
eccomania said:
yes i tried that method too.. but no luck =(
i can't click programming button thats the problem... it's kinda deactivated I think
Click to expand...
Click to collapse
so, how did you solve this problem? Ive got exactly same trouble wasting my time for days...
Do You ha e a screenlock code on the device. I had to remove my Outlook account, which requires a screenlock code, remove the code and then I was good to go.
Sent from my Lumia 800 using Board Express
anseio said:
Are you opening product code RM-801 or have you moved the firmware to a different folder? Not much can be done from the RM-801 folder.
Click to expand...
Click to collapse
This. In order for the Programming menu to be available, you need to select "Open Product" from the File menu and choose the correct product code (RM-819, RM-801, etc.).
My problem is I can never get passed the "Checking Mode" or "Starting" stage. I keep pressing the volume up button + insert USB cable until I feel a short vibration. After that, Windows will recognise my device as DLOAD and after a short while, the device restarts. Nokia Case Suite will then prompt me to unplug the USB cable, shutdown the device and do the volume up + insert USB cable routine again. Rinse and repeat. What did I do wrong? I am using Windows 7 64-bit.
EDIT: I solved my problems by going to the C:\Program Files (x86)\Nokia\Nokia Care Suite\Drivers\ directory and manually installing all the x64 drivers.
Im also having a few problems with NCS... i just figured I would piggy back off this thread rather than start a whole new one....
When installing I get a error that says.... "ERROR 1904.Module C:\Program Files (x86)\CommonFiles\nokia\Service Layer \C\Service Modules\ServiceModule_00003\msml4.dll failed to register" I hit ignore but now when i connect my phone to my PC... it isnt being recognized as DLOAD or QC or anything. I am at a loss... i went through and installed the drivers that were in the Nokia folder manually, except one it wouldnt install for some reason. Any help would be greatly appreciated.
I am having the same problem on my lumia 920. I didn't find a solution yet. This thread is the only thing I found so far.
Edit: I tried ncs on x64 w7 and x86 w8
Not starting
my phone is not sarting after installing nopkia evolve
eccomania said:
Hi all, I have problem with nokia care suite,
i follow the tutorial for debranding lumia 800 (I have Tmobile DE) but when it comes to step "click programming and choose refurbrish" i can't do that =( because if i click the programming tab it doesn't do anything =(
i think i did everything correct, i downloaded the fw version changed the product code, the grey cube button turned to green, also the program recognize my phone and shows "USB1-RM801" but i can't flash it....
also i tried every usb ports on my computer
p.s. I use windows 7 64bit and original usb cable.
I hope someone can help me
Click to expand...
Click to collapse
I had same stupid problem. You have to change your o.s.country and region from control panel. Try UK or USA. Both will work..
Hope this will help.
Hi guys, I have found a workaround for those having trouble with installing drivers for fastboot in Windows7. This process requires you to do things in the right order and to be quite fast during some steps, so it may take a couple of goes to understand what you are doing before you nail it. First let me explain what seems to be the problem, to help you understand the method I about about to share with you:
It seems that if the drivers aren't installed in Windows7, the Xperia S will disconnect from fastboot mode, and go back to charging. What we need to do is install drivers in this small time period it does connect to your computer.
The solution to this problem will involve being quick at two stages of this process and I will note where these times are as best I can.
Both these stages are when we connect the phone to the computer in Fastboot mode.
Steps to install drivers:
1. Open device manager
2. Connect you phone in fastboot as normal
3. As soon as you plug your device in, ignore any messages stating the driver did not install and look in device manager for the new device 'S1Boot Fastboot' . Right click this and click 'update driver'. This is the first stage you need to be quick at. As soon as you click this and the update driver window pops up you can relax! You can let go of the volume up button now also, as the device will disconnect in the background anyway! You can also unplug the phone now too.
[NOTE: If windows is still trying to install this device, you won't see update driver until it stops/fails. This is when you have a few seconds to click update driver, so be quick!]
4. Click 'Browse my computer for driver software'
5. Click 'Let me pick from a list of device drivers on my computer'
6. Click next with 'Show All Devices' highlighted
7. Click 'Have disk'
8. Click 'Browse'
9. Go to the the .inf file and open it
10. Click 'ok'
11. You will now have a list of three models. Select 'Android Bootloader Interface'. (It is easy to miss this step out and accidently choose the default model so make sure to select it correctly!)
12. BEFORE you click next, we need to get the phone connection ready again, this is the second stage where quick actions are required.
Disconnect you phone if you already haven't. Connect the phone once more in Fastboot mode. As soon as it is connected click next on the window to install drivers
13. If you followed this right you will have installed drivers before the phone had time to disconnet
14. Now that the drivers are installed for the Xperia S, it will no longer disconnect from fastboot mode and work as it should!
Now contiune to follow Sony's guide
I hope this helps you fellow Xperia S users that have problems!
The solution has already been found and posted. I know you mean well, but use search
http://forum.xda-developers.com/showthread.php?t=1527159
For Win7 x64, the Arc drivers are needed otherwise it appears the drivers aren't read properly.
For Arc drivers see last page as the first post isn't updated yet.
Thanks! Was looking for this
Sent from my LT26i using XDA
Also, for 64bit system, make sure in the android_winusb.inf you have the following entry under [Google.NTamd64].
; SonyEricsson
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
Apparently some versions of the inf only have that under [Google.NTx86].
You can copy and paste it in the same format as the rest of the entries.
shmoejoe said:
The solution has already been found and posted. I know you mean well, but use search
http://forum.xda-developers.com/showthread.php?t=1527159
For Win7 x64, the Arc drivers are needed otherwise it appears the drivers aren't read properly.
For Arc drivers see last page as the first post isn't updated yet.
Click to expand...
Click to collapse
Sorry. I don't need to use search as I already read (and just re-read) this post and still had problems.
And seeing as this is a different solution, and quite detailed for those not too familiar with Windows, it may help.
Even means users can use the files all from the official sites. If users search for this in the future, member posted files may be deleted, like I have found on numerous occasions.
Next time, I'll keep it to myself
No reason not to share it. it is a bit easier to read through than dooms instructions, just don't open threads when it could have been easily put in the existing thread
Sent from my LT26i using XDA
I see
I guess I should have stated, but I couldn't reply to the thread as it is in the dev section and I have less than 10 posts
I would usually help more, but usually with the amount of time I have to browse the forums and after searching, someone already has a solution! I guess this is only a good thing!
Maybe it could be added or linked to if necessary
Thank you footyfanatic:
Do you mind if I translate your solution and I post it in HTCMania? a user of that forum is having problems to install his phone's drivers.
Yes this will be fine
Not work for me..phone continue to disconnect on my eeebox (work percect and bootloader unlock on my main PC) WHY ,_;
On eeebox Win 7 home premium 32 bit
On main Win 7 ultimate 64 bit
EDIT UPDATE
Worked for me if I select Android ADB interface and not Android Bootloader Interface
You saved my life! Many thanks!
Thanks a lot! been trying for days and i dont have any XP machine,
Regards! ^_^
Evil_Sephiroth said:
Not work for me..phone continue to disconnect on my eeebox (work percect and bootloader unlock on my main PC) WHY ,_;
On eeebox Win 7 home premium 32 bit
On main Win 7 ultimate 64 bit
EDIT UPDATE
Worked for me if I select Android ADB interface and not Android Bootloader Interface
Click to expand...
Click to collapse
Yes sir! you are right! ADB interface worked
Best Answer
I have searched for this answer all over the net and no one has answered this problem to install fastboot better than this person.
Thanks a lot.
I can't seem to get it. Under what category in device manager does it appear on when you plug it in?
Small Info
I followed all the steps and I thought the drivers installed properly but after getting the key and trying to get into fastboot mode, I faced same problem it went into charging. then I tried repeating the same steps but with one change.
I selected Android ADB interface and not Android Bootloader Interface and it worked like a charm.
Sorry if this is dumb (probably is as others have had no problem) but I am attempting this and am stuck on step 9. When I click browse, the System32 folder opens and I dont know which .inf to open. Is there a specific location and filename.
footyfanatic said:
7. Click 'Have disk'
8. Click 'Browse'
9. Go to the the .inf file and open it
10. Click 'ok'
Click to expand...
Click to collapse
Griggs88 said:
Sorry if this is dumb (probably is as others have had no problem) but I am attempting this and am stuck on step 9. When I click browse, the System32 folder opens and I dont know which .inf to open. Is there a specific location and filename.
Click to expand...
Click to collapse
Before you got to my walk through, you would have been following this guide from Sony: http://unlockbootloader.sonymobile.com/instructions
It is at step 10 which mentions the .inf file
I guess I should have made it more clear and told you to refer back to the Sony guide and where you have that file stored
it really works, I really thank you
I'm having a problem here. Mine is x64
Whichever option I select it says Windows cannot find the file specified, what do I do?
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?