The last phone I came from that I flashed custom roms etc is the nexus 6. Just got a one plus 7 pro and things seem to be more complicated then just booting into twrp and flashing a custom rom and gapps. I used the all in 1 tool to unlock bootloader, flash twrp, and magisk. I've been doing a lot of reading in guides and q and a and just seem to get more confused. Am I over thinking and can just flash a custom rom zip with reflashing twrp and magisk or am I in over my head from the old nexus 6 days? Any advice or if anyone could point me in the right direction would be much appreciated. Thanks in advance
steveo24 said:
The last phone I came from that I flashed custom roms etc is the nexus 6. Just got a one plus 7 pro and things seem to be more complicated then just booting into twrp and flashing a custom rom and gapps. I used the all in 1 tool to unlock bootloader, flash twrp, and magisk. I've been doing a lot of reading in guides and q and a and just seem to get more confused. Am I over thinking and can just flash a custom rom zip with reflashing twrp and magisk or am I in over my head from the old nexus 6 days? Any advice or if anyone could point me in the right direction would be much appreciated. Thanks in advance
Click to expand...
Click to collapse
Slightly different but overall same concept. You did it then you can do it now. Just look up a guide and follow step by step. Its pretty simple after couple trail and errors. Good luck and enjoy.
Related
I see threads on how to downgrade but none explaining how to upgrade to latest build. Most threads are years old 13.1.2-ZNH2KAS3P0 being the latest i could find
My phone came with V.6.0.1. Cyanogen OS v. 13.1-ZNH2KAS1KN.
why not custom roms ? like lineage os , resurreciton remix etc.
The best way to upgrade is via a custom rom.
Follow this: https://forum.xda-developers.com/showthread.php?t=2788632
13.1.2-ZNH2KAS3P0 indeed the latest official version. If you want to get further updates, only customized ROMs can help you with that.
That was what I was trying to do was install custom ROMs, both new and old failed with TWRP error 7...so i figured there was an update i needed before i could install them. I installed 13.1.2-ZNH2KAS3P0. Still no go...
I already had followed that threads instructions but all ROMs failed. TWRP error 7.
I was finally able to install a ROM. Lineage-14.1-20170814-nightly-bacon-signed https://download.lineageos.org/bacon I am still confused as to why this one worked and the others didn't though... now I am too paranoid to flash any other ROMs until I figure this out .
Any explanation or advice would be greatly appreciated I Hate not understanding how I did something lol. Thanks for all your help!
once you follow the Lineage Os guide your unlocked and good to go. I usually sideload the install using TWRp..
Hello guys im looking for a rooted rom my build is MHA-L29C567B190 my bootloader already unlocked and also flashed twrp or can you please help me root my stock rom thanks for your help
grodri19721 said:
Hello guys im looking for a rooted rom my build is MHA-L29C567B190 my bootloader already unlocked and also flashed twrp or can you please help me root my stock rom thanks for your help
Click to expand...
Click to collapse
Download and flash: https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
You should now be rooted with Magisk.
Make sure you have TWRP 3.1.x from the twrp thread
ante0 said:
Download and flash: https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
You should now be rooted with Magisk.
Make sure you have TWRP 3.1.x from the twrp thread
Click to expand...
Click to collapse
Is it really that easy? i have mine rooted with TWRP 3.1, i can flash that file and I'll have magisk? I'm on the same HW/SW version as the OP.
since the Oreo is coming out, will I need to flash stock to get the Stock Oreo update when its released? I assume so. I am new to the Mates and they seem to have a much different flash method/path than the Nexus 6p and HTC devices i have done in the past. I'm kind of leery to pursue Installing ROM's and Magisk (never used it yet) but would like to. Any tips or links to detailed instructions for the Mate flashing? I cant find, what I feel, to be detailed instructions on XDA.
thanks
sgtduckyboy said:
Is it really that easy? i have mine rooted with TWRP 3.1, i can flash that file and I'll have magisk? I'm on the same HW/SW version as the OP.
since the Oreo is coming out, will I need to flash stock to get the Stock Oreo update when its released? I assume so. I am new to the Mates and they seem to have a much different flash method/path than the Nexus 6p and HTC devices i have done in the past. I'm kind of leery to pursue Installing ROM's and Magisk (never used it yet) but would like to. Any tips or links to detailed instructions for the Mate flashing? I cant find, what I feel, to be detailed instructions on XDA.
thanks
Click to expand...
Click to collapse
If you're rooted with SuperSU or Phh you will need to restore your stock boot image before flashing Magisk,
this can be done by downloading your firmware from http://pro-teammt.ru/firmware-database/ then extacting update.app and opening it in Huawei Update Extractor where you extract BOOT.IMG.
Flash it using fastboot flash boot boot.img.
As long as you're using firmware B182+ (Loop device support) and TWRP 3.1.x you can install official Magisk/SuperSU.
Oreo will be a full firmware so it shouldn't need to verify any partition, meaning you will only need to restore stock recovery.
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol
Hey everyone,
I have an unlocked OP 7 pro.
Lately, I decided to go back to custom roms after a year or so of sticking with rooted stock.
I've tried to flash Pixel Experience & Flamingo OS and while both completed successfully, they won't pass the bootloader.
Then I tried to install crDroid using the script the author has provided and suddenly it does boot to recovery and I was able to flash the rom completely and boot to it.
Has anyone encountered such a case and has a workaround for it?
Thanks
E1adi said:
Hey everyone,
I have an unlocked OP 7 pro.
Lately, I decided to go back to custom roms after a year or so of sticking with rooted stock.
I've tried to flash Pixel Experience & Flamingo OS and while both completed successfully, they won't pass the bootloader.
Then I tried to install crDroid using the script the author has provided and suddenly it does boot to recovery and I was able to flash the rom completely and boot to it.
Has anyone encountered such a case and has a workaround for it?
Thanks
Click to expand...
Click to collapse
Just wanna to let any future visitors of this thread how I've solved it.
1. I use the msmtool to reflash stock and lock the bootloader on the way. (Here)
2. I installed OTA stock updates.
3. I unlocked the bootloader again
4. Voila, now I was able to flash stuff.
Good luck everyone
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Maybe ask in an appropriate thread, but you could try dirty flash, stock is flashed the same way.
Odeya said:
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Click to expand...
Click to collapse
Backup all data and dirty flash. If you get errors, clean flash is helpful
Since it's a jump from one Android version to another, it's better to clean flash. Although, a dirty flash should still be possible once you wipe OS.
There should be a new, updated recovery file to flash as well. Tbh, the jump from A12 to 13 is not as big as the previous upgrades, with not much gains.