yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] leoni1980:
the problems people are experiencing and the seeming lack of issues for other people with the same ROMS must have something to do with the Kaiser variants people are using. I can think of no other reason why I can have the same ROM, radio and SPL as someone else and yet cannot get a fix, while they can. I have an Orange branded TyTn 2 from the UK. I am currently using the Dutty Diamond V1, hard spl 3.29 and the 1.65 radio that comes with the diamond ROM. I believe my Kaiser model number is KAI130. Does anyone else have the same model and ROM etc as me and is able to get a fix?

Ive tried 5 different ROMs and umpteen radio, disabling and enabling A-gps - even installing different quick GPS cabs. No luck.

I never had any problems like this on my N95, and everyone criticise its GPS!
[Tilt, TyTN II, MDA Vario III General] Autourdupc:
hi,

i use now last updated htc rom in french (wm6.1) with tomtom 6.0 and quickgps V1.0 from htc.

Effectively, it takes now more time (1..3 minutes) than before (few seconds, under wm6.0) to get a fix, but it works has before.

Seem that the fix takes now much more time...

May be you are right, wm6.1 has somthing to do wuth t is problem.

Best regards,

Laurent
[Tilt, TyTN II, MDA Vario III General] mikegadd:
McGuider GPS

This program picks up signal in under 15 secs
[Tilt, TyTN II, MDA Vario III General] mikeeey:
I have an AT&T Tilt, I live in the US.

I'm using Radio 1.64.06.04

Im using Dutty's WM6.1 4/29 Rom

I have the Qualcomm 7200 chip (not 7201)

My Kaiser's Model Number is KAIS160.

Now that i think about it, i cant confirm this kaiser ever had a good GPS fix, being that this is my 2nd kaiser, my first one broke, and this one is the free replacement. hm...

The poll results are really surprising me, at least half the people's GPS is fine for them. I would upgrade to anything newer than dutty's 4/29 but most diamond builds dont support direct draw, i cant play quake, quake 2, or duke nukem. most other games or apps that use direct draw don't work either. i still have to try hyperdragon 6/24 build and L26_Kaiser Diamond 6/25. Does anyone know if GPS AND direct draw are working on these roms?
[Tilt, TyTN II, MDA Vario III General] jym04:
Indeed I miss the fast fixes from 6.0 ROMs. Within 20 seconds I would already have a fix from a cold start. Now it takes up to 3 minutes, its reaaally annoying. In fact, I also found it strange that half of the people here were not complaining about their GPS's. More than once I needed those fast fixes and had to wait for 2 minutes or so, and had to stop at dangerous (:eek::rolleyes:) places waiting for it. I tried different solutions but none of them seemed to work. And I really don't feel like going back to 6.0 ROMs so..
[Tilt, TyTN II, MDA Vario III General] mikeeey:
if your on the freeway and it takes 3 minutes, you can already drive a mile or so before you realize you need to turn back :mad:
[Tilt, TyTN II, MDA Vario III General] sgarciaone:
Good GPS

I Have a Wizard that I used with an external GPS before I got my new Tilt. I really like this one. I think if anything the tilt is so much better. I haven't seen any change one way or another. I certainly NEVER got a sig in 5-20 secs. Either way still take about 45-90 secs to grab sig.
[Tilt, TyTN II, MDA Vario III General] motocrossmann:
about 20 seconds for me:

ROM: Dutty's Hybrid v2

Radio: 1.58.11.07

Use QuickGPS

Baud: 38400

HardSPL v3.28
[Tilt, TyTN II, MDA Vario III General] vwauditech:
I am using Tom Tom 7 right now and have QuickGPS disabled and I get a lock in about 30-40 seconds. I went Geocaching earlier tonight and worked flawlessly everytime. I am using 1.65.20.29 radio for about 2 weeks now and I may keep it, seems to be working really well for me. I just got a Titan to play with in the mail on Wednesday and it is a little quirky. Have to run app to get a lock then launch Tom Tom or other in order to make it work. Had to flash 6.1 on it just to unlock the GPS hardware. It's a decent device though.
[Samsung Galaxy S9+ Guides, News, & Discussion] nicolaimai:
So here is my question, all around the world speaking about Samsung s9plus snapdragon but difrent model such SM-G965U1 ( I know this is unlocked) or SM-G965F or etc.... this model SM-G965U snapdragon its everywhere but no one speak about beta android 10 or at least flashing the beta or vice versa

So we have a one ui 2 beta on this model: Samsung SM-G965U????

I'm not speaking about SM-G965U1 !

I tried to install the beta one ui 2 on my phone SM-G965U.

The firmware was SM-G965U1 but no luck !

Some one tried to install the beta Android 10 on this model SM-G965U?
[Samsung Galaxy S9+ Guides, News, & Discussion] natibongo:
I'm not sure anyone has Android 10 beta on the Snapdragon variant yet. Currently only the Exynos variant is running the beta.

I suggest we all wait patiently for the official firmware which should hopefully roll out in a few weeks :)
[Samsung Galaxy S9+ Guides, News, & Discussion] nicolaimai:
I understand that.

But you maybe dont know cose already on SM-G965U1 they already roll beta android 10 ,I'm disappoint on this model (SM-G965U)
[Samsung Galaxy S9+ Guides, News, & Discussion] natibongo:
If someone can make tar files from the G965U1 firmware then we can all flash it via ODIN so until then we only have to wait
[Samsung Galaxy S9+ Guides, News, & Discussion] leonardojt:
Many dev's won't want to help or contribute because it has already been done. Use the advanced search feature to search it will help you. I've SM-G965U. Then I converted it to SM-G965U1 using moded odin from this forum followed the tutorial on this forum. Then flashed the beta of U1 and even the final firmware. You can even later go back forth. I don't have much data sub on my phone I would have done for you using teamviewer. Good luck
[Samsung Galaxy S9+ Guides, News, & Discussion] nicolaimai:
To convert from SM-G965U to SM-G965U1 you have to wipe everything or just flash?? ,

repeat I already tried but no luck with ODin patch ,I didn't wipe or factory reset!
[Samsung Galaxy S9+ Guides, News, & Discussion] nicolaimai:
I found the thread here but I dont want to wipe or factory reset https://xdaforums.com/galaxy-s9-plus/help/flash-g965u-verizon-to-g965u1-965u-t-t3871415/page2
[Samsung Galaxy S9+ Guides, News, & Discussion] Imaginos:
Nico, the official one is coming soon. Just hang on a little while and let the final non-beta release come to you.
[Samsung Galaxy S9+ Guides, News, & Discussion] leonardojt:
That's it, I mine was sprint SM-g965u to SM-G965U1 but I never look back ever since. Yes wipe is necessary except u used home csc. But I will strongly advice for wipe. Also, you can use smart switch to backup or any method you prefer. Or be patient until final version. But I'm not a fan of bloatware from branded firmware
[Samsung Galaxy S9+ Guides, News, & Discussion] nicolaimai:
So how this working ?when SM-G965U BECAME SM-G965U1 ? Never or after pay off the device?
[Xiaomi Mi A2 / 6X Questions & Answers] dandrake47:
If I use the patched boot.img method (which includes usage of Magisk to enable Camera2api), would I be rooted?

Would I lose the root access once I do fastboot oem lock again afterwards?

Thanks in advance!
[Xiaomi Mi A2 / 6X Questions & Answers] pureexe:
Don't do oem lock, if you are patch boot image. Device will failed on verify that your boot image is from OEM and cannot boot
[Xiaomi Mi A2 / 6X Questions & Answers] mariosenta:
And if you relock bootloader you will lose cam2api.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] elessar18:
I have version with snapdragon 636, it's whyred right?

Last time when I installed twrp and rooted phone it was about 2 years ago, for this time miui updated to 11, and I'd like to know which versions of twrp and magisk should I flash?

Maybe there is actual guide for miui 11? I searching for 1h already, all are for Vince, and for miui 10. I don't want do mistakes with versions like 2 years ago when I spend 8h to unbrick and finally root my phone, that's why I asking.

In short: I need a guide to root my redmi note 5 with miui 11. Thanks in advance for help.
[Xiaomi Redmi Note 5 / 5 Plus Questions & Answers] madhurajkumar:
Follow this guide

One thing is use Orange Fox recovery at the place of TWRP to avoid data getting encrypted again and again
[OnePlus 7 Pro Questions & Answers] sixisixsix:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?

Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.

Thank you, I'm willing to donate for help.
[OnePlus 7 Pro Questions & Answers] Lossyx:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
[OnePlus 7 Pro Questions & Answers] Bagpuss:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.

That's what I've done and it works just fine.

This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
[OnePlus 7 Pro Questions & Answers] sixisixsix:
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?
[OnePlus 7 Pro Questions & Answers] sixisixsix:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.

What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?

Forgive my ignorance, I am still in the learning process.
[OnePlus 7 Pro Questions & Answers] QUBiCA:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.

To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).

Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
[OnePlus 7 Pro Questions & Answers] Lossyx:
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!

[MENTION=10422115]sixisixsix[/MENTION] please ignore everything I've said! I will edit my posts.

Sorry once again
[OnePlus 7 Pro Questions & Answers] redpoint73:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).

The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).

The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.

It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).

So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------

Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:

1) Unlock bootloader

2) fastboot boot twrp.img

Note that this is just remote booting a TWRP image,

not

installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.

3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.

4) Also in "booted" TWRP, flash the Magisk zip.

The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.

The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
[OnePlus 7 Pro Questions & Answers] sixisixsix:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
[OnePlus 7 Pro Questions & Answers] QUBiCA:
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.

If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.

Flashing/installing TWRP generally is not necessary and like [MENTION=660462]redpoint73[/MENTION] explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What [MENTION=660462]redpoint73[/MENTION] explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.
[OnePlus 7 Pro Questions & Answers] redpoint73:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.

I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.

---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------

Actually, no (as QUBiCA touched on above).

Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.

The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.

No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
[OnePlus 7 Pro Questions & Answers] sixisixsix:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
[OnePlus 7 Pro Questions & Answers] tech_head:
NO.

You need to go through the process and flash Magisk from inside Magisk Manager.
[OnePlus 7 Pro Questions & Answers] sixisixsix:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.

Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
[OnePlus 7 Pro Questions & Answers] redpoint73:
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:

---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------

You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.

For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.

My recommendation is follow this guide: https://xdaforums.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368

I can't possibly see how it can be any more in depth.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] AndyYan:
This thread hosts personal builds of LineageOS 17.x and PixelExperience 10 for Mix 2. Full credits to Arian, Wight and others doing the actual bringup, allowing us to build upon the awesome work.

Small changes in my builds:

Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup

Grey-blue DeskClock color scheme (when possible)

Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)

Signature spoofing support from MicroG

Revived navbar layout tuning via sysui_nav_bar tunable

...

What's working:

Everything?

Instructions:

Use firmware Stable V11.0.3.0

Use official TWRP

Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)

Reboot to TWRP

Flash the latest build, GAPPS and whatever other additions you need

Reboot

Extras:

Read here if you want to use unencrypted data - post is from Oreo thread, but still applies

Downloads:

SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "10" folder

Root: use Magisk

Google Apps: http://opengapps.org/

Source Code:

https://github.com/LineageOS/

Donation:

Donate to @NeoArian

Donate to @wight554

Donate to me

XDA:DevDB Information

LineageOS 17.x, ROM for the Xiaomi Mi Mix 2

Contributors

AndyYan, NeoArian, wight554

Source Code: https://github.com/LineageOS/

ROM OS Version: Android 10

ROM Kernel: Linux 4.x

ROM Firmware Required: MIUI V11.0.3.0

Based On: LineageOS

Version Information

Status: No Longer Updated

Created 2020-01-11

Last Updated 2020-02-27
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] AndyYan:
Reserved

I don't know for how much longer I'll be able to keep building these, but even if I do stop, these should still serve as a good basis for installing GSIs, so you can leverage many of them out there, including my own. As far as I've tested the only major bug on that front is the proximity sensor.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] AndyYan:
Compared to the test builds of last year...

- Now using official LOS device trees - you might have to clean flash even if you come from a previous test build by me

- IMPORTANT regarding PE - if you're clean flashing, flash the package twice so that /system can be populated properly. I have no idea why this is happening...
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] Mollic:
is there any ETA on android 10 Resurrection Remix?

also thanks for your work as usual! :)
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] AndyYan:
Its customization-centric role has largely been replaced by Havoc nowadays, so with my limited SSD space I'm dropping that as well.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] Grick713:
Screen time have a bug, is look like this.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] Devager:
great job for years :)
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] AndyYan:
Have you changed your system font? Seems incompatible.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] dairinin:
Have a problem while installing new PE.

Wiped everything (system, vendor, data). Installed zip (twice, as advised), no error messages.

TWRP warns on reboot that no OS is installed. Phone reboots to fastboot.

Tried twice with the same result. Tried re-downloading zip without success.

Ok, managed to solve the problem. As the device tree is from LOS, the solution is in the LOS thread. Need a recovery with support for SAR. Seems like official TWRP does not. So flashed recovery from the first post of LOS thread and the OS have installed just fine.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] AndyYan:
Thing is, I tried Wight's SAR TWRP and it's the same thing on my side - I really had to flash it twice (but not in the same queue/go).

This shouldn't have happened in the first place either, as LOS flashed just fine without this hassle.
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] SanHelios:
[MENTION=4467696]AndyYan[/MENTION]

Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.

I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
[Xiaomi Mi Mix 2 ROMs, Kernels, Recoveries, & Other] candiduslynx:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/

However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). [MENTION=4467696]AndyYan[/MENTION], can you look into it?

Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.