Related
Latest release
Built from whoshotjr2006/touchpro's sources with minimal changes. All credit to original devs.
I'm not going to commit to regular updates but I'll try to do occasional ones.
Recommend using this TWRP (also stolen from touchpro).
Installation:
Enable developer options in stock ROM (tap build number a bunch of times)
Enable 'Advanced Restart' in developer options
Hold power button, select restart, restart to bootloader
Use fastboot to unlock bootloader
Use fastboot to flash TWRP recovery
Reboot to recovery using fastboot command
Wipe everything in TWRP, format data, and factory reset
Push ROM to /sdcard/ and install
Optionally push Gapps and/or LineageSU and install
Boot and enjoy (first start might take a while)
Tested on a T-Mobile LG G Stylo, all seems well.
As far as I can tell, everything is working fine. You should be able to dirty flash if you are using another Lineage 14.1 build but I haven't tested it.
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
ItzBluestone said:
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
Click to expand...
Click to collapse
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
jsheradin said:
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
Click to expand...
Click to collapse
oh, well that's unfortunate...
So what is different? Just security updates?
This ROM breathed new life into my old MetroPC version of this phone (2GB/16GB)!
I bought this phone two years ago refurbished and carrier-unlocked (other than banned on MPC) off Amazon. Looked brand new. I just installed a new battery last month. Original battery wore out.
ROM works beautifully. Nice to be free of the factory cruft. Also, the TWRP from your OP works much better than the one I had been running. (Neither TWRP reads the current time/date through.)
I had been rooted with SuperSU, now I'm rooted with Magisk. I flashed mini Gapps 7.1.
I have not tested NFC yet.
Thank you for this ROM and your post!
My TMo h631 will not take the image. During the install it will kernel panic and throw an error.
I do factory reset, wipes, formats but still no go.
Anyone knows how I can fix it?
Will this work fine on the LGM631?
why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......
Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?
There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.
Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.
Hi,
My Xiaomi 12 still hasn't gotten an new update and is stuck on MIUI 13.0.27.0( SLCEUXM) with security patch of oktober 2022.
I would like to get to the latest miui 14 and would like to know what is the best way to manually update this safely with a original ROM?
Should I do this incrementally start at MIUI 13.2.6.0 and then go to the next till I get to the latest or can I just update to the latest MIUI 14 directly?
Tnx
Gradually is the safest method.
Skipped the Beta stables.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Thank you for the quick response.
I downloaded the MIUI downloader app are those ROMS good to?
I need to choose for a recovery ROM and then I can install it with the updater app right? So starting with version MIUI 13.2.6.0 would be the safest?
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
NOSS8 said:
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
Click to expand...
Click to collapse
You mean this one right?
It says it's only around 80mb is that correct?
When it's for a update from Android 12 to Android 13.
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
So I tried to install the stable recovery ROM MIUI 13.2.6.0.TLCEUXM but it didn't work I keep getting this message "can't verify update can't flash this stable rom"
Then I tried a newer version recovery ROM MIUI 14.0.5.0.TLCEUXM but same message.
Also tried your suggestion to use the incremental update of the current ROM V13.0.27.0 but then I got the message "can't verify update can't downgrade ROM version"
Do you have any other ideas on how to fix this problem?
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
NOSS8 said:
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
Click to expand...
Click to collapse
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Jappie3 said:
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Click to expand...
Click to collapse
Nope, you can re-lock the bootloader after installing the stock rom.
No need with a Xiaomi Eu rom (certified play store, everything works).
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Jappie3 said:
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Click to expand...
Click to collapse
Nope,only solution unlock the bootloader.
Just to be sure I downloaded the 2 latest versions that I hadn't tried yet.
The recovery ROM of version MIUI 14.0.7.0.TLCEUXM and 14.0.8.0.TLCEUXM.
And they both seem to work
Since I'm still on Android 12 now and missed so many updates in-between these 2 latest versions. Would it be safe to install one of these?
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
NOSS8 said:
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
Click to expand...
Click to collapse
So it's not safe to just install one of these recovery versions manually with the updater?
Jappie3 said:
So it's not safe to just install one of these recovery versions manually with the updater?
Click to expand...
Click to collapse
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
NOSS8 said:
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
Click to expand...
Click to collapse
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Jappie3 said:
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Click to expand...
Click to collapse
Zero risk does not exist and this risk increases when you force the update by skipping versions.
NOSS8 said:
Zero risk does not exist and this risk increases when you force the update by skipping versions.
Click to expand...
Click to collapse
Oke, yeah I wanted to do it step by step till I got to the latest miui 14 and still don't get why the older versions don't work.
The only older version I could find that also worked was version V13.0.33.0.SLCEUXM but can't find much about that update.
Logical sequence