Related
I have moto x play xt1562.and its got patten I try to unlock patten from recovery mode wipe data factory reset.now without veryfy google I can't use the mobile. Also flash with stock img android 6.0.1.still facing this problem.and devloper mode can't enable.by clicking build number. Plese help.
chotu2010 said:
I have moto x play xt1562.and its got patten I try to unlock patten from recovery mode wipe data factory reset.now without veryfy google I can't use the mobile. Also flash with stock img android 6.0.1.still facing this problem.and devloper mode can't enable.by clicking build number. Plese help.
Click to expand...
Click to collapse
Try getting TWRP flashable rom, extract it on your PC, go to /system, edit build.prop with some good editor, line Notepad++ for Windows, find the following entry:
Code:
ro.setupwizard.mode=OPTIONAL
and change it value to DISABLED. Zip everything back, go to TWRP, wipe data, factory reset and flash. It will hopefully work
But I am not able to flashing twrp recovery. When I try to unlock bootloader its say first allow the bootloader to be unlock. From devloper option.
chotu2010 said:
But I am not able to flashing twrp recovery. When I try to unlock bootloader its say first allow the bootloader to be unlock. From devloper option.
Click to expand...
Click to collapse
Dev settings must be present when clicking in the build version 7 times. Never didnt work for me
chotu2010 said:
I have moto x play xt1562.and its got patten I try to unlock patten from recovery mode wipe data factory reset.now without veryfy google I can't use the mobile. Also flash with stock img android 6.0.1.still facing this problem.and devloper mode can't enable.by clicking build number. Plese help.
Click to expand...
Click to collapse
This guy has a solution for MM stock with january security update, if you can flash rom with jan update (maybe older would work as well) through fastboot, try his way:
https://www.youtube.com/watch?v=HuPIhiFZoaI
Patch security 1 march 2016, impossibile unblock
Sorry my bad inglish
If i flash with lollipop frimware. There is any chance to break google account.
Benjamin_L said:
Dev settings must be present when clicking in the build version 7 times. Never didnt work for me
Click to expand...
Click to collapse
I already know about your concept but after factory reset from recovery you can't enable devloper mode.by clicking bild number.running on android 6.0.1.because if you want to use your device you must put Gmail previous owner.
chotu2010 said:
If i flash with lollipop frimware. There is any chance to break google account.
Click to expand...
Click to collapse
Moto X Play originally had LL 5.1.1 which had factory reset protection implemented anyway. I'd try flashing 6.0 version with 1st november 2015 security patch and follow this tutorial:
http://www.hardreset.info/devices/motorola/motorola-moto-x-play-xt1562/faq/bypass-google-protection/
Ok let me try
chotu2010 said:
Ok let me try
Click to expand...
Click to collapse
Did you resolve this problem ?
This is my situazion
Android 6.0.1 , march security patch ! IMPOSSIBLE enable Developer Option from Clicking Build Number
Impossible Unlock BootLoader from fastboot because DeveloperOptions enable nedded
Impossible flash stock rom from fastboot because bootloader in locked
impossible flash stock 5.1.1 from recovery "Apply update from SDCard" because footer is wrong , signature failed
how do i enable developer options ?
fullmetaldark93 said:
Did you resolve this problem ?
This is my situazion
Android 6.0.1 , march security patch ! IMPOSSIBLE enable Developer Option from Clicking Build Number
Impossible Unlock BootLoader from fastboot because DeveloperOptions enable nedded
Impossible flash stock rom from fastboot because bootloader in locked
impossible flash stock 5.1.1 from recovery "Apply update from SDCard" because footer is wrong , signature failed
how do i enable developer options ?
Click to expand...
Click to collapse
Same problem bro.but I am not trying to flash 6.0 just download firmware today.but I think flash willbe done.beacause if bootloader is lock.may be flash via factory signed.img ok let me flash today I will post if I success.
Did you guys at least try the workaround that worked on previous security patches?
minimale_ldz said:
Did you guys at least try the workaround that worked on previous security patches?
Click to expand...
Click to collapse
yes , the thing with the japanes languace etc... ! Yes i tried but the build number don't give the Developer Option ! i clicked a thousands time but nothing
i also try to flash the update of 6.0 (the package of 500 mb ) from the recovery , the installation STARTED but ended immediatly beacuse the update is to do from 5.1.1 and not from 6.0.1
i cheked everything ! there is any method left ?
fullmetaldark93 said:
yes , the thing with the japanes languace etc... ! Yes i tried but the build number don't give the Developer Option ! i clicked a thousands time but nothing
i also try to flash the update of 6.0 (the package of 500 mb ) from the recovery , the installation STARTED but ended immediatly beacuse the update is to do from 5.1.1 and not from 6.0.1
i cheked everything ! there is any method left ?
Click to expand...
Click to collapse
The thing is Factory Reset Protection will work as long as you reset the device with Google account present and some sort of lock screen set (PIN/Password/Pattern), so the workaround doesn't neccesarily mean accessing Developer Options - you only need to access Settings somehow and do a Factory Reset from Backup & Reset menu on the device that doesn't have either Google account or Screen Lock set. Try if this will work for you:
https://youtu.be/nOymYg3lswI
minimale_ldz said:
The thing is Factory Reset Protection will work as long as you reset the device with Google account present and some sort of lock screen set (PIN/Password/Pattern), so the workaround doesn't neccesarily mean accessing Developer Options - you only need to access Settings somehow and do a Factory Reset from Backup & Reset menu on the device that doesn't have either Google account or Screen Lock set. Try if this will work for you:
https://youtu.be/nOymYg3lswI
Click to expand...
Click to collapse
yes i know , you need to enable DevOp because the button "RESET PHONE" is white and i can click in it ! for do this i have to enable DevOp and send a comand trough adb to abilitate it !
fullmetaldark93 said:
yes i know , you need to enable DevOp because the button "RESET PHONE" is white and i can click in it ! for do this i have to enable DevOp and send a comand trough adb to abilitate it !
Click to expand...
Click to collapse
Sorry, I didn't know
use Android device manager to change the pattern or pin
bablu048 said:
use Android device manager to change the pattern or pin
Click to expand...
Click to collapse
for error i factory reset the phone from recovery before do all this operation! i never know about FRP !
Hello People,
I have the same situation with this moto x play. I gifted this Moto X Play to my friend who is not tech savvy. He created a google account just to access playstore. Now he doesn't remember any details of that email so I cant help him recover the password. so I tried almost all the options that are available on internet and you-tube but nothing works. The phone was updated to 6.0.1, Security patch level is 1 march 2016 and no matter how many times you hit on the build number, the developer options doesn't come up. I have rooted like 40 phones so far, but never came across this kind of situation. I just hope somebody finds a solution to this, coz the phone is as good as paper weight.
Hi all,
Recently we find a way to go back to 8.1.0 from Android P DP1 with Verizon locked bootloader on the Android Beta Program community. Thanks Ziauddin Sameer for try it.
All you need is:
1- Google Pixel or Pixel XL with locked bootloader (Don't know if it work on Pixel 2 or Pixel 2 XL but it may work)
2- Android P DP1 installed on your device
3- Full April 2018 OTA link here https://developers.google.com/android/ota
4- ADB/FASTBOOT drivers link here https://forum.xda-developers.com/showthread.php?t=2588979
Now that you have all that and the drivers intalled let's do this:
You'll lose all your data after this, so backup before continue
1- Install the drivers
2- Put the Full April OTA zip on the adb folder located on C:/
3- Turn you Pixel off and go to recovery mode
4- Select "Apply update from ADB"
5- Plug in your Pixel via USB to the computer
6- Inside the adb folder Hold "Shift" and right click, select Open Powershell/CMD here"
7- Inside the Powershell/CMD type
Code:
abd sideload filename.zip
8- When its done your Pixel will try to boot and since it has the Android P data (cause sideloads dont erase data) it would said that the data is corrupted and it will suggest you to factory reset.
9- Select factory resert and it will boot on Android 8.1.0
Psdt: Sorry for my bad english.
You can confirm it in here https://plus.google.com/101606265756083327418/posts/cshGmedy5ZX
I can confirm that this does work! THANKS! I am happily back to 8.1! Don't get me wrong "P" is awesome and stable, but having the WiFi Calling feature broke in "P" is a deal breaker for me. I will just have to wait until DP2 to see if it gets sorted out.
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
I tried this after going to Android P beta. It did not work for me.
I followed the steps and when I ran adb sideload xxx.zip I received this...
verifying update package
E:footer is wrong
update package verification took 0.2 s (result 1)
E:Signature verification failed
E:error: 21
Installation aborted.
Any help would be greatly appreciated, basically I opted into beta and then opted out but never received the image to go back and apps are not working for me...gear s3, libby and some others.
whreed said:
EDIT do not use the May 2018 file, use April, this one is transferring now, below error is because of MAY file.
.
Click to expand...
Click to collapse
So for downgrading from Android P DP2 we need to use 8.1 April OTA, right?
I ultimately did get the push of the image to my device to pass but the image didn't work for me... When I wiped and rebooted and after initial setup up I received the message to go back to Oreo from Google....I was previously in the beta but opted out.
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
caloysilva said:
Does not work for me even for April OTA. It says package being updated is older than the currently installed. I'm on Android P May patch.
Is it possible that I can downgrade when the June OTA is out because of the timestamp?
Click to expand...
Click to collapse
Just opt out of the beta and an OTA will appear to go back to Oreo
It doesn't seem this method will work to downgrade the OTA 9.0 update? My phone has been completely unusable since the 9.0 update applied (the radio modem has worked all of about 2 days since the update). I've tried everything and have been on the phone with google many times over this. When I try to place a call, I'll either get the message "Radio off" or " Cannot place calls in Airplane mode" errors. Rebooting, cycling data and airplane modes have no effect, resetting networking does nothing, even factory resetting does nothing. My phone is completely useless without mobile data. I'll never purchase anything from Verizon again, with their opting to lock the bootloader on their phones!
I was also curious if this method would work for an OTA 9.0 device ?
Oh boy, Huawei trying to screw us all over. Magisk apparently is no longer working, so no root for once a new OTA installs for Huawei devices.
https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
https://forum.xda-developers.com/showpost.php?p=77418253&postcount=6557
New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.
That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..."
Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.
Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)
→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak
I attach here the patch from Huawei for P9 - may you take a look, thanks
Click to expand...
Click to collapse
I have dm-verity always off (not enabled in Magisk Manager) and I have also avb disabled in /vendor/etc/fstab.ext4.hi.... and fstab.f2fs.hi.... (I have different Huawei devices)
To make the issue clearer here is another summary:
I made a Rebrand Thread for Huawei P9-EVA here: https://forum.xda-developers.com/p9/...9-eva-t3820849
The main reason for this is to allow users to unofficially update their device to Android 8 Oreo. Huawei has rolled out the Oreo OTA update in China, but has no plans to release this update outside of China. Although Oreo runs much better on the devices.
To make this possible, root is an important part, otherwise the mobile network will not work on the rebranded devices. Many users were very happy because they can now also use Oreo Treble Roms by the Open Kirin Team.
Okay → Devices rebranded to EVA-AL10 and updated to the official Oreo Firmware b528. With some modification everything is working fine.
→ Yesterday OTA Patch01 was available. I flashed the unmodified original Huawei ramdisk.img, uninstalled Magisk Manager and flashed the original EMUI Recovery. Then I agreed to the OTA update. The update was succesful installed.
After that I flashed the Magisk patched_ramdisk.img again, but the phone did not boot → it booted only with original b528 ramdisk.img
We were three people who tested it. Me and @dkionline and @zgfg We tried everything that came to our mind. → flashing first original ramdisk and kernel.img and booted to system. Then flashing patched ramdisk.img b528 with Magisk 16, Magisk 16.7 with flag "force encryption" and without "force encryption" (related to - if device is with data encrypted or data decrypted)
Flashing TWRP was not a problem, and together with the original Huawei ramdisk.img phone was able to start to system. To get Root again, we must downgraded to b528 without this Patch.
→ The Patch includes a Fix for mms and Fix for gaming (changes a Line in a local.prop) and it includes also a Kernel patch.
Looking back, we should have tested a little more. What we did not test → making dd with TWRP from ramdisk.img after the OTA Patch and then patch the "dump" ramdisk.img with Magisk. → Maybe that would have worked - we do not know it now and I do not feel like reproducing it again. But perhaps @zgfg can try this in a view days (he did not downgrade yet, because he is outside).
With this last test we could say it for sure, if the Kernel patch includes something to make Huawei Phones unbootable together with Magisk.
And coincidentally I read then in the Mate 10 forum that there also a user (with ALP-L29c636) got an OTA with a Patch01 and similar problem " I got a patch notification so I download it, rebooted and the patch installed (phone booted and I checked version and it was patch1). Cool. So then I rooted using magisk and phone was soft bricked..." : https://forum.xda-developers.com/sho...&postcount=256
My first thought was simple, Huawei is now trying to prevent root with this patch01 and much confirms this theory....
→ Bootloader Unlock Site closed
→ TrustSpace is a new App in system which definitely check and disable Root (we had this app disabled and two of us has it deleted in system)
→ Downgrade with unofficial methods become danger for hardbrick, because of two different Xloader.img in the Firmware (Mate 10)
Click to expand...
Click to collapse
Big thanks to @Tecalote for bringing this to my attention.
Not sure if this will hit the Honor 7x, it probably will. I am prepared for the worst, really hate it when Huawei does this.
Its looking like Huawei just shot themselves in the foot on this if its infact the case, there is nothing worse then developers getting middle fingered and scorned. If you think a Developer using a fork (github joke) is dangerous just wait till they nuke that commit/submit button! This is not going to bold well for honor/huawei
As i have already stated if this turns out to be Honor/Huawei out right middle fingering devs and users choice I will be looking for another phone pronto.
Click to expand...
Click to collapse
Holy shiet
Yes, i can confirm this, please do not flash that Patch01, it will make your device stuck on boot message after you flash magisk.
I'm on Huawei Nova 2s.
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
heindrix said:
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
Click to expand...
Click to collapse
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
battleforce said:
How can you tell if you've gotten the Patch01 update?
My phone is currently BND-L24 8.0.0.341(C567), with a July 1 2018 Android security patch.
For the link you posted im assuming id have to use "B) If the TWRP for your device has not access to encrypted /data then you can do the following:"
The site here http://pro-teammt.ru/firmware-database/?firmware_model= that has firmware doesn't seem to show 8.0.0.341? Should I use BND-L24AC567B330 (8.0.0.330) because it seems to be an update from May, and when I google my build number Huawei tweeted that it was a May security update? Or will using that brick my phone? Of the availible BND-L24 firmwares, which one should I use?
Also do I already need TWRP installed? can I do that on my unrooted device?
Click to expand...
Click to collapse
You can see it in System->About.
See at Build Number section, it will be printed XXX-XXXX X.X.X.XXX(XXXPatch01).
You can use Huawei Firmware Finder : https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Go to Common Base menu, and set (click gear button) this value (G:2649 g:1699), that value is identifier for Honor 7x.
And type L24 in the search box.
After that, click on search button (magnifier glass button), you'll see all available updates for Honor 7x.
And there you go, all of firmware lists for Honor 7x L24.
I made some screenshot for you.
Enjoy.
Picked up a Moto 6 Plus (XT1926-7, retla) last month and have been running the latest 8.0 (8.0.0_OPWS27.113-89-5) with unlocked bootloader and Magisk. Working flawless. :good:
Decided to take the plunge to Pie last night, which ended up with me have to do a full restore of a 8.0.0_OPWS27.113-89-5, then taking the OTA to 9.0
Upon successful OTA to 9.0, I then rebooted and used fastboot TWRP to try to take a clean nandroid backup. I could backup all partitions except Data (fork failure to make the rar).
I then rebooted again (still stock, no Magisk install yet), and noticed that I was getting a "dm-verity disabled" warning on my bootup screen and then a warning under System Update check that says "Updates are disable for this device due to compromised system integrity".
Have others tried the same yet? Is this "compromise" due to the unlocked bootloader, or did TWRP trip something? Is it possible to run Pie with Magisk and still be a google certified device?
Just tried again:
* Clean wipe and install to 8.0 (89-5)
* Bare bones phone config.
* enable USB Debug
* Accepted OTA Update and reboot
* Successful update to 9.0 (PPW29.116-11, patch level Dec 1, 2018)
* Play Store version 13.0.23-all [0] [PR] 227930514
* enable USB Debug
* reboot
* following warning on the blue/yellow bootup screen: "Verity mode is set to disabled"
* System Update page: "System Integrity is Compromised", "As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software."
EDIT:
* Magisk rooting still works: https://forum.xda-developers.com/g6-plus/how-to/3-how-to-install-root-aka-magisk-t3854244
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs
RokCruz said:
Can you share wich files do you use to upgrade? (Screenshot)
Sent from my Motorola moto g(6) plus using XDA Labs
Click to expand...
Click to collapse
I used the files below to return to stock 8.0 prior to upgrade. I did not use files to upgrade to 9.0, I used the OTA system updater.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETLA/
thump said:
* TWRP installer works: https://forum.xda-developers.com/g6-plus/how-to/twrp-installer-zip-evert-t3875657
Click to expand...
Click to collapse
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.
May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir
Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?
weazie said:
Hmm. I would not use the twrp installer, since I haven't heard anywhere that it would work flawless with evert. Skip that and use fastboot boot twrp.img to access recovery. Do not flash. Boot.
Click to expand...
Click to collapse
I've used both, but the installed one worked identically so far for backing up and installing Magisk.
The_Pacifier said:
May i ask you a question kind sir. I have the same model (G6 plus) de same oppw thingy (8.0.0_OPWS27.113-89-5) and when i hit the update button did not get any OTA. It says i have the latest version and still in november security patch. How did you trigger the OTA? Or you sideload it? Thanks kind sir
Click to expand...
Click to collapse
I'm on the retla software channel, which I believe is the first to get the Pie OTAs.
knevelsg-j said:
Nice to see that you had an OTA to Pie. I was about to ask where you live, because I don't have the OTA here in Belgium yet. But then I saw you have a RETLA device, so I guess I will have to wait some more!
Is the phone working well on Pie?
Click to expand...
Click to collapse
Yep.. purchased on Amazon in the US (I don't think they ever officially released G6+ model direct to US). So far, working smooth. Haven't found any bugs.
Should also note that even with the Verity and "not update eligible" issues, and now rooted with Magisk, it does still show as Play Store Certified.
@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too ??
The_Pacifier said:
@thump i am in the retla too. I did not get the pop up update neither via security o update section. I have the same OPWS as yours too
Click to expand...
Click to collapse
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
Yes maybe... latin america is pretty wide...going to keep pressing the update button or in the case a factory reset may help or not?
thump said:
Weird. Mine badgered me every hour with a "Software Update is Available" notification for the past week. Even when I did the clean stock reflash to 89-5, it notified me a few minutes after clean reboot, before I even got around to checking System Updates. Maybe rolling it out in staggered waves of some type?
Click to expand...
Click to collapse
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.
The_Pacifier said:
@thump Hello kind sir!! Remember me? Yes the updates are released in staggered waves, just got prompted the Android Pie update!! ?? Appreciate your help.
Click to expand...
Click to collapse
Excellent. Good luck!
Hello everyone,
my Moto G6 Plus does not detect wifi or mobile networks.
This happened when I rooted the smartphone and after testing what I wanted, I tried flashing the original Motorola rom and after that, blocked the bootloader again.
When the smartphone restarted, I noticed that it does not detect wifi or sim card and consequently does not detect mobile networks.
I tried flasing other roms to the smartphone, but the messages I get: permission denied
I tried more than 50 roms, it didn't work.
I installed Gnirehtet and can connect to the internet, but the OEM Unlock option remains grayed out.
Does anyone have any tips on how to revive my smartphone?
Current Android version: 8.0.0
Patch Level: november 1, 2018
Baseband version: Unknown
Kernel version: 4.4.78
Build number: OPWS27.113-92-5
Thanks in advance.
adaoduque said:
Hello everyone,
my Moto G6 Plus does not detect wifi or mobile networks.
This happened when I rooted the smartphone and after testing what I wanted, I tried flashing the original Motorola rom and after that, blocked the bootloader again.
When the smartphone restarted, I noticed that it does not detect wifi or sim card and consequently does not detect mobile networks.
I tried flasing other roms to the smartphone, but the messages I get: permission denied
I tried more than 50 roms, it didn't work.
I installed Gnirehtet and can connect to the internet, but the OEM Unlock option remains grayed out.
Does anyone have any tips on how to revive my smartphone?
Current Android version: 8.0.0
Patch Level: november 1, 2018
Baseband version: Unknown
Kernel version: 4.4.78
Build number: OPWS27.113-92-5
Thanks in advance.
Click to expand...
Click to collapse
Hello, try blankflashing or waiting 7 days with phone on and try to update it after.
mrsiri said:
Hello, try blankflashing or waiting 7 days with phone on and try to update it after.
Click to expand...
Click to collapse
Hello mrsiri, thanks for replying.
I waited more than 3 months, without restarting / turning off the smartphone and did not unlock the option to OEM Unlock.
Do you have a link that I can download a blankflash that works on this smartphone model?
Thanks in advance.
adaoduque said:
Hello mrsiri, thanks for replying.
I waited more than 3 months, without restarting / turning off the smartphone and did not unlock the option to OEM Unlock.
Do you have a link that I can download a blankflash that works on this smartphone model?
Thanks in advance.
Click to expand...
Click to collapse
That won't be toggleable for any time. Can you not update phone like regular OTA? or you're on latest version?
Blankflash link: https://mirrors.lolinet.com/firmware/moto/evert/
mrsiri said:
That won't be toggleable for any time. Can you not update phone like regular OTA? or you're on latest version?
Blankflash link: https://mirrors.lolinet.com/firmware/moto/evert/
Click to expand...
Click to collapse
Currently, Android 8.0 is installed.
When I check for updates, the system informs me that it has no updates.
I will test the blankflash and come back with the result
It says phone is updated or system is compromised? On my phone it used to show any new updates and let me install it too. There were no additional problems when updating. Same problems persisted during updates until the last pie update, which fixed my phone.
mrsiri said:
It says phone is updated or system is compromised? On my phone it used to show any new updates and let me install it too. There were no additional problems when updating. Same problems persisted during updates until the last pie update, which fixed my phone.
Click to expand...
Click to collapse
I installed the android 8.0 ROM on this phone.
My failure was after installing this ROM, executing the bootloader lock without first checking that everything was OK with the phone.
Blankflash say: < waiting for device >
... and nothing happens.
I tried EDL mode, but the smartphone restarts for the operating system.
Any ideas on how I could get this device into EDL mode so I can install the blankflash ?
Thanks in advance.
adaoduque said:
I installed the android 8.0 ROM on this phone.
My failure was after installing this ROM, executing the bootloader lock without first checking that everything was OK with the phone.
Blankflash say: < waiting for device >
... and nothing happens.
I tried EDL mode, but the smartphone restarts for the operating system.
Any ideas on how I could get this device into EDL mode so I can install the blankflash ?
Thanks in advance.
Click to expand...
Click to collapse
You have to open back of the phone and short circuit the test points in the circuit board