the idea is to simply deggogle my a10. i found a few videos on how to do it. however i took the liberty of making a note of the base build number and after searching the internet, i found a firmware farchive that contained several md5 files. i figured i may need this in case anything went wrong.
so i went into settings and developer mode, turned on unlocking oem and usb debugging and attempted to flash the phone by booting into rescue mode (power off phone then power on while holding the volume up button) then selecting boot into bootlader from the menu before using a toll called odin on my pc, which given the threads i've seen on here, most of you are aware odin. i tried to flash the tar file reccomended on the site. odin reported failure. so without rebooting i flashed the firmware that matched my phone my selcting the respective md5 files and telling odin to do it. it reported neither success nor failure but gave a message of something like cs select. i have no idea what that means. however on rebooting the phone it booted fine. no errors or anything, just a completely reset phone. I like to add that this is not may main phone as i am a newbie on this area and wouldn't be so reckless as to experiment on my main phone. hower there is an app on there now called lazade which i beleiv is a shopping app based in the asian continent which isn't where i'm from. i unlocked developer mode once again as it had reset and found that the unlock oem option is missing. is it becasuse of the firmware i burned on it and to i need to reburn another? or is ther another way to get it back?
the baseband version is a105gdxu8cvg2
android 11
one ui 3.1
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
V0latyle said:
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
Click to expand...
Click to collapse
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
fjb59 said:
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
Click to expand...
Click to collapse
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
V0latyle said:
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
Click to expand...
Click to collapse
are they available here?
fjb59 said:
are they available here?
Click to expand...
Click to collapse
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
V0latyle said:
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
Click to expand...
Click to collapse
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
fjb59 said:
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
Click to expand...
Click to collapse
i found the site for it but the a10 is not listed on thier choice of phones
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
V0latyle said:
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
Click to expand...
Click to collapse
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
fjb59 said:
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
Click to expand...
Click to collapse
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
V0latyle said:
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
Click to expand...
Click to collapse
oem lock onu1)
looks like it's on. how do i disable it for this phone?
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
V0latyle said:
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
Click to expand...
Click to collapse
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
fjb59 said:
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
Click to expand...
Click to collapse
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
fjb59 said:
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
Click to expand...
Click to collapse
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
V0latyle said:
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
Click to expand...
Click to collapse
yep it does. i had a little bit of trouble between installing the first and second file. it kept reporting a corrupt operating system but i noteiced it cycled a reboot wo i held hte power and volume up buttons together when it cycled. this allowed me into rescue mode. from there i was able to power down the phone so i could reboot it back into download mode then upload the rescue file contained in the zip file mentioned. after that it booted ok but keeps claiming that the operating system isn''t offician but then boots into android ok. i expect installing the disable_drm_very app wil fix that. then i can try installign a new os.
but that's for tomorrow
Jjflick said:
I noticed this thread and would like to keep looking
Click to expand...
Click to collapse
i hope it helps you. i've detailed the steps i took as best as i could.
Related
I got my Honor 7 secondhand, and in the state it is I suspect it's bricked, as the system doesn't boot but fast boot does. I've been able to start in up in fast boot mode, but I couldn't flash recovery because fast boot shows an error saying I have no permission. I can unlock the bootloader if I had the IMEI of the phone, but I cannot boot therefore can't see it. I did not get the original box, so I can't get it from there either. The SIM tray was lost ¬¬. I have tried fastboot getvar IMEI, but I get the same error. Is there any tool or any way I could obtain the IMEI or skip the IMEI process indefinitely? Worst case scenario I would have to disassemble the phone to get it, which I prefer not to do.
even with the imei, the unlock site now requires you to use the actual device (with an account) on their site for 14 days so that doesn't help!
without the sim tray you can't flash stock either (as you have no access to internal storage, and i doubt stock recovery allows adb push)
you could try the eRecovery. it's supposed to get packages via wifi:
plug in usb data (connected to a pc)
turn it on holding vol+ until the eRecovery starts up
from my Huawei flashing experiences i doubt it will actually work :silly: but worth a try before you have to ring Huawei...
sminki said:
you could try the eRecovery. it's supposed to get packages via wifi:
plug in usb data (connected to a pc)
turn it on holding vol+ until the eRecovery starts up
Click to expand...
Click to collapse
Thanks for the reply. Unsure what specific tool this eRecovery is, so can you link it? (looked around and saw 'Acer eRecovery' not sure if that's it)
pawelam said:
Thanks for the reply. Unsure what specific tool this eRecovery is, so can you link it? (looked around and saw 'Acer eRecovery' not sure if that's it)
Click to expand...
Click to collapse
it's part of the firmware, so it's already on your phone, there is a second recovery partition (it's probably on there)
if you try the instructions in the previous post it should start it up
IMPORTANT: It appearance that Huawei is no longer going to provide bootloader unlocking services for their devices. Because of this, this guide is of no use unless you can find a way to get a code or you just held onto the code.
Hello, this is a guide for unlocking the bootloader and rooting the Huawei Ascend XT. I am writing this because the current guide is not very well written and does not contain bootloader unlock instructions. This will be split into two parts: Part 1, unlocking the bootloader, and Part 2, rooting the phone.
PLEASE NOTE THAT FOLLOWING THESE INSTRUCTIONS WILL WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR AND DAMAGE DONE TO YOUR PHONE!
THINGS YOU WILL NEED:
1. A Huawei Ascend XT with at least 60% of battery left
2. A computer with adb drivers, fastboot drivers, and the Huawei USB drivers
3. A Micro-SD card for your backups (THIS IS VERY IMPORTANT! PLEASE MAKE BACKUPS!)
4. TWRP for this phone. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933 (credits to enigma2446)
5. The ZIP containing SuperSU. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933
6. The SDK Platform Tools. These can be found on the android studio website.
PART 1: UNLOCKING THE BOOTLOADER1. Geting the Bootloader Unlock Code: You need to get your bootloader unlock code. You can get this by going to https://emui.huawei.com/en/plugin.php?id=unlock
(EDIT: It appears that this website is down. I have read that if you PM Huawei on Twitter or call them and provide all the details of your phone, they will give you a code. I have not tested this method, bit people have said it worked with the mate 10.) and signing into your Huawei ID. If you dont have one, create one. Then, follow the instructions given to you by Huawei to get the code.
2. Enabling the Enable OEM Unlock Option: To enable this option, you must enable developer options. To do this, go to Settings>About Phone and tap the Build number until it says "You are now a Developer". back out of About Phone, and go to Developer options. turn on "Enable OEM unlock" and press Enable.
3. Enable USB Debugging: While you are still in Developer options, enable the option 'USB debugging" and press OK.
4. Booting Into the Bootloader: once you have completed the first three steps, you can now boot into the bootloader. Connect your phone to your computer, and open the Platform Tools folder you should have downloaded and extracted. Shift-Right click, and press "Open Command Window Here" or "Open Powershell Window Here", depending on your version of windows. Once it is open, make sure your device is detected by typing "adb devices". If it displays your device, you are good to continue. If not, something is not set up right on your computer or phone. Once you verified that your phone is detected, type "adb reboot bootloader".
5. Unlocking the Bootloader: Once your phone has booted into the bootloader, you can now unlock the bootloader. YOUR PHONE WILL BE WIPED ONCE YOU TYPED THIS COMMAND. You can unlock it by typing "fastboot oem unlock <your bootloader unlock code>". Once it has finished, you can reboot your phone, and just run through the setup fast, because you will still have to wipe it again.
PART 2: ROOTING YOUR PHONE1. Move the TWRP image you downloaded (called
Xtrecovery) to your Platform Tools folder and rename it to "TWRP.img"
2. Insert Your Micro-SD Card
3. Move the SuperSU Zip you downloaded to the SD card
4. Re-Enable USB Debugging: Enable Developer options by going to Settings>About Phone and taping the Build number until it says "You are now a Developer". Back out of About Phone, and go to Developer options, and enable USB debugging, and press OK.
5. Boot Into the Bootloader: Type "adb reboot bootloader" into your open CMD window or Powershell window.
6. Verify That your Phone says that the Bootloader is unlocked
7. Type "fastboot boot TWRP.img"
8. TWRP should boot. Tap "Keep Read Only"
9. You should now be in TWRP. Go to Backup>Select Storage and choose your Micro-SD card and tap OK. Uncheck everything and check "Recovery". Then, Swipe the slider to back up your stock recovery partition.
10. Once it has finished backing up, reboot your phone to the bootloader.
11. Once it is in the bootloader, type "fastboot flash recovery TWRP.img" to flash TWRP as your recovery. (I believe this is the point where your warrenty will be invalidated by Huawei, so be careful.)
12. When it finishes flashing TWRP, reboot your phone to TWRP by holding down the power button and volume up
13. It should boot to TWRP. Tap "Keep Read Only", then go to (YOU ARE ABOUT TO WIPE IT AGAIN)Wipe>Format Data and type yes, and hit the enter button.
14. Once it finishes, go to Backup>Select Storage, select your SD card and hit OK, then check every box to backup all six partitions, and swipe to back them up. (At the end, it may seem to get stuck at 98-99%, DO NOT STOP IT! It is generating an MD5 checksum)
15. When it finishes backing everything up, go back to the home screen of TWRP, then go to Install, navigate to where you stored the SuperSU ZIP, select it, then swipe to flash it.
16. When it finishes flashing the SuperSU ZIP, tap "Clear Cache/Dalvik" and swipe to clear them.
17. Reboot your phone. IT WILL REBOOT MULTIBLE TIMES AND APPEAR TO BE STUCK SOMETIMES, BUT DONT TOUCH IT! This is normal and it will eventually boot like normal.
That's it!
Your phone should now be rooted and have SuperSU installed. Please note that this is a Systemless root, and will be removed if you factory reset your phone.Thanks to divineBliss for creating the original instructions.
What do we do after we get root to install custom ROMS? please advise
nedfred0 said:
What do we do after we get root to install custom ROMS? please advise
Click to expand...
Click to collapse
To install a custom ROM, you need the ROM you want to install, gapps depending on the ROM, and the proper firmware. The firmware you are on can be found under about phone and is the last 4 digets of the build number (in the format of B1xx). Once you are on the proper firmware, have your ROM and other things it may require, (every ROM is different), and a backup (just in case), you can flash the ROM from TWRP. Follow the instructions provided by the creator of the ROM to properly flash it.
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
BTJustice said:
Where do you get the USB driver at because I am not seeing it at
Click to expand...
Click to collapse
The drivers come with HiSuite. Download it and you should be good to go.
randomness725 said:
The drivers come with HiSuite. Download it and you should be good to go.
Click to expand...
Click to collapse
Thanks. I tried that but couldn't get it to go so I downloaded these instead which did the job:
https://www.androidfilehost.com/?fid=817550096634745788
does this work on the new h1711 huawei assend xt2
xaneth201 said:
does this work on the new h1711 huawei assend xt2
Click to expand...
Click to collapse
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
bricked 1711
randomness725 said:
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
Click to expand...
Click to collapse
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
You need a copy of the stock H1711 recovery image to use
"fastboot flash recovery H1711-stock-recovery.img" to restore the stock recovery. Until someone creates a working H1711 TWRP, I don't know where you'll find a stock H1711 recovery image file.
scrungydoolittle said:
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
Click to expand...
Click to collapse
download hisuite, enable oem unlocking and usb debbuginig, you gotta also get tha password or the unlocking, denn u run cmd and type:
adb devices
i hope i helped
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
BTJustice said:
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
Click to expand...
Click to collapse
Here is the site for USB drivers for all Huawei models:
http://huaweiadvices.com/download-huawei-usb-drivers/
Good luck....
Does the phone even have a fastboot mode?
RomLord14495 said:
Does the phone even have a fastboot mode?
Click to expand...
Click to collapse
Sure it does
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Click to expand...
Click to collapse
Optionally you put phone into bootloader/fastboot or recovery modes by typing from an adb prompt "reboot bootloader" or "reboot recovery"
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
dominoes20 said:
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
Click to expand...
Click to collapse
You'll have to use DC Unlocker and pay to unlock until the page returns
Since unlocking the bootloader is no longer supported, I have a suggestion but am afraid to try myself.
So, download stock version of rom (aka fastboot rom). Extract, replace recovery.img with twrp (renamed to recovery.img). Restart phone in EDL mode, flash. In theory, edl is working fastboot mode so it shouldn't matter if bootloader is unlocked, correct?
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Imma try this out, I’m stuck in a weird situation where my sd card slot broke. When I sent it in for service, they said it was rooted and refused to fix it. I specifically did not root it so that I could send it in for warranty service. So it’s mission to try and root, unlock boot loader etc so that I can have more storage space
---------- Post added at 11:50 AM ---------- Previous post was at 11:36 AM ----------
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Can you be a little more specific? I didn’t get that info on google
What's needed:
latest Android Pie firmware for Xperia XZ1 (I used 47.2.A.4.41_R4C UK or any version of the 47.2.A.6.30) from XperiFirm
newflasher_v13 tool here
Minimal ADB and Fastboot
TWRP Recovery here
last Magisk.zip here
first copy Magisk.zip to the sd card and insert it into the device
Install TWRP:
launch flashtool and download the latest firmware 47.2.A.4.41_R4C with XperiFirm ....
follow the path C: users / name / .flashTool / firmwares / Download
locate the unzipped firmware, open the folder and delete all the .ta files; then open the boot and partition folders and do the same thing
search the internet or XDA newflasher_v13 tool and place all 7 files in the C: users / name / .flashTool / firmwares / Download / 47.2.A.4.41_R4C folder
connect the device in flash mode
launch the .exe command
press "n" and again "n"
finished the firmware flash unplug the phone
When the first ignition is finished, open the debug and connect the mobile phone to the PC
open the folder Minimal in the path C: Program / Minimal and paste in the folder the recovery.img, run cmd.exe type the following commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery namerecovery.img
fastboot reboot
finished the start of the phone, turn it off and go into recovery mode (volume down + power button)
flash Magisk from the sd
turn on the cell phone and the root is done
Special thanks
oF2pks for the TWRP
munjeni for the newflasher
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
I have pie stock...can i start guide from point 10 ?
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
look at this thread for backup/restore your DRM keys
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
In my experience I can tell you that nothing is lost on the camera neither in the sound effects nor the color effects on the photos ...
ilblago81 said:
I have pie stock...can i start guide from point 10 ?
Click to expand...
Click to collapse
Absolutely yes
From the use I note that the recovery doesn't read the internal data, but only the sd card. I still don't understand if it's the firmware that has bugs or the twrp that still isn't calibrated for Adroid Pie.
Edit: I found in the XDA site the recovery for the new firmwre and everything works fine here
Would this work on SOV36 (AU XZ1)?
sinkoo1979 said:
Would this work on SOV36 (AU XZ1)?
Click to expand...
Click to collapse
Honestly I don't know, but if in your device install the firmware that we install in the g8341 means that you can. I'm thinking it's the same thing!
Sorry, but the requirement is always with unlocked bootloader?Thanks
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
lilbrat said:
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
Click to expand...
Click to collapse
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
dwang040 said:
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
Click to expand...
Click to collapse
What OS is on your computer?
lilbrat said:
What OS is on your computer?
Click to expand...
Click to collapse
Windows 10
dwang040 said:
Windows 10
Click to expand...
Click to collapse
Did you disable the driver verification signature?
(https://www.howtogeek.com/167723/ho....1-so-that-you-can-install-unsigned-drivers/) then reinstall min adb fastboot drivers and Sony companion and let it detect your phone..
chiacla said:
Sorry, but the requirement is always with unlocked bootloader?Thanks
Click to expand...
Click to collapse
you have to unlock the bootloader
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
theflanker said:
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
Click to expand...
Click to collapse
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
theflanker said:
you have to unlock the bootloader
Click to expand...
Click to collapse
He won't be able to unlock his bl till he figures out the issues with his drivers.. whether he uses the ones in flashtool, installs min adb and fastboot drivers or the android sdk..
---------- Post added at 05:34 PM ---------- Previous post was at 05:29 PM ----------
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Once you get your driver's fixed, just follow the directions given by Sony.. Your phone screen will remain black as all info will be done on your computer..
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Absolutely no, flashtool doesn't need to unlock the bootloader, rather serves to re-lock it in some xperia devices. To unlock it you have to use cmd commands in adb & fastboot, but you can find it here in the XZ1 section.
The cell screen remains black and a blue led appears if you connect in fastboot mode, if you connect in flash mode the screen remains black, but a green LED appears.
if you have problems with the recognition of the device on your PC I can link my guide, it's in italian but if you use google translator you understand it well here
arslancn said:
look at this thread for backup/restore your DRM keys
Click to expand...
Click to collapse
I've checked out the thread but it appears only a few with the xz1 have tried it and they didn't report the outcome, well except one who somehow managed to turn his device in an expensive paperweight.. But I will check it out this weekend..
I just received an LG K40 and wanted to root it or potentially install a custom OS.
Unfortunately, it forced me to update upon resetting the device, which locked me out of being able to use mtk-su, the most viable root method. I regained hope upon seeing that I was able to tick "Enable OEM Unlocking" from the developer options, so it would be easy to unlock the bootloader.
For some reason, it seems like LG has completely disabled fastboot mode on this phone. If I hold down volume down and power at boot, I get LG's horrible stripped down recovery which is only a factory reset dialog. If I do the same but with volume up, the phone boots normally. If I hold down volume up with the phone off then plug in USB, I get to LG's download mode which can only be used to flash stock ROMs with their proprietary Windows-only software. With volume down, I get the "low power" screen that I would get if the phone's battery was dead.
These combinations are not documented anywhere and I have compiled them from various random sites and people from all across the web. I have tried many drivers, running adb reboot bootloader (which just reboots back to Android), and every possible combination of keys, but I cannot get to an environment where fastboot can be run.
Does anybody know of a method by which I can unlock the bootloader without using fastboot (OEM unlocking is enabled)? Or at least an alternative root method for this device not involving recovery or fastboot? This is a very tough issue to tackle.
there is a long outdated method to force (hidden) fastboot by erasing LAF partition, but I guess fastboot is meanwhile removed entirely so this would most likely just brick.
however you could try to unlock from mtkclient (should able to by-pass MediaTek Secure Boot)
Code:
python3 mtk da seccfg unlock
Perfect, I was able to unlock the bootloader from download mode with that application and install Magisk from there. Thank you for this!
BenTheTechGuy said:
Perfect, I was able to unlock the bootloader from download mode with that application and install Magisk from there. Thank you for this!
Click to expand...
Click to collapse
Hi!
Can you please explain the steps, as i can't use magisk successfully.
Thanks
Gian-Fr said:
Hi!
Can you please explain the steps, as i can't use magisk successfully.
Thanks
Click to expand...
Click to collapse
The steps are outlined in this section of the README. The only difference is you should use stock Magisk instead of the outdated Chinese fork they used (the changes in that fork have been in upstream Magisk for a while now).
BenTheTechGuy said:
The steps are outlined in this section of the README. The only difference is you should use stock Magisk instead of the outdated Chinese fork they used (the changes in that fork have been in upstream Magisk for a while now).
Click to expand...
Click to collapse
thanks, it works, but when i lock bootloader, it goes bootloop, do you encounter the same problem?
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL