Hi
My friend bought a used Mate 9 MHA-L29 but build number shows NRD90M test-keys. The phone is on Android 7 with EMUI 5.
Is there a way to know the firmware region to flash the correct one. He tried Firmware Finder app but it didn't recognize the phone
Thanks in advance.
Kdachraf said:
Hi
My friend bought a used Mate 9 MHA-L29 but build number shows NRD90M test-keys. The phone is on Android 7 with EMUI 5.
Is there a way to know the firmware region to flash the correct one. He tried Firmware Finder app but it didn't recognize the phone
Thanks in advance.
Click to expand...
Click to collapse
Try with Fastboot.
Install Minimal ADB and Fastbbot to PC (find on XDA).
Enable Settings/System/Developer Options (tap 7 times to Build number in Settings/System/About).
In Developer options enable (in that order)
- Allow ADB debugging in charge only mode
- USB debugging
Connect to PC (wait to install drivers if needed), confirm PC key on the phone screen, run Minimal adb and fastboot
Run the following commands (you can copy commands to *.bat file and run that batch file in Minimal adb and fastboot window):
Code:
adb devices
PAUSE
adb reboot-bootloader
PAUSE
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar rescue_enter_recovery
PAUSE
fastboot reboot
Thanks
The phone is on C900 region, will it be sim locked if I flash the C900 firmware? The phone is from Europe but we live in Africa.
And is it possible to rebrand to C432 firmware without unlocking bootloader?
Kdachraf said:
Thanks
The phone is on C900 region, will it be sim locked if I flash the C900 firmware? The phone is from Europe but we live in Africa.
And is it possible to rebrand to C432 firmware without unlocking bootloader?
Click to expand...
Click to collapse
C900 is some global cust, it must not lock the SIM (to which provider to lock the SIM if that is global cust?) but let someone with c900 confirm about
You cannot rebrand without unlocking Bootloader - rebranding requires flashing and flashing is blocked with the Bootloader locked
zgfg said:
C900 is some global cust, it must not lock the SIM (to which provider to lock the SIM if that is global cust?) but let someone with c900 confirm about
You cannot rebrand without unlocking Bootloader - rebranding requires flashing and flashing is blocked with the Bootloader locked
Click to expand...
Click to collapse
Thanks for the answer
It's true that it says the region is C900 but in the same time the sticker on the phone box says EU which should mean C432, also i've read here on xda that if u flash for example C185 firmware on a C432 phone it will result in C900 and no OTAs.
His vendor information say this Vendor: hw country: normal
So i'm a bit suspicious.
Also even dload method won't work if he try to flash stock firmware with locked bootloader?
Btw he didn't use ur method to verify the region, he sent me a screenshot of version info which says: CVersion:C900 DVersion:Cust so i assumed the region is global.
Kdachraf said:
Thanks for the answer
It's true that it says the region is C900 but in the same time the sticker on the phone box says EU which should mean C432, also i've read here on xda that if u flash for example C185 firmware on a C432 phone it will result in C900 and no OTAs.
His vendor information say this Vendor: hw country: normal
So i'm a bit suspicious.
Also even dload method won't work if he try to flash stock firmware with locked bootloader?
Click to expand...
Click to collapse
Any flashing by fastboot requires unlocked bootloader, dload does not require
But flashing by dload another cust may results in brick, or in the 'better' case with test keys (like you have)
What is written on the box corresponds to which firmware (cust) was originally installed by Huawei.
Once the phone was rebranded (that is why rehranding does) you can forget what the phone was originally, then the phone has new vendor, oeminfo - this is why I asked you to check by fastboot what the phone declares about its current/last firmware (it can be read even on the bricked phones if they can boot to fastboot, and then it can help for unbricking)
Project menu, Vendor hw means that SIM is not locked, it's not about firmware cust
zgfg said:
Any flashing by fastboot requires unlocked bootloader, dload does not require
But flashing by dload another cust results in brick, or in the 'better' case with test keys (like you have)
What is written on the box corresponds to which firmware (cust) was originally installed by Huawei.
Once the phone was rebranded (that is why rehranding does) you can forget what the phone was originally, then the phone has new vendor, oeminfo - this is why I asked you to check by fastboot what the phone declares about its current/last firmware (it can be read even on the bricked phones if they can boot to fastboot, and then it can help for unbricking)
Click to expand...
Click to collapse
Everything is clear now, i'll ask him to check by fastboot, the phone is used and don't know what the original user did to it.
So he check by fastboot and this is what he got
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot-bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) MHA-L29
OKAY [ 0.017s]
finished. total time: 0.017s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/normal
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :NRD90M test-keys
OKAY [ 0.017s]
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29C652B109
OKAY [ 0.018s]
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar rescue_enter_recovery
(bootloader) This is sec phone! !
(bootloader) NOT secboot recovery image!
getvar:rescue_enter_recovery FAILED (remote: FAIL:verify secure image fail!)
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
I see C652, I can't find a firmware for it? Is that the correct region
Or is there another way to fix it? He is on android 7 now.
Kdachraf said:
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :NRD90M test-keys
OKAY [ 0.017s]
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29C652B109
OKAY [ 0.018s]
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar rescue_enter_recovery
(bootloader) This is sec phone! !
(bootloader) NOT secboot recovery image!
getvar:rescue_enter_recovery FAILED (remote: FAIL:verify secure image fail!)
finished. total time: 0.033s
Click to expand...
Click to collapse
Im a bit suspicious about "NOT secboot recovery image!" but this must be all about the improper flashing resulting also with Test-keys
Kdachraf said:
I see C652, I can't find a firmware for it? Is that the correct region
Or is there another way to fix it? He is on android 7 now.
Click to expand...
Click to collapse
Use Firmware Fonder (install from Playstore) and choose Add Model and enter MHA-L29c652 (see screenshot)
However, your b109 (Nougat) is old, I cannot see there any firmware older than b158 Pie 9.01
Kdachraf said:
Hi
My friend bought a used Mate 9 MHA-L29 but build number shows NRD90M test-keys. The phone is on Android 7 with EMUI 5...
Click to expand...
Click to collapse
You are (your friend) lucky - with Nougat you can instantly and only for 4-5 $ buy the Bootloader key - when contacting them, emphasize that phone is still on Nougat MHA-L29c652b109:
https://ministryofsolutions.com/paid-services/amp
https://www.dc-unlocker.com/
Actually, you can also (up to 20 $ or so) ask them for help/tools to install proper firmware, to get rid of Test-keys
Once you upgrade to Oreo (EMUI 8, Security patch Mar 2018 or newer) or even Pie (EMUI 9), obtaining Bootloader code is much more costly (45+ $) and you need to wait for a month or more.
However, BL code is unique for the lifetime of the phone and you can always (re)use it for relocking/unlocking no matter if you rebrand, upgrade, etc
Once you will have the BL code, you can follow the guides on this XDA Mate 9 subforum to rebrand to c432 and upgrade to the latest Pie 9.01 or even 9.1 (although, you can also read on this subforum that video stabilization and night photos were much better with Nougat and Oreo; to the other side, battery longs laster with Oreo or Pie, there are also other differences pro & contra)
Thanks a lot my friend
I searched on xda and found that C652 can mean demo firmware, maybe the original user tried to flash C432 firmware which resulted in test-keys.
So basically DC unlock will generate the bootloader code and then rebrand to C432 region. I'll ask him to take it to a repair store for the code since we don't live in the same city. And assist him with the rebrand.
Thanks again my friend
Kdachraf said:
Thanks a lot my friend
I searched on xda and found that C652 can mean demo firmware, maybe the original user tried to flash C432 firmware which resulted in test-keys.
So basically DC unlock will generate the bootloader code and then rebrand to C432 region. I'll ask him to take it to a repair store for the code since we don't live in the same city. And assist him with the rebrand.
Thanks again my friend
Click to expand...
Click to collapse
With DC, you need to buy credits in advance - so ask them and discuss with them if you/your friend want only the BL code or also 'unbricking' from Test-keys (you can give them Fastboot results and make a screenshot from Settings/About), and/or rebranding to c432
Then you don't need Huawei repair shop (?), and with DC you only communicate online, they provide you tools and assist
If taking Ministry, they want to remote connect to your PC by TeamViewer to do themselves (they are also little cheaper) - present them also Fastboot queries and About screenshot
zgfg said:
With DC, you need to buy credits in advance - so ask them and discuss with them if you/your friend want only the BL code or also 'unbricking' from Test-keys (you can give them Fastboot results and make a screenshot from Settings/About), and/or rebranding to c432
Then you don't need Huawei repair shop (?), and with DC you only communicate online, they provide you tools and assist
If taking Ministry, they want to remote connect to your PC by TeamViewer to do themselves (they are also little cheaper) - present them also Fastboot queries and About screenshot
Click to expand...
Click to collapse
That's the problem, in my country u can't buy credit or services online from the outside unless u go to black market and generally repair stores have access to these tools.
Related
Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..
YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.
zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.
Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:
lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s
That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Im have the same issue but I have no recovery installed..Anyway to do this
i have same issue plz give me any solution if you found any???plz let me know plzzzzz
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?
Any ideas guys?
aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.
Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed
NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
Install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Hmmm ill help you with your answer if u can get help for me with mine
Zaq1xsw222 said:
Hmmm ill help you with your answer if u can get help for me with mine
Click to expand...
Click to collapse
So help me and give me your answer, let me see if i can help you
CheckS86 said:
So help me and give me your answer, let me see if i can help you
Click to expand...
Click to collapse
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Zaq1xsw222 said:
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Click to expand...
Click to collapse
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
CheckS86 said:
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
Click to expand...
Click to collapse
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Zaq1xsw222 said:
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Click to expand...
Click to collapse
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
CheckS86 said:
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
Click to expand...
Click to collapse
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Ok now its your turn
Zaq1xsw222 said:
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Click to expand...
Click to collapse
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
CheckS86 said:
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
Click to expand...
Click to collapse
Have you tried to restart your phone in safety mode?
Zaq1xsw222 said:
Have you tried to restart your phone in safety mode?
Click to expand...
Click to collapse
It doesn't work, this just led me to de begining too.
The phone can't start, so maybe re-install his firmware is the best option. I already search the firmware for this phone (to try flash it with SP Flashtool), even here in XDA there is an RUU Collection for this phone, but none of them is compatible with mine. This is the firmware compatible:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip
but is only available to buy... here for example:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip | Easy Firmware
easy-firmware.com
IDK why this firmware is not in other pages .
Reinstall stock firmware so you can boot into system. Then follow instructions to unlock with unlock code
hi, name's Josh, i was trying to downgrade my moto g8 plus, but i had this issue with "please lock bootloader" loop so i tried locking it, but now i cannot even pass from bootloader:
"no booteable A/B slot
failed to boot linux, falling back to fastboot
fastboot reason: Fall-through from normal boot mode"
i've tried to fix it with the rescue and smart assistant but it keeps failing, i also tried flashing it with fastboot but i get the message "failed to identify current slot", when i try to "--set-active=a" it shows (either for b):
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.172s
And when i type "fastboot getvar current-slot" i get this:
current-slot:
finished. total time: 0.064s
I don't really know what to do now, even recovery mode won't prompt, it just restarts bootloader, does anyone have a solution for this? i never had this kind of issue with samsung devices, this is my first motorola and since i bought it i had problems with touch being laggy so i was trying to downgrade android 10 to 9 but i was unable, and now i can't even use it at all, i would really apreciate if somebody could help me, in advance thanks for your time and attention
Can you unlock the bootloader again?
gfrank227 said:
Can you unlock the bootloader again?
Click to expand...
Click to collapse
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
darkhonor said:
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
Click to expand...
Click to collapse
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
gfrank227 said:
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
Click to expand...
Click to collapse
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
gfrank227 said:
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
Click to expand...
Click to collapse
ok so i tried to blankflash it but i got this error i guess is time to say goodbye jajaj
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM7
[ 0.005] Detecting device
[ 34.666] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.666] Check qboot_log.txt for more details
[ 34.666] Total time: 34.668s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
CodyF86 said:
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
Click to expand...
Click to collapse
well im uncertain of how that is made, i just followed up a tutorial , downloaded official firmware and flashed it with fastboot comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
and yeah i tried flashing the newest official firmware that rescue and smart assistant showed, but since i cannot determine slot it says "failed to identify current slot"
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
CodyF86 said:
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
Click to expand...
Click to collapse
So there's no other way to fix it?