Related
Question/issues solved - thread done!
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.
CTR01 said:
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.
Click to expand...
Click to collapse
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?
alray said:
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?
Click to expand...
Click to collapse
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook Pro 13" with Retina display and Mac OSX 10.9.4 and internet connection.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.
CTR01 said:
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook bla bla bla.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.
Click to expand...
Click to collapse
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.
alray said:
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.
Click to expand...
Click to collapse
@alray:
Great, thanks for that and I will be sure to update here as soon as it is all setup.
@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.
CTR01 said:
@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.
Click to expand...
Click to collapse
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend
alray said:
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend
Click to expand...
Click to collapse
@alray:
My first post has a link to a picture of what the current status is of my phone, if you missed it before.
I will look at this part in more detail after I'm done with work
I'll post asap when I get a chance. Thanks!
@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!
CTR01 said:
@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!
Click to expand...
Click to collapse
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"
alray said:
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"
Click to expand...
Click to collapse
@alray:
No worries, I'll try that and get back to you.
Thanks.
Sent from my HTC One_M8
@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?
CTR01 said:
@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?
Click to expand...
Click to collapse
yes you need the drivers, but better to have htc sync uninstalled
alray said:
yes you need the drivers, but better to have htc sync uninstalled
Click to expand...
Click to collapse
Great, thanks for that clarification. I'll update you when I get a chance to run through the steps!
@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8
CTR01 said:
@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8
Click to expand...
Click to collapse
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?
alray said:
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?
Click to expand...
Click to collapse
@alray:
Yeah, the drivers installed just fine.
However, I actually just showed my friend the phone with CM10 on it and told him the pros/cons and he was just fine with everything since he just wanted a phone that would work and not freeze/lag like his current phone does.
So thank you for your help and the situation has been solved!
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John
jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.
i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..
7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
y5r43l said:
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
Try the unlocking code again
sd_shadow said:
Try the unlocking code again
Click to expand...
Click to collapse
It won't allow. It asks to enable OEM Unlock under Settings -> Developer Options.
Thanks for the answer!
y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7.
Sent from my ali using XDA Labs
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
pastorbob62 said:
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
Click to expand...
Click to collapse
This was his way of knowing that, you and i, we have been here for a long time, i learned this years ago, now he knows it
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
y5r43l said:
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
Click to expand...
Click to collapse
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
y5r43l said:
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
Click to expand...
Click to collapse
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
darkherman said:
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
Click to expand...
Click to collapse
Hi, darkherman,
thank you for you reply.
Unfortunately it won't work as according to documentation: "Make sure you enabled adb debugging on your device(s)."
I have to boot the system to enable it in Developer Options.
Thanks anyway!
Is there a way to bypass the Google Wizard and boot the system without logging in?
About the warning on startup I've read somewhere that's not possible because of some var value obtained from:
Code:
fastboot getvar allCODE]
Don't remember exactly what var, but its value may be 0, 1 or 2 that means locked, unlocked and relocked (not necessarily in this order)
-- runnig the above command I saw some variables such as securestate, verity-state and iswarrantyvoid than may mean something.
But, as far as I know, we have no command such as "set-iswarrantyvoid false" or "set-verity-state 1" or something like that.
Maybe this could be done by replacing/updating the firmware if possible, but I think it doesn't worth the risk of making the device irreversibly bricked.
Thanks again for your reply.
It seem there's no way to rescue it.
Gonna just give up and throw it away.
Thanks for those who tried to help!
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
KtownJeff said:
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
Hi, thank you for your reply!
I really never have took apart a phone nor know about test point shorting so this is not an option for me. I could even try to do it but probably won't be able to mount it back.
It's a no carrier phone, but in my country, there's no so easy return policy that I know of, unfortunately.
The bypass won't work because the second pass, "Connect your Motorola Moto G7 Plus to your Wi-Fi", as I think this is the biggest problem, I cannot connect to Wi-Fi. I also tried the method suggested by @darkherman throught gnirehtet with no success.
Click to expand...
Click to collapse
UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.
I'd appreciate it someone could provide instructions for a numpty, in a manner that the numpty (myself) can understand.
I unlocked the Bootloader on my Asus Zenfone 8 with a view to flash the stable version of Android 12.
My mistake was not having enough skill to 1. Flash Android 12 and 2 relock the Bootloader. I unlocked the Bootloader by using the official method from the Asus site.
Oh yes, I also retrospectively realised that I lost the ability to use Google Pay and Netflix. Oh, and I may not gain any OTA updates as well.
I've read and re-read countless articles and tried to follow many "how to's" but not being successful ... to me, it seems I'm missing a common sense step that everyone knows so well, that they feel doesn't need to be included in the how to's.
So I'm seeking a fool proof step by step guide for numpties (me) or someone who could step me through it
via DM.
I'm pretty much at the point to pay someone to assist me and sort out my Zenfone with Android 12 and a relocked bootloader.
Thank you in advance for any assistance.
Thomas
Follow the steps to revert back to Android 11 at the bottom of the page. This does not require an open bootloader https://www.asus.com/Content/Android-12-Beta/
You will then be able to place the latest update firmware on the phone with a computer. From that it will detect the update files and start the procedure.
Adaoh said:
Follow the steps to revert back to Android 11 at the bottom of the page. This does not require an open bootloader https://www.asus.com/Content/Android-12-Beta/
You will then be able to place the latest update firmware on the phone with a computer. From that it will detect the update files and start the procedure.
Click to expand...
Click to collapse
Hi Adaoh,
Thank you for the suggestion, but I have another query, before I proceed.
The link provided refers to the Android 11 version WW-30.11.51.115 but the stable version Android 12 version WW-31.1004.0404.81 states on the Asus website that it will only update to this version from Android 11 version WW-30.12.112.72
The Android 12 version referred to in the link provided is WW-31.0803.0403.54 a beta version which is older than the stable Android 12 mentioned above.
Are you aware of a Android 11 version WW-30.12.112.72 image file that can be utilised? I've not found one.
And my bootloader is already unlocked (referring to your comment that this does not require an open bootloader) so I would be seeking step by step instructions how to relock.
I'm keen to update to the Stable Android 12 version as I've read I may not receive any OTA updates, and so in my mind, a stable newer version of Android 12 is superior to an older beta version of Android 12.
Thoughts please?
Thanks for your input.
Thomas
TferThomas said:
Hi Adaoh,
Thank you for the suggestion, but I have another query, before I proceed.
The link provided refers to the Android 11 version WW-30.11.51.115 but the stable version Android 12 version WW-31.1004.0404.81 states on the Asus website that it will only update to this version from Android 11 version WW-30.12.112.72
The Android 12 version referred to in the link provided is WW-31.0803.0403.54 a beta version which is older than the stable Android 12 mentioned above.
Are you aware of a Android 11 version WW-30.12.112.72 image file that can be utilised? I've not found one.
And my bootloader is already unlocked (referring to your comment that this does not require an open bootloader) so I would be seeking step by step instructions how to relock.
I'm keen to update to the Stable Android 12 version as I've read I may not receive any OTA updates, and so in my mind, a stable newer version of Android 12 is superior to an older beta version of Android 12.
Thoughts please?
Thanks for your input.
Thomas
Click to expand...
Click to collapse
Hi, I do not think that there is a script provided like in the Back to Android11 link I gave you. I have used this method to recover my phone from a boot loop, so I think that the OS version does not matter but I am not sure, it is not impossible that it would brick the phone...
if you are still on A11, I did this script when I was on the latest Android 11 build and it reverted me to the old one in the script. So in my opinion it will be fine for whatever the condition of your phone are.
After this script, since you will not have OTA updates because your phone is blacklisted from Asus' servers, you will need to flash the last Android11 (from my understanding) and then once that's done flash a12.
Flashing updates is very simple, just do the last steps I gave in the original post
TferThomas said:
I'd appreciate it someone could provide instructions for a numpty, in a manner that the numpty (myself) can understand.
I unlocked the Bootloader on my Asus Zenfone 8 with a view to flash the stable version of Android 12.
My mistake was not having enough skill to 1. Flash Android 12 and 2 relock the Bootloader. I unlocked the Bootloader by using the official method from the Asus site.
Oh yes, I also retrospectively realised that I lost the ability to use Google Pay and Netflix. Oh, and I may not gain any OTA updates as well.
I've read and re-read countless articles and tried to follow many "how to's" but not being successful ... to me, it seems I'm missing a common sense step that everyone knows so well, that they feel doesn't need to be included in the how to's.
So I'm seeking a fool proof step by step guide for numpties (me) or someone who could step me through it
via DM.
I'm pretty much at the point to pay someone to assist me and sort out my Zenfone with Android 12 and a relocked bootloader.
Thank you in advance for any assistance.
Thomas
Click to expand...
Click to collapse
Try flashing a GSI using Android Flash Tool. Then use adb to reboot it into fastboot mode. Then just do
Code:
fastboot flashing lock
$cronos_ said:
Try flashing a GSI using Android Flash Tool. Then just use adb to reboot it into fastboot mode. Then just do
Code:
fastboot flashing lock
Click to expand...
Click to collapse
Hi $cronos_,
What is a GSI please? As mentioned at the start of my post, the simpler and more detailed the reply the better as I'm the numpty and happy to admit to that.
Thank you
Thomas
Adaoh said:
Hi, I do not think that there is a script provided like in the Back to Android11 link I gave you. I have used this method to recover my phone from a boot loop, so I think that the OS version does not matter but I am not sure, it is not impossible that it would brick the phone...
if you are still on A11, I did this script when I was on the latest Android 11 build and it reverted me to the old one in the script. So in my opinion it will be fine for whatever the condition of your phone are.
After this script, since you will not have OTA updates because your phone is blacklisted from Asus' servers, you will need to flash the last Android11 (from my understanding) and then once that's done flash a12.
Flashing updates is very simple, just do the last steps I gave in the original post
Click to expand...
Click to collapse
Hi Adaoh,
So what you're saying is to follow this link and take me to an older Android 11 version but then flash the most recent Android 11 version, then flash Android 12?
Question for you that has stumped me .... most people on forums and websites quickly gloss over flashing of an Operating System but don't actually go through the exact every step .... are you able to assist here please?
Again, as per the start of my post, I'm the numpty and happy to admit that, but do need to know comprehensively each and every step.
Thank you in advance,
Thomas
TferThomas said:
Hi $cronos_,
What is a GSI please? As mentioned at the start of my post, the simpler and more detailed the reply the better as I'm the numpty and happy to admit to that.
Thank you
Thomas
Click to expand...
Click to collapse
generic system image
TferThomas said:
Hi Adaoh,
So what you're saying is to follow this link and take me to an older Android 11 version but then flash the most recent Android 11 version, then flash Android 12?
Question for you that has stumped me .... most people on forums and websites quickly gloss over flashing of an Operating System but don't actually go through the exact every step .... are you able to assist here please?
Again, as per the start of my post, I'm the numpty and happy to admit that, but do need to know comprehensively each and every step.
Thank you in advance,
Thomas
Click to expand...
Click to collapse
Updating from an update fileOk, so to update your phone when you can't receive OTAs:
Download the version that you need from the Asus Zenfone 8 Support page
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
Flashing the Stock ROM (Android 11)Note: doing this will remove any data on your phone, back it up if it is important to youThis also works if your phone is stuck in a bootloop or other problems of the sortIf your question was about the flashing of Android 11 from the Android12 page with the older version, the instructions on the page at the bottom should be enough, but I can try to make them clearer.
Turn off the phone
When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.
If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".
Plug the phone in your computer
Decompress the zip file on your computer
Execute the script file that is made for your computer
Windows: update_image.bat
Ubuntu: update_image.sh
MacOS: update_image_for_mac.sh
Wait for the process to finish, it'll take a while. You'll know it is done when the window that openned when you executed one of the script files says something along the lines of "Flashing done, press Enter to reboot"
I hope this helps!
$cronos_ said:
generic system image
Click to expand...
Click to collapse
Thank you!
Thomas
Adaoh said:
Updating from an update fileOk, so to update your phone when you can't receive OTAs:
Download the version that you need from the Asus Zenfone 8 Support page
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
Flashing the Stock ROM (Android 11)Note: doing this will remove any data on your phone, back it up if it is important to youThis also works if your phone is stuck in a bootloop or other problems of the sortIf your question was about the flashing of Android 11 from the Android12 page with the older version, the instructions on the page at the bottom should be enough, but I can try to make them clearer.
Turn off the phone
When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.
If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".
Plug the phone in your computer
Decompress the zip file on your computer
Execute the file that is made for your computer
Windows: update_image.bat
Ubuntu: update_image.sh
MacOS: update_image_for_mac.sh
Wait for the process to finish, you'll know it is done when the window that openned when you executed one of the scripts says something along the lines of "Flashing done, press Enter to reboot"
I hope this helps!
Click to expand...
Click to collapse
Hi Adaoh,
I am really glad you have taken my request as seriously as this and I thank you for the very specific detailed reply.
I'm going to try this over the next couple of days (I hope) and report back, but really do appreciate this!
Thomas
Adaoh said:
Updating from an update fileOk, so to update your phone when you can't receive OTAs:
Download the version that you need from the Asus Zenfone 8 Support page
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
Flashing the Stock ROM (Android 11)Note: doing this will remove any data on your phone, back it up if it is important to youThis also works if your phone is stuck in a bootloop or other problems of the sortIf your question was about the flashing of Android 11 from the Android12 page with the older version, the instructions on the page at the bottom should be enough, but I can try to make them clearer.
Turn off the phone
When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.
If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".
Plug the phone in your computer
Decompress the zip file on your computer
Execute the script file that is made for your computer
Windows: update_image.bat
Ubuntu: update_image.sh
MacOS: update_image_for_mac.sh
Wait for the process to finish, it'll take a while. You'll know it is done when the window that openned when you executed one of the script files says something along the lines of "Flashing done, press Enter to reboot"
I hope this helps!
Click to expand...
Click to collapse
Hi Adaoh,
This worked on the second attempt! ..... now the Zenfone 8 is updated to the stable Android 12 OS.
Thank you and made clear runnings for this numpty!
Thomas
$cronos_ said:
Try flashing a GSI using Android Flash Tool. Then just use adb to reboot it into fastboot mode. Then just do
Code:
fastboot flashing lock
Click to expand...
Click to collapse
Hi $cronos_,
I got the Zenfone 8 into recovery mode and connected to the PC and initiated a Windows Powershell and typed the following to confirm the PC could find the Zenfone 8.
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot devices
M4AIB7626606MH7 fastboot
So it found the Zenfone 8
When I tried to Lock the Bootloader I got the following:
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot oem lock
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.005s
And tried your suggested command:
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot flashing lock
...
FAILED (remote: Unrecognized command flashing lock)
finished. total time: 0.005s
Any thoughts on what I am doing wrong please?
Thank you in advance.
Thomas
Hi,
I had the same problem as you, couldn't use Google pay.
All I did was open powershell and use the following command.
fastboot oem asus-csc_lk
Now it's relocked and works as before.
Hope this helps you.
Craig
mef206 said:
Hi,
I had the same problem as you, couldn't use Google pay.
All I did was open powershell and use the following command.
fastboot oem asus-csc_lk
Now it's relocked and works as before.
Hope this helps you.
Craig
Click to expand...
Click to collapse
Hi Craig,
I haven't seen this one before, so will definitely give it a go.
Thank you!
Thomas
mef206 said:
Hi,
I had the same problem as you, couldn't use Google pay.
All I did was open powershell and use the following command.
fastboot oem asus-csc_lk
Now it's relocked and works as before.
Hope this helps you.
Craig
Click to expand...
Click to collapse
Hi Craig,
This sounds really promising so had a go, but was not successful.
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot devices
M4AIB7626606MH7 fastboot
PS C:\Users\roma_\OneDrive\Desktop\platform-tools> fastboot oem asus-csc_lk
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.005s
Any thoughts or suggestions would be much appreciated!
Thanks in advance,
Thomas
Hi,
Sorry I forgot to mention that I had followed the steps on the official Asus website to revert back to android 11 before I had run the command, as I wanted Google pay back.
fastboot oem asus-csc_lk
I hadn't tried to relock bootloader with Android 12 installed.
I did see in somewhere on line that the device requires factory reset after command is used. Also you could try some of these codes from following link.
hope you get it sorted.
craig
Relock the Bootloader?
I know asking this question at a very early point would be very foolish, I tried searching various places for the answer but didn't, can anyone from previous experience or with answer tell me how can the Bootloader be locked again? Thanks in...
forum.xda-developers.com
mef206 said:
Hi,
Sorry I forgot to mention that I had followed the steps on the official Asus website to revert back to android 11 before I had run the command, as I wanted Google pay back.
fastboot oem asus-csc_lk
I hadn't tried to relock bootloader with Android 12 installed.
I did see in somewhere on line that the device requires factory reset after command is used. Also you could try some of these codes from following link.
hope you get it sorted.
craig
Relock the Bootloader?
I know asking this question at a very early point would be very foolish, I tried searching various places for the answer but didn't, can anyone from previous experience or with answer tell me how can the Bootloader be locked again? Thanks in...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Craig
That is a good point you raise ..... and believe where I may have stuffed up was not flashing the device back down to Android 11 (currently it has the Stable Android 12). I am presuming this step would wipe the Official Asus Unlock Device App which was downloaded originally, which of course unlocked the bootloader?
Steps taken today:
1. Downloaded the Zipped Android 11 Image and unzipped on the PC.c
2. Put the Zenfone 8 into Fastboot Mode and opened up CMD powershell to confirm it was in Fastboot mode
PS C:\Users\roma_\OneDrive\Desktop\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release_for_google> fastboot devices
M4AIB7626606MH7 fastboot
PS C:\Users\roma_\OneDrive\Desktop\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release\WW-ZS590KS-30.11.51.115-MR0-user_20210826-release_for_google>
3. In the Unzipped Android 11 image found the windows update_image (I checked properties to confirm this was the Windows Batch File (.bat)
4. Right clicked, Run as Administrator.
5. I got this ....
fastboot cmd : fastboot
The script can't be used in this devices,hwid=,project=project FAILED (remote
Press any key to continue . . .
I am so missing something here, no doubt something really simple, but something really frustrating lol.
Any pointers would be appreciated.
Thank you!
Thomas
Hi,
I had done exactly as you have described.
Downloaded zip android 11
Unzipped and just double clicked on bat file whilst phone in fastboot.
Afterwards ran that command after rebooting phone back into fastboot.
Im sorry I can't be of anymore help I can't see why yours is not working the same.
Craig
mef206 said:
Hi,
I had done exactly as you have described.
Downloaded zip android 11
Unzipped and just double clicked on bat file whilst phone in fastboot.
Afterwards ran that command after rebooting phone back into fastboot.
Im sorry I can't be of anymore help I can't see why yours is not working the same.
Craig
Click to expand...
Click to collapse
Hi Craig,
Thank you and good to know I was following the directions.
Got me stumped, but I'll keep at it.
The only thing I am curious about is the unzipped file is in the desktop of my laptop (easy to find) but the desktop is set to back up to OneDrive .....I wondered if that could cause a problem (outside the limits of my ability)?
Thanks again for your input.
Thomas