Database Info

[Q] How to root this device without deleting any data?

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.

Hard Bricked after customization..

I bricked my Photon Q while customizing with font apks and soft key customization.. I cannot access recovery, as it just attempts to normally boot. When it normally boots, it gets to the final frame in the boot animation and does not do anything else. I do not have boot loader unlocked and this is a last resort for me. :crying:
I will answer any necessary questions to getting my phone unbricked!
Thanks!

Have you tried flashing stock firmware via RSDlite?

rabinhood said:
Have you tried flashing stock firmware via RSDlite?
Click to expand...
Click to collapse
I have not, trying to boot in any mode except Fastboot will go through the normal boot, also I am running a Linux OS and do not know if I can run RSDLite through Wine or not.

MotoLegacy said:
I have not, trying to boot in any mode except Fastboot will go through the normal boot, also I am running a Linux OS and do not know if I can run RSDLite through Wine or not.
Click to expand...
Click to collapse
Do NOT run RSDLite thru Wine (or a VM for that matter).
Borrow a Windows machine if you have to.

RSDlite runs with no problems on VirtualBox (closed source binary version - with USB pass through) running XP. At least it worked well with Motorola Droid 2.
[edit]
I know flashing bootloader may be more risky, but for many (countless) times I flashed Droid 2 and 3 under linux running a VirtualBox VM with XP installed, and never had any problems. I haven't done it with PQ, since I had no need to flash it.

rabinhood said:
RSDlite runs with no problems on VirtualBox (closed source binary version - with USB pass through) running XP. At least it worked well with Motorola Droid 2.
[edit]
I know flashing bootloader may be more risky, but for many (countless) times I flashed Droid 2 and 3 under linux running a VirtualBox VM with XP installed, and never had any problems. I haven't done it with PQ, since I had no need to flash it.
Click to expand...
Click to collapse
I'm not saying that it is impossible - certainly with USB passthru it *should* work.
But why risk it? I can't recommend using that method - again, may work... but may turn your device into a permanent paperweight if something flakes during the flashing process.

arrrghhh said:
I'm not saying that it is impossible - certainly with USB passthru it *should* work.
But why risk it? I can't recommend using that method - again, may work... but may turn your device into a permanent paperweight if something flakes during the flashing process.
Click to expand...
Click to collapse
I will borrow a Windows machine and try RSDLite, I will post results in a day or two..
I'm still wondering why I was bricked by installing simple customization applications. Maybe it was just a coincidence though.

Unable to unlock bootloader

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).

T-Mobile OnePlus 7 Pro bricked

Hi there!
I have experience with unlocking bootloaders and rooting, but I am really really stuck here. I tried following these instructions with this MSM tool to convert it to an Unlocked version. My OP7P is stuck in an endless boot cycle and says "Upgrade download failed! Please check your download flow is right!" I don't like to leave it on the charger for very long because it just reboots endlessly and I don't think that's good for the phone, but otherwise it won't charge. My Windows computer doesn't recognize the device when checking for adb or fastboot in CMD. I can get it to be recognized in the MSM tool by holding the volume buttons and then plugging it in, and the process starts correctly, but fails after 10-15 seconds.
I have uninstalled and deleted and reinstalled drivers countless times. I've tried to follow these directions and these as well with the same results.
This is replacing a broken LG G6 with a non-functioning speaker mode, abysmal battery life, terrible camera quality, and slow performance. My purchase of the OP7P was supposed to solve all of that with a premium smartphone and right now it's just an expensive paperweight sitting on my desk.
What can I do? Thanks so much in advance!

Tool all in one, fastboot mode, flash Factory Images, download stock rom, check wipe all data and reboot after flash

Ya do what he said do. But if using the msm tool open up device manager and plug in it phone and adb reboot edl whatever that command is. Then go to ports on the device manager and check and see if I have the qcom driver installed. I forget exactly what it supposed to say but it has 9008 in it. I am just gonna tell you I have 2 oneplus 7 pro both tmo brand. I converted them. But idk what it is tho. Each time I change phones to flash rom or whatever I do sometimes the way I do it changes. I am firm believer idc what so and so says it may work one way or another. These phones are crazy weird. The processes change like when I flash using the tool he is talking bout sometimes I lose my network sometimes I don't. Some ppl say when u flash twrp using magisk u gotta flash the the twrp zip once in twrp. Sometimes I don't have to. But when I do it says I lose root but I don't. Just check ur drivers and make sure ur using the right msm tool either global or the T-Mobile

I'll try those, thanks! I can't seem to find the T-Mobile stock ROM though.

You been MSM tool for tmobile it's here on the forum.

twoxa said:
You been MSM tool for tmobile it's here on the forum.
Click to expand...
Click to collapse
I keep getting "Param preload - device not match image" on the MSM tool.

[/COLOR]
daybeers said:
I keep getting "Param preload - device not match image" on the MSM tool.
Click to expand...
Click to collapse
I'm getting that if I'm trying to use wrong MSM tool on my TMO phone. It has to be one for TMO specifically, not any other universal MSM tool. So make sure you got TMO one.
Thread is here
https://forum.xda-developers.com/on...-one-plus-7-pro-msm-tool-revert-t3936528/amp/

twoxa said:
[/COLOR]
I'm getting that if I'm trying to use wrong MSM tool on my TMO phone. It has to be one for TMO specifically, not any other universal MSM tool. So make sure you got TMO one.
Thread is here
https://forum.xda-developers.com/on...-one-plus-7-pro-msm-tool-revert-t3936528/amp/
Click to expand...
Click to collapse
That's the one I've been using.

daybeers said:
That's the one I've been using.
Click to expand...
Click to collapse
Did you find a solution for this issue?

Anyway to return to stock? or Install TWRP/ Rom

I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP

Passportpowell said:
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Click to expand...
Click to collapse
do you have usb debugging enabled, are your sdk tools up to date?

Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.

Passportpowell said:
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Click to expand...
Click to collapse
then you need to update your htc drivers.

here you go.

Aldo101t said:
do you have usb debugging enabled, are your sdk tools up to date?
Click to expand...
Click to collapse
Aldo101t said:
here you go.
Click to expand...
Click to collapse
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
I've done a format data on twrp and it won't ask for a password anymore but I still can't sideload anything. Going to try to copy the rom to the storage and see what happens there
I've only could see a twrp folder on my phone when I connect it to my pc while still in twrp so I copied a rom there and went into install zip, data, media, twrp. My file was there.
Installing rom now I'll update if it worked.

Passportpowell said:
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
View attachment 5087597
View attachment 5087599
Click to expand...
Click to collapse
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.

here is magisk

if you are on pie that viper rom is based on oreo. just so you know.

Aldo101t said:
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
Click to expand...
Click to collapse
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Aldo101t said:
if you are on pie that viper rom is based on oreo. just so you know.
Click to expand...
Click to collapse
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you

Passportpowell said:
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Click to expand...
Click to collapse
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34

Aldo101t said:
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Click to expand...
Click to collapse
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?

Passportpowell said:
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Click to expand...
Click to collapse
3.37.617.1 is for the us-unlocked

Hello to everyone...I just got from my older brother his HTC U11 4gb 64gb phone. And it has locked bootloader and does not have root. So please what should I have to do so I can install custom rom. Stock rom is old full of bloatrware. There is so many information that I am confused.
Thx so much !