Related
Ive noticed many people with older TWRP versions having problems with the updater script when installing 4.4 roms you need to be on the latest version of twrp (CWM may also need to be on a recent version). This tutorial will cover TWRP. Goo manager will not work for installing the latest TWRP recovery version on grouper. The following will give you the basics on how to use fastboot to flash a recovery.img (In this case twrp)
Things you will need:
A PC
Android SDK http://developer.android.com/sdk/index.html
TWRP recovery.img for grouper http://techerrata.com/browse/twrp2/grouper
A basic understanding of terminal/command prompt
You will need a PC and the android SDK (SDK http://developer.android.com/sdk/index.html) for fastboot to push the recovery file. TWRP can be found here (http://techerrata.com/browse/twrp2/grouper) you need the 2.6.3.0 version. Extract your android sdk and move your twrp image file (openrecovery-twrp-2.6.3.0-grouper.img) to the platform-tools folder in the sdk (This is where fastboot/adb are). For simplicity's sake rename your twrp file to recovery.img Enter command prompt or terminal depending on what OS you are using (windows/linux) and navigate to to your platform-tools folder in the SDK folder (where you should have moved your recovery.img) using the cd command. (plug device in) Once there check to see if you device is connected and seen with the adb devices command hopefully you will see a wonky alpha numeric code with "device" after it. If you dont you need to enter developer setting to enable adb. You do that by going into settings/about tablet and tapping build number 7 times. That should give you a developer options in settings check to make sure USB debugging is enabled. If all is well reboot your device into the boot loader with the adb reboot bootloader command once your device is at the bootloader check fastboot with fastboot devices you should see another wonky output with "fastboot" after it. The final command to push your new twrp image will be fastboot flash recovery recovery.img You should see some output saying how long it took to push the file it should not take that long. That should cover it! Now you should be good to go with the 4.4 rom's floating around.
There are many tutorials online explaining this process I just thought customizing it to the grouper would help those less comfortable with adb/fastboot. It's always a good idea to know how to use these tools you never know when you might need to use them. Anyone with question's feel free to ask.
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That will work. But knowing your way around adb/fastboot can't hurt. There won't always be a GUI to do everything for you.
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know of flashify, awesome. Thx, really fast and easy method. Best thing is I didn't even need my pc for it
Thanks for the tutorial but surely this belongs in q&a, help etc not android development ;p
Sent from my Nexus 4 using XDA Premium 4 mobile app
Actually it's suited to the General section (guides and all). I appreciate you advising the fastboot method (I use it too), but it can b a pain for people who don't have their devices configured (configuring it can be a pain sometimes too). Flashify, as one member said, is a great alternative. BUT you *may* brick your device if you flash something to the wrong block device (possibility of that happening to an expert user: 0.0001%; possibility of that happening to a new user: 1%). Just my two cents.
I agree guys this should be in general. I've never posted anything but a build and didn't even think about it. Do I need to get a mod to move it? As for flashify sounds like a great tool. I've never had the pleasure of using it but if it works and people are comfortable with it more power to it. Personally fastboot is what I'm comfortable with it might seem a little in depth but really its quite simple especially if you use adb for logcats and are setup.
OP No worries, moved and thank you.
To flash 4.4 ROMs one could follow this tutorial, or one could simply flash this .zip of the latest version of CWM:
http://forum.xda-developers.com/showpost.php?p=46053223
So, i've bricked it already.
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
ziffius said:
Hello experts and knowledgeable persons!
First, i'm a noob.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery, copied to PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated.
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
So now what do I do, as I don't want to make things worse. I am doing a factory reset before installing. The error i'm getting is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
Click to expand...
Click to collapse
I'm sure this is not what you want to hear but if all else fails push the factory.IMG you will be starting from square one. You can try pulling your backups off but might as well start over for 4.4
blankit said:
Or just install flashify and it basically does all of this for you. I did it and it worked.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much for this recommendation. Really nice. Simple and took out all the nervousness of using the computer to push these files etc.
REally truly best for flashaholics.
question
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Ergina95 said:
Won't it work too if you just flash the zip from twrp itself? I'm running 2.6.3.2 and I read somewhere that i can simply install the new version (2.7.0.0.) zip from the recovery itself..Is it right??
Click to expand...
Click to collapse
Did you ever try just flashing it and if so, did it work?
for some reason i cannot download the twrp ..it stuck at 99%
tried 2 version of twrp..hurm
Mookie2014 said:
Did you ever try just flashing it and if so, did it work?
Click to expand...
Click to collapse
yeap! did it! worked perfectly :good: just flash zip updates through the recovery
Hey guys,
I recently purchased a Mi5 in China and had a hellish experience trying to get a working rooted international ROM on it even though I am definitely not a noob at android. I found out that most issues I had were result of small/stupid mistakes that can be easily avoided with the proper knowledge, so I decided to write a super quick how to on the process for anyone that might need it in the future. There are similar guides out there, and I will refer to some (all credit goes to original posters) but I found that most are incomplete/not updated/plain wrong. Please also note that this guide is updated to June 20th, newer ROM versions might require different steps.
This how to assumes you are familiar with the standard ROM flashing process, in case anyone needs a more detailed explaination of some of the steps, you can reply or search XDA elsewhere, most of the stuff has been mentioned here and there before.
1. Check that your hardware is ok (dial *#*#64663#*#* in dialer, you will enter hardware test mode, check every single item carefully)
2. Request a bootloader unlock from Xiaomi, unlock the bootloader: follow instructions here http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
3. Now that Your bootloader is unlocked, you have 3 main options for working ROMs: Xiaomi's Global Stable, Xiaomi's Global Dev, Xiaomi.eu's unofficial Stable. If you want to play it safe, I suggest to go with the Xiaomi's Global Stable, otherwise choose Xiaomi.eu's unofficial Stable. I did not test extensively all three, so this is just a general recommendation.
4. In any case, you will need to use the official Xiaomi's flashing tool (Miflash) to do your first ROM flash. Just follow the process here: http://en.miui.com/a-234.html and you'll have flashed your new ROM. In case you want to flash Xiaomi.eu's unofficial Stable, follow the same process but get the flashable ROM here: https://xiaomi.eu/community/threads/xiaomi-eu-multilang-rom-for-xiaomi-mi5-unlocked-bl-only-released.31231/
5. Boot into your newly flashed ROM, check once again that hardware is ok (see step 1.). Please also see step 10b for a tidbit of additional info if You're in China.
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
7. Once you are in TWRP, the recovery will ask you for a decryption password, just press cancel, then "Swipe to allow modifications"
8. Sideload (you cannot install from internal storage since you will not be able to access it at the moment) the latest SuperSU stable, which you can find here: http://forum.xda-developers.com/showthread.php?t=1538053. Please note that you WILL need the latest version, anything earlier might just get you a bootloop. And please do NOT format /Data to make it accessible to TWRP as that will also likely result in bootloop. Just sideload whatever you need.
9. Do NOT wipe Dalvik or Cache, reboot into System.
10. Congrats, You're done. Have a beer/coffee/tea and pat yourself on the back.
10b. In case You're in China, and this is Your first Android 5.0+ ROM, you will happen into a "bug" (it's not really a bug, but a result of China's Great Firewall), where whenever you connect to a Wifi, the phone will think you have no internet access and that will cause a whole host of issues (won't reconnect automatically, will try to default to 4G etc.). If so, just enable ADB Debugging and type adb shell "settings put global captive_portal_server httpstat.us/204" . That will mostly solve it (you might still get some weird result with some APs, but toggling Wifi should solve the problem for that AP forever.
Lazer Bear said:
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
m_adnan said:
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
Click to expand...
Click to collapse
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
no, nothing happens on the screen, it stays in fb mode without any reaction. adb and fb devices doesn't return any device connected.. if i do an fb reboot it told me "waiting for any device" so the only option to get it run again is to power off.. yes of course, it's the recovery.img with the modified boot.img..
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
i want only to inform you, i get it to work.. the problem was my rom, miui 8.. for miui 8 you will need a new version of twrp, which you can download here: https://yadi.sk/d/oj6Z-0u7sXdw6 after that, i was able to boot to the twrp recovery without flashing it, so i keept everything original like it was and was able to sideload the supersu and get root without to format my data.. when you start the recovery it came in chinese, but when you click on the right button you can choose your language.. that's it.. thank you for you support dude!!
Is it only way to switch from chinese ROM to official global ROM to have unlocked bootloader? If it is, is there any other way of unlocking it, waiting 15 days to get permission seems ridiculous.
Lovely step by step guide. But, any idea if it will wipe the user data and/or internal sdcard when moving from the chinese to international version?
I have successfully unlocked the bootloader using the requested unlock code.
Connected device to computer and sent commands using adb and Motorola drivers.
I would like to root the device (in order to obtain more control over install/uninstalling Apps)
I would like to continue with the STOCK ROM that I have.
I would like a system backup including the recovery. I want to install and use TRWP for that purpose before rooting the device using Magisk (as this modifies the recovery partition).The problem is first
1) confusion over my device on several posts. This is the UK version Pettyl XT1920-15 variant. (some posts are for the U.S. model, which has a fundamentally different system).
2)The tutorial says to install TWRP before Magisk, however to flash TRWP does it not require that the device be rooted?
I have attempted to follow the tutorial to install Magisk to root. I can not flash TWRP.
I have placed this file TWRP-3.2.3-TwrpBuilder-pettyl-2018-10-28_04-33.img in the adb folder from where I issue commands using PowerShell on windows.
3)I get the error: '(bootloader) uncertified or corrupt image)' straight away.
I now get an annoying message displayed in the top left when booting.
message: bad key
In addition to the tutorial(https://www.xda-developers.com/how-to-install-magisk/) I have carefully read this:
https://forum.xda-developers.com/moto-e5/help/moto-e5-xt1920-15-pettyl-unlock-t385958
and this one: https://forum.xda-developers.com/moto-e5/how-to/root-magisk-moto-e5-xt1944-2-norarow-t3824856
The bad key message persisted after I re-lock the bootloader.
Someone with this problem was advised to install stock ROM then re-lock the bootloader but I have not touched my ROM.
Any assistance would be appreciated.
You should be having a similar problem to what I had with my XT1924-4. You must remove the encryption from the device for the recovery work. By removing the encryption all your data will be lost so it's good to have a backup before:
https://forum.xda-developers.com/mo...very-twrp-3-2-3-x-moto-e5-plus-t3912189/page2
Can you give me a step-by-step procedure to follow remember that I am using windows not Linux to connect.
If I just wanted to get it back to as it was (without the bad key) can someone please assist a newbie.
Could you identify what these are and which ones are needed ?
Moto E5 Play pettyl 3.2.3
Moto_E5_XT1920-15-recovery.img
Moto_E5_XT1920-15-rooted_magisek_boot.img
platform-tools_r28.0.2-windows.zip
TWRP Backup Tool v1.1.zip
TWRP-3.2.3-TwrpBuilder-pettyl-2018-10-28_04-33.img
twrp-3.3.0-0-nora.img
XT1920-15 STOCK ROOTED FIXED.zip
XT1920-15_PETTYL_TESCOGB_8.1.0_OPGS28.54-53-2_cid50_subsidy-TESCOGB_regulatory-DEFAULT_CFC.xml.zip
- In case some step fails, just make sure your bootloader is unlocked.
- I assume you have a working adb and fastboot. I used the official Google package: https://developer.android.com/studio/releases/platform-tools . It's possible you will still have an older version installed because some "pack" installed it and put it in your path. How to edit PATH? What is PATH?! https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
- Advanced Reboot is an option so you can easily enter recovery/fastboot mode. Enable it in Developer Options. How to enable Developer Options? Tap Build Number several times.
I realize the guide is long but it's overly detailed. If you get stuck, have questions, just ask and I will also edit the OP to answer more questions / clarify on points I guess.
Let's go back to latest OOS9.
Make sure to back everything up. If you have Google One, you can do a backup there. If you have root, even better, you can do a full backup with TWRP. I would also copy every important files over to my PC as well - just in case.
Make sure you are unlocked. This can reset if you flashed a full system update or anything so just make sure. If not, unlock.
Grab the MSM toolkit - we will use this to flash back OOS9. See: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In my case I didn't have to mess with drivers or anything, just had to run the tool as admin. However, do read the steps, follow them in case you run into any trouble. Also, I just plug in the phone from a power off state with VOL buttons held down, start it, and I can start the flash process.
At this point you are locked, but does not matter for now. Thing is, now you are on a bit borked image. The stock image has broken fastboot, and might be AA or BA. Point is, you have to flash the correct update at this point. Grab the correct 9.5.11 for your device (AA = global; BA = EU): https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
Just copy it up to your device and use System Update -> Local Update once again to flash it.
Now it's time to flash LineageOS 16.
Now it's time to bootloader unlock again. (Via Developer Options, enable oem unlock and advanced reboot, go into Bootloader, use fastboot oem unlock.)
Now download the latest LineageOS rom from the official site: https://download.lineageos.org/guacamole
Copy up the files to your phone. You can also use adb push at later step. I leave it to you. Copying up might be easier.
Use fastboot boot ...img to boot up the latest unofficial TWRP: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 . You need the .img, but also grab the installer. Make sure you grab the Pie version, LOS16 == Android 9 (Pie).
Once you are in TWRP, go Install, and pick the Lineage zip. Then make sure to do a Wipe from the TWRP menu.
Reboot, let phone boot LineageOS. Shut down once it's booted. No need to set anything.
Press VOL_DOWN + Power to go into Lineage Recovery. Press Sideload here.
You need to grab "Mindthegapps" package from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps and you need to use adb sideload ...zip to load it onto the phone. It will cry about the zip being unverified, just tap proceed.
Now, once it's installed, wipe again from LineageOS Recovery again. At this point, you can also sideload TWRP. You need to use the .zip, and again - make sure you have the Pie version.
Phew, we are almost there! Reboot, log in to Google, do whatever. Set up your device.
Now, finally, let's finish up with SafetyNet.
Once everything is done, install the Magisk Manager APK and grab the ZIP from here. Since you have TWRP, you can just grab the zip to the phone itself.: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Enter TWRP by using Advanced Reboot, Install magisk ZIP.
Almost done!
Go into Magisk Manager, make sure all is green. Go into the left hamburger menu -> Downloads. Grab "MagiskHide Props Config", Install. Reboot.
Now you have to install "Busybox" from Play Store, and you need to install a Terminal Emulator from Play Store as well. Just grab any.
Go into BusyBox, grant root, Install.
Open Terminal, type "su", then type "props".
Just go through the menu system and pick your phone. Just type in a number, and enter. And so on. If you get stuck / afraid to do harm, just reboot the phone and install busybox again, open terminal again, try again. Or ask.
Upon rebooting as you go through the tool, SafetyNet should 100% pass upon reboot.
Thanks for this guide. I can' use MSM toolkit because I'm not on windows. Is there a linux version? Why can't I just dirtyflash 9.5.1.1 zip over installed OOS 10?
Great guide. I just have one question for you. I have a GM1910 Model of the phone with international rom. I'm currently on Oxygen OS 10.0.2, can I still follow your steps to downgrade to the 9.5.1.1 and then flash Lineage as per your instructions? I'm new to the OnePlus devices and I want to be sure before doing something that I'll end up regretting. I know that with my S10+ I was able to downgrade between builds easily, but don't know what to do with my OP7P.
Thanks for your time and help in advance.
Edit: How stupid of me, I didn't even read properly before commenting. My apologies. Your title clearly states how to install Lineage OS from OOS10. Disregard my question about downgrading. I just would like to know if my GM1910 model is supported with Lineage or other OOS ROMs. I would think yes, but better to make sure of course.
wp007 said:
Thanks for this guide. I can' use MSM toolkit because I'm not on windows. Is there a linux version? Why can't I just dirtyflash 9.5.1.1 zip over installed OOS 10?
Click to expand...
Click to collapse
Usually, you cannot dirty flash an older Build to downgrade. This will most likely cause an issue. You need to perform a clean install. I'm not entirely sure in OP7s case, but I do know this applies to Samsung devices and many others as well.
If one unlocks bootloader, flashes twrp and then installs LineageOS16 + openGapps only on guacamole, will they pass safetynet or do they need magisk?
Iolaum said:
If one unlocks bootloader, flashes twrp and then installs LineageOS16 + openGapps only on guacamole, will they pass safetynet or do they need magisk?
Click to expand...
Click to collapse
Magisk is most definitely required. Without it you cannot pass safetynet.
[*] Just go through the menu system and pick your phone. Just type in a number, and enter. And so on.
[/LIST]
Click to expand...
Click to collapse
I have followed all of your instructions and have successfully installed Lineage, TWRP, and Magisk. I've even downloaded the Magisk hide prop from downloads. The only thing I DO NOT understand is STEP 7. PLEASE explain what you have to exactly do here. I don't understand what you mean by: "Just go through the menu system and pick your phone. Just type in a number, and enter. And so on." After I type su, and then props, I get the following options:
1. Edit Device Fingerprint
2. Device Simulation(Disabled)
3. Edit MagiskHide props
4. Add/edit custom props
5. Delete prop values
6. Script settings
7. Collect logs
r. Reset all options/settings
b. Reboot Device
e. Exit
Where do I go to select my phone and number as you're mentioning? And when you say just type in a number and enter? What does that mean? What exactly do I type in? Any random number and enter? I don't understand this at all.
I'd appreciate some feedback here.
- Thanks
Edit: Turns out it only needs the fingerprint to be updated. (ro.build.version.security_patch) Do you have such a code. The developer says he has OP7P added to the list, but I for one, cannot seem to find it. What have you put for yours?
Edit #2: Issue has been resolved. Just did some digging of my own and figured it out. So all that needs to be done is you need to pick your device from the options of 1. Edit device fingerprint, follow the menu options until you see select from certified devices, and then you will see a list of certified devices.
Edit#3: Unfortunately, my devices model is not listed for the certified fingerprints. My model is GM1910, and I tried using the 1911 model, but it doesn't seem as though it worked. Because Google Play is still saying device not certified. Any other model numbers I can try for my model (GM1910)?
Edit #4: What a rough day it has been LOL. Finally found a working version. GM1913 works fine and I can confirm that my device has been indeed certified by Google Play Store. So for my model (GM1910) the GM1913 is the one that works. Ignore all of the above as I've explained it all here in case someone else is confused.
malimt said:
I....
Click to expand...
Click to collapse
Oh man, I am terribly sorry I wasn't really around. Sorry.
One major thing that I cannot figure out - I wasn't able to update.
For some reason after I updated LOS (via TWRP), my whole installation of LOS + Gapps broke.
Now, I needed my phone ASAP so I had to revert to OOS quickly because I needed my phone the next morning.
But, maybe it would work if you update from LineageOS itself.
I would VERY, VERY heavily recommend doing a TWRP full backup before attempting a LOS upgrade.
Shouldn't take long, for me it was like 10 minutes tops, I copied over the files to my PC and that was it. If something breaks, just copy the backups back and restore the backup.
If someone figures out a safe way to upgrade from LOS to LOS... let us know and I'll update the thread.
Ps.: In case your LOS breaks during an upgrade and your backup doesn't restore, you can install OpenGapps now via TWRP (you need the bigger package). This way you'll still have permission issues (like for some reason all Google apps will have bad permissions, so you have to give all perms to each one-by-one) BUT you will have a kinda working phone...
h8Aramex said:
Oh man, I am terribly sorry I wasn't really around. Sorry.
One major thing that I cannot figure out - I wasn't able to update.
For some reason after I updated LOS (via TWRP), my whole installation of LOS + Gapps broke.
Now, I needed my phone ASAP so I had to revert to OOS quickly because I needed my phone the next morning.
But, maybe it would work if you update from LineageOS itself.
I would VERY, VERY heavily recommend doing a TWRP full backup before attempting a LOS upgrade.
Shouldn't take long, for me it was like 10 minutes tops, I copied over the files to my PC and that was it. If something breaks, just copy the backups back and restore the backup.
If someone figures out a safe way to upgrade from LOS to LOS... let us know and I'll update the thread.
Ps.: In case your LOS breaks during an upgrade and your backup doesn't restore, you can install OpenGapps now via TWRP (you need the bigger package). This way you'll still have permission issues (like for some reason all Google apps will have bad permissions, so you have to give all perms to each one-by-one) BUT you will have a kinda working phone...
Click to expand...
Click to collapse
Thank you for your response. Never apologize, you have a great guide here. I understand you were busy and had to step away. Also, I'm not sure why you experienced that because I followed your guide every step of the way and everything went perfectly, aside for the safetycheck but I managed to figure that out so you're good! Furthermore, I used Dec. 3 build and right after I installed it, there was an update. I updated the phone in the settings of LOS itself and it worked flawlessly, I downloaded the OTA and updated, rebooted and it was great! No issues there. Did yours use the OTA update? If not, give that a try.
Thanks again for a such an easy guide! Its great! Really works!
I hate A/B partitioning. It only works in increments with your guide, outdated tools everywhere and a ****ty system, on top of not having an sd card. I loved my Samsung. Not for the Touchwiz, bloat etc, but they had sd cards an the old system, which just....worked. Either the gapps fails, the twrp gets overwritten or it boots, without actually loading magisk or gapps. It seems random if the lineage recovery wants to boot to a or b. This is horrible, but now I have to finish it....
You have not specified what you include in a "wipe". This is never the same for anyone, often not necessary and mostly something people do superstitiously - Therefore clarification would be nice. Still fighting with getting this ****ty system to work. Hope it will be restored with a OOS10 flash, if this keeps failing
malimt said:
Usually, you cannot dirty flash an older Build to downgrade. This will most likely cause an issue. You need to perform a clean install. I'm not entirely sure in OP7s case, but I do know this applies to Samsung devices and many others as well.
Click to expand...
Click to collapse
https://www.getdroidtips.com/how-to...d-10-q-to-android-9-0-pie-on-oneplus-7-7-pro/
h8Aramex said:
- In case some step fails, just make sure your bootloader is unlocked.
- I assume you have a working adb and fastboot. I used the official Google package: https://developer.android.com/studio/releases/platform-tools . It's possible you will still have an older version installed because some "pack" installed it and put it in your path. How to edit PATH? What is PATH?! https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
- Advanced Reboot is an option so you can easily enter recovery/fastboot mode. Enable it in Developer Options. How to enable Developer Options? Tap Build Number several times.
I realize the guide is long but it's overly detailed. If you get stuck, have questions, just ask and I will also edit the OP to answer more questions / clarify on points I guess.
Let's go back to latest OOS9.
Make sure to back everything up. If you have Google One, you can do a backup there. If you have root, even better, you can do a full backup with TWRP. I would also copy every important files over to my PC as well - just in case.
Make sure you are unlocked. This can reset if you flashed a full system update or anything so just make sure. If not, unlock.
Grab the MSM toolkit - we will use this to flash back OOS9. See: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In my case I didn't have to mess with drivers or anything, just had to run the tool as admin. However, do read the steps, follow them in case you run into any trouble. Also, I just plug in the phone from a power off state with VOL buttons held down, start it, and I can start the flash process.
At this point you are locked, but does not matter for now. Thing is, now you are on a bit borked image. The stock image has broken fastboot, and might be AA or BA. Point is, you have to flash the correct update at this point. Grab the correct 9.5.11 for your device (AA = global; BA = EU): https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
Just copy it up to your device and use System Update -> Local Update once again to flash it.
Now it's time to flash LineageOS 16.
Now it's time to bootloader unlock again. (Via Developer Options, enable oem unlock and advanced reboot, go into Bootloader, use fastboot oem unlock.)
Now download the latest LineageOS rom from the official site: https://download.lineageos.org/guacamole
Copy up the files to your phone. You can also use adb push at later step. I leave it to you. Copying up might be easier.
Use fastboot boot ...img to boot up the latest unofficial TWRP: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 . You need the .img, but also grab the installer. Make sure you grab the Pie version, LOS16 == Android 9 (Pie).
Once you are in TWRP, go Install, and pick the Lineage zip. Then make sure to do a Wipe from the TWRP menu.
Reboot, let phone boot LineageOS. Shut down once it's booted. No need to set anything.
Press VOL_DOWN + Power to go into Lineage Recovery. Press Sideload here.
You need to grab "Mindthegapps" package from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps and you need to use adb sideload ...zip to load it onto the phone. It will cry about the zip being unverified, just tap proceed.
Now, once it's installed, wipe again from LineageOS Recovery again. At this point, you can also sideload TWRP. You need to use the .zip, and again - make sure you have the Pie version.
Phew, we are almost there! Reboot, log in to Google, do whatever. Set up your device.
Now, finally, let's finish up with SafetyNet.
Once everything is done, install the Magisk Manager APK and grab the ZIP from here. Since you have TWRP, you can just grab the zip to the phone itself.: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Enter TWRP by using Advanced Reboot, Install magisk ZIP.
Almost done!
Go into Magisk Manager, make sure all is green. Go into the left hamburger menu -> Downloads. Grab "MagiskHide Props Config", Install. Reboot.
Now you have to install "Busybox" from Play Store, and you need to install a Terminal Emulator from Play Store as well. Just grab any.
Go into BusyBox, grant root, Install.
Open Terminal, type "su", then type "props".
Just go through the menu system and pick your phone. Just type in a number, and enter. And so on. If you get stuck / afraid to do harm, just reboot the phone and install busybox again, open terminal again, try again. Or ask.
Upon rebooting as you go through the tool, SafetyNet should 100% pass upon reboot.
Click to expand...
Click to collapse
GeeAyeZee said:
https://www.getdroidtips.com/how-to...d-10-q-to-android-9-0-pie-on-oneplus-7-7-pro/
Click to expand...
Click to collapse
Awesome! Thanks. I guess I'm liking the OnePlus more than my S10+ now. Samsung makes much more difficult to rollback using Odin and such. But this is just great!
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.
kouzelnik3 said:
There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.
Click to expand...
Click to collapse
Thank you so much... Can you link a tutorial or something to show how to root my phone? I wanna use substratum and I read Andromeda no longer works I've been on iPhone too long I forgot all the cool things android can do
s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
OnePlus 10 Pro NE2215 ***ROOTED*** (EX01 Update! READ BEFORE UPDATING)
This is for the NE2215 Rom. Step 1: Unlock your bootloader. Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary. https://github.com/topjohnwu/Magisk Step 3: You can use either patch the stock boot or use my...
forum.xda-developers.com
s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help
s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help
Your first step will be to quickly set up the phone so your ready to handle the bootloader. Get past all set up, it doesn't matter what you do as your wipe the device anyway.
Second is going about the tackling the bootloader (oem unlocking) Plenty of guides however please use below Make sure your sat on the home screen (unlocked)
Bootloader link bro
(Once you have done this leave the terminal open, you need this again.)
Afterwards, do a quick setup, nothing major to this as your be wiping again anyway
g96818 was kind enough to post a quide here : Rooting​
I will refer to his links shared from now however in such a way you can stay here.
Assuming bootloader unlocked, device setup, now download and install the apk :Magisk root
You will also want his stock boot file being this here : Boot.img
With magisk open go to 'install' and select the boot image to patch it. Once it is patched up, connect back to the PC and copy the file to the same folder as the bootloader/ADB files . (rename the file to "patched_boot")
*terminal used before*
\To Reboot to bootloader - this also checks connection indirectly ( Copy from here and right click in CMD/terminal to paste it in)
Code in terminal:
adb reboot bootloader
(after a minute for two)Followed by:
fastboot boot patched_boot.img
After, reboot the phone so it powers up, maybe takes a tad longer but it should actually be very quick. (This is known as a temporary boot)
Then simply, "Open Magisk and perform a direct install". Afterwards i personally would reset the phone and set it up again properly (accounts, email, porn ect). The files you need remain.
Once set up, just be sure to reactivate developer options (OEM will now remain unlocked however re-enable USB debugging (if you have any issues this will save you!!!!!!!)) you cannot perm brick this phone unless you miss this one critical step up.
Reinstall magisk (I found my phone kept it however i also have it naturally on my play account so i may have missed it installing) Just check its there, any concerns you can now just directly flash again with no need for the PC now. Otherwise use a root checker off the play store however just get magisk anyway.
I then updated to A12 from the settings update and afterwards just for peace of mind, i redid a direct install via magisk incase the boot.img differed. I booted up perfectly fine after my update but for peace of mind i would recommend it.