Database Info

Lineage OS 14.1 Release 1 (uploaded January 17 1025pm eastern)

Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!

beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631

wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.

Awesome work! I've finally got me a full featured daily driver

I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...

After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.

Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk

I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..

This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.

I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.

Any update?

pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.

Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.

won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated

whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance

gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.

derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.

Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.

elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH

derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.

'Official TWRP app' 1.17 is missing features?

To All who could help.
#1
I updated the official twrp app 1.17 on my Sprint HTC U11, running 7.11 & Bad Boyz 2.0 ROM, w/the FW build # 1.28.651.3 & now I've got none of the buttons to go into Install, Backup, Wipe, etc. that showed on the older version's startup screen; & I want to make a new nand backup.
Do I need to get ahold of an older version ofthe Official TWRP android app? If so, where to find it?
#2
Also, using the older version, whose startup screen shows all options Install, Wipe, Backup, etc, could I have accidentally encrypted my phone or TWRP or somethingthat would have caused this? I recall pressing a dbutton on the lower right corner of the old app, & some process ran on my screen too fast to see; I thought I was just 'exploring' what the older Official TWRP App could do & instead some script ran & I had to enter my security pattern & a msg showed that my pkone is encrypted & I have 30(?) attempts to enter the pattern before the phone would be wiped. Oddly, this behavior went away, the prompt for my pattern, when I went into old Official TWRP App & wiped Cache & Dalvik.
With this new version, I wouldn't be able to do that, or Restore a nand backup ? which makes me very concerned.
Please advise. TIA, oldwolf
All I get is what shows on this screenie:

What I see is only the TWRP App that is installed on the ROM to update your TWRP.
Did you reboot to recovery and check? If so please post some pictures and some logs.
In addition this would.habe belonged into the Q&A section, or - if pictures and log would've been available - into the TWRP thread. But let's leave it here for now and get this thread moved to Q&A later.
Sent from my HTC U11 using XDA Labs

5m4r7ph0n36uru, thanks for your reply! I guess I really mixed things up in my mind... I figured that since twrp is a recovery, my question belonged there. Feel free to move it if it is called for; please just leave me a link as to where it will be…
I have worked w/Odin & Safety Strap mod tools on my obsolete S4 & older Droid Razr utils. I only used twrp when I installed a custom rom once, I switched to Sprint just this past June… so I'm not as comfortable yet working w/twrp & its ins & outs.
The thumbnail I attached was fm what I thought would change me over to the new 3.2.1-2 version of twrp.
I followed your advice & rebooted into recovery & voila! The features are all there, Backup, Install, etc.(should have known better - but we all have to learn from our mistakes I guess).
In Recovery mode, I'm still on version 3.1.1-0 of twrp- running FW 1.28.651.3 & 7.1.1 Nougat OS.
#1. Can I put 3.2.1-2 onto my device w/the listed OS & FW versions? or do I need to bring it up to latest FW?
#2. If 3.2.1-2 will work with my current FW, should it be flashed from my computer & if so in which mode? Recovery Mode- or using the Official TWRP App, on my fone?
Not sure what the Official TWRP App fm that thumbnail is for…now I am confused
Your help is much appreciated. oldwolf

New (to me) TMo OP7Pro and my plans - will this work?

I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?

Jaxidian said:
I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?
Click to expand...
Click to collapse
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom

jamescable said:
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom
Click to expand...
Click to collapse
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.

Jaxidian said:
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.
Click to expand...
Click to collapse
I am running open beta on a stock TMobile 7pro. Works great. You don't need to do all the updates. Just flash the open beta after you switch to international.

Hey if u do the call screening magisk way. Be sure to use the Google dailer 39. Apkmirror and make sure the updates is turned off for it.

Alright, so I was in the same boat as you, I bought a T-Mobile 7 Pro model earlier in the week; and nicely asked T-Mobile support through the App a few times to help me SIM-Unlock it so I could do my bootloader unlock and linked the Oneplus Support website and the Unlock page.
I ran into many issues so I'll help you out as I just finished my 6 day journey of making it functional.... Along the way, I lost cell service, I lost all my sensors.... So I'd recommend taking a TWRP backup everytime you're able to successfully boot into the device; Note: my goal was Havoc, so I ended up in a different place than where you're trying to go. I don't know what exact problems you'll run into, but I'm letting you know what I think makes sense from my previous experience over the week.
Your scripted-out plan:
0. Sure, test it, but you'll end up automatically wiping it later when you unlock the bootloader.
1. Sure, install the drivers.
2. You probably don't need to flash stock T-Mobile firmware as it's already running it.
3. You probably don't need to update it.
4. Yes, Flash it to international.
5. You probably don't need to update it. However I'd recommend to unlock the bootloader here;
5a. (The Damned T-Mobile model makes flashing TWRP a bit difficult) I'd recommend taking a note on what Slot is currently active (A or B).
Use "fastboot getvar current-slot" to find out; Then I'd recommend switching to the other slot ( If you're on Slot A, switch to Slot B, vice versa) to flash TWRP first (this overrides your boot image on your active slot, but is the only way to boot TWRP on the T-Mobile variant) and then flash the TWRP installer (this will flash TWRP to both Slots).
5b. After using the TWRP installer from your 2nd Slot, Use TWRP to swap back to the 1st Slot. Now make a complete full TWRP backup with all the boxes checked. Then, copy that backup to your computer so that it won't get wiped in the next few steps. (Do not skip this. If you did this correctly, You will have a place to come back to just in case you **** up your sensors, and cell service like I did.).
5c. Doublecheck if you can actually boot to your original Slot and if everything's functioning. Check if you can boot to your other Slot and see if everything's functioning. (This is where you super-need to make sure you have a safe place to come back to).
6. Sure, you can try flashing the latest Open Beta, but you might have to install TWRP again back in step 5b.
7. You might or might not have to unlock the bootloader, depending on what method you use to flash the Open Beta, your bootloader status might save; Sure, flash Magisk using TWRP.
8. Sure, flash xXx NoLimits using Magisk Manager.
9. Why undo your work and flash the Open Beta again? Don't do this.
With that you should be done.
If at any point you had an issue, I'd recommend using the TWRP backup you created earlier in 5b.
If you super-super have an issue, you'll have to use MSM to go back to stock International firmware.
In my case.... I had super-super issues and I had no TWRP backups.... and I had to use MSM to go back all the way back to T-Mobile stock firmware and start over because I had no service, and no sensors (proximity, gyroscope, accelorometer, etc).
But in the end, I think I have everything functioning the way I want to on HavocOS.

It's been a minute but I now have an update to my journey.
I had to take a quick pause at step 4 of my plan. The phone was SIM-unlocked but the bootloader itself was locked. So I had to do the dance with OnePlus and wait a couple weeks for that unlock code. Well, I finally got that puppy, so was able to start this project this weekend. Here's what I've done and where I'm at so far:
0. Device checked out well. Works great, aside from the screen burn-in issues (which is why I got it so dang cheap).
1. Drivers installed. ADB & Fastboot work great.
2. I used MSM to flash back to TMo firmware after my previous failings when I hit the locked bootloader wall. It worked great to get me to the point where I could generate the phone unlock code request to send to OP.
3. Not needed, although I did this while waiting 2 weeks for OP to send me a code.
4. Done. Worked perfectly. Hello, TMo-less firmware. Also, hello SIM #2 (the 2-week delay gave me time to buy a dual-sim tray).
5. Factory reset as part of the flashing and unlocking. Not bothering with system updates yet.
6. Not yet done this.
7. Bootloader is now unlocked. Magisk is installed but TWRP is not yet installed. This is where I'm at now.
Not hitting any problems. Just ran into dinnertime and my kiddo's bedtime. Thought I'd post this update before I started back up. So far, so good, other than that surprise 2-week delay waiting for an email.

Question Newbie trying to get a12

hello people, I have a small Problem, i have a redmi Note 11 Pro 5g global bought over Amazon in Germany, before i got it i checked for sure that it will get a12 now in my news app they are talking about the Note 11 Pro 5g will get a12, the last Update was only November Security Patch.
and cuz' i read a Bit more about it there are custom Roms, but without twrp so If it gets updatet i need to Reset my Phone again.
sooo is there a way currently to get me a12 or a newer Version with OTA Updates?
since in the MIUI Downloader App there is a global MIUI 13 a12 Rom, with Recovery i read so much about those Things now i dont have a clue anymore i'll attach some Screenshots downbelow.
If there is a Option with only one time resetting the Phone i would do it, with a safe Guide thanks for Reading.

Fendonacci said:
hello people, I have a small Problem, i have a redmi Note 11 Pro 5g global bought over Amazon in Germany, before i got it i checked for sure that it will get a12 now in my news app they are talking about the Note 11 Pro 5g will get a12, the last Update was only November Security Patch.
and cuz' i read a Bit more about it there are custom Roms, but without twrp so If it gets updatet i need to Reset my Phone again.
sooo is there a way currently to get me a12 or a newer Version with OTA Updates?
since in the MIUI Downloader App there is a global MIUI 13 a12 Rom, with Recovery i read so much about those Things now i dont have a clue anymore i'll attach some Screenshots downbelow.
If there is a Option with only one time resetting the Phone i would do it, with a safe Guide thanks for Reading.
Click to expand...
Click to collapse
If you checked that the update is for your device, then you can take it, and flash it through your stock recovery.
By taking the other route, i.e. flashing a custom recovery, and so on, you always can return totally to stock, to take the update you want, if it is available. Also, when some TWRP appears (based on your words), then you can flash any stock ROM, that is prepared to be flashed through recovery.

SubwayChamp said:
If you checked that the update is for your device, then you can take it, and flash it through your stock recovery.
By taking the other route, i.e. flashing a custom recovery, and so on, you always can return totally to stock, to take the update you want, if it is available. Also, when some TWRP appears (based on your words), then you can flash any stock ROM, that is prepared to be flashed through recovery.
Click to expand...
Click to collapse
i would need a Guide dir this why is it so hard

Fendonacci said:
i would need a Guide dir this why is it so hard
Click to expand...
Click to collapse
Sorry for delay, I will show you with images.
Go to Settings/about phone:
Then open it, and tap on 13
Then tap 7 times on 13 Miui 13, to have more options
Then go to the three dots, up to the right, then you'll see the options to flash the package to your device, download the latest ROM package, and navigate to it, then your device will make the rest. Be sure to enable USB debugging previously, and set all the drivers correctly, to have more options, just in case.

Question Help please. Downgrade from A14 to A13 and now stuck on the initial setup. [SOLVED]

So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.

Spell out the adb tools used.. version #
Steps used to "downgrade" your mentioning many different roms, especially confusing because you must flash (all ?) partitions to downgrade especially bootloader and such.
If you used factory web flasher or not. Or another all in one tool. Even just adb tools and double click flash-all.
I thinking you need to use factory flasher, wipe all, flash all partitions. Keep bootloader UNLOCKED.
The statement of trying to transfer data makes no sense since you likely can't get past system installation to get to transfer data.
So post steps please of your methods to get to your post question.
Maybe a better spot to post question, lots of great people in this thread!
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com

SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...

simplepinoi177 said:
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
Click to expand...
Click to collapse
Have got it all sorted now. Went back to 05 May beta and that's working fine. Was using the official flashing tool and flashing all partitions and wiping butbthar was where I was getting the issue.. But now if I just wipe it works all ok.

SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks

shivdubey said:
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
Click to expand...
Click to collapse
i have the same problem, any help?

Had the same issue, I sideloaded latest Android 14 beta 2 OTA image for my pixel 5 and that fixed the problem.
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com

A14 Beta 2.1 was just released and includes the following fix aimed at addressing this issue:
Fixed an issue that prevented users from completing device setup after opting a device running an Android 14 beta build out of the beta program. However, this fix is not backward compatible, so users that want to opt out of the beta program should take the following steps beforeopting out:
Update the device to Android 14 Beta 2.1, either through the over-the-air (OTA) update prompt, or by downloading an OTA image and then applying the update manually.
Reset the pin, pattern, or password that's used on the device by navigating to Settings > Security & privacy > Screen lock. You can use the same pin, pattern, or password that was used previously, but you need to go through the setup flow.
Opt out of the beta program by following the instructions listed for the "How can I opt out and return to a public Android release" question in the FAQ section of the Android Beta Program page.