Related
Hello, I was looking to build a TWRP recovery for my phone (LG G7) but since the recovery is now part of the boot image I'm not sure if the old guides will work for my situation. I already have experience building ROMs (still a semi-beginner). Is it any different than before or it still the old guides would work?
LameMonster82 said:
Hello, I was looking to build a TWRP recovery for my phone (LG G7) but since the recovery is now part of the boot image I'm not sure if the old guides will work for my situation. I already have experience building ROMs (still a semi-beginner). Is it any different than before or it still the old guides would work?
Click to expand...
Click to collapse
I have the G5 and I will like to learn how to build pie for it too
Hi, I have MIUI 11/ Android 10 11.0.1 (Indonesia ROM) installed on my device and I have rooted it successfully with Magisk without TWRP.
Let me Tell you some Main Points about this device after my months of experience and Lot of Research about this device.
- Latest official TWRP version doesn't work on this device, and device goes into bootloop. Doesn't matter whatever you do, You have to flash ROM again to prevent bootloop.
- After Flashing ROM or Magisk, You must need to disable AVB, to prevent bootloop, you can find the command on TWRP web.
- MediaTek Processor on this device isn't a mess now, as Kernel source code has already released by Xiaomi.
And there are number of developments have been done already to prevent device from brick.
- Cameras on this Device are Great from Hardware side, but Unfortunately MIUI stock cam is garbage, and can't produce Nice quality Pictures.
- I have personally bricked this device many times, and fortunately always found a solution to get out of the mess.
Anybody reading this post, has any type of question, can ask And I will try my best to Help him/her
Overall, This Device is a great Powerhouse and
I request Developers to Kindly plz continue Development regarding Camera and I hope Xiaomi.eu will support this device for their ROM's in near future
Regards,
Moaz-Qudeer
I want to update to A10 but i am afraid i will lose factory preloader.... any ideas? i mean the anti brick preloader
Saadbinaamer said:
I want to update to A10 but i am afraid i will lose factory preloader.... any ideas? i mean the anti brick preloader
Click to expand...
Click to collapse
No, You can update software without worries it would b better if you're updating through OTA, otherwise .zip method is also safe, just make sure that you have removed root access from your device (if rooted) before updating.
Moazqudeer said:
No, You can update software without worries it would b better if you're updating through OTA, otherwise .zip method is also safe, just make sure that you have removed root access from your device (if rooted) before updating.
Click to expand...
Click to collapse
This contradicts some reports on the Megathread. I strongly recommend against OTA and zip sideloading/recovery install, unless you're ok with losing anti-brick preloader.
u8ububu said:
This contradicts some reports on the Megathread. I strongly recommend against OTA and zip sideloading/recovery install, unless you're ok with losing anti-brick preloader.
Click to expand...
Click to collapse
Read my 1st post again, I already said developments have been done in this regard already and there are much less brick risks now, I updated my device Android 9>>10 with recovery .zip method by placing .zip file into "downloaded_rom" folder. And Let me mention that my device had Bootloader unlocked before updating you can check attached screenshot.
Moazqudeer said:
Read my 1st post again, I already said developments have been done in this regard already and there are much less brick risks now, I updated my device Android 9>>10 with recovery .zip method by placing .zip file into "downloaded_rom" folder. And Let me mention that my device had Bootloader unlocked before updating you can check attached screenshot.
Click to expand...
Click to collapse
Yes, you can update Android 9 -> Android 10. The question is: Do you still have the factory preloader? Because that's what @Saadbinaamer was asking about. Otherwise, yeah, sure, you can update any way you want to Android 10.
u8ububu said:
Yes, you can update Android 9 -> Android 10. The question is: Do you still have the factory preloader? Because that's what @Saadbinaamer was asking about. Otherwise, yeah, sure, you can update any way you want to Android 10.
Click to expand...
Click to collapse
Yes, you should have Factory Preloader after Updating, Just make sure your device is not rooted before update.
Moazqudeer said:
Yes, you should have Factory Preloader after Updating, Just make sure your device is not rooted before update.
Click to expand...
Click to collapse
Kindly confirm at your end
Saadbinaamer said:
Kindly confirm at your end
Click to expand...
Click to collapse
Yes, confirmed from my side, I have factory preloader installed after update
Moazqudeer said:
Yes, confirmed from my side, I have factory preloader installed after update
Click to expand...
Click to collapse
Okay so I updated to MIUI 12; Android 10 (China Beta Rom). Though I have TWRP and Magisk installed but I don't have factory pre-loader anymore. I watched a YouTube video in which the uploader said that the new factory pre-loader will be available soon for the said Android version and the former one can't be used.
soleali said:
Okay so I updated to MIUI 12; Android 10 (China Beta Rom). Though I have TWRP and Magisk installed but I don't have factory pre-loader anymore. I watched a YouTube video in which the uploader said that the new factory pre-loader will be available soon for the said Android version and the former one can't be used.
Click to expand...
Click to collapse
I don't know about MIUI 12, as I said already, I have MIUI 11, Android 10 Installed.
My Phone is HARDBRICK and haven't installed preloader lk
How you Unbrick your device without preloader instal before..? In Android 9...
there should be clear tutorials and in execution order because often not very clear and people will not understand everything
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.
vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.
I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.
On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.
I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?
I really want that update as I'm reading it made the battery much better. What to do!
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.
Hello folks,
I need your help, I bought myself a OnePlus 9 Pro a few months ago and still use my OnePlus 6 because it still isn't configured finally. There are unfortunately too many open questions.
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
I nearly sure it's theoretical possible to find the solutions myself, so sorry for my maybe stupid questions.
Edit: after sending I see this guide.
What does AA, BA and DA mean?
Hope someone could help!
THX mcdoubleyou
mcdoubleyou said:
Hello folks,
I need you help, I bought myself a OnePlus 9 Pro a few months ago and still use my OnePlus 6 because it still isn't configured finally. There are unfortunately too many open questions.
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
I nearly sure it's theoretical possible to find the solutions myself, so sorry for my maybe stupid questions.
Edit: after sending I see this guide.
What does AA, BA and DA mean?
Hope someone could help!
THX mcdoubleyou
Click to expand...
Click to collapse
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
No. TWRP is ready for A12 ROMs as of now.
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
Yes, Magisk is the best solution...
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
Did not understand what you mean by 'stuck' If it is a brick, use MSM tool to flash back to stock.
What does AA, BA and DA mean?
These are just builds for specific regions.
AA - Global
BA - EU
DA - India
Sorry for my late reply vipinpvarghese and thank you very much.
As far as I know Magisk Hide isn't exist anymore so I have to use Zygisk - right?
Cheers mcdy
Is there a Custom Recovery (like TWRP) for Android 12 or should I better stay at OOS 11?
No, OnePlus has not released A12 source code so this (as well as true A12 roms) cannot be built.
My OnePlus 6 isn't rooted at the moment but previously I used Magisk. Is this still state of the art?
Magisk is still the preferred root method.
The OnePlus 9 Pro is OEM unlocked already, but now I'm stuck!
Make sure you've set the option in developer options but also run "fastboot oem unlock" in your fastboot, which WILL wipe your device.
What does AA, BA and DA mean?
AA = Global
BA = Europe
DA = India
Hey folks,
Don't know what I did wrong, but now I really stuck.
I downloaded Boot 12.C44_BA.zip linked in the other thread and installed it.
After that my phone reboots and I installed Magisk in Magisk and make a reboot.
Now I'm only able to boot into fastboot.
In a Thread I read that I could try to change my slot back, after that it start's normal.
So I decided to update Magisk in Magisk and then install Magisk again from inside Magisk, but it happens again.
What should I do to root my device not only temporary?
THX mcdy
mcdoubleyou said:
Hey folks,
Don't know what I did wrong, but now I really stuck.
I downloaded Boot 12.C44_BA.zip linked in the other thread and installed it.
After that my phone reboots and I installed Magisk in Magisk and make a reboot.
Now I'm only able to boot into fastboot.
In a Thread I read that I could try to change my slot back, after that it start's normal.
So I decided to update Magisk in Magisk and then install Magisk again from inside Magisk, but it happens again.
What should I do to root my device not only temporary?
THX mcdy
Click to expand...
Click to collapse
Which magisk build are you using? Afaik stable magisk still only supports OOS11. You need canary for OOS12.
terlynn4 said:
Which magisk build are you using? Afaik stable magisk still only supports OOS11. You need canary for OOS12.
Click to expand...
Click to collapse
Thanks, I tried it this way but with the same effect.
First I change the slot, then opened Magisk and change to Canary.
After that I do an update and installed to the inactive slot.
Any ideas?
THX mcdy
mcdoubleyou said:
Thanks, I tried it this way but with the same effect.
First I change the slot, then opened Magisk and change to Canary.
After that I do an update and installed to the inactive slot.
Any ideas?
THX mcdy
Click to expand...
Click to collapse
When you say you "change to Canary" did you actually install the latest Canary to your current slot and reboot, then make sure magisk is completely up to date? You need to actually be running the latest Canary prior to performing the update, as far as I know. At least that's how it worked a couple of versions ago with Alpha.
terlynn4 said:
When you say you "change to Canary" did you actually install the latest Canary to your current slot and reboot, then make sure magisk is completely up to date? You need to actually be running the latest Canary prior to performing the update, as far as I know. At least that's how it worked a couple of versions ago with Alpha.
Click to expand...
Click to collapse
Hey terlynn4,
it looks like it's jinxed.
After your info, I moved the phone back to the other slot, then let it boot.
Logged in and opened Magisk, checked that Canary is still there. Updated the app - seems there was one by now - and reinstalled Magisk to the current slot. Then installed Magisk on the other and rebooted.
But unfortunately it was then in fastboot again.
So I changed the slot again and was afraid that it would be useless because of the update, but fortunately it booted normally.
In short, on one slot the Magisk version seems to work, on the other not. Oo
Any ideas?
Thanks! mcdy
As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks
Goooober said:
As title really, never flashed a custom ROM (at least not since my Galaxy S2) and while wait the 7 days to unlock the bootloader i'm trying to gather as much info as possible. So here goes;
1) Whilst I wait for the bootloader to unlock can I still turn off my phone and swap sim cards or will it reset the timer?
2) My Poco F3 is on MIUI Global 13.0.7.0 (SKHEUXM) - do I need to downgrade to 13.0.3.0 as per the instructions here?
3) The instructions for installing Crdroid lists an optional step for installing "DFE" but I cant seem to find out what DFE actually is.
4) Is it important to know if my phone has an A/B partition system and if it is how do I check for it?
5) After installing Magisk what other modules/tools/apps do I need to ensure Google Pay/Wallet will work as it seems a recent update has made it harder to fix.
6) Are there any bits of advice you can give for a avoiding a bootloop and/or bricked phone situation? Are there any common mistakes people make leading to a bootloop or bricked phone?
I think that's everything for now
Thanks
Click to expand...
Click to collapse
1) Yes.
2) No, 13.0.3.0 is the required minimum, you can always use higher.
3) It disables forced encryption.
4) Poco F3 is A/B.
5) If any issues arise, you can always hide magisk and use safetynet fix.
6) When people don't follow installation instructions properly.
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works, with DFE you can flash files from internal storage in twrp. But it also compromises phone security, so it's recommended not to use it.
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
Almost all modern phones now ship with A/B partitions. So no, just follow the instructions given by the rom developer.
1. I unfortunately can't answer.
2. I wouldn't, 13.0.3 to 13.0.7 is very minor
3. DFE = Disable-Force-Encrypt = Android by default is encrypted.
DFE.zip removes the Boot-argument responsible for encrypting the Userdata-partition on the first boot, located in /vendor/etc/fstab
4. Poco F3 has an A/B-Partitionlayout. Most phones released with ~Android 10+ have A/B.
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
6. If you flash using Fastboot Mode and the Flash aborts during a Partition-flash, don't reboot your phone, because otherwise your phone may never reboot back into Fastboot etc, and only show a Black screen.
ApexPrime said:
Dfe is disable force encryption but i dont think it works for android 12 so no need to flash it
Click to expand...
Click to collapse
It works on Android 12.
Goooober said:
If my phone is A/B do i have to do anything different when i flash Crdroid in TWRP?
Click to expand...
Click to collapse
No difference.
Further Notes about DFE:
If you don't use DFE before First Boot, userdata-partition gets encrypted, which means, beyond that, only TWRP SKKK will be able to access the userdata-partition.
If you decide to flash DFE once, you must flash it directly after every Update in TWRP, otherwise your phone may bootloop. At least that was the case for me! Before an update I decided I want my storage encrypted, but I got a bootloop. ^^
I wouldn't use DFE. Just leave it encrypted.
cyanGalaxy said:
5. Personally, with the recent change, I tried many things to get GPay to work, got fed up with the Cat & Mouse Game with Google, and locked my BL.
Click to expand...
Click to collapse
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
Your phone will bootloop if you do that, because locked bootloader prevents custom roms from starting, thus it can only be used on stock roms.
Goooober said:
If you lock your bootloader after flashing a custom ROM does the custom ROM still work as intended or do you have to go back to stock?
Click to expand...
Click to collapse
No, I don't use a Custom ROM anymore. I'm back to Stock ROM, MIUI 13.0.7 for Europe.
Don't lock the BL with a Custom ROM. Only the Official ROM. Otherwise you risk hardbricking your phone.