Question Cannot activate OEM unlock - Moto G30

Hello,
I cannot activate OEM unlock on my Moto G30.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Firmware: RRCS31.Q.Q1-3-34-1-4 (EU Retail), the device is not from the carrier, just from the shop (yesterday "out of the box").
I have "OEM unlock" code from Motorola, but that doesn't help (because "OEM unlock" is not active).
I tried to do hard reset, but under "Recovery Mode" I get "no command". After a few attempts, I was able to start "Recovery Mode" and do "wipe / factory reset", but that doesn't help as well.
Even "Rescue" with LMSA from Motorola could not solve the problem (I tried 3-4 times).
I can't do anything with fastboot either, because "OEM locked" = access denied.
Is there a solution here or do I have to wait until a new OTA update comes and repairs(?) the firmware?
TIA
t.

traber said:
Hello,
I cannot activate OEM unlock on my Moto G30.
View attachment 5333033
Firmware: RRCS31.Q.Q1-3-34-1-4 (EU Retail), the device is not from the carrier, just from the shop (yesterday "out of the box").
I have "OEM unlock" code from Motorola, but that doesn't help (because "OEM unlock" is not active).
View attachment 5333035
I tried to do hard reset, but under "Recovery Mode" I get "no command". After a few attempts, I was able to start "Recovery Mode" and do "wipe / factory reset", but that doesn't help as well.
Even "Rescue" with LMSA from Motorola could not solve the problem (I tried 3-4 times).
I can't do anything with fastboot either, because "OEM locked" = access denied.
Is there a solution here or do I have to wait until a new OTA update comes and repairs(?) the firmware?
TIA
t.
Click to expand...
Click to collapse
Try contacting motorola customer support or wait out for an OTA update which could fix it. But its best to contact motorola customer support first

traber said:
Hello,
I cannot activate OEM unlock on my Moto G30.
View attachment 5333033
Firmware: RRCS31.Q.Q1-3-34-1-4 (EU Retail), the device is not from the carrier, just from the shop (yesterday "out of the box").
I have "OEM unlock" code from Motorola, but that doesn't help (because "OEM unlock" is not active).
View attachment 5333035
I tried to do hard reset, but under "Recovery Mode" I get "no command". After a few attempts, I was able to start "Recovery Mode" and do "wipe / factory reset", but that doesn't help as well.
Even "Rescue" with LMSA from Motorola could not solve the problem (I tried 3-4 times).
I can't do anything with fastboot either, because "OEM locked" = access denied.
Is there a solution here or do I have to wait until a new OTA update comes and repairs(?) the firmware?
TIA
t.
Click to expand...
Click to collapse
It's not unusual for OEM unlocking on Moto devices, to be greyed out.
You need to connect to wifi/LTE and it should be available in 3 or so days after that.

sd_shadow said:
It's not unusual for OEM unlocking on Moto devices, to be greyed out.
You need to connect to wifi/LTE and it should be available in 3 or so days after that.
View attachment 5333139
Click to expand...
Click to collapse
Thank you, you give me hope (BTW I didn't have this problem with my G7 Plus two years ago...)
This screenshot was taken without wifi access, but I also saw this hint and activated wifi (and inserted a SIM card as well), but it didn't help.
If that's the case, then I'll wait a few more days (like with Samsung phones, where you also have to wait about 7 days for the developer menu to appear - at least that's how I read it).

traber said:
Thank you, you give me hope (BTW I didn't have this problem with my G7 Plus two years ago...)
This screenshot was taken without wifi access, but I also saw this hint and activated wifi (and inserted a SIM card as well), but it didn't help.
If that's the case, then I'll wait a few more days (like with Samsung phones, where you also have to wait about 7 days for the developer menu to appear - at least that's how I read it).
Click to expand...
Click to collapse
I use to see threads like this once and a while from people with devices on RetLA and a few others.
But now since 2020, I see this problem a lot.

sd_shadow said:
I use to see threads like this once and a while from people with devices on RetLA and a few others.
But now since 2020, I see this problem a lot.
Click to expand...
Click to collapse
For your statistics - my device has RETEU.
So... after about 24 hours nothing happened and I inserted a SIM card to be sure (but internet connection only via WLAN). Then after about 1 hour "OEM unlock" was active.
Maybe it's a topic for the FAQs "how to root": "you should not be afraid, in some cases this option can become active after 3(?) days / some time"?
What really worries me is the fact that a brand new device ("out of the box", not yet manipulated) has problems with "recovery mode" - an another reason to install TWRP to make backup properly.
And now I want to be sure: it is necessary to flash boot.img twice, so
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
?
"It works. I rooted mine, just keep in mind that since this is an A/B device, you have to flash the boot image to both boot_a and boot_b."
It's new for me, I have not done this (flash A&B, it was just "flash boot.img" once) on G7 Plus and it works very well (with EdXposed, XprivacyLua and so on). At that time I also read that with G7 I can't install TWRP permanently because it's such an "A&B device" (like G30 now...) and I have to choose, root or TWRP, or re-root the device after each use of TWRP, so "delete" TWRP again.
How does it look here?
t.

traber said:
For your statistics - my device has RETEU.
So... after about 24 hours nothing happened and I inserted a SIM card to be sure (but internet connection only via WLAN). Then after about 1 hour "OEM unlock" was active.
Maybe it's a topic for the FAQs "how to root": "you should not be afraid, in some cases this option can become active after 3(?) days / some time"?
What really worries me is the fact that a brand new device ("out of the box", not yet manipulated) has problems with "recovery mode" - an another reason to install TWRP to make backup properly.
And now I want to be sure: it is necessary to flash boot.img twice, so
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
?
"It works. I rooted mine, just keep in mind that since this is an A/B device, you have to flash the boot image to both boot_a and boot_b."
It's new for me, I have not done this (flash A&B, it was just "flash boot.img" once) on G7 Plus and it works very well (with EdXposed, XprivacyLua and so on). At that time I also read that with G7 I can't install TWRP permanently because it's such an "A&B device" (like G30 now...) and I have to choose, root or TWRP, or re-root the device after each use of TWRP, so "delete" TWRP again.
How does it look here?
t.
Click to expand...
Click to collapse
I have had 4 or so a/b devices and I just used
Code:
fastboot flash boot patched_boot.img
which will flash the active partition
but flashing to both is probably better.

traber said:
For your statistics - my device has RETEU.
So... after about 24 hours nothing happened and I inserted a SIM card to be sure (but internet connection only via WLAN). Then after about 1 hour "OEM unlock" was active.
Maybe it's a topic for the FAQs "how to root": "you should not be afraid, in some cases this option can become active after 3(?) days / some time"?
What really worries me is the fact that a brand new device ("out of the box", not yet manipulated) has problems with "recovery mode" - an another reason to install TWRP to make backup properly.
And now I want to be sure: it is necessary to flash boot.img twice, so
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
?
"It works. I rooted mine, just keep in mind that since this is an A/B device, you have to flash the boot image to both boot_a and boot_b."
It's new for me, I have not done this (flash A&B, it was just "flash boot.img" once) on G7 Plus and it works very well (with EdXposed, XprivacyLua and so on). At that time I also read that with G7 I can't install TWRP permanently because it's such an "A&B device" (like G30 now...) and I have to choose, root or TWRP, or re-root the device after each use of TWRP, so "delete" TWRP again.
How does it look here?
t.
Click to expand...
Click to collapse
Author of that thread here.
At first i only did:
fastboot flash boot patched_boot.img
and it only flashed to the active boot img, which was b. Then to make sure i just flashed to boot_a and it worked flawlessly.

As for a TWRP, we might never even get one. TWRP doesn't support devices that ship with Android 11 yet.
Just hoping the device trees get made soon so i can attempt to build a custom ROM.

Здравствуйте !!!
Помогите пожалуйста разобраться у меня moto g30 11(RRC31.Q1-3-34-1) в режиме разработчика включена отладка по usb и oem разблокировка тоже включена,что можно сделать?!?!
заранее спасибо!!!

Pasha1705 said:
Здравствуйте !!!
Помогите пожалуйста разобраться у меня moto g30 11(RRC31.Q1-3-34-1) в режиме разработчика включена отладка по usb и oem разблокировка тоже включена,что можно сделать?!?!
заранее спасибо!!!
Click to expand...
Click to collapse
English only on XDA Please.
Google translation.
Hello !!!
Please help me figure it out moto g30 11 (RRC31.Q1-3-34-1) in developer mode debugging by usb is enabled and oem unlocking is also enabled, what can I do?!?!
thanks in advance!!!
Click to expand...
Click to collapse
Edit; try using the latest SDK Platform-Tools from Google

Pasha1705 said:
Здравствуйте !!!
Помогите пожалуйста разобраться у меня moto g30 11(RRC31.Q1-3-34-1) в режиме разработчика включена отладка по usb и oem разблокировка тоже включена,что можно сделать?!?!
заранее спасибо!!!
Click to expand...
Click to collapse
Hello, maybe it's not the reason of your problem, but did you start cmd as administrator?
Sorry for my polish version of Windows

traber said:
Здравствуйте, может это не причина вашей проблемы, а вы запускали cmd от имени администратора?
[ПРИКЛЮЧИТЬ] 5371661 [/ ПРИКЛЮЧИТЬ]
[ПРИКЛЮЧИТЬ] 5371675 [/ ПРИКЛЮЧИТЬ]
[ПРИКЛЮЧИТЬ] 5371673 [/ ПРИКЛЮЧИТЬ]
Извините за мою доработанную версию Windows
Click to expand...
Click to collapse
нет только что спробывал всьо тоже !!!

this is solve?

Related

BlackView BV9600 Pro + LineageOS?

Hi! Could you please explain if this ROM will be compatible with my smartphone? I'm not sure, I don't found it on the list on LineageOS website.
Well, someone need to compile it for our bv9600 - i also would appreciate it, but i don't have thoose skills...
Also, lenovo vibe c2
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
giannhs_n said:
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
Click to expand...
Click to collapse
jup, runs root - magisk
AMDFenics said:
jup, runs root - magisk
Click to expand...
Click to collapse
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
giannhs_n said:
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
Click to expand...
Click to collapse
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
AMDFenics said:
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
Click to expand...
Click to collapse
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
giannhs_n said:
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
View attachment 4705498
Click to expand...
Click to collapse
exact same version.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
First u need to go to fastboot mode, to unlock "OEM UNLOCK"
This is easy via adb
-> reboot fastboot
Did u install the correct driver? (ADB driver) is ur device listed?
i tried repacking it myself but with no luck so far, also tried various treble GSI, all booting on my BV9600Pro and basically working but mobile data and phone are broken so that's not an option for now
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Root with sp Flash tool
Hi please Anyone could explain this procedure with Sp Flash Tool and post it?
serg2327 said:
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Click to expand...
Click to collapse
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
AMDFenics said:
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
Click to expand...
Click to collapse
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
serg2327 said:
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
Click to expand...
Click to collapse
I'm glad to hear that it works that way to you. But that doesn't worked for me. So i wrote the way i took, to root. Let the others choose, wich way works for them. :fingers-crossed::good:
I am using another MTK device and SP FlashTool is great it lets you recover from any software brick. So I will advice people to use this method.
I am planning on buying bv9600 pro and having twrp ported and root is a good start to custom roms.
The touch driver issue on twrp should be easily solved with the good kernel module for the twrp. And official twrp support would be nice.
Subscribed to the thread will see where it goes.
hi guys, can you share a clean system twrp backup of bv9600? because my USB is damaged and i can not use sp flash tool to clean restore. thanks!
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
dark-wulf said:
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
Click to expand...
Click to collapse
Maybe there is a way, but i don't know him. It is a common way for many manufacturer, to say, "here u did something you are not supposed too"
https://www.mediafire.com/file/0j0bx6cb0cb58f5/BV9600Pro_30042019_full.zip/file
Latest Firmware (04.2019) Clean SP Flash tool Backup

HOW TO PROPERLY INSTALL TWRP on [LG G7 ThinQ] "LM-G710AWM" (Judyln)?

Ok so after following a few guides to unlock bootloader on my LM-G710 (Judyln), now I want to PROPERLY install TWRP, with full access to all partitions so I can flash a custom ROM.
I can now root with Majisk.
It seems I can only install TWRP using Majisk Manager apk, if I use QFIL or fastboot (after deleting lafs) to flash TWRP I get bootloops.
I've followed this guide for TWRP and DM Verity/Disableforceencryption:
LG-V35-Tinkering-Instructions/README_EN.MD at master · kaneorotar/LG-V35-Tinkering-Instructions
Unleash your LG V35 ThinQ. Contribute to kaneorotar/LG-V35-Tinkering-Instructions development by creating an account on GitHub.
github.com
And this is the main guide I followed to unlock bootloader:
[GUIDE] Guide to unlock bootloader for every LG SDM845 except G710TM (With PHOTOS)
IMPORTANT: NEVER ERASE THE ENTIRE FLASH (IT WILL BRICK YOUR PHONE **STILL CAN BE RECOVERED**) IMPORTANT: FOLLOW ALL THE STEPS IN ORDER TO UNLOCK BOOTLOADER SUCCSSEFULLY; DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING...
forum.xda-developers.com
I'm having issues with TWRP not able to do anything in terms of mounting internal storage.
Also the 'system' partition is missing.
It can't mount anything, internal storage shows 0mb, and I can't wipe or flash anything!
I'm at the step in the first guide where I'm supposed to format data after flashing DM-VERITY where I get errors, it fails and I get a TON OF ERRORS
(The guide says its normal to get ONE error 'unable to unmount vendor' upon flashing DM-VERITY)
Also, a big red flag that I noticed is when loading TWRP for the first time, its supposed to ask me permission to swipe to 'allow system modifications', which didn't happen in my case.
So I think its something to do with LG and I've confirmed the bootloader is unlocked by going into fastboot.
Now when booting into fastboot (after deleting lafs) I got two different fastboot screens in different circumstances, one had red text which says 'unlocked', the other had green/blue text with instructions how to unlock bootloader.
(TWRP partition log below).
Please help! This is driving me crazy and I spent days on this phone!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Glad to see so many people willing to help...:/
Ok so I don't think TWRP has access to system modifications, because it doesn't ask me to allow system modifications when loading TWRP like it should. Can't proceed!
Okay you duplicated but if ya need help ill be here.
Kenora_I said:
Okay you duplicated but if ya need help ill be here.
Click to expand...
Click to collapse
Ok thanks, I'll make sure I don't duplicate in the future, I appreciate the heads up.
So my biggest issue here is I don't seem to be able to format any partitions within TWRP for some reason, I confirmed the bootloader is unlocked by [ a) device fastboot screen, b) developer options c) fastboot command]
However, in TWRP when I proceed switch slots (a or b) it says 'failed' but when I return to the TWRP reboot menu it lists the slot I tried to change to, so is it the version of TWRP I am using is just broken and I should try another one?
Problem is there's no official TWRP for my model.
I got the same model as you i just gave up installing twrp to this device bcs encrypted storage and no bootloader fastboot access with volume down button
kunarbale said:
I got the same model as you i just gave up installing twrp to this device bcs encrypted storage and no bootloader fastboot access with volume down button
Click to expand...
Click to collapse
Yeah I gave up too, I turned to somebody who might be able to do it.
LG locks their phones so people won't uninstall their apps, and this model is quite a doozy!
kunarbale said:
I got the same model as you i just gave up installing twrp to this device bcs encrypted storage and no bootloader fastboot access with volume down button
Click to expand...
Click to collapse
Just take off your password or pin.
Data is encrypted usually when you have a lock screen password.
LameMonster82 said:
TWRP 3.3.1-0+ for the LG G7 ThinQ​
Warning: This TWRP Recovery is only useful for installing custom ROMs.
Currently there's no way to use this recovery on stock in any meaningful way without future addons
(Data partition cannot be read because of LG default encryption)
You cannot install or backup anything while you have LG Encryption enabled. A future addon can disable it.
<-- Requirements​
An Bootloader unlocked LG G7 ThinQ by any means. (official or unofficial) (G710TM Models are impossible to be supported, sorry)
More information on officially unlocking the LG G7 here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Running minimum LG Stock Android 9 Pie (AOSP GSI does not count)
A PC and ADB + Fastboot
The temper to read twice
<-- Needed files​
You only need this boot image:
https://drive.google.com/open?id=1FcIBNfL3_72cQwuxd2TyZSjnC-ItnNTt
For developers who want to build their own TWRP Boot image here's the device-tree for it
https://github.com/LameMonster82/android_device_lge_judyln-twrp
<-- Installation
Note: This TWRP is only temporarily (it does not overwrite the bootimage). When you reboot it will dissapear and you will need to redo the fastboot command.
You're done. Now you can use TWRP to install custom ROMs
------------------------------------------------------------------------------------------------------------------------
Legacy tutorial. Do not use unless you use TWRP older than Feb 2020.
↓
Code:
[SIZE="5"][B][I][CENTER]<-- Needed files[/CENTER][/I][/B][/SIZE]
[LIST]
[*]You only need this boot image:
[url]https://drive.google.com/open?id=1n2wKdwARddx_KCIdLi10KawY_THlcRi4[/url]
[*]For developers who want to build their own TWRP Boot image here's the device-tree for it
[url]https://github.com/LameMonster82/android_device_lge_judyln-twrp[/url]
[/LIST]
[SIZE="5"][B][I][CENTER]<-- Installation[/CENTER][/I][/B][/SIZE]
[QUOTE][SIZE="3"][B]Step 1: Enter Fastboot mode[/B][/SIZE]
[LIST]
[*]Connect your phone to your PC with a USB Cable
[*]Restart the phone
[*]While the phone is restarting hold Volume down button.
[B]Note[/B]: Make sure you hold Volume down button before you see the [U][B]black and white[/B][/U] "LG G7 ThinQ" text
If you see the red LG Logo you either messed up or you don't have access to fastboot mode witch is another problem i can't solve easily.
[*]If done correctly you should be in Fastboot now :)
[/LIST]
[SIZE="3"][B]Step 2: Install the boot image[/B][/SIZE]
[LIST]
[*]Open the command prompt or your terminal (depending on what PC Platform you are)
[*]Type:
[/LIST]
[CODE]fastboot flash boot_a [B][TWRP Boot image location] --set-active=a[/B]
The best way you can set the TWRP Boot image location is to manually "drag and drop" the file itself in your command prompt
Also make sure you "drag and drop" the TWRP Boot image before you type --set=active=a
Don't forget --set-active=a has 2 little lines at the beginning. No space between them.
Step 3: Enter Recovery mode
Restart the phone (using power button if you're still in fastboot)
Before the phone turns off hold Volume down and power button
The moment you see the black and white "LG G7 ThinQ" Text start clicking the power button as much as you can without letting the Volume down button.
If done correctly you should see a white screen with "Factory reset" text on top.
If you done step 2 correctly clicking yes on both prompts on the phone will get you to TWRP
For people who still have trouble getting into recovery mode here's a visual example of how to enter recovery mode (youtube)
Note: You don't have to be in system. Rebooting from bootloader will still work
Click to expand...
Click to collapse
Congratulations you now have TWRP Recovery on your LG G7 ThinQ :highfive:[/CODE]
Join our Telegram Group here:
>> t.me/lgg7thinqmain <<​
I would like to thank:
@Sellerie_ and @J0SH1X for their help on the TWRP Project for LG G7 ThinQ
Here be dragons!
This the TWRP you used?
This is temporary but try to use this and check.
Kenora_I said:
Just take off your password or pin.
Data is encrypted usually when you have a lock screen password.
Click to expand...
Click to collapse
first off do you have the LG G7 AWM model ?
for newer android system vendor is encrypted by default with or without password/lockscreen, even when I can boot up to twrp and able to format system to install dm verity disabler you can't use stock firmware anymore and this AWM canadian model is pain in the arse because you cant just enter bootloader mode with button combination the culprit is because bootloader partition doesnt exist the only way is to trigger it using lg v35 boot.img
Kenora_I said:
Congratulations you now have TWRP Recovery on your LG G7 ThinQ :highfive:[/CODE]
Join our Telegram Group here:
>> t.me/lgg7thinqmain <<​
I would like to thank:
@Sellerie_ and @J0SH1X for their help on the TWRP Project for LG G7 ThinQ
Here be dragons!
This the TWRP you used?
This is temporary but try to use this and check.
Click to expand...
Click to collapse
I used the same version from the github link
https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
I don't have a screen lock password, and I unlocked bootloader with v35 from this post
[GUIDE] Guide to unlock bootloader for every LG SDM845 except G710TM (With PHOTOS)
IMPORTANT: NEVER ERASE THE ENTIRE FLASH (IT WILL BRICK YOUR PHONE **STILL CAN BE RECOVERED**) IMPORTANT: FOLLOW ALL THE STEPS IN ORDER TO UNLOCK BOOTLOADER SUCCSSEFULLY; DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING...
forum.xda-developers.com
kunarbale said:
first off do you have the LG G7 AWM model ?
for newer android system vendor is encrypted by default with or without password/lockscreen, even when I can boot up to twrp and able to format system to install dm verity disabler you can't use stock firmware anymore and this AWM canadian model is pain in the arse because you cant just enter bootloader mode with button combination the culprit is because bootloader partition doesnt exist the only way is to trigger it using lg v35 boot.img
Click to expand...
Click to collapse
Yeah its AWM Canadian model. I unlocked bootloader with the instructions here:
[GUIDE] Guide to unlock bootloader for every LG SDM845 except G710TM (With PHOTOS)
IMPORTANT: NEVER ERASE THE ENTIRE FLASH (IT WILL BRICK YOUR PHONE **STILL CAN BE RECOVERED**) IMPORTANT: FOLLOW ALL THE STEPS IN ORDER TO UNLOCK BOOTLOADER SUCCSSEFULLY; DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING...
forum.xda-developers.com
So there no hope for this model? What about this guide: https://androidbiits.com/root-lg-g7-thinq-lmg710awm-lm-g710awm-easily/. I guess that's just a quick guide for rooting not really addressing OP's desire to have TWRP installed.

[Simple method] Root N10 5G using Magisk for factory stock

First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Reserved !!
hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp
iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588
raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome
Why it wait forever for attached device, even removing and reconnecting phone?
Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.
I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue
PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.
(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)
Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first

Motorola G Power (2022) (TONGA)

Moto G Power 2022
Picked up this phone free.
Rootable with 90hz display
R/w with magisk root
Dolby viper all work
On MetrobyT-mobile but was able to flash
"Retus" firmware no issues..link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel 12 GSI 100% working on this phone.
ATTENTION please ATTENTION please!!!!
I new this GSI rom
[GSI][UNOFFICIAL][12] Pixel Experience
Pixel Experience for GSI What is this? Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation) Their mission is to offer the maximum possible stability and...
forum.xda-developers.com
was special. I decided to get a free Motorola G Power (2022) (Tonga) from MetroPCS and after root I said I remember reading LTE and mediatek phones were having less issues.
So I said I'll flash this on my new moto g Power 2022 and wow ... VOLTE works... Bluetooth... everything....yessssssss!!
Forget my stylus 5 G and 5G ace this is my new daily driver....
jhjhjhjhjhjh said:
Pixel 12 GSI 100% working on this phone.
ATTENTION please ATTENTION please!!!!
I new this GSI rom
[GSI][UNOFFICIAL][12] Pixel Experience
Pixel Experience for GSI What is this? Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation) Their mission is to offer the maximum possible stability and...
forum.xda-developers.com
was special. I decided to get a free Motorola G Power (2022) (Tonga) from MetroPCS and after root I said I remember reading LTE and mediatek phones were having less issues.
So I said I'll flash this on my new moto g Power 2022 and wow ... VOLTE works... Bluetooth... everything....yessssssss!!
Forget my stylus 5 G and 5G ace this is my new daily driver....View attachment 5525479
Click to expand...
Click to collapse
Send me your stylus 5g
Just joking, congratulations
On another note, this isnt the right place for your device. Looks like a forum hasnt been created yet for the 2022 g power.
Bonus !!!!!Android Auto works on this rom
First rom I ever had that supported AA
Geekbench on a11 single core "183" mulitcore "983. Now on A12 look at the boost jump Single ""814 Multi "3160..
Beetle84 said:
Send me your stylus 5g
Just joking, congratulations
On another note, this isnt the right place for your device. Looks like a forum hasnt been created yet for the 2022 g power.
Click to expand...
Click to collapse
jhjhjhjhjhjh said:
Pixel 12 GSI 100% working on this phone.
ATTENTION please ATTENTION please!!!!
I new this GSI rom
[GSI][UNOFFICIAL][12] Pixel Experience
Pixel Experience for GSI What is this? Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation) Their mission is to offer the maximum possible stability and...
forum.xda-developers.com
was special. I decided to get a free Motorola G Power (2022) (Tonga) from MetroPCS and after root I said I remember reading LTE and mediatek phones were having less issues.
So I said I'll flash this on my new moto g Power 2022 and wow ... VOLTE works... Bluetooth... everything....yessssssss!!
Forget my stylus 5 G and 5G ace this is my new daily driver....View attachment 5525479
Click to expand...
Click to collapse
Hey bro can you do me a favor have you tested it all completely out for bugs? Let me know which ones there are if any... Also what process did you use did you use fastboot flash system_a?
rogjr1986 said:
Hey bro can you do me a favor have you tested it all completely out for bugs? Let me know which ones there are if any... Also what process did you use did you use fastboot flash system_a?
Click to expand...
Click to collapse
Read this to the "T'.
Install Android 12 Pixel GSI instructions:
1 Unlocked bootloader
2 Windows laptop or CPU
3Your Region Stock "Tonga" firmware from lolinet.. and the PIXEL 12 GSI firmware from GitHub. Product.img file to resize the GSI (see attachment)
Open two folders on computer and put Tonga stock firmware in one and the GSI 12 ROM in the other folder along with the product.img file and the vbmeta.img from your stock firmware.
4.Turn off device and on the computer open a command prompt inside the Stock firmware folder.
5.While Holding "volume down" connect phone to computer you'll be in fastboot mode.
6 Flash stock firmware using these commands. Just copy and paste into the command prompt.
(After about 10 minutes phone will reboot to stock welcome screen)
This is Metro by T-Mobile so if using a different stock firmware only difference is the number of (super.img_sparsechunk) so check your stock firmware folder and add or delete any super.img_sparsechunks commands if necessary...you see Metro by TMobile has "24" of them..
fastboot set_active a
fastboot flash preloader preloader.img
fastboot flash lk lk.img
fastboot flash tee tee.img
fastboot flash scp scp.img
fastboot flash sspm sspm.img
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash spmfw spmfw.img
fastboot flash scp scp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash md1img md1img.img
fastboot flash gz gz.img
fastboot flash boot boot.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot flash super super.img_sparsechunk.16
fastboot flash super super.img_sparsechunk.17
fastboot flash super super.img_sparsechunk.18
fastboot flash super super.img_sparsechunk.19
fastboot flash super super.img_sparsechunk.20
fastboot flash super super.img_sparsechunk.21
fastboot flash super super.img_sparsechunk.22
fastboot flash super super.img_sparsechunk.23
fastboot flash super super.img_sparsechunk.24
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot -w
fastboot reboot
Ready to flash Android 12 let's go!!!!
After you see welcome screen turn off device.
1.Open Pixel GSI 12 folder and open a command prompt inside the folder
2Connect phone to PC and put back into fastboot mode.
3Copy and paste these commands to flash the ROM .(Note the GSI you download and unzip the name will be pixel..ab..slim....img..Rename it to "system.img")
fastboot set_active a
fastboot reboot fastboot
fastboot flash product product_gsi.img
fastboot flash system system.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
After about 10 minutes you will boot up to Android 12 Pixel ROM. Yay..
Now to get Bluetooth ,VOLTE,MMS and SMS working follow these instructions.
1.Go through the set up screen and set up everything "offline" uncheck all options .
2 Go into settings and look for "PHH Treble Settings" (Magic happens here) lol
Go to "MISC Features and check these three boxes for Bluetooth fix
"Use alternative way to detect headset.."
"Force -disable A2DP offlload"
Option called Bluetooth Workaround( check Mediatek)
LTE VOLTE FIX
PHH Treble settings
3 Go to "IMS Features" and check the last two boxes then hit "install ims for Mediatek.." then lastly hit "create ims apn"
4 once the ims apk downloads, manually install it from the notification drop down. (Don't reboot if it says to)
5. Open stock GSI ROM phone dialer and type
*#*#4636#*#* Three options will appear choose 'phone information"
6 Change data option using the little arrow drop down to (GSM WCDMA LTE (PRL) see full image.
7 Reboot phone,,,, Once rebooted go to mobile data settings and check the VOLTE options... ...Now test calls and text you should have VOLTE BLUETOOTH in call voice, MMS,SMS everything working like me...
8 Root if you want ,,same way just patch the boot image with magisk manager 23 or 24. And fastboot flash the magisk boot.img.
Profit... Now set up your phone to your liking.
Product.img to resize any GSI to fit any device.
Oh I have no bugs to report.
Zero!!!
jhjhjhjhjhjh said:
Android Auto, Viper, Dolby, Magisk, Magisk Modules all working...on GSI Pixel 12 release "h"
Click to expand...
Click to collapse
Kernel Update!!
TMO and Boost Mobile has an update for December 2021
I extracted the boot.img from the newest firmware and noticed a November security patch and performance boost.
Out of the box this phone was laggy and felt like a 100 dollar phone. Now with Android 12, an updated kernel and keeping refresh rate at 90mhz. This phone feels just as fast as the stylus 5G 480 soc. This mediatek Helio G37 is not that bad once it's overclocked ..
I set governor to "performance'
CPU min Big clusters 2.3ghz
Little clusters 1.8ghz
I can't find a way to overclock the GPU yet.
GPU high frequency is 650mhz. Similar to stylus 5 g..
Running smooth with Great battery life..
Well out the gate this phone was pretty decent but with the media check for some reason they have more bloatware than actual system apps.. it's ridiculous I went about half of my whole list of programs system and user included and disabled half of the system apps because they were all bloatware
Mediatek not media check
safety net passes also on this rom just fyi guys!!
Ram management has been excellent on this GSI 12 pixel. I added 2gb of swap for virtual ram and i can actually see its working..
4gb hardware ram +,2gb of virtual ram =6gb..sweet spot for a laggless experience...
If anyone is wondering why my device says pixel 6 pro..
i used magisk module "Pixelify-v1.81.zip"
and spoofed the pixel 6pro
I noticed more pixel options became available like "Device Controls"
in the drop down bar"
Phone/dialer live caption and more....
Hey I've got bootloader unlocked & the firmware flashed successfully. And I've tried 4 times to flash pixel12 & a different gsi and Everything works till it goes to flash part 4 of 12 and it fails. The 2nd gsi was in 11 chunks and it failed à the 4th chunk. Any help would be great ñ
So I got the tonga about a week ago, bootloader unlocked rooted with magisk and firmware flashed all successful without a hiccup.
But every time I go to flash the pixel 12 or an alternate GSI of the same criteria everything works up until when it's flashing the system it fails that trunk four of 12, and when I try and flash a different GSI it too freezes at chunk four of 11. This is my daily driver so after messing up I always got to reflash the new firmware and start from scratch. Does anybody have any clue what it might be? Could it possibly be the drivers on my windows 11 laptop? That's the only thing I can think of unless I'm missing something.
I installed the GSI according to the directions up top. And ain't no help will be greatly appreciated thank you.
I thought I posted about this earlier so if it's a double post if I notice it all fall back and delete it.
I got it flashed & working, with the fastboot codes provided, only thing is I had to flash vbmeta in regular fastboot not fastbootd. This phone seems to be vary gsi friendly. I'm running corvus v52.1 right now and it runs great, not much of a lag other then with the camera. I like a11 more. Biggest thing is LTE works with this rom I couldn't get it working consistently with other roms
is there any other way to flash a rom to this phone i tired doing it the way it is posted but i get errors when trying to flash it. bootloader is unlocked. when trying to flash boot.img it says partion not found so i looked it up and its a a/b partion so i had to flash the rooted boot.img to boot_a and boot_b for that to work. its rooted but i rater have it on a custom rom.
I just got a Moto Power G (2022) from Google Fi. I was able to unlock the bootloader and root the system with Magisk.

[GUIDE][MTK] How to bypass detection for UNLOCKED BOOTLOADER ?

WARNINGS:
First of all you should BACKUP IMEI.
Remember to NEVER touch the NVRAM.
People who does NOT backup imei or touches the NVRAM, are susceptible to the loss of IMEI.
If you try to share NVDATA between different devices, it may cause bootloop due verification of IMEI (slot1).
If you already lost IMEI, you probably may need to write IMEI again.
Works with:
Xiaomi Redmi Note 9 and ALL other MediaTek devices which uses SECCFG for unlocking/locking bootloader.
How does it work ?
After you turn on the device, the booting procedures checks if the device is unlocked and if there is any modified partition.
If your device is locked and any partition is modified, the device will not boot.
If your device is unlocked, the device will boot perfectly.
On booting, the device verifies if the device is unlocked or not, inside the partition: SECCFG.
After booting procedures, the partition SECCFG can NOT be read.
Due this, some variable settings are written to the partition NVDATA, because the system can read the partition NVDATA.
These variable settings contain details about locked/unlocked bootlader as many other details about the developer settings and some sensitive data like IMEI, Wifi MAC and Bluetooth MAC.
So, we just need to mix an unlocked SECCFG together a locked NVDATA.
How to do ? (Without formatting data)
1. Be sure to have UNLOCKED BOOTLOADER.
2. Backup the partition: SECCFG.
3. Format the partition: SECCFG. (Begin Address: 0x17800000 Format Length: 0x800000)
4. Format the partition NVDATA. (Begin Address: 0xc4a2000 Format Length: : 0x4000000)
5. Boot the device. It will write a new NVDATA.
6. Turn off the device.
7. Flash the partition SECCFG (with UNLOCKED BOOTLOADER).
Done !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to do ? (Formatting data)
1. Be sure to have UNLOCKED BOOTLOADER.
2. Backup the partition: SECCFG.
3. Backup your files and data, if you want.
4. Now, RE-LOCK BOOTLOADER. Or just erase the partition: SECCFG.
5. Format user data. It will erase NVDATA too.
6. Boot the device once, you don't need to accept terms or enter in system. It will write a new NVDATA.
7. Turn off the device.
8. Flash the partition SECCFG (with UNLOCKED BOOTLOADER).
Done !
Useful links:
VD Infos: Capture device infos and details with an ULTRA root/magisk/riru/xposed DETECTOR
https://forum.xda-developers.com/t/app-v1-10-vd-infos-package-com-vitaodoidao-vdinfos.4097379/
Scatter file for flashing using flash tool to MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
What should I backup before trying to customize my MERLIN device
https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
How to restore the state of UNLOCKED BOOTLOADER in MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
How to properly solve the errors of the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
Read Back file for backuping using flash tool from MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
DA files for flashing to MERLIN using FLASH TOOL
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
How to properly use the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/
Credits:​VD171​
Thank you for your contribution, I am a newbie in the subject of smartphones but I would like to know if with these modifications of your tutorial the momo application still detects the bootloader unlocked?
momo-v4.0.1.apk
drive.google.com
enzokart19 said:
Thank you for your contribution, I am a newbie in the subject of smartphones but I would like to know if with these modifications of your tutorial the momo application still detects the bootloader unlocked?
momo-v4.0.1.apk
drive.google.com
Click to expand...
Click to collapse
Since momo is closed source, you should not care for its results.
Momo uses many and many detections by native methods and they are hidden to anyone.
So, no one banking app can use momo detections.
But, the answer is: NO, momo can NOT detect unlocked bootloader using my method. And no other app or any other method can detect unlocked bootloader using my method.
Enjoy
Ps: Momo is already on version 4.3.1:
Magisk alpha
如果 「代码注入」 仍有假阳性情况,请入群反馈,感谢。
t.me
VD171 said:
Since momo is closed source, you should not care for its results.
Momo uses many and many detections by native methods and they are hidden to anyone.
So, no one banking app can use momo detections.
But, the answer is: NO, momo can NOT detect unlocked bootloader using my method. And no other app or any other method can detect unlocked bootloader using my method.
Enjoy
Ps: Momo is already on version 4.3.1:
Magisk alpha
如果 「代码注入」 仍有假阳性情况,请入群反馈,感谢。
t.me
Click to expand...
Click to collapse
Excellent thank you very much. Do you know if there is any way to do the same on snapdragon devices?
enzokart19 said:
Excellent thank you very much. Do you know if there is any way to do the same on snapdragon devices?
Click to expand...
Click to collapse
I have no ideia, I'm sorry.
All ok
Does safetynet hardware attestation work with this method??
0xf331dead said:
Does safetynet hardware attestation work with this method??
Click to expand...
Click to collapse
No
Flashing Magisk, enabling Zygisk and installing Universal SafetyNet Fix also hides unlocked bootloader.
hi i apolodize. is there a way to unlock the bootloader without using a mi account ?
because i use only my redmi with wifi and dont have a sim card to do it (and dont want to leave my infos on a chineese site)
ty
alcadon said:
hi i apolodize. is there a way to unlock the bootloader without using a mi account ?
because i use only my redmi with wifi and dont have a sim card to do it (and dont want to leave my infos on a chineese site)
ty
Click to expand...
Click to collapse
Try mtkclient:
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
ty btw i forget to precise im under w7 64...
Windows 7 does not support python 3.9, but I think that 3.8 will also work. If not, you can use ReLiveDVD v4.
Deleted
hi do u think mediatek bootloader unlock works with python 3.8 ?
i put the 2 dll it asked but got an 0xc000007b error....
will try re live dvd ty
btw do u know what is this menu in chineese access by usb and vol+ ?
alcadon said:
hi do u think mediatek bootloader unlock works with python 3.8 ?
i put the 2 dll it asked but got an 0xc000007b error....
Click to expand...
Click to collapse
I do not know what did you mean. I only think that it should work, but not tested. It may work or not.
alcadon said:
will try re live dvd ty
Click to expand...
Click to collapse
It's the best solution.
alcadon said:
btw do u know what is this menu in chineese access by usb and vol+ ?
Click to expand...
Click to collapse
I don't know which menu you are describing, but on some Xiaomi devices there is a menu that allows you to reboot to bootloader, recovery, fastbootd etc and do some tests. I think it is part of MIUI Recovery. On some phones it is in Chinese by default (mostly those bought in China, but also some bought outside China), but you can change the language to English by pressing the 中文 button.
well i get my wife sim card so i did the normal way... must wait 168 hours... willNEVER buy one of thopse ****S again

Categories

Resources