Just got a Pixel 3XL - Google Pixel 3 XL Questions & Answers

I just received a Pixel 3XL as a free hand me down and need some assistance. I know it's a couple of years old but still seems to be a solid phone. I basically need to wipe this thing completely clean. The problem is that it's rooted with an unlocked bootloader with TWRP. While that might not be a huge issue it's also on a older Android version 9. I've been reading but I'm not exactly sure where to start in regards to what to do first. I know my share of rooting and flashing ROMs but my knowledge is back with the Nexus and older HTC phones. Any help would be greatly appreciated.

rootbox15 said:
I just received a Pixel 3XL as a free hand me down and need some assistance. I know it's a couple of years old but still seems to be a solid phone. I basically need to wipe this thing completely clean. The problem is that it's rooted with an unlocked bootloader with TWRP. While that might not be a huge issue it's also on a older Android version 9. I've been reading but I'm not exactly sure where to start in regards to what to do first. I know my share of rooting and flashing ROMs but my knowledge is back with the Nexus and older HTC phones. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi,
Pretty much everything you need to know is here: https://forum.xda-developers.com/t/guide-root-pixel-3-xl-android-11-r.4160447/
You can go ahead and just flash whatever factory image you want from here, (mostly) just like a Nexus device:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just use the flash-all script, don't flash one partition at a time...
It will remove root and wipe your phone clean. Root on Pixels doesn't work how it used to back in the Nexux days, as TWRP is not fully supported on 10 or 11 yet.
Just be sure the previous owner Google account has been properly removed before you proceed, otherwise you won't be able to log in with yours: FRP (Factory Reset Protection).
Post in the thread i linked you or here if you need further assistance.
Cheers...
Sébastien.

5.1 said:
Hi,
Pretty much everything you need to know is here: https://forum.xda-developers.com/t/guide-root-pixel-3-xl-android-11-r.4160447/
You can go ahead and just flash whatever factory image you want from here, (mostly) just like a Nexus device:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just use the flash-all script, don't flash one partition at a time...
It will remove root and wipe your phone clean. Root on Pixels doesn't work how it used to back in the Nexux days, as TWRP is not fully supported on 10 or 11 yet.
Just be sure the previous owner Google account has been properly removed before you proceed, otherwise you won't be able to log in with yours: FRP (Factory Reset Protection).
Post in the thread i linked you or here if you need further assistance.
Cheers...
Sébastien.
Click to expand...
Click to collapse
Thanks for the reply, much appreciated. His account is completely gone and mine is the current one. I basically want to update it but I do want to keep root for a few things. I was mainly concerned since it's on an old version of 9 and I know there were some bootloader changes which is what really had me concerned.

rootbox15 said:
Thanks for the reply, much appreciated. His account is completely gone and mine is the current one. I basically want to update it but I do want to keep root for a few things. I was mainly concerned since it's on an old version of 9 and I know there were some bootloader changes which is what really had me concerned.
Click to expand...
Click to collapse
Hi,
You said you have read, but don't know where to start... If you state your goal, it would be easier to help you!
Keep root with stock firmware? What Android version?
Cheers,
Sébastien.

5.1 said:
Hi,
You said you have read, but don't know where to start... If you state your goal, it would be easier to help you!
Keep root with stock firmware? What Android version?
Cheers,
Sébastien.
Click to expand...
Click to collapse
Good point. I'd like to get updated to the most stable android version and keep root with the ability to flash custom kernels. I've been using this for a bit on 9 and it's definitely showing it's need to be updated. The option to flash ROMs would be nice but definitely not necessary. I'm not opposed to doing a complete wipe but if I could keep my data that would obviously be optimal even though I highly doubt that will be possible. Thanks again for the reply.

rootbox15 said:
Good point. I'd like to get updated to the most stable android version and keep root with the ability to flash custom kernels. I've been using this for a bit on 9 and it's definitely showing it's need to be updated. The option to flash ROMs would be nice but definitely not necessary. I'm not opposed to doing a complete wipe but if I could keep my data that would obviously be optimal even though I highly doubt that will be possible. Thanks again for the reply.
Click to expand...
Click to collapse
You should be able to update and save data.
Flash the factory image as mentioned above, however before you run the flash-all bat file edit it with notepad. Near the end of the file remove the -w and save it. Then run the flash all. That will update you and save data.
Then you reroot following one of the rooting guides. Copy boot.img from the factory image to your phone,. Install Magisk Manager and patch the boot.img. Copy that back to your computer and flash it.

TonikJDK said:
You should be able to update and save data.
Flash the factory image as mentioned above, however before you run the flash-all bat file edit it with notepad. Near the end of the file remove the -w and save it. Then run the flash all. That will update you and save data.
Then you reroot following one of the rooting guides. Copy boot.img from the factory image to your phone,. Install Magisk Manager and patch the boot.img. Copy that back to your computer and flash it.
Click to expand...
Click to collapse
Thanks for the reply. I read about doing that but just wasn't sure if that would all work properly since the bootloader was unlocked and TWRP was installed. I'm guessing the factory image flash will get rid of TWRP. It also doesn't matter going to say 11 straight from 9? Sorry for all the dumb questions but this is way different than it used to be when I started back with the original Galaxy S, HTC DesireHD, and Nexus 4.

rootbox15 said:
Thanks for the reply. I read about doing that but just wasn't sure if that would all work properly since the bootloader was unlocked and TWRP was installed. I'm guessing the factory image flash will get rid of TWRP. It also doesn't matter going to say 11 straight from 9? Sorry for all the dumb questions but this is way different than it used to be when I started back with the original Galaxy S, HTC DesireHD, and Nexus 4.
Click to expand...
Click to collapse
Correct, this flash will remove twrp. You are done with twrp it is not working on pixels 10 and up.
9 to 11 should be fine, there is always a risk upgrading a full version. That risk is not any greater because you are jumping two versions.

Related

Update 4.1 - Doesn't work, still in 4.0.4

Hello,
So, I will try to explain clearly my problem. I'm french, so I have an Galaxy Nexus with Android 4.0.4 (IMM76I) - Yakju.
I bought my phone at the very beginning, with the first ICS version. After that, I tried to use " Font changer ", and my phone rebooted, and loading... infinite
So, that was a big problem. To recover it, I tried so many thing, Wipe data, cache, etc... And I flashed the phone with the Factory Image. And it worked. Since this incident, I ALWAYS must flash the new factory image to use new versions of ICS. For 4.0.4 and 4.1. Because on every update, my phone reboot, it loads, and I get the Bugdroid with Warning icon :/
But I'm pissed of, and I want to do something, I'm bored to have that phone, and must do so much tricks for a simple update
So, I'm coming to you, for answers, if there are ?
Thanks !
So when you flashed the factory images, have you been flashing the corresponding radio, bootloader and recovery? And have you modified any system files since then? All of these things will prevent you from applying an OTA.
I used all factory elements from here : h**ps://developers.google.com/android/nexus/images?hl=fr
But now you ask me if I flashed bootloader, recovery, and radio, and I'm not sure :/
If I use the Gnex Toolkit, does he flash all of this himself ? Because I didn't use it before, and I don't remember me flashing the recovery.
I will wait for the 4.1 factory image to be released by Google, and do all of this
Thanks !
draentor said:
I used all factory elements from here : h**ps://developers.google.com/android/nexus/images?hl=fr
But now you ask me if I flashed bootloader, recovery, and radio, and I'm not sure :/
If I use the Gnex Toolkit, does he flash all of this himself ? Because I didn't use it before, and I don't remember me flashing the recovery.
I will wait for the 4.1 factory image to be released by Google, and do all of this
Thanks !
Click to expand...
Click to collapse
Don't use a toolkit and you will know what gets flashed. Follow steps in post #1 here.
Ok, I will follow all steps with 4.1 update.
And after that, I still can use the Toolkit right ?
draentor said:
Ok, I will follow all steps with 4.1 update.
And after that, I still can use the Toolkit right ?
Click to expand...
Click to collapse
No. Follow the steps in the link I sent you, and you will get the OTA update for 4.1.1 shortly after.
Yeah, I thinked about it, and that's the better solution.
But for root and others things, absolutely use your way ?
And what's the avantages and inconveniences of the tho methods ?
draentor said:
Yeah, I thinked about it, and that's the better solution.
But for root and others things, absolutely use your way ?
And what's the avantages and inconveniences of the tho methods ?
Click to expand...
Click to collapse
Use any way you want. Except when you are learning, you should not use any toolkits or 1-click methods <-- you don't know what they are doing, and if something messes up, it will be difficult for you to troubleshoot.
erec, icandoit
Yeah, seems logical.
I must do it the old way, before use new things
So, thanks for all your quick answers, there are much more knowledge here than the FrAndroid French forum

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

Does rooting require you to wipe your phone? (and other basic rooting questions)

The last time I rooted a phone was with a GS3 to install CyanogenMod. I've recently picked up a Pixel 2 XL, and I had some fairly noob-esque questions:
1. Do I have to wipe my phone to root it? That is, there is no "in-place" rooting?
1a. Are there any good methods to make a full backup *without* root before rooting it, and then restore it after I root?
2. Does rooting my phone make future OS updates more difficult/impossible? Ie: Will I still get OS updates, or will I have unroot my phone to get updates, then reroot it, possibly wiping everything?
3. What's the best method to go about doing this now? Googling around, and looking around here, I see a few different, but similar methods. I also see references to a "critical unlock," but no matter how many guides I read, I don't understand it. I'm starting to feel like I don't understand enough anymore to root my phone :-/
I really want to just be able to get back hosts-file based ad blocking again, and maybe a few other tweaks.
1, 1a: Go here and start reading, if you haven't already done so. To root requires unlocking the bootloader, which will cause the device to be wiped. It's best not to put anything important on the device until afterward.
2: OTAs must be applied manually. See the link I provided for instructions.
3: The P2XL is apparently unique in having two unlock commands. The non-critical unlock unlocks the bootloader while still providing some protection. The critical unlock strips all protections from the bootloader. To be on the safe side, execute both commands as mentioned in the link I provided.
Strephon Alkhalikoi said:
2: OTAs must be applied manually. See the link I provided for instructions.
Click to expand...
Click to collapse
Does that require re-wiping the device? Will I still get notified of updates, or will I have to keep track of new releases on my own?
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Strephon Alkhalikoi said:
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Click to expand...
Click to collapse
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
LucentPhoenix said:
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
Click to expand...
Click to collapse
Seems daunting. But read and ask till your comfortable. Lots of really helpful and Patient people on this lovely site. Stock + Root is the ish.
G
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
LucentPhoenix said:
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
Click to expand...
Click to collapse
Some have "dirty flashed" P over oreo with removing the -w flag from flash-all.bat script in the P factory image with mixed results. Your best bet is to clean flash the P build with fastboot to avoid any potential problems. However, yes, it will wipe your phone
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
LucentPhoenix said:
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
Click to expand...
Click to collapse
Yes you would be able to upgrade to the beta releases. However, you'd likely have to go back to Oreo, which would require a full wipe and clean flash, then upgrade to the betas. The first beta release is due out this month according to all the scuttlebutt I've read, so I think your best bet is just to wait a little longer. Here's a thread on the PDP1 that several folks are using :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/android-9-0-developer-preview-1-t3757268

Need some help

I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.
pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
Anyone tried Google's flashing update tool?
Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now
Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.

Could someone with a rooted Mi 10T Lite try this?

Hello,
I have recently entered the world of Xiaomi after a history with Sony Devices (Xperia, Xperia SP, Xperia Z3). I'm so far delighted with the Mi 10T Lite, it's feature rich and blazingly fast. However, I miss one feature I had installed on my SP and Z3 that made their batteries live extra long. It's this:
Battery Charge Limit [ROOT] - Apps on Google Play
Stop charging at desired level to preserve battery health for most devices!
play.google.com
With this tool, you can essentially leave your device permanently on the charger and it will stay within the limits you have set. I used to have it set to 71-80%. So when the charge dropped to 70% it started charging, until reaching 80%. I therefore balanced keeping the battery charged for short intervals and at a sweet spot for its health, with having enough charge in case I wanted to grab my phone and leave the house. I really love this app.
The problem is, it requires root privileges.
I understand that rooting my Xiaomi is not particularly hard, but since it is a new device I would not want to void its warranty. It's possible that some defect shows up and I am left without a warranty. It would be a particularly big bummer if I discovered I rooted the device only to see that the app does not work properly with it.
So, could someone with a rooted device try out this fantastic app and let me know if it works? You might end up with a battery life extender you never knew existed!
Many thanks,
Yanni
Athens/Greece
Friendly bump! Could somebody try this nifty app for battery life optimization on their rooted 10T Lite? Let me know if it works so I can go ahead with arcane rooting magick, hehe.
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
egor27 said:
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
Click to expand...
Click to collapse
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
funkyjester said:
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
Click to expand...
Click to collapse
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
_mysiak_ said:
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
Click to expand...
Click to collapse
Thanks for the link. Besides the EU statutory warranty, a quick search reveals that the company itself allows rooting without voiding your warranty. So I'm a happy camper I guess.
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Hemerson Silva said:
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Click to expand...
Click to collapse
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
_mysiak_ said:
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
Click to expand...
Click to collapse
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Hemerson Silva said:
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Click to expand...
Click to collapse
Maybe if you provide step by step guide how to extract xqcn file and remove sensitive information from it before uploading to the internet, someone will be willing to do it.
In each case, we are heavily offtopic here.
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
funkyjester said:
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
Click to expand...
Click to collapse
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
_mysiak_ said:
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
Click to expand...
Click to collapse
I should have figured out what VF means. I think I will take the straightforward way and use QJSEUXM which I have found readily available. Thanks!

Categories

Resources