sorry for my bad english,i am chinese
items needed:
blu_spark twrp(people says it is better than official twrp.less bug,somehow i cant fully restore a backup in official twrp,get bootloop or error 255,i have not try to use this twrp to do a full restore yet,maybe official twrp will work for you)
i am using
twrp-3.2.3-x_blu_spark_v9.85_op6.img
twrp-3.2.3-x_blu_spark_v9.85_op6.zip
download link
blu_spark twrp:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
unbrick tool:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
los
from lineage-15.1-20180819_185755-UNOFFICIAL-enchilada.zip
to lineage-16.0-20180913_083011-UNOFFICIAL-enchilada.zip
https://forum.xda-developers.com/oneplus-6/development/rom-lineageos-16-0-t3839750
step:
0 already in a working los 15.1 rom
1 remove screen lock(maybe not necessary)
2 backup data partition in twrp(dont need other partion unless you will go back to los 15.1),then copy to a computer,you need to copy other files manualy to a computer for example: photos
3 use unbrick tool to install oneplus rom (nothing bad will happen using this,this way is cleaner,the real reason i use it is because when i installed open beta 3,some serious bug happened,i cant boot into official twrp,i get qualcomm crashdump mode instead and i get device is currupted where it should say bootloader is unlocked),maybe you can skip step 3 and 4 if you are lucky
4 oem unlock
5 download open beta 2 rom to your computer
6 fastboot boot twrp.img
7 wipe then install open beta 2 rom+twrp(twrp says no OS installed when chose reboot ,but it is fine)
8 i booted into open beta 2 rom just to make sure it works,maybe not necessary
9 reboot into twrp ,wipe then install los 16.0+twrp
10 reboot into twrp (twrp says no OS installed when chose reboot ,but it is fine)
11 intall opengapps+magisk
12 boot into los to make sure it works
13 reboot into twrp
14 restore data partition (dont need manually wipe before this)
15 wipe dalvik/art cache(maybe not necessary)
16 boot into system(may take 4 minutes)
i used for a few hours,works fine,no serious bug,dont need to login apps.if you have errors,plz follow this guide precisely,it works for me at least,and i tried this method twice,it works
tip:you can use adb to copy mutiple files or folder at the same time, for example
adb push "F:\oneplus twrp ubrick\lineage-16.0-20180913_083011-UNOFFICIAL-enchilada.zip" "F:\oneplus twrp ubrick\open_gapps-arm64-9.0-nano-20180915.zip" "F:\oneplus twrp ubrick\twrp ob3\twrp-3.2.3-x_blu_spark_v9.85_op6.zip" "F:\oneplus twrp ubrick\Magisk-v17.1.zip" /sdcard/
adb push "F:\oneplus twrp ubrick\TWRP" /sdcard/
bugs i discovered,these bug exist even using normal clean install method(dont keep app data ),this restore method is fine
using opengapps nano or stock
dont have adaptive battery and adaptive brightness(the google AI version),cant copy text in recent view,but have digital wellbeing
privacy guard not working,force close,other appops apps like appopsx not working
Thank you for posting this guide. I have a couple edits/notes.
After you use the unbrick tool, you'll need to use the version of TWRP here, and not the blu-spark version: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Once OB2 is installed, you need the blu-spark version.
Step 7 needs to be repeated. OB2 must be installed twice to cover both A and B slots.
I had trouble finding the Qualcomm drivers, but eventually found something that didn't seem to be bundled with some other software and *also* worked on 64-bit Windows. Some of the links out there are designed for Windows Vista.
0xScott said:
Thank you for posting this guide. I have a couple edits/notes.
After you use the unbrick tool, you'll need to use the version of TWRP here, and not the blu-spark version: https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Once OB2 is installed, you need the blu-spark version.
Step 7 needs to be repeated. OB2 must be installed twice to cover both A and B slots.
I had trouble finding the Qualcomm drivers, but eventually found something that didn't seem to be bundled with some other software and *also* worked on 64-bit Windows. Some of the links out there are designed for Windows Vista.
Click to expand...
Click to collapse
Somehow I only used one twrp,it works for me,I think when you install OnePlus rom in twrp,it has two steps,I think it automatically install in both slots
You may get some battery issus after using this install method,it will automatically fixed in a few days,it seems battery need to adjust
Related
Hi,
I'm about to install CM11 (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip) on my Nexus 5, but wanted to be sure I'm not about do something obviously stupid. I tried using the CM Installer, but it said 'firmware not supported'.
I have
- Minimal experience.
- LG Nexus 5, hammerhead
- unlocked and rooted. (it did a factory reset on unlocking)
- Fresh Android 5.1.1 with bootloader version HHZ12h.
- TWRP 2.8.7.1 (took a backup and copied the whole TWRP folder to my laptop), flashed manually using fastboot flash recovery twrp.img.
- Latest TWRP manager installed from Play Store.
- standalone adb and fastboot installed on my Windows 7 laptop. No SDK. 'adb devices' lists the phone when connected.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip is also present in same folder as adb.exe and fastboot.exe.
Questions are:
- Hope this build of CM is compatible with my Nexus 5 & the bootloader version and whatever else there might be compatibility issues.
- How should I do this: According to "official CM installation on Nexus 5 guide" on wiki.cyanogenmod.org it seems like I'm supposed to push the zip file to /sdcard/0, but /sdcard seems to be a link to /sdcard/emulated/legacy, which contains no folder named '0'. Should I create it and put it there?
If you're coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/
Click to expand...
Click to collapse
OR
Given that "cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/", can I just: boot to recovery, click on Install, select the zip file and swipe to flash?
Finally a general query: Is there any reason I have to connect the phone to my laptop and run any adb, fastboot commands except to transfer the zip file from laptop to phone and to boot into bootloader or recovery with fastboot command? I already have TWRP running.
Thanks
Kashyap
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
I don't use cm, but that sounds like the right file. It doesn't matter which location the zip file is on your sdcard as far as I know, I think they've just said /sdcard/0 to make it easy to find from within twrp. Sounds to me like you've covered all your bases, nice to see someone manually flashing a nexus as a start. I'd go ahead and flash the zip, don't forget to factory reset if you're coming from stock. Also, you may want to find a gapps package if you haven't already. Since you seem to have taught yourself the right way, and your PC is setup for fastboot already, it should be easy to flash back to stock/restore under twrp. You don't even need adb to push files to your phone, you can just download them straight to the device. I generally only use my PC for fastboot flashing to stock,or transferring large amounts of data. Good luck, enjoy your nexus - first boot will generally take just long enough that you'll start wondering if its broken.
Thanks for the quick response.
scissors_cut_paper said:
don't forget to factory reset if you're coming from stock.
Click to expand...
Click to collapse
Just curious why?
If i do a factory reset, will it not delete /sdcard/cm-11-20141008-SNAPSHOT-M11-hammerhead.zip? Do I just copy it from laptop to phone after reset and proceed to flashing? Or there is some way to not wipe 'sdcard' during factory reset?
scissors_cut_paper said:
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
Click to expand...
Click to collapse
I did do a TWRP backup, but selected what to backup in the TWRP manager app, there is no option called EFS. Anyway, I'm creating a new using the recovery UI, where there is a check box called EFS. Thanks!
scissors_cut_paper said:
nice to see someone manually flashing a nexus as a start.
Click to expand...
Click to collapse
Didn't know there was any other more automated option/way. , is there? Only thing I knew was the CM Installer, which said the firmware isn't supported. .
scissors_cut_paper said:
Also, you may want to find a gapps package if you haven't already.
Click to expand...
Click to collapse
Yes, I was planning to, but taking it step at a time. .
I was planning to get gapps-kk-20140606-signed.zip from cyanogenmod.org, but lets see. I'll probably post another question here asking which is the compatible one.
Factory reset just wipes data/cache/dalvik, it should leave your sdcard storage intact. Just out of interest,why cm11? KitKat is pretty long in the tooth, and I've always found aosp based ROMs to perform better than cm on nexus 5. The problem with having no gapps will be no access to play store/google account services, so you'll have to get apps from less trustworthy sources.
Worked
Thanks.
It worked fine. Though it was totally useless without either the play store or basic CM apps. Couple of notes:
- After wipe/factory-reset (from TWRP Recovery UI) /sdcard was untouched.
- Installed the ROM using TWRP Recovery UI -> Install -> Select the zip file from /sdcard and swipe.
- CM Installer on Windows 7 laptop worked fine once the CM was installed. But it downgraded the build from Nov to Aug-2014.
- Also CM Installer removed my TWRP and replaced it with CWM. Not happy.
So actually all that's needed is:
- Unlock the bootloader and root.
- Install TWRP Manager
- Try to use the TWRP Manager's "Install TWRP" to install the TWRP Custom Recovery. If that doesn't work then do it manually. Download twrp.img
- Install ADB and fastboot, you don't need the whole 1GB Android SDK. Just search for "ADB Fastboot without SDK".- Enable USB debug, connect the phone and ensure that 'adb.exe devices' prints a device.- fastboot flash recovery twrp.img- Download the ROM zip file you wanna install on the phone itself, no need to involve the laptop.
- Boot into recovery (e.g. using TWRP Manager -> Reboot options) and do what I did above.
Once you've installed Cyanogenmod, DO NOT use CM Installer. This is written in July'2015. May be things would improve in future.
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
TWRP and Rooting a Cubot Cheetah 2 (Nougat)
Android_Dog_Walker said:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
I have done a lot of searching and found the following;
a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,
b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.
The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.
Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).
Thanks
Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.
rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.
The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.
This thread can now be closed
I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.
Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?
I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.
Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.
Gotcha, hopefully someone will
chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....
Cubot Cheetah 2 Android 7 Root by EpicFail2017
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?
I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?
I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?
What is the 'R' near the signal in your screenshots?
I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..
I was already on the same version of nougat as the download before I started.
1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).
* Note, install the drivers with the phone NOT connected via USB.
2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)
3. Move the patched boot.img from the magisk folder back to the computer.
4. Run the SPFlash tool load the scatter file, select DOWNLOAD and untick everything asides from boot.img
5. With phone switched off, connect it via USB
Flash
Wait until complete
Reboot
Rooted
No loss of IMEI or data.
It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.
Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.
That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/
Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Android_Dog_Walker said:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Click to expand...
Click to collapse
EpicFail2017 said:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Click to expand...
Click to collapse
Anyone uploading a mirror of nougat TWRP, please.
Also i´m kind of shy flashing the recovery with patched boot.img, any experience?
Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"
Do you password protect your recovery?
I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.
An point worth noting is that if you are a new user on needrom, you need to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.
Hi,
Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.
any can fix it on TWRP 3.1.1.1 ?
EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^
Still did not find a public nougat TWRP download
Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?
Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://forum.xda-developers.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943
EDIT: switched to supersu, busybox now working
Yesterday xposed appsops was getting a fix it is still unoffical
https://forum.xda-developers.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89
Edit:
updated to magisks unoffical xposed framework 3.1.4
I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work
liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?
Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.
Hi, I am new to custom ROM's and Rooting my device. And i hope you can help me with my Problem. I have a OnePlus A6003
What i tried so far:
Before i tried installing CustomROM's my device was on OOS 10.3.0
Then i needed to use the "twrp-3.3.1-16-enchilada-Q-mauronofrio.img" to get into TWRP
in TWRP i followed the Instructions from the LinageOS site:
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the previous menu and tap Advanced Wipe, then select the System partition and then Swipe to Wipe.
Sideload the LineageOS .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip
(Optionally): If you want to install any additional add-ons, run adb reboot sideload, then adb sideload filename.zip those packages in sequence.
info_outline
Note: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
(Optional): Root your device by installing LineageOS’ AddonSU, (use the arm64 package) or by using any other method you prefer.
Once you have installed everything successfully, run ‘adb reboot’.
Click to expand...
Click to collapse
I was sure this wasn't the right way cause after i rebooted the device i couldn't get to LinageOS.
After that i could get the "twrp-installer-3.3.1-2-enchilada.zip" (The official version from the TWRP site to work)
Flashed LinageOS the proper way (that's what i thought, lol) through install in TWRP
after that i had the same problem i could boot one time into LinageOS and that was it.
Current State of the Phone:
Bootloader unlocked (check)
Recovery Mode starts LinageOS Recovery
Fastboot is working fine
TWRP is not installed
What i am basically trying to do is:
Install a Privacy Focused ROM (open for Suggestions but i think LinageOS is good)
Root with Magisk
Flash NanoDroid Packages
Flash AFWall+
Flash AdAway
Some questions that i have
Do i need the customized TWRP because my phone did originally run OOS 10.3.0?
Whats the proper way to install a ROM on this device and Root it afterwards with Magisk?
Hi,
Phone : Realme 5 Pro EU version 4GB/128GB.
As the title says, I am trying to install LineageOS then MicroG on my Realme 5 Pro. So far... I've been at this for a couple of days and I've learned a lot, but that was worth it. Still have to see after a couple of days if this install is stable enough.
Usual disclaimer that this is not because it worked for me that it'd work for you etc...
What files are necessary to follow this post?
-> vbmeta.img & twrp.img here : https://drive.google.com/drive/folders/1MUEJkl25gL7zUPXNKFx_I5HLHyfCAzz7 as posted in this guide : https://forum.xda-developers.com/t/...install-twrp-and-install-custom-roms.4177511/
-> C12 Stock ROM from realme : https://download.c.realme.com/osupdate/RMX1971EX_11_OTA_1120_all_s0mRvUGlCJAI.ozip
-> the Lineage 17.1 ROM provided by @kemo12533 here : https://sourceforge.net/projects/myholly****/files/ROMs/RMX1971/LineageOS/
-> the NikGApps Core for Android 10 ARM64 : https://sourceforge.net/projects/ni...ps-core-arm64-10-20210130-signed.zip/download
-> Magisk : https://github.com/topjohnwu/Magisk/releases/download/v22.1/Magisk-v22.1.apk
-> NanoDroid-patcher : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-23.1.2.20210117.zip
-> NanoDroid-MicroG : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-microG-23.1.2.20210117.zip
What I have done so far that works (after tons of FAIL)?
-> Unlocked the device
I managed to unlock the device without too much issue following the guide (link to the guide on this forum is provided above).
-> Installed TWRP
rebooted into bootloader.
"fastboot flash recovery twrp.img"
then proceeded in recovery to TWRP.
Lesson Learned: when "fastboot flash ..." behaves funky (as in not the expected result which is OK), change cable/usb port/computer and don't bother trying to troubleshoot it (I spend a day on this for no result). I have to go on my parents windows computer to fastboot flash but hey it works.
-> Installed latest version of RealmeUI OS (C12 from late march 2021)
TWRP wiped (Dalvik, Cache, System, Vendor, Data)
TWRP format data.
TWRP installed RealmeUI OS C12 without issue
(I did boot it without problem and enabled debugging but I don't think it is required)
-> reinstalled TWRP that had just been overwritten by C12 install.
rebooted in bootloader
"fastboot flash recovery twrp.img"
"fastboot flash vbmeta vbmeta.img"
then booted in recovery to TWRP.
-> Installed LineageOS 17.1 with NikGApps.
TWRP wiped (Dalvik, Cache, System, Vendor, Data) and then formatted data.
TWRP installed LineageOS 17.1
TWRP Install NikGApps.
TWRP installed magisk (which roots the OS).
Rebooted and LineageOS booted without issue.
Note 1 : I tried to install this LineageOS on its own to do a clean MicroG install but on its own it wouldn't boot (same with OpenGApps pico). BitGApps and NikGapps Core both make Lineage Boot, but I settled on NikGApps because it seems automatically 'removed' afterwards when installing MicroG, see later.
Note 2 : The magisk app says that the realme5pro does not have ramdisk. It seems that this is wrong: Magisk does say that phones from 2019 & 2020 are a mess to detect and that the RAMDISK test (Yes or No) is unreliable for those. I followed the manual for No Ramdisk and it corrupted my recovery partition. I followed the manual for yes and it works without issue since.
-> Installing MicroG.
I am now in LineageOS
Magisk Installed Magisk from the same apk and follow instructions to install Magisk properly.
Magisk Installed NanoDroid-patcher & rebooted
Magisk Installed NanoDroid-MicroG & rebooted
at this point the play store icon and app have disappeared (most probably removed by the NanoDroid-MicroG install) and the MicroG Settings app is installed. You still have some permissions to give MicroG and configure it properly, but the following video does a good job of that so I'll leave is at that.
Learned along the way :
It seems to be really hard to brick that phone (good stuff). As long as you can still boot in fastboot you can recover, even if system and recovery don't work.
when "fastboot flash ..." commands don't work when "fastboot devices" lists your device, find another computer, don't waste your time trying to fix this with no result.
write down what works for future reference. I am now documenting every step that works.
Edit 1 : Added Magisk bit. Reorganised post and added details.
Edit 2 : Added MicroG bit. Reorganised post and added details. I guess it's a sort of a guide now...
Hi there!
Does anyone know if it is currently possible to install LineageOS+MicroG on a Samsung Galaxy S20FE Exynos with OneUI 4.1 and Android 12 (SM-G780F/DS)?
Or is there another OS that would allow me to have a degoogled and privacy-friendly smartphone?
Thank you all for your help!
Search for "Lineageos with microg". LineageOS with microgn and f-droid already installed