Hay,
the Surnia of my doughter is rooted, TWRP installed with xposed and some deleted system-apps for space reasons.
I want to upgrade to LAOS directly without installing all the original firmwares between, because of updating-problems (watch out for deleted system-apps and mofiied system partition).
Is it possible or has someone already tried to flash the modefiles of the 5.1 rom and then make a full wipe, installing LAOS and GAPPS and is doing fine?
Can someone help me going the easiest way up to LAOS?
Thanks a lot,
Markus.
Edit: Did it myself. Works great. Just making a full backup with TWRP, flashing modem files of 6.0, rebooting into TWRP, full (!) wiping, installing LAOS and GAPPS, restarting, BINGO
Related
This is just stock LineageOS for the vs985 with no modifications (except baked in root in one edition) built daily from their source code. It's not terribly useful to anyone but people who want to be on the bleeding edge of development for whatever reason (like me), but I figured I'd share. I'll be doing these daily builds for the foreseeable future as long as I own the device or don't change OSes personally.
To install, do one of the following:
If you want to start fresh (or are coming from a non-Lineage based rom):
1.) In TWRP, wipe system, cache, dalvik, and data. Install the standard build (or the standard build with root). Do not install a migration build. Now Install open-gapps if desired. Reboot.
If you want to keep your data (and are coming from a Lineage based rom, official most likely)
1.) In TWRP, wipe system, cache, and dalvik. Install the migration build first, and then an open gapps build if desired. Reboot (it may take a bit). Once you are at your homescreen, reboot back to TWRP, and AGAIN wipe system, cache, and dalvik. Now flash a NORMAL build (with or without root) of your choosing. Again, flash open-gapps. Reboot. All done.
To upgrade, you simply wipe system/cache/dalvik and flash a non-migration build and appropriate gapps.
A warning about migration builds
Migration builds only need to be used once, but they appear to be a one way street. Once you are on my build, you can't "migration-build" your way back to official builds (or at least, I was not able to). You will need to data wipe to go back there. So, caveat emptor. Be sure this is what you want.
Find my dailies (along with build dates) here:
https://www.androidfilehost.com/?w=files&flid=164143
Open-gapps can be downloaded here: http://opengapps.org/
LineageOS Source can be found from the LineageOS github. It was compiled unmodified from this repo:
https://github.com/lineageos
Please, although these are stock code based, they are UNOFFICIAL BUILDS. Please do not bother the LineageOS project for support of these unless you can confirm the issue in an official build.
Thanks for looking! I'll most likely have a new build up tomorrow.
EDIT: Please make sure you are on the 35B bootstack prior to install:
Just flash this via TWRP if you are not sure: https://www.androidfilehost.com/?fid=24052804347843993
Has anyone installed this yet and can confirm compatibility?
I use them daily so they are compatible (if you can trust my word that is).
That said, they are not exactly bug free, but no LineageOS build bleeding edge ever can be.
The build server was thrashing it's disk space for a few days due to a build script failing to clean up after itself... this means a few days of builds were missed. This has been fixed, and we should have daily builds again.
Not sure if anyone uses this, but hey, just an update.
Hands down best ROM I've used on the G3. Everything works, very little FC if ever and I've even gotten Dolby Atmos to work with it. Never going back to anything else.
Glad to hear it. My build server had issues again yesterday, but it appears to be related to a bad stick of ram. I hope to have daily builds moving again tonight.
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
dweezle said:
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
Click to expand...
Click to collapse
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
R-T-B said:
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
Click to expand...
Click to collapse
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Question please.
What's different about this "unofficial" stock Lineage from the "official" Lineage that is avail for VS985?
Why would one want this one vs that one?
It is just built more frequently from source to get more daily changes. Otherwise it is identical. It's mainly for those who like to track bleeding edge changes.
dweezle said:
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Click to expand...
Click to collapse
A twrp restore should work regardless of the bootstack flash.
I just Flashed lineage-14.1-20170623-nightly-vs985-signed and open_gapps-arm-7.1-mini-20170707 it all went ok but it don't find my SIM card on boot, so how am I gonna get my sim card active. plz otherewise I would have to withdraw my choice of this Namely Custom ROM.
Please helpp!! I was using Lineage OS on my LG G3 VS985 it doesn't come with prebuilt root so I was rooting through SuperSU. I reboot my phone into twrp recovery and installed SuperSU.zip and then reboot my phone but now it is showing Secure Boot Error, boot certification failed. Please tell me how to fix this issue
and how is the camera quality of this rom as compared to stock and other aosp/cm based rom?
I flash the 35B bootstack before all and my phone goes wrong.. It is on power off, there's just 2 flicking red and blue led. When I go to the recovery mode, I can choose any proposition, my phone come back to this condition.. Can someone help me please ?^^ I was on Fulmics Rom
This rom hasn't been updated in some time as I no longer have the phone, so I am unsure how to help.
I got Resurrection Remix 7.1 (official 3/15) installed and working and I have never run a custom ROM before on any phone, but I must say WOW. This work(ed) so beautifully. Very responsive and clean interface and the battery life was looking phenomenal. It was basically everything I could have wanted and then some.
Now the bad news. I was trying to run a file manager that seemed to lack root access and I clicked on SuperSu which said it needed to update, I chose "update normally" instead of via TWRP. It ran and said it succeeded but needed a reboot. Now I am in the "Get Resurrected" bootloop and I don't know if there is any way to recover at this point. I can obviously get back into TWRP and I tried wiping and re-flashing 35B bootstack and RR ROM zips. No luck.
Before this ROM I was thinking seriously of upgrading from G3 to something newer but after seeing how well this runs on the G3 hardware I don't see any reason to upgrade given how well this run, though I only had it up to test for 4-5 hours.
Any help would be appreciated. I did find another post on CM13 in bootloop from SuperSu install/update and flashing a 'make permissive selinux' fix which worked for this situation. I am wondering if it may work for RR bootloop as well? Again any help would be appreciated.
Big thanks to Rohlm who suggest system format before re-installing!
I went into the Wipe options in TWRP and selected the format data and then went through the install steps again. Data, cache, Dahlvik wipe, 35B bootstack flash, RR 7.1 flash, gapps 7.1 arm flash and I'm now "Re-Resurrected!" And I checked still have root access!
Cheers,
-Scott
Okay. I am tired of constantly bricking and reinstalling my stock rom onto my Cubot. If not for Titanium Backup i would be so frustrated. So i have decided to ask for help with flashing the Phhusson ROM.
The problem i have is that i do not know the proper steps to install the ROM.
I have unlocked bootloader, installed TWRP, cleared cache, data, vendor, dalvik and installed system.img and magisk for root, but no luck.
I keep getting NO OS installed.
Anyone who successfully installed a CUSTOM ROM for their Cubot X18 Plus please give a tutorial here. Preferably a video tutorial. :good:
Also, if you have any pointers for restoring base band (i have tried flashing stock, copying emmc to root, having driver issues with magic box) i would love help on that but you can private message me if you wanna help (ill pay if you want to be paid, but not much)
You don have to whipe vendor because this is the base folder of the phone its like the kernel but in treble.
You habe to search a pre tested rom on cubot x18 pluss Like AOSP 9.0 from PHHUSSON on GitHub
i wish you good luck, im going to install it to in my cubot, and sorry for my english because im Chilean.
kene200 said:
Okay. I am tired of constantly bricking and reinstalling my stock rom onto my Cubot. If not for Titanium Backup i would be so frustrated. So i have decided to ask for help with flashing the Phhusson ROM.
The problem i have is that i do not know the proper steps to install the ROM.
I have unlocked bootloader, installed TWRP, cleared cache, data, vendor, dalvik and installed system.img and magisk for root, but no luck.
I keep getting NO OS installed.
Anyone who successfully installed a CUSTOM ROM for their Cubot X18 Plus please give a tutorial here. Preferably a video tutorial. :good:
Also, if you have any pointers for restoring base band (i have tried flashing stock, copying emmc to root, having driver issues with magic box) i would love help on that but you can private message me if you wanna help (ill pay if you want to be paid, but not much)
Click to expand...
Click to collapse
Hi, I was able to useflash phh GSI (works just great btw). This is how I ended up doing it:
1. Flash TWRP.
2. In TWRP you'll see errors due to the encryption of the partitions. To resolve this you have to format the userdata partition either with fastboot either with TWRP
3. After fixing the encryption problems in TWRP mount and transfer Magisk to the phone and flash it using TWRP.
4. Transfer the GSI image (A only) and flash it using TWRP. At this stage you could flash it with fastboot as well if you reboot to the bootloader, but don't boot into the system yet. As I said before I used PHH AOSP 9 GSI image.
5. Wipe using TWRP and reboot to system.
The first time I tried to flash it I used the stock recovery wipe function which wipes out the IMEI and stuff, this forced me to reinstall stock rom to set the IMEI with the MTK engineering tools and restart the whole process.
Hej everyone,
I flashed a custom rom from mi-globe a few months. It was working great. Then I had the not so incredible idea of updating with latest miui eu 12, because the weekly update from the update menu was not working. It kinda worked, but it got too buggy. So I wanted to come back to a xiaomiEU Stable Rom.
It is now that problems begin. When I flashed miui eu 12, I got recovery loop. Lost all my data trying to fix, but I was able to flash the stock rom via the amazing XiaomiADBFastbootTools in my GNU/Linux distro. It worked! But the main issue is can not flash the custom rom again. I download the custom rom in the internal storage, flash the twrp via fastboot, enter recovery, create full backup, wipe to factory reset and flash the custom rom. Everything seems successful, but then I get a recovery loop again and when I try to restore the backup, the data folder is filled with folders and files with random chars in the names. Apparently the data folder becomes read-only for some reason as well. Then I have to flash the stock rom and tried everything again. I have done it at least 5 times now. I have searched a lot for some solution and nothing works
I have tried the OrangeFox recovery and the mi-globe rom, same issue. I really want a custom rom :fingers-crossed:, but I have no idea what to do anymore. If I could at least restore my backed up stock rom, it would help a lot.
Please help me out and sorry I posted in the wrong section.
Hi there,
I've reinstalled my Lineage OS in May and have recently installed the latest upgrade. Today, I was using my phone just fine before a subway trip, then after it was stuck in a boot loop (lineage OS circles). My guess is that I accidentally restarted it.
What is the procedure to repair the phone without loosing the data?
I tried:
- Reinstalling recovery, lineage, MindTheGApps in that order
- Wiping the cache partition, wiping the dalvik cache
So far I have not seen any progress. Am I missing something?
I really want to avoid wiping my data as I just set the phone up two months ago.
Did you try dirty flashing the ROM zip by only Wiping the System partition but not Data? I use NikGApps and its not necessary to reflash it during a dirty flash but I flash the latest GApps build in any case. I pretty much use crDroid exclusively and dirty flashing works reliably. Not encrypted though.
Ok, so I did the following
Action -- What I think it does
Install TWRP recovery via fastboot -- to selectively wipe partitions
Wipe System -- to remove system files from the previous update
Wipe Cache & Dalvik cache -- to remove cache files that have previously been written on startup
Install lineage os -- to install a clean OS
Install MindTheGapps -- to install the Google subsystem
System reboot
Files used:
twrp-3.6.2_9-0-beryllium.img
lineage-19.1-20220618-nightly-beryllium-signed.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
Again with:
lineage-19.1-20220716-recovery-beryllium.img
lineage-19.1-20220716-nightly-beryllium-signed.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
Still caught in the boot loop.
I feel a bit lost here.
I did nothing special. Just installed the newest Lineage OS from the GUI and then apparently accidentally restarted it (or it crashed). This should be a common use case. I would expect there to be a guide or wiki that explains and solves this. But from my own Google searches I mostly see recommendations in the line of try wiping and reinstalling.
I am pretty sure, my data is encrypted. Does this mean I am screwed? (i.e., all not backup-ed data is lost?) Was flashing a new Lineage OS & GApps the step that doomed me?
Before the bootloop did you have TWRP installed instead of LOS recovery? Flashing the OTA update via TWRP can be problematic.
I had recovery installed. I reinstalled the Image from Lineage recovery. After this didn't work I tried it with TWRP.
Did you try flashing the build you were using before the bootloop occurred? No clue otherwise how to resolve this. Hopefully someone else can help you out.
Yes, first I tried installing only MindTheGapps, then lineageOS (last version I had) + MindTheGapps. And I tried a number of recent releases.
I also tried the most recent version and now I cannot install earlier versions anymore: "Current SPL: 2022-07-05 Target SPL: 2022-06-05 this is considered a downgrade".
I gave up. Reinstalled everything. Lost a ton of messages for which I did not have the right backup.
Depressing. Nothing I did was special. So I can expect this to happen anytime. I will improve my backup. But still, in the long term I need to find something that is reliable.
Thanks @amn1987 for the suggestions.
Use Swift Backup for backing up apps and their data, SMS, call logs etc. on a regular basis. Works very reliably. You can backup messages to Google Drive as well. Probably can schedule the backups.