Related
Hi All,
I have a non-DE XT1060 with an unlocked bootloader. I am attempting to flash a custom recovery, but I am running into issues. When I go into fastboot, it shows the device is indeed unlocked, but says Status Code: 3, where it would normally say Status Code: 1.
I am guessing this is part of my issue, since when I run the command ADB DEVICES, my device does not appear on the list. However, when I run the command ADB FASTBOOT DEVICES, it will list my device out. Because of this, I am having trouble flashing a custom recovery and obtaining root.
If anyone knows what Status Code: 3 actually means or has other ideas what might be going on, I would appreciate your help. I did a fair amount of searching online already, but nothing seemed quite the same as the issue I was having. Thanks in advance for any help.
I recently unlocked my device with the same status code 3 and had difficulties flashing the recovery also... In the android development section theres a post called recovery unlocked they mention that the correct command to flash would be mfastboot instead of fastboot (i guess its a motorola thing) also Adb commands don't run while in fastboot...
I think I had a misunderstanding of what fastboot was, but your reply prompted me to read more and I get it now. That being said, when I attempt to flash the recovery via fastboot, I receive the error: (bootloader) Variable not supported!
For the record, it does respond to commands such as fastboot devices and fastboot reboot-bootloader
Never had that outcome but having the latest adb/fastboot files would make things easier... If it still occurs
Is your command prompt path correct to the same folder as your recovery.img and your fastboot and mfastboot.exe files?
Yeah, you beat me to it... I had the directory wrong... needed C:\adb\
D'oh!! Thanks for your help though.
i have status 3 its normal or not ?
Apparently its normal as it all worked fine for me once I had the correct directory.
JustROLLIN said:
Apparently its normal as it all worked fine for me once I had the correct directory.
Click to expand...
Click to collapse
sure ? all have unlock bootloader have status 3 ?
maxou88 said:
sure ? all have unlock bootloader have status 3 ?
Click to expand...
Click to collapse
Status code 3 is perfectly normal and it indicates an unlocked bootloader in the case of the moto x. Nothing to worry about there. Every unlocked moto x displays status code 3. :good:
Oh ok thx my friend
my phone MOTO E stucks on warning bootloader unclocked.....plz help me...????
while doing fastboot its shows its not recognized by internal or external command...
samwathegreat said:
Status code 3 is perfectly normal and it indicates an unlocked bootloader in the case of the moto x. Nothing to worry about there. Every unlocked moto x displays status code 3. :good:
Click to expand...
Click to collapse
If you relock the bootloader will the status code change and will the software status change from modified to whatever it says before it was unlocked?
HELP please
mine is the moto g turbo edition XT1557 running marshmellow 6.0
and i unlocked the bootlocker status code 3
while trying to boot the phone it vibrates once and gets stuck on the "warning boot locker unlocked screen"
tried the logo thing, the wipe data thing. Noting is working can anyone help me ???
Hi friends,
I have just bought Moto G 2nd generation smart phone with 16 gb internal memory. To root device, I tried to unlock bootloader. But it didn't go smooth. When I hit command fastboot oem unlock <key>, I got success message with status Device unlocked. Status 3.
But what the heck this status 3?. I am not getting any info about this.
Google search is showing that, at time of unlocking bootloader, few messages are shown like 'unlocked' then 'restarted' and device restarts. But this didn't happen with me. So I manually restarted my device for custom recovery. And flashed rom using TWRP2.7.1.1-titan-motog-2014. This command also showed me success message. Before this I copied UPDATE-SuperSU-v2.02.zip in device.
But after restarting and hitting recovery, device is not showing any thing and just black screen and then turning off.
Apart from this device is working fine, with normal boot.
P.S. RootChecker is showing that Root access is not properly installed on this device.
So what is the way out to root the device again properly?
Thanks in advance.
zoozope said:
Hi friends,
I have just bought Moto G 2nd generation smart phone with 16 gb internal memory. To root device, I tried to unlock bootloader. But it didn't go smooth. When I hit command fastboot oem unlock <key>, I got success message with status Device unlocked. Status 3.
But what the heck this status 3?. I am not getting any info about this.
Google search is showing that, at time of unlocking bootloader, few messages are shown like 'unlocked' then 'restarted' and device restarts. But this didn't happen with me. So I manually restarted my device for custom recovery. And flashed rom using TWRP2.7.1.1-titan-motog-2014. This command also showed me success message. Before this I copied UPDATE-SuperSU-v2.02.zip in device.
But after restarting and hitting recovery, device is not showing any thing and just black screen and then turning off.
Apart from this device is working fine, with normal boot.
P.S. RootChecker is showing that Root access is not properly installed on this device.
So what is the way out to root the device again properly?
Thanks in advance.
Click to expand...
Click to collapse
Status=0 is Locked never been unlocked
Status=2 is relocked HAS been unlocked
status=3 is UNLOCKED
you will never get status 0 back its a once only condition (some says a poly fuse blows- i personally think it's more a case of write once memory has a marked added, and thus cant be reverted back)
but dont worry there is no need to relock boot loader to 2 (as 2 and 3 both void warranty)
Boot loader lock or unlock has NO relation to being able to receive OTA updates or installing them.
TWRP is now 2.8.40 for moto g 2014 use search
super su is now 2.45 again search
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail
GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!
GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete
For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
MotoJunkie01 said:
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
Click to expand...
Click to collapse
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
foxcell said:
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
Click to expand...
Click to collapse
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
MotoJunkie01 said:
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
Click to expand...
Click to collapse
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
foxcell said:
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
Click to expand...
Click to collapse
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Well I got some bad news... phone is stuck in a boot loop now, and no longer loads TWRP. I followed your directions and Oreo installed with no errors or warnings. Since going to Reboot -> System, it boots, says "N/A", then reboots.
I can get out of the boot loop by pressing volume down + power key, and from there I can access Android recovery (says 'bad key' when booting, instead of 'N/A') which gives me various options. It can still read SD cards and even says the proper OS.
I think it can still be saved since I can access Android recovery. I haven't tried the format system or cache options from Android recovery, because that might permanently screw it up.
Anyways... I'm here if you have any advice on what I can do. Maybe I should of bought an E4, lol.
Would you suggest I follow this?
https://forum.xda-developers.com/moto-e5/how-to/firmware-restoring-moto-e5-play-to-t3820053
I have no data on the phone so everything can be wiped no problem.
MotoJunkie01 said:
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Click to expand...
Click to collapse
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
foxcell said:
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
Click to expand...
Click to collapse
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
MotoJunkie01 said:
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
Click to expand...
Click to collapse
I did as followed, and phone is restored!!! Now when starting up it says "bad key" so I assume that means bootloader is still unlocked?
I still want to root and such, but I think I'll wait because rooting instructions I found were vague and trying to follow them got me into the situation I was in, lol.
Thanks for your help!!
foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77283595&postcount=196
Hi, i will not waste anyones time, i just want to share with you the steps that i took to convert my T-mobile Revvlry+ into a Moto G7 Plus, obviously, this is just a software conversion, also with this conversion, you will now have Android 10 on your device, and if you want to, Root, so, lets get started.
DISCLAIMER
Please read the guide completely before trying anything on your device, i will not be responsible for anything that happens to your phone, if you dont understand something or you dont feel comfortable doing one of the steps, please clear all of your doubts in the comment section, ill try my best to help you trough the steps.
Also, because the first steps involve unlocking your bootloader, your warranty will now be void.
Prerequisites:
Motorola device drivers: HERE
android sdk platform-tools: HERE
Moto g7 plus retail android 10 firmware: HERE for this i used the QPWS30.61-21-11 build
Flash conversion.bat: at the end of the post
logo.bin: HERE thanks to @luiz_neto for this mod, please thank him on his post
Instructions:
First download all the files, install the motorola device drivers if you dont have them already, extract the platform-tools to your desktop for easy access and inside of this folder extract the firmware, logo.bin and flash conversion.bat files, the platform-tools will now be a working ADB and Fastboot enviroment, if you are using windows 10 please follow THIS guide to enable this folder in powershell, just change the path of the guide for the path where you extracted the platform-tools folder.
Now you need to unlock your bootloader, you have to know that this will erase all your data, so please first backup all of your files, then go to settings and enable the developer settings by clicking 7 times on the "Build number" option in the "About phone" section, then go into system>developer settings and enable "oem unlock", now turn off your phone and pressing volume down, connect the usb cable, the phone will boot into bootloader, some drivers will automaticaly install, after this, go to the Motorola bootloader unlock website HERE and log in or create an account, after this just follow the steps on the website to unlock your bootloader, you will use platform-tools as your ADB and Fastboot enviroment for this, just download it and extract it to your desktop for easy access.
Basicaly what you have to do is send a fastboot command to get some info out of the phone
Code:
fastboot get oem_unlock_data
this is done on windows command prompt (CMD), after sending this command, the phone will return bunch of text, you select and copy this text and put it trough the data scrubbing tool present on the motorola website to get only the alfanumeric string of data, you put this data on the website and it will thell you wheter your bootloader can be unlocked or not, the Revvlry+ is an unlockable model, now at the bottom of the page a button will appear to ask for the unlock code, this code will get delivered to your email, now you just have to run a command twice and your bootloader will be unlocked
Code:
fastboot oem unlock UNIQUE KEY
The unique key is the one that motorola will send to your email.
At this point you can root your phone, install TWRP and a custom rom, but i will not go intos this, the guides made for the Moto G7 plus work for our phone, now we will proceed to make the conversion.
If you are using this guide with a newer build, please open the flash conversion.bat with notepad++ and check that the files mentioned on the .bat match the files on the newer firmware, if its missing a file, or it has more files listed, just add or erase the line that points to it, specialy the sparsechunk files wich can vary from firmware versions.
Now you just have to run the flash conversion.bat and wait, the script will automaticaly flash the moto g7 plus firmware including the modded logo.bin that will hide the unlocked bootloader warning screen, it takes a few minutes to do so, just be patient.
When the script finishes it will close and your phone will reboot, just give it a few minutes and you will be greeted with the android 10 setup wizard and thats it, your Revvlry+ is now a Moto G7 Plus softwarewise, at this point you can follow a guide to install TWRP and Root your phone, the guides for the Moto G7 Plus are aplicable for our device.
And thats it, thank you for your time and i hope this guide is helpful to you.
I actually tried it in another Revvlry+ 3 months ago but the boot warning is not removed and safetynet does not pass it, in bootloader state it says:flashing locked instead of being restored as oem_lock in bootloader
darkherman said:
I actually tried it in another Revvlry+ 3 months ago but the boot warning is not removed and safetynet does not pass it, in bootloader state it says:flashing locked instead of being restored as oem_lock in bootloader
Click to expand...
Click to collapse
None of the g7 plus varients can restore the oem lock....just the flashing lock.... I use a mod boot logo .for the bootloader Msg
If you are rooted
Flash magisk mods riru core and riru edxposed. install hidden core modules.apk......reboot and enabled the hidden core mod in edexposed mgr
Clear cache and data for playstore and Google play services...then reboot.....enable cts check in magisk...reboot....
Use this command to flash logo
fastboot flash logo Developer_Logo.bin
KtownJeff said:
None of the g7 plus varients can restore the oem lock....just the flashing lock.... I use a mod boot logo .for the bootloader Msg
If you are rooted
Flash magisk mods riru core and riru edxposed. install hidden core modules.apk......reboot and enabled the hidden core mod in edexposed mgr
Clear cache and data for playstore and Google play services...then reboot.....enable cts check in magisk...reboot....
Use this command to flash logo
fastboot flash logo Developer_Logo.bin
Click to expand...
Click to collapse
no thanks too many modifications for logo.bin and not pass safetynet
Is it like a full ROM flash?
Will VoLTE and Wi-Fi Calling stay intact after conversation to Android 10?
darkherman said:
no thanks too many modifications for logo.bin and pass safetynet
Click to expand...
Click to collapse
well this is the only solution for the safety net issue..... If you find or develop a new one please post
mingkee said:
Is it like a full ROM flash?
Will VoLTE and Wi-Fi Calling stay intact after conversation to Android 10?
Click to expand...
Click to collapse
Yes its a full flash but i believe that VoLTE will not work, im in mexico and VoLTE and Wifi Calling is not a thing so i cant test it