hi, ive been having issues rooting this phone.
Ive tried 4 different cables & 2 different laptops.
Have the latest usb drivers + the samsung drivers. I did notice that it cant be found in device manager.
when i click on the bat file in qbkings one click root folder, i get "device not found". <duh
Usb debugging is enabled. Could the phone itself be damaged?
You're better off unlocking the bootloader and flashing custom recovery through adb. The directions aren't difficult to find (I'd link you but I'm on my phone). That way if something goes wrong you know where it failed instead of being dependent on a piece of software.
I wish everybody did it this way. Plus, I 100% agree with your statement. Not only that, you learn a few things along the way
mrmondaynight said:
hi, ive been having issues rooting this phone.
Ive tried 4 different cables & 2 different laptops.
Have the latest usb drivers + the samsung drivers. I did notice that it cant be found in device manager.
when i click on the bat file in qbkings one click root folder, i get "device not found". <duh
Usb debugging is enabled. Could the phone itself be damaged?
Click to expand...
Click to collapse
Before trying to root the phone, did you ever connect to any computer at all?
And what ru on...GB 2.37?
Vs Nexus S 4G
063_XOBX said:
You're better off unlocking the bootloader and flashing custom recovery through adb. The directions aren't difficult to find (I'd link you but I'm on my phone). That way if something goes wrong you know where it failed instead of being dependent on a piece of software.
Click to expand...
Click to collapse
man, im slow. Im having a hard time locating the directions :crying:
vidaljs said:
Before trying to root the phone, did you ever connect to any computer at all?
And what ru on...GB 2.37?
Vs Nexus S 4G
Click to expand...
Click to collapse
Yes.
Same issue. Even with usb storage.
phone is on ICS 4.0.4 via ota update.
http://forum.xda-developers.com/showthread.php?t=1623481
Step by Step Root is here in the sticky. If the phone isn't seen just to see the SD card then the phones USB may be shot and that is a hardware issue.
Hello everyone,
I've been a member since the I had my Sony Xperia X10 and Samsung Galaxy S3 and both phones were rooted using xda forums. I greatly appreciate this community and should contribute more but I'm not that advanced as most users here. I do have a little some experience tinkering around with the computer but I'm mainly a hardware type of guy and know only a little on software.
But here is my problem. I tried a few methods of trying to root my One Plus One and had little success. I came to a conclusion that it's a driver issue. When i use the command adb devices, it wouldnt show any devices. When I look in the device manager with my OPO plugged in, the drivers are missing. I tried to manually download android sdk and install from there but still no luck. I tried using the GUI toolboxes which has the adb and drivers to install. But still came out with no luck.
Can anyone assist me with my situation? When I turn on Developer Options and checked Android Debugging and USB Debugging Notify, I would not get the message to confirm and give access to the computer. I can open all folders in Windows 7 of my OPO and I use the original data cable supplied with my phone.
Thanks in advance!
Try manually installing the correct driver in device manager. Chances are that Windows is picking a matching but incompatible driver from your old device or tries to be smart.
d4fseeker said:
Try manually installing the correct driver in device manager. Chances are that Windows is picking a matching but incompatible driver from your old device or tries to be smart.
Click to expand...
Click to collapse
Sorry for the noob question, but where would I find the drivers?
archanphel said:
Sorry for the noob question, but where would I find the drivers?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2386956
I know OPO isn't listed but the driver works for OPO.
is that for windows 8.1? I'm running windows 7
archanphel said:
is that for windows 8.1? I'm running windows 7
Click to expand...
Click to collapse
Works on Windows 7 as well, thats why its called "Universal"
and read more carefully the thread says,
2 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
Click to expand...
Click to collapse
zephiK said:
Works on Windows 7 as well, thats why its called "Universal"
and read more carefully the thread says,
Click to expand...
Click to collapse
Yup, sorry about that. I figured it out by the step by step tutorial. Thanks
I have successfully rooted my phone. Thanks again for all the help!
Hey guys,
this has been bugging me for a while and I can't seem to find a fix. I have googled it but all threads that I have read has not been succesfful for me. Anyone knows how to make the Sensation USB work on W8.1?
Cheers
Ilithius said:
Hey guys,
this has been bugging me for a while and I can't seem to find a fix. I have googled it but all threads that I have read has not been succesfful for me. Anyone knows how to make the Sensation USB work on W8.1?
Cheers
Click to expand...
Click to collapse
type here in xda "how to set up adb/fastboot on windows 8"
you will find some useful threads
rzr86 said:
type here in xda "how to set up adb/fastboot on windows 8"
you will find some useful threads
Click to expand...
Click to collapse
Been there, done that. Nothing helpful came out of it
Ilithius said:
Been there, done that. Nothing helpful came out of it
Click to expand...
Click to collapse
have you seen these threads?
http://forum.xda-developers.com/showthread.php?t=2232799
http://forum.xda-developers.com/showthread.php?t=1583801
Those threads are useless. It doesn't recognize my device AT ALL son I can't do the method it says
Ilithius said:
Those threads are useless. It doesn't recognize my device AT ALL son I can't do the method it says
Click to expand...
Click to collapse
maybe some videos from youtube may help you
also have you enabled usb debugging mode from settings?
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
This one solved it on every computer I used. Now I can even use fastboot over usb 3.0.
Wtf are you talking about. I don't care about fastboot, I just want to be able to copy from and to my phone....
Ilithius said:
Wtf are you talking about. I don't care about fastboot, I just want to be able to copy from and to my phone....
Click to expand...
Click to collapse
are your using the original cable from htc?
use usb 2.0 ports not 3.0(in case if you have usb 3.0 ports)
also you didn't answer the question in my previous post
Ilithius said:
Wtf are you talking about. I don't care about fastboot, I just want to be able to copy from and to my phone....
Click to expand...
Click to collapse
mind your words ... u r seeking help but where ur manners?
Yes I am using the HTC cable, a usb 2.0 slot and do have USB debugging enabled. All I get from windows is "unrecognized USB device"
Ilithius said:
Yes I am using the HTC cable, a usb 2.0 slot and do have USB debugging enabled. All I get from windows is "unrecognized USB device"
Click to expand...
Click to collapse
then you have to solve the connectivity issue with w8
some of the threads provided in previous posts help a lot of users to solve it
search in xda if you find anything else
i am out of ideas
edit: have you installed htc sync in your pc?
I both tried with HTC sync, and with HTC usb drivers
Let me just start by saying I'm pretty much completely new to this, I've only ever rooted one phone before (Galaxy note 5 about 5 years ago) but I'm having several issues trying to root my OnePlus 7 pro. I've enabled usb debugging and oem unlocking but when I try to load into the bootloader the phone doesn't respond to the command. Alternatively I've also tried to to root using Kingo (both apk and PC versions) but it fails. Model is GM 1917 and I'm on Android 11.0.5.1 Any help would be greatly appreciated
how are you trying to boot into the bootloader?
nathanalbat said:
how are you trying to boot into the bootloader?
Click to expand...
Click to collapse
at 1:33 is where I'm getting jammed up it's acting as if the phone isn't plugged in
Are you on a T-Mobile network?
oregonhynita said:
Are you on a T-Mobile network?
Click to expand...
Click to collapse
No AT&T
Capezza990 said:
No AT&T
Click to expand...
Click to collapse
Oh ok was thinking we had the same issue but I'm on T-Mobile. Did you get it rooted?
check your driver on computer and your data line
malibug said:
check your driver on computer and your data line
Click to expand...
Click to collapse
Uninstalled and reinstalled the driver's twice used two different cords and tried on two different PC's all same results
Capezza990 said:
Uninstalled and reinstalled the driver's twice used two different cords and tried on two different PC's all same results
Click to expand...
Click to collapse
Once the phone is connected to the PC, go to the windows update section , try updating, then go to
View optional updates,, and install those drivers that pertain to your phone. Reboot, then try again, hth
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
LinhBT said:
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
Click to expand...
Click to collapse
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
rodken said:
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
Click to expand...
Click to collapse
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
LinhBT said:
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
Click to expand...
Click to collapse
It seems that your device is a candidate for a replacement if you cannot enter EDL.
rodken said:
It seems that your device is a candidate for a replacement if you cannot enter EDL.
Click to expand...
Click to collapse
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
LinhBT said:
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
Click to expand...
Click to collapse
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
This I know, but it applies for 8T more than OP8 since op8 only have one LPDDR4 variant, and also in the ops extracted image, there was only 1 xbl and xbl_config image, none xbl5. Thats why I feel weird.
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
LinhBT said:
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
Click to expand...
Click to collapse
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Daniha said:
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
Click to expand...
Click to collapse
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
rodken said:
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Click to expand...
Click to collapse
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
LinhBT said:
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
Click to expand...
Click to collapse
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
LinhBT said:
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
Click to expand...
Click to collapse
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
rodken said:
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
Click to expand...
Click to collapse
Sure man, just like before, based on the information I have from our forum, I was successfully restore a dead OP 8T TMO with Testpoint trick after few months after it bricked. That thread, I believe still somewhere at 8T Forum
Daniha said:
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
Click to expand...
Click to collapse
Pls kindly re-check my reply at #12
Anyone? Anyone have any information pls!!!
LinhBT said:
Anyone? Anyone have any information pls!!!
Click to expand...
Click to collapse
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Xryphon said:
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Click to expand...
Click to collapse
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
LinhBT said:
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
Click to expand...
Click to collapse
There is an interesting write-up regarding your issue.
Not to mention that there is the possibility of corrupting the Param Partition that will cause EDL to not function under the MSM Tool with the old param mismatch.