Hi, Please i really need help unlocking my device (Gionee S10 lite) Bootloader.
I have enabled both "OEM unlocking" and "USB debugging" in developers settings, CMD detects my device in fastboot,
but when the "fastboot oem unlock" or "fastboot flashing unlock" is run, it says OEM unlock is not available.
Kindly the image below;
https://i.postimg.cc/W1HLGVny/image.png
please help? :crying:
samm14 said:
Hi, Please i really need help unlocking my device (Gionee S10 lite) Bootloader.
I have enabled both "OEM unlocking" and "USB debugging" in developers settings, CMD detects my device in fastboot,
but when the "fastboot oem unlock" or "fastboot flashing unlock" is run, it says OEM unlock is not available.
Kindly the image below;
https://i.postimg.cc/W1HLGVny/image.png
please help? :crying:
Click to expand...
Click to collapse
Well it's really hard to say what's wrong in this case because I've never encountered such a problem.
Your USB and Fastboot drivers are fine since your PC detects your phone, so I really don't know what's wrong in this case.
Maybe try to turn the phone back on, disable then re-enable OEM unlocking, and retry to unlock the phone.
In case the files are faulty (which might be the case), here's a guide with (apparently) working files. This outside of XDA though : https://romprovider.com/gionee-s10-lite-root/
Hope that help
Try out Zykuflasher to unlock bootloader on gionee devices
RaiZProduction said:
Well it's really hard to say what's wrong in this case because I've never encountered such a problem.
Your USB and Fastboot drivers are fine since your PC detects your phone, so I really don't know what's wrong in this case.
Maybe try to turn the phone back on, disable then re-enable OEM unlocking, and retry to unlock the phone.
In case the files are faulty (which might be the case), here's a guide with (apparently) working files. This outside of XDA though : https://romprovider.com/gionee-s10-lite-root/
Hope that help
Click to expand...
Click to collapse
Maybe try to turn the phone back on, disable then re-enable OEM unlocking, and retry to unlock the phone.
Click to expand...
Click to collapse
I've done this several times, it same thing
Here's what i got from XN Rootkit
https://i.postimg.cc/ncshBg0r/image.png
xSil3nt said:
Try out Zykuflasher to unlock bootloader on gionee devices
Click to expand...
Click to collapse
Help with link please.
I can't download it from their site
RaiZProduction said:
Well it's really hard to say what's wrong in this case because I've never encountered such a problem.
Your USB and Fastboot drivers are fine since your PC detects your phone, so I really don't know what's wrong in this case.
Maybe try to turn the phone back on, disable then re-enable OEM unlocking, and retry to unlock the phone.
In case the files are faulty (which might be the case), here's a guide with (apparently) working files. This outside of XDA though : https://romprovider.com/gionee-s10-lite-root/
Hope that help
Click to expand...
Click to collapse
i await you sir, i have replied you above
To help you help me further i tried all of these from someone who's also trying to help
https://postimg.cc/1gxSY9kT
https://postimg.cc/9wHWmVD2
https://postimg.cc/RWKDmj21
https://postimg.cc/vg1P8hKJ
samm14 said:
i await you sir, i have replied you above
To help you help me further i tried all of these from someone who's also trying to help
https://postimg.cc/1gxSY9kT
https://postimg.cc/9wHWmVD2
https://postimg.cc/RWKDmj21
https://postimg.cc/vg1P8hKJ
Click to expand...
Click to collapse
Thanks for the screenshots, I took a look at them.
So first of all make a little test:
- enable OEM Unlock
- reboot to fastboot mode
- when you're in fastboot, reboot to system and check if the OEM Unlock option in dev settings is still enable.
If it is it's very confusing, if it's not you might wanna look on the web why your device does that.
Also try to don't touch your phone while rebooting to fastboot, by that I mean once you enable OEM Unlock on dev setting:
- plug your phone to your computer
- see if OEM unlocking is still enabled, maybe connecting to a PC makes it disappear (if it disappeared re-enable it)
- now check if adb and fastboot recognize your device (command: adb devices, fastboot devices)
- If they are recognized enter the command "adb reboot bootloader"
- Now check if fastboot recognizes your device
- if it does enter "fastboot oem unlock"
- see if it works
If despite all of this you can't solve this issue, I would be able to help you any further, hope this works!
PS: you seem pretty new to xda so please take time to read the rules, and press the thank button each time someone helps you (or give you any guidance). Have a good one
RaiZProduction said:
Thanks for the screenshots, I took a look at them.
So first of all make a little test:
- enable OEM Unlock
- reboot to fastboot mode
- when you're in fastboot, reboot to system and check if the OEM Unlock option in dev settings is still enable.
If it is it's very confusing, if it's not you might wanna look on the web why your device does that.
Also try to don't touch your phone while rebooting to fastboot, by that I mean once you enable OEM Unlock on dev setting:
- plug your phone to your computer
- see if OEM unlocking is still enabled, maybe connecting to a PC makes it disappear (if it disappeared re-enable it)
- now check if adb and fastboot recognize your device (command: adb devices, fastboot devices)
- If they are recognized enter the command "adb reboot bootloader"
- Now check if fastboot recognizes your device
- if it does enter "fastboot oem unlock"
- see if it works
If despite all of this you can't solve this issue, I would be able to help you any further, hope this works!
PS: you seem pretty new to xda so please take time to read the rules, and press the thank button each time someone helps you (or give you any guidance). Have a good one
Click to expand...
Click to collapse
I've done this severally, i did it again because you asked me to and it same. https://postimg.cc/xN0MH8pG
PS: you seem pretty new to xda so please take time to read the rules, and press the thank button each time someone helps you (or give you any guidance). Have a good one
Click to expand...
Click to collapse
Yes i am, Thanks for the guidiance and noted.
I guess i just have to accept my fate. Thanks alot for your time.
samm14 said:
i await you sir, i have replied you above
To help you help me further i tried all of these from someone who's also trying to help
https://postimg.cc/1gxSY9kT
https://postimg.cc/9wHWmVD2
https://postimg.cc/RWKDmj21
https://postimg.cc/vg1P8hKJ
Click to expand...
Click to collapse
Hi there, just one last thing.
Maybe try to uninstall and reinstall USB drivers and change the USB cable. It's very unlikely they're the problem, but maybe, we never know.
Good luck
RaiZProduction said:
Hi there, just one last thing.
Maybe try to uninstall and reinstall USB drivers and change the USB cable. It's very unlikely they're the problem, but maybe, we never know.
Good luck
Click to expand...
Click to collapse
It same but thanks for your effort
Use kryton_toolkitDemo mtk universal by Romadd.com to unlock the bootloader or try using miracle box v2.82 use custom settings and choose model make sure you tick it boot your phone into fastboot mode and connect... U can also use da file method...if u need let me know but first try the first 1.
Related
My phone is stuck on bootloop. I have cyanogenmod 13 installed on my moto g 3rd gen(2015). I can't seem to get into my system recovery either, which is now twrp and it just shows the logo for twrp recovery. I also for some dumb reason disabled my usb debugging mode, so i can't flash my phone either. Help plzz
Maybe go to bootloader and reflash TWRP
minimale_ldz said:
Maybe go to bootloader and reflash TWRP
Click to expand...
Click to collapse
Doesn't work, can't connect to bootloader
znyght said:
Doesn't work, can't connect to bootloader
Click to expand...
Click to collapse
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
minimale_ldz said:
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
Click to expand...
Click to collapse
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
znyght said:
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
Click to expand...
Click to collapse
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
http://forum.xda-developers.com/showthread.php?p=48915118
and if it doesn't install correct drivers for you, you can get them here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
first thing to do is check what fastboot returns after this command:
Code:
fastboot devices
if it shows your device ID you're good to go
I'd suggest downloading stock firmware first and flashing it before messing with custom recovery. Just remember Motorola often updates bootloader with new firmware so don't flash anything older than you had on your phone before.
Good luck
EDIT: you can also use RSD Lite to flash a new software, it basically automates fastbooting proccess, so theres no risk of misspelling or doing other stuff wrong
EDIT2: firmware is here:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
also, the OP (lost101) is a great, helpful guy who may give you some advice if you need
Thanks I'll give them a try
Originally Posted by minimale_ldz
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
Click to expand...
Click to collapse
I've tried these but they didn't seem to work
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 tried to do it my self. follow an instruction from a official website and other
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
https://www.getdroidtips.com/how-to...-plus-i3213-i4213-i4293-i3223/#Pre-Requisites
which i got stuck at, when i boot into bootloader mode . the phone seem to restart and appear only black screen with blue indicator.
then i tried to check if it still connect to adb or not, with {adb devices} its not listed there
PS.
-the drivers work fine
-my Xperia 10 plus model is I4293
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Zaben said:
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Click to expand...
Click to collapse
one thing weird
i using a Xperia Tool (Xperia Companion) and it display the text that my phone need to unlock the screen or allow to use data tranfer
which i already check a USB debugging to be on, and every time i connect it to my PC, it still ask me a permission to be allow or not
maybe this is a problem here ?
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Haxk20 said:
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Click to expand...
Click to collapse
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
ZimpleThing said:
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
Click to expand...
Click to collapse
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Haxk20 said:
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Click to expand...
Click to collapse
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
ZimpleThing said:
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
Click to expand...
Click to collapse
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Haxk20 said:
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Click to expand...
Click to collapse
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
ZimpleThing said:
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
Click to expand...
Click to collapse
There is a thanks button. Hit it instead of saying it.
Haxk20 said:
There is a thanks button. Hit it instead of saying it.
Click to expand...
Click to collapse
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Glad I could help
I know its been a long time but maybe someone can help me.
I can get into the bootloader but when I trie to use the unlock code, mentioned above, and the sony unlock key it always says waiting for device but nothing happens. Any clue?
Edit fixed the Problem
Xperia 10 plus stuck on waiting for device
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
I was using windows 10. From what I can remember, my problem is that I didn't install driver correctly (I'm not sure which one). I am not really sure if this fastboot driver the one I used. I saw my device in Device Manager, but I got waiting on device... just like you. So what I have done was locate my device in Device Manager and install the sony driver over that device. If sony's driver was not the correct one, then it was another driver that I can't remember, but the instruction still the same. Sorry for an unclear message, but I can barely remember anything now.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
Go in Windows Device Manager and check the device . If needed install drivers manually
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
I have a Samsung Galaxy A5 2017 (SM-A520F/a5y17lte/android 8.0.0 oreo) but I cannot install TWRP on it. I tried many methods but its not letting me to do it:
-unlock bootloader /failed
-OEM unlock in dev options /hidden and cannot access/failed
-flash stock rom to unlock OEM /failed
-root phone with adb /no fastboot access /failed
-root phone with Odin /failed
-flashing TWRP with adb /no fastboot access/failed
-flashing twrp with odin /"only official binaries are allowed to be flashed" error message in download mode /failed
-uding heimdall (wtf is this program ive never heard it b4) /failed
Anyone got solution to install TWRP ? So i can flash to android 9 and also root my phone. Thank you if you suggest any solution that actually works.
ItsSuperPlayz said:
I have a Samsung Galaxy A5 2017 (SM-A520F/a5y17lte/android 8.0.0 oreo) but I cannot install TWRP on it. I tried many methods but its not letting me to do it:
-unlock bootloader /failed
-OEM unlock in dev options /hidden and cannot access/failed
-flash stock rom to unlock OEM /failed
-root phone with adb /no fastboot access /failed
-root phone with Odin /failed
-flashing TWRP with adb /no fastboot access/failed
-flashing twrp with odin /"only official binaries are allowed to be flashed" error message in download mode /failed
-uding heimdall (wtf is this program ive never heard it b4) /failed
Anyone got solution to install TWRP ? So i can flash to android 9 and also root my phone. Thank you if you suggest any solution that actually works.
Click to expand...
Click to collapse
Hello and good afternoon, @ItsSuperPlayz
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
First you have to access developer mode. You have to tap several times on the build number. (Settings/about the phone) In developer mode you heve to enable oem unlocking and usb debugging. Wait for permission request on the phone for access of your PC when attached to the phone.
Next step is to unlock the bootloader.
After this you will be able to install TWRP, which finally gets you to the point where you can install a new ROM. Just follow step by step:
Install LineageOS on a5y17lte | LineageOS Wiki
wiki.lineageos.org
Of course, instead of Lineage, you can use any suitable ROM
chrysopra said:
First you have to access developer mode. You have to tap several times on the build number. (Settings/about the phone) In developer mode you heve to enable oem unlocking and usb debugging. Wait for permission request on the phone for access of your PC when attached to the phone.
Next step is to unlock the bootloader.
After this you will be able to install TWRP, which finally gets you to the point where you can install a new ROM. Just follow step by step:
Install LineageOS on a5y17lte | LineageOS Wiki
wiki.lineageos.org
Of course, instead of Lineage, you can use any suitable ROM
Click to expand...
Click to collapse
Thank you for replying but as I said above i cannot unlock bootloader in any way i tried. So maybe can u find another solution? (Note: i tried following the link u send me and its not working)
How far did you get? OEM unlocking and usb debugging successful?
When putting your phone in fastboot mode and attaching it to the pc, check with "adb devices", if your phone is properly recognised. Using windows, it´s often the drivers. On my system, I had to manually select the ADB driver, since I got no connection before.
chrysopra said:
How far did you get? OEM unlocking and usb debugging successful?
When putting your phone in fastboot mode and attaching it to the pc, check with "adb devices", if your phone is properly recognised. Using windows, it´s often the drivers. On my system, I had to manually select the ADB driver, since I got no connection before.
Click to expand...
Click to collapse
thanks for replying again
i tried to oem unlocking and usb debugging but unsucessful
furthermore my pc cant even recognise my phone when i turn on usb debugging or change the usb to media transfer protocol (mtp) mode after i flash stock firmware (it worked before i flash the firmware)
how am i gonna install anything if my pc cant even recognise my phone????
(ps: your question "how far did you get" my answer is i cant flash any mods or unlock anything. bootloader locked.)
Can you see the "developer options" in settings/system when scrolling down ? If not, then:
How to access developer options in Android
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. ...
Step 4: Once developer options are activated, you will see a message that reads, You are now a developer.
Within developer options there are options to enable usb debugging and oem unlock. I recently did this on a Galaxy tab and saw..nothing.
First I had to establish a network connection to my wifi base. Weird, but this brought those wanted menu items...
For further connection, check your computer drivers. Both the manufacturers usb drivers and adb driver are necessary. While connected to a PC, check, if you´re on Windows, the device manager, if the proper driver is chosen.
chrysopra said:
Can you see the "developer options" in settings/system when scrolling down ? If not, then:
How to access developer options in Android
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. ...
Step 4: Once developer options are activated, you will see a message that reads, You are now a developer.
Within developer options there are options to enable usb debugging and oem unlock. I recently did this on a Galaxy tab and saw..nothing.
First I had to establish a network connection to my wifi base. Weird, but this brought those wanted menu items...
For further connection, check your computer drivers. Both the manufacturers usb drivers and adb driver are necessary. While connected to a PC, check, if you´re on Windows, the device manager, if the proper driver is chosen.
Click to expand...
Click to collapse
I see the developer options and the usb debugging switch
But there are 2 problems
1. My pc running windows 10 cannot detect my device (like showing it as a disk so i can copy files to )
2. In developer setting there is no OEM unlock option, which is weird. I triee many solutions but cannot get acess to OEM unlock. I even tried to unlock it with ADB ut its useless since my phone cant even access fastboot mode.(download mode is considered to be fastboot but ADB wont recognise my phone)
*why are you putting so much effort replying me*
*also drivers seem to be down*
As for the drivers, you could try:
Samsung Galaxy A5 (2017) USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
As for the OEM unlocking, Samsung seems to be tricky:
How to Fix Missing OEM Unlock in Developer Options on Samsung
Are you looking for the OEM Unlock in developer options but couldn't find it? Here's how to fix missing OEM unlock in developer options.
www.ytechb.com
or:
How to fix the missing OEM unlock in developer options on Samsung devices - KrispiTech
There are different methods available to fix the missing OEM unlock in developer options on Samsung devices. By using this option, you will
krispitech.com
ItsSuperPlayz said:
*why are you putting so much effort replying me*
Click to expand...
Click to collapse
Maybe I´m a reincarnation of genghis khan, trying to earn some good karma...
chrysopra said:
As for the drivers, you could try:
Samsung Galaxy A5 (2017) USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
As for the OEM unlocking, Samsung seems to be tricky:
How to Fix Missing OEM Unlock in Developer Options on Samsung
Are you looking for the OEM Unlock in developer options but couldn't find it? Here's how to fix missing OEM unlock in developer options.
www.ytechb.com
or:
How to fix the missing OEM unlock in developer options on Samsung devices - KrispiTech
There are different methods available to fix the missing OEM unlock in developer options on Samsung devices. By using this option, you will
krispitech.com
Maybe I´m a reincarnation of genghis khan, trying to earn some good karma...
Click to expand...
Click to collapse
heimdall finally recognise my phone but whenever i try to flash twrp.img it says
"Only official binaries are allowed to be flashed(RECOVERY)" (the phone itself) HELP!!!!
*good karma +1*
On any other device, you would have enjoyed your new TWRP since several days. But Samsung is eager to build as many hurdles as possible, to prevent changing the original software. They invented "KnoxGuard" to "protect" the phone. In your case, it´s aprotection against it´s owner
The error message means, that your phone isn´t successfully unlocked.
Try this:
"FIXED IT!!
The time trick actually worked.
All I had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!"
The following Link may also be of interest:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
chrysopra said:
On any other device, you would have enjoyed your new TWRP since several days. But Samsung is eager to build as many hurdles as possible, to prevent changing the original software. They invented "KnoxGuard" to "protect" the phone. In your case, it´s aprotection against it´s owner
The error message means, that your phone isn´t successfully unlocked.
Try this:
"FIXED IT!!
The time trick actually worked.
All I had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!"
The following Link may also be of interest:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
Click to expand...
Click to collapse
Sorry to say this but the method is useless. Its never gonna work.
Perhaps this (long) Thread may be helpful:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com