As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
linx1287 said:
As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
Click to expand...
Click to collapse
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
lonewolf2k2 said:
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
Click to expand...
Click to collapse
Sorry but mine isnt any carrier phone GM1910 is the chinese international running GM21AA
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
redpoint73 said:
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
Click to expand...
Click to collapse
null0seven said:
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
Click to expand...
Click to collapse
Yes adb devices does register and adb reboot bootloader command does take me to the bootloader, but when i tried the fastboot devices it didnt register, so i think you are on to something. I will check again once i get home today. Thanks
I was on open beta, i reverted to 9.5.10 Pie in order to unlock bootloader and root.
If its not too much trouble, could you link me to the drivers (i would ask adb too but seeing as it works when i do adb devices command, i think thats working fine)? Thanks
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
null0seven said:
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
Click to expand...
Click to collapse
Thanks. This was the version i was working with yesterday. Could you link me to the usb drivers i might need? Since response stops at fastboot i am assuming the drivers are to blame
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
redpoint73 said:
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
Click to expand...
Click to collapse
Thank you. You were right about the driver issue....going through the device manager yielded the driver situation. Had to enable debugging to finally let the driver install. I completely forgot about this. I had to do this same thing when i had to unlock bootloader and twrp for my HTC 10.
Now that i am done with this, a few final things i would like to clear out....doing the local update on root to restore stock system is still valid right? and if i want to go full stock from say custom roms like los and so on, a flash through MSM tool? Will doing that also relock the bootloader? Sorry for all the noob questions and thanks in advance.
Local upgrade works with/without root or twrp.
MSM tool revert youre phone like it's out of the factory. Bootloader locked, no root, no twrp.
If you come back to Oos from custom roms you need to Format Data (this will wipe ALL in youre phone. everything).
Related
Hi,
Since ICS update I have been going insane with the speed of my phone, and today I saw my friends Desire HD running Jelly Bean and it was flying. So naturally I have spent the last 5 hours reading up on how to get it!
I'm an absolute noob with Android, this is my first android and I my other smart phones ran windows 5.5 and 6.5 so however buggy the new OS it can not beat them.
I am confused about a couple of things and I have found many many guides that go in circles. my HBOOTS 1.29
1. Do I need S-off or do I just need my device rooted?
I have found the following guides that seem the most effective:
http://forum.xda-developers.com/showthread.php?t=1661631
2. What is Flashing Firmware and why do I need to do it?
http://forum.xda-developers.com/showthread.php?t=1472298
http://forum.xda-developers.com/showthread.php?t=1377759
3. It seems the best ROM is this:
http://forum.xda-developers.com/showthread.php?t=1782009
Are there anything better?
I don't care about looks, I want the usual phone features, speed, GPS, better battery life and bluetooth connectivity to my external Pressure Variometer (I use it for Paragliding). I don't care about issues with Wifi!
Many Thanks and sorry for repeating previous posts at times
You have 2 options. 1.) S-OFF your device, following the guide you linked. It opens up the whole phone, so after that you can do whatever you would like to. (Recommended)
2.) Unlock your bootloader through HTCDEV.COM website. (If you choose this, you can still install custom roms, but are unable to flash firmware/radio. For more info how to install custom roms with s-on see HERE)
Flashing the newest firmware is "always" an extra. They all come with stability/performance/radio... enhancement. ICS firmwares are 3.32 or 3.33. Whichever you have installed on your device, you are good to go as all recent ICS and Jelly Bean roms are working under both firmware. Some of them recommend 3.33 but are still working on 3.32. As far as I know 3.33 comes with newer radio...?
Rom-wise... It is really up to you what you are looking for and what you expect from your phone. Have a look around in the development section, there are plenty of custom roms/kernel about, either it is aosp/cm or sense based roms. They are all excellent and come with amazing support.
Have fun and good luck! :good:
edit: Have a look HERE too for some more info!
S-on/off
Is it possible to install a ROM on the phone with S-on and on the new rom later turn S-off if required. As I mentioned I'm new so I want to do one step at a time.
kapateh said:
Is it possible to install a ROM on the phone with S-on and on the new rom later turn S-off if required. As I mentioned I'm new so I want to do one step at a time.
Click to expand...
Click to collapse
in order to S-OFF you must have rooted stock rom
it is mentioned also in S-OFF guide
HTC Sync issue
Hi,
I have just tried to get started on the process of rooting from HTCDev however my phone is unable to connect to my PC. (not a great start I know )
I have installed HTC sync however it can not connect to my PC either. Would resetting my phone to factory settings sort the issue?
Many Thanks
kapateh said:
Hi,
I have just tried to get started on the process of rooting from HTCDev however my phone is unable to connect to my PC. (not a great start I know )
I have installed HTC sync however it can not connect to my PC either. Would resetting my phone to factory settings sort the issue?
Many Thanks
Click to expand...
Click to collapse
Hi,
You do not need to do anything to your phone.
You need to have the correct drivers on your PC.
If you are on a windows 7 or 8 then use THESE DRIVERS
Did you restart your PC after installing HTCSync?
kapateh said:
3. It seems the best ROM is this:
http://forum.xda-developers.com/showthread.php?t=1782009
Are there anything better?
Many Thanks and sorry for repeating previous posts at times
Click to expand...
Click to collapse
I think u should try this one..and leave ur friends 4.1.2 behind and came up with 4.2.1..hehehe :laugh:
http://forum.xda-developers.com/showthread.php?t=2115520
issue
malybru said:
Hi,
You do not need to do anything to your phone.
You need to have the correct drivers on your PC.
If you are on a windows 7 or 8 then use THESE DRIVERS
Did you restart your PC after installing HTCSync?
Click to expand...
Click to collapse
Thanks for the email, but do you have the 32 bit drivers?
I have also restarted my PC
kapateh said:
Thanks for the email, but do you have the 32 bit drivers?
I have also restarted my PC
Click to expand...
Click to collapse
Hi,
Sorry,no,I do not have 32 bit drivers.
Did your pc recognize your phone after the reboot?
kapateh said:
Thanks for the email, but do you have the 32 bit drivers?
I have also restarted my PC
Click to expand...
Click to collapse
try universal naked drivers...these will surely solve your problem.. just open the device manager and select driver location..
http://forum.xda-developers.com/showthread.php?t=1998650
HTCDev
Hi, Thanks for the help.
I have uninstalled HTC sync and installed the naked drivers. I have been following the HTC Root, when I run the command "fastboot oem get_identifier_token" in fast boot, it displays 'waiting for devices'. How long do you normally have to wait for the token?
Many Thanks
connection problem remains
kapateh said:
Hi, Thanks for the help.
I have uninstalled HTC sync and installed the naked drivers. I have been following the HTC Root, when I run the command "fastboot oem get_identifier_token" in fast boot, it displays 'waiting for devices'. How long do you normally have to wait for the token?
Many Thanks
Click to expand...
Click to collapse
Hi, I just installed HTC Sync however my phone still fails to connect.
any more solutions?
kapateh said:
Hi, I just installed HTC Sync however my phone still fails to connect.
any more solutions?
Click to expand...
Click to collapse
Hi,
Make sure you are not using a USB hub or USB 3.0 connection.
Try different USB ports.(front and back)
Try a different PC/laptop.
connection problem remains
malybru said:
Hi,
Make sure you are not using a USB hub or USB 3.0 connection.
Try different USB ports.(front and back)
Try a different PC/laptop.
Click to expand...
Click to collapse
I tried all of the above (last one both on win 7), still no connection
kapateh said:
I tried all of the above (last one both on win 7), still no connection
Click to expand...
Click to collapse
did you enable usb debugging mode from settings?
Debugging
rzr86 said:
did you enable usb debugging mode from settings?
Click to expand...
Click to collapse
No, it automatically enables. Even when I disable it and try syncing, it enables by itself, with a notice of course.
kapateh said:
No, it automatically enables. Even when I disable it and try syncing, it enables by itself, with a notice of course.
Click to expand...
Click to collapse
r u using fastboot through sdk...or alone...means only fastboot.exe and adb.exe and some other dll files instead of sdk...if that...than open ur system properties...click advanced system setting..click environment variables..in list select path..and edit..add ur fastboot.exe path there if its not present...just like that..."C:\fastboot\fastboot.exe;"(without quotation marks)..ur problem 'll be solved
Problem still there
Jawwad.John said:
r u using fastboot through sdk...or alone...means only fastboot.exe and adb.exe and some other dll files instead of sdk...if that...than open ur system properties...click advanced system setting..click environment variables..in list select path..and edit..add ur fastboot.exe path there if its not present...just like that..."C:\fastboot\fastboot.exe;"(without quotation marks)..ur problem 'll be solved
Click to expand...
Click to collapse
Problem still persists, waiting for device.
Also I have installed MyPhoneExplorer which can sync from my phone.
kapateh said:
Problem still persists, waiting for device.
Also I have installed MyPhoneExplorer which can sync from my phone.
Click to expand...
Click to collapse
Problem is not about htc sync or other software...Follow the steps...fastboot works even without adb or others..personally tried on senation and atrix..
1)Install drivers (naked)..check in device manager..it ll show htc device...
2)Download fastboot..and place it on any drive where u can access easily...file attached..
3)Set Path if already not...snap attached..
4)Trun off ur device and boot into hboot...select fastboot and it 'll show bootloader and other options...
5)attach ur device now...and start with start here.bat file..
6)if not worked..then run above file as admin or try to restart ur pc..
whoohoo
Jawwad.John said:
Problem is not about htc sync or other software...Follow the steps...fastboot works even without adb or others..personally tried on senation and atrix..
1)Install drivers (naked)..check in device manager..it ll show htc device...
2)Download fastboot..and place it on any drive where u can access easily...file attached..
3)Set Path if already not...snap attached..
4)Trun off ur device and boot into hboot...select fastboot and it 'll show bootloader and other options...
5)attach ur device now...and start with start here.bat file..
6)if not worked..then run above file as admin or try to restart ur pc..
Click to expand...
Click to collapse
Great, thank you that seemed to have worked I'm going to now proceed with S-off and ROM installation. Will undoubtedly re-post again.
Just one more question, Do I need to delete/format the files off my SD card or not, I have backed up anything of value.
Also the network is not unlocked, would the network be unlocked with a new ROM?
Hi everyone,
I need a little help here as I find myself stuck between a lot of possibilities and I don't know which one to take or generally what to do.
My girlfriend has an HTC One S4 with unlocked bootloader (HBOOT 2.15), recovery installed, running Viper ROM 3.1.
However because she only has the 1.15 RADIO on the device it tends to reboot quite a lot and she can't have a phone that reboots that often to use on a daily basis.
I want to S-OFF the device so I can upgrade the RADIO.
I've heard of Moonshine method and rumrunner method, however both of these only work with fastboot drivers installed and working.
This is not the case for her S4. I have a desktop (win 8.1, with USB 2 and USB 3.0) and a laptop (win 8.0 with only USB 3).
And none of them can find the device when it is connected while in fastboot. Therefore I can't S-OFF the device that way..
Could anyone point me in the right direction or have some suggestions on what to do?
Hammerbak said:
This is not the case for her S4. I have a desktop (win 8.1, with USB 2 and USB 3.0) and a laptop (win 8.0 with only USB 3).
And none of them can find the device when it is connected while in fastboot. Therefore I can't S-OFF the device that way..
Could anyone point me in the right direction or have some suggestions on what to do?
Click to expand...
Click to collapse
Did you try a Ubuntu Live CD? That's what I had to do to get things working reliably.
How did you install fastboot and adb?
808phone said:
Did you try a Ubuntu Live CD? That's what I had to do to get things working reliably.
How did you install fastboot and adb?
Click to expand...
Click to collapse
No I haven't tried with an Ubuntu Live CD, and tbh I'm not that well known in the Linux systems.
Well I installed the Google Drivers from the "Android SDK Manager" and I tried a lot of different methods I found on posts alike.
The problem is that neither of my two computers can find the device when it's connected and in fastboot.
Hammerbak said:
No I haven't tried with an Ubuntu Live CD, and tbh I'm not that well known in the Linux systems.
Well I installed the Google Drivers from the "Android SDK Manager" and I tried a lot of different methods I found on posts alike.
The problem is that neither of my two computers can find the device when it's connected and in fastboot.
Click to expand...
Click to collapse
How about using some friends computer /laptop?
LS.xD said:
How about using some friends computer /laptop?
Click to expand...
Click to collapse
Well I guess I could try out her PC when I get home later today, but I doubt there will be a lot of difference.
However her PC runs Win 7. I will return here as soon as I know more!
Hammerbak said:
Well I guess I could try out her PC when I get home later today, but I doubt there will be a lot of difference.
However her PC runs Win 7. I will return here as soon as I know more!
Click to expand...
Click to collapse
Is it a unbranded phone hboot 2.15 eu ??
For me Facepalm was the only wotking one.
The biggest problem is that without adb and fastboot working, you probably won't get anywhere.
The reason I mentioned the Ubuntu live CD is that I have working fastboot and adb and still had problems with windows 7.
I finally created the Ubuntu live CD (actually USB) and it worked. It doesn't take too long to create the live CD/USB and it's worth a try.
LS.xD said:
Is it a unbranded phone hboot 2.15 eu ??
For me Facepalm was the only wotking one.
Click to expand...
Click to collapse
Well tbh I don't know if it is unbranded - Since I don't know what that term means.
We live in Denmark and I think she got the phone from germany - bought on a sale somewhere.
Whenever it was booting up (before I rooted and unlocked the bootloader) it came with a splash screen saying "T-Mobile".
Does that mean it is branded to T-Mobile?
808phone said:
The biggest problem is that without adb and fastboot working, you probably won't get anywhere.
The reason I mentioned the Ubuntu live CD is that I have working fastboot and adb and still had problems with windows 7.
I finally created the Ubuntu live CD (actually USB) and it worked. It doesn't take too long to create the live CD/USB and it's worth a try.
Click to expand...
Click to collapse
The LiveCD/LiveUSB sounds like an idea and will be my first attempt after "trying" Win 7.
Does the moonshine S-OFF method only support Stock ROM/Firmwares?
I guess I am to try the rumrunner method once on the LiveCD/LiveUSB.
Thanks in advance and again I will return when I know more
Hammerbak said:
Well tbh I don't know if it is unbranded - Since I don't know what that term means.
We live in Denmark and I think she got the phone from germany - bought on a sale somewhere.
Whenever it was booting up (before I rooted and unlocked the bootloader) it came with a splash screen saying "T-Mobile".
Does that mean it is branded to T-Mobile?
The LiveCD/LiveUSB sounds like an idea and will be my first attempt after "trying" Win 7.
Does the moonshine S-OFF method only support Stock ROM/Firmwares?
I guess I am to try the rumrunner method once on the LiveCD/LiveUSB.
Thanks in advance and again I will return when I know more
Click to expand...
Click to collapse
moonshine only supports "supported" firmware versions listed on the moonshine.io homepage (page 3)..
LS.xD said:
moonshine only support "supported" firmware listed on the homepage...
Click to expand...
Click to collapse
So I will be using rumrunner then..
Thanks however.
Hammerbak said:
So I will be using rumrunner then..
Thanks however.
Click to expand...
Click to collapse
wish you best luck
LS.xD said:
wish you best luck
Click to expand...
Click to collapse
I am sitting on a LiveUSB right now, but I find that the instructions on the rumrunner webpage doesn't work.
Any suggestions?
It goes through the first steps and I will get to answer ''Yes'' twice.
After a please wait message I get: "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
I followed the instructions to perfection. Will I need to install drivers on Linux?
Hammerbak said:
I am sitting on a LiveUSB right now, but I find that the instructions on the rumrunner webpage doesn't work.
Any suggestions?
It goes through the first steps and I will get to answer ''Yes'' twice.
After a please wait message I get: "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
I followed the instructions to perfection. Will I need to install drivers on Linux?
Click to expand...
Click to collapse
Do you have USB Debugging on? When you are booted into the phone and connected to the computer. Type adb devices and see if it returns a valid value (not offline).
No, you don't have to install drivers on Linux. Also I never was able to get anything but moonshine.io working.
808phone said:
Do you have USB Debugging on? When you are booted into the phone and connected to the computer. Type adb devices and see if it returns a valid value (not offline).
No, you don't have to install drivers on Linux. Also I never was able to get anything but moonshine.io working.
Click to expand...
Click to collapse
Well USB debugging is enabled on the device, however it doesn't show the USB debugging icon on the phone that it does when connected to a Windows PC.
I will try to check is ADB is active later tonight.
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
Hi guys. Recently I have this problem with my nexus 5 drivers, not all of them just the bootloader ones, I have tried a lot of times to completely uninstall them, the reinstall but in the end i get the same error. in device manager Code 10 this device cannot start.
I want to mention that i have Cataclysm ROM installed and also elementalx kernel, the fact that once i erased all my internal storage, and that I have watched a lot of tutorials but none of them worked.
EDIT:how do I add attachments?
EDIT2:i think its something wrong with the computer, cause i tried on another pc and it worked.
They are no specific drivers for the bootloader. Did you install fastboot on this computer?
Primokorn said:
They are no specific drivers for the bootloader. Did you install fastboot on this computer?
Click to expand...
Click to collapse
Yeah that drivers i am talking about, I tought bootloader=fastboot.
dinho23 said:
Yeah that drivers i am talking about, I tought bootloader=fastboot.
Click to expand...
Click to collapse
Bootloader = software that loads the OS as its main purpose
Fastboot = set of commands that can be executed while the phone is running the bootloader but has not loaded the OS yet.
Kb2005 international version just purchased. Rooted but lost wifi access tried to fix and bricked stuck in fastboot repeat and red boot loop
Hi,
You may try to boot to safe mode. Just a thought. If you choose to do it, I am not responsible if it would not work or if something else wrong happens.
Good luck!
Have you MSM'd back to stock? https://androidfilehost.com/?fid=2188818919693750637
craznazn said:
Have you MSM'd back to stock? https://androidfilehost.com/?fid=2188818919693750637
Click to expand...
Click to collapse
Mam isnt working this should work on a vm too right ive installed all usb drivers too
amplatfus said:
Hi,
You may try to boot to safe mode. Just a thought. If you choose to do it, I am not responsible if it would not work or if something else wrong happens.
Good luck!
Click to expand...
Click to collapse
Thanks for the reply thats fine im ok i just want to try and get it back its a brand new phone
Method 1. Download Full ROM, and Payload Dumper. Extract payload.bin and put it to payload_input folder and all *.img files will be in payload_output folder. Use fastboot flash boot boot.img command and reboot. Device should work after reboot. If you need root, either flash a patched boot.img or use flashboot to flash TWRP and then install Magisk from TWRP.
Method 2. Manually flash *.img files. Reference: [GUIDE] Unbrick or restore to OOS using only fastboot
Method 3. Use MSMtool to wipe and restore your phone.
Note: If you lost WiFi AFTER your device is rooted, and if you ever installed a custom kernel, it's probably the RAMDISK (can't remember where I saw it before) causing the issue. Easy solution, flash same custom kernel again. Or try different kernels.
So these unbricktools here don't work for you?
Index of /list/Unbrick_Tools/OnePlus_8T
Millyrocker said:
Mam isnt working this should work on a vm too right ive installed all usb drivers too
Click to expand...
Click to collapse
EDL mode will disconnect/reconnect several times and change connection protocol. Your virtual machine may lost device due to this process.
So better on Windows PC.
ULTRAJC said:
EDL mode will disconnect/reconnect several times and change connection protocol. Your virtual machine may lost device due to this process.
So better on Windows PC.
Click to expand...
Click to collapse
Im on linux right now im trying to find a way to install windows but even thats not working smh
Millyrocker said:
Im on linux right now im trying to find a way to install windows but even thats not working smh
Click to expand...
Click to collapse
I applaud your use of linux! Unfortunately, I've not found a good solution under linux to do what the windows MSM tool can do. I had to book in to a full Win install in order to use it on my phone as well.
On a positive note, it's nearly impossible to truely brick these phones. The negative is the MSM tool needs windows. Unless someone can point to a linux solution (which I'd love) you may need to find a friend with Windows and borrow their computer...
The fact you are in fastboot loop makes me think you should be able to just fastboot flash everything manually. MSM is the nuclear option. I'd try getting the stock full ROM and manually flashing everything in fastboot.
What fastboot are you using? I've found that the one in many linux distributions are old. Download the latest from Android https://dl.google.com/android/repository/platform-tools-latest-linux.zip and use this.
Millyrocker said:
Im on linux right now im trying to find a way to install windows but even thats not working smh
Click to expand...
Click to collapse
EDL mode will reboot itself if there was no command sent to the phone. So you need to run MSM tool first and once you see the phone is recognized, just execute.
A real Windows should make whole process a lot more easier. If you use a VM, as long as Windows can recognize Qualcomm Modem driver, it should work too.