Making a Custom Boot image - OnePlus 2 Q&A, Help & Troubleshooting

is there any up to date tutorials for making a boot image for my OP2? all tutorials seem old and i don't want to follow incase the fact theyre outdated screws me over somewhere down the line. Im on rooted OxygenOS 3.1.0
thanks

Related

Upgrade to newer build after rooting with locked BL?

Some background on what I've done with the phone:
It came with B29 on it.
I used DrakenFX's BootStack and System files to downgrade it to B27
From there, I tried the steps in Tenfar's thread to root the phone without unlocking the boot loader.
I screwed something up along the way and after many hours, got my phone booting properly again and downgraded to B20.
From there, I followed the steps posted by mmamedov in tenfar's thread to actually get my phone rooted properly.
I'm pretty new to rooting and all this stuff since I'm jumping ship from iPhone, but I've done a bit of tinkering.
I don't quite understand where the "root" part resides and what updates would affect it.
Now, I'm on B20 but would like to upgrade to some of the newer versions. What are my options for doing that and would I have to wipe the phone to update?
Could I use the backup tool to flash the stock recovery instead of TWRP, and use the built in update through settings?
Or should I use TWRP and DrakenFX's newer BootStack/System files to update?
or something else?
Thanks
- Android Newbie
mozerxdaven said:
Some background on what I've done with the phone:
It came with B29 on it.
I used DrakenFX's BootStack and System files to downgrade it to B27
From there, I tried the steps in Tenfar's thread to root the phone without unlocking the boot loader.
I screwed something up along the way and after many hours, got my phone booting properly again and downgraded to B20.
From there, I followed the steps posted by mmamedov in tenfar's thread to actually get my phone rooted properly.
I'm pretty new to rooting and all this stuff since I'm jumping ship from iPhone, but I've done a bit of tinkering.
I don't quite understand where the "root" part resides and what updates would affect it.
Now, I'm on B20 but would like to upgrade to some of the newer versions. What are my options for doing that and would I have to wipe the phone to update?
Could I use the backup tool to flash the stock recovery instead of TWRP, and use the built in update through settings?
Or should I use TWRP and DrakenFX's newer BootStack/System files to update?
or something else?
Thanks
- Android Newbie
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 rooting makes the OTA from ZTE not work
I've been going through a similar learning curve as you I think.
I recommend @DrakenFX's nearly stock rom.
You will need to unlock the bootloader (I'm pretty certain) I believe that is covered and/or linked in the rom's page.
If it doesn't make sense keep reading until it does, is the advice I gave to myself.
I'm pretty new to certain parts of all the options involved in rooting and bootloaders etc. but I believe that the bootloader can be relocked if you don't get it officially unlocked and you do it yourself, I haven't confirmed that yet so don't take my word for it.
I ran into confusion when I unlocked and had driver issues with fastboot but I got there.
DrakenFX had a few posts that are really helpful. I used his B29 image and bootstack after I had TWRP installed.
He has another TWRP unlock zip that allows unlocking with ADB and then fastboot.
I ran into issues like I said and posted in his bootstack thread if you'd like to see if my problems might shed some light. My post didn't prompt any meaningful conversation but my driver issues sorted themselves out so I didn't have to pursue it much further.
Sorry for the lack of links but I hope this helps in some way.
Here's the ROM from DrakenFX that is close to stock B29, it looks like it will evolve into Nougat, can't wait for that.
http://forum.xda-developers.com/axon-7/development/rom-zaxon-dmix7-stock-base-rom-t3495970

Android noob coming from iOS, really need some guidance

Hey, sorry if this thread is a little dumb.
I havent had an Android since Froyo, and I've been a jailbroken iOS user since until now. And I am LOST.
I'm not a noob when it comes to tech so I normally catch on quickly but I'm just overwhelmed with the amount of new information and how instructions for installing stuff are usually a little vague
Basically, I wanna root. I dont care about updates and I dont care about roms. I just want root to get GCam, Substratum, Greenifiy, Tasker, AdAway, liveboot (and boot animations) AND get Franco Kernel. The usual stuff.
But the more I try to understand what I have to do the more confused I get. I know that I have to do the whole fastboot bootloader unlock, that seems to be universal, but then if I'm not on 8.0 or 7.1, I cant install TWRP permanently because there isnt an installer.zip for it? So then I just have to downgrade with Mi Flash tools, and then its just a sea of image files and I dont know which one I have to pick.
I would really appreciate it if someone could tell me what exactly do I have to do to root on 8.1 while also getting permanent TWRP so I can use Franco Kernel
Thanks
Ugh, yeah, you're a bit lost. Just follow this video
. Then just flash magisk zip and reboot. After that, follow this video
start from 4:01 onwards. Then youre good to go
Since you already have unlocked bootloader you now just have to install twrp recovery and flash magisk file in twrp to get root access. Just follow this guide its very easy to install recovery and flash magisk
https://www.google.com.pk/amp/s/for...ery-twrp-3-1-1-0-touch-recovery-t3688472/amp/

[Stock Pie] Humble Request: Tutorial to switch from stock to custom ROM

Hello dear users and highly appreciated developers!
I reckon I am not the only one who is stuck on stock Pie and would really like to switch to a custom ROM but either don't know how, or aren't sure about it because of all the threads with bricked phones and all that stuff.
If there is anybody who has a complete tutorial/way of doing it - switching from stock Android Pie - January Security Update to any custom ROM, without bricking the phone, losing IMEI, signal etc. would be so kind to share it with us? Step by step would be convenient because there are people who aren't experienced at all with flashing and stuff like that. Especially in these "circumstances".
Very much thanks in advance, any help is much appreciated!
sainth4tred said:
Hello dear users and highly appreciated developers!
I reckon I am not the only one who is stuck on stock Pie and would really like to switch to a custom ROM but either don't know how, or aren't sure about it because of all the threads with bricked phones and all that stuff.
If there is anybody who has a complete tutorial/way of doing it - switching from stock Android Pie - January Security Update to any custom ROM, without bricking the phone, losing IMEI, signal etc. would be so kind to share it with us? Step by step would be convenient because there are people who aren't experienced at all with flashing and stuff like that. Especially in these "circumstances".
Very much thanks in advance, any help is much appreciated!
Click to expand...
Click to collapse
Hotboot latest official twrp using fastboot command "fastboot boot name of twrp.img
Take a backup of efs partition
Wipe system,data and factory reset
Flash the rom of ur Choice
Flash twrp installer by cosmicdan
Reboot>recovery
Flash gapps+magisk
Reboot to system
Thats what i did
And you didn't get any "Your system has been destroyed" messages after hotbooting TWRP or stuff like that?
hot booting twrp is fine, just dont flash it. it mess up everything on pie.
make a efs backup on twrp fist then make a copy of it on your computer.
hot booting to twrp may take up to 30 seconds, dont panic.
@apexashwin
Hey, can you please link me that "twrp installer by cosmicdan"?
Also, if I flash Pixel Experience do I have to still do the steps which'd come after flashing the ROM? (installing cosmicdan's stuff, gapps, etc.)
sainth4tred said:
@apexashwin
Hey, can you please link me that "twrp installer by cosmicdan"?
Also, if I flash Pixel Experience do I have to still do the steps which'd come after flashing the ROM? (installing cosmicdan's stuff, gapps, etc.)
Click to expand...
Click to collapse
It's easy to find. Just find it in the rom/kernel/recovery section.
And as they stated in PE OP, it included gapps so you don't have to flash gapps.
I did in fact do what you said and I managed to flash Pixel Experience without any trouble! Thank you very much

[HELP] How to go back to stock —using PE and Magisk

Let me start by saying that I know there are multiple posts and comments around surrounding this topic, but I almost damaged my phone once since not all the instructions apply to everyone's situation. So I am hoping someone can help me with the details I am giving of my phone, which I want to give to my mom now and she doesn't need any fancy customizations.
I am using the Pie Pixel Experience ROM with the December security patch and also rooted with Magisk. What I need to do is be able to unroot the phone and install to it the latest available official build for the device and lock the bootloader. Also I remember when I did all the process of installing this ROM that it has two partitions (in case this affects in anything the process of going back to stock).
So if anyone could help me out with a step by step explanation (and resources) I would be truly thankful.
Flash stock pie by miflash, you find it on xda, be careful to take fastboot image pie!
Just get twrp flashable stock rom and flash it..... This will flash stock rom and as well as stock recovery on your phone... Plus you will aslo recive stock ota updates

Stuck in fastboot after flashing TWRP (Mi 9T)

First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up
cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Your mistake is to not use Official TWRP instead of an old TWRP version...
Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.
blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days

Categories

Resources