It all started with an error while in B330 oreo, try to install the latest version b343, and by mistake place the firmware of b151 naugat in the folder of HWOTA, without realizing I slipped in twrp and stayed in the logo, it was impossible to revive it by fastboot , the partitions had been totally erased, a technician revived it with a dongle box, installing everything from scratch. I am in b151 naugat and the boot manager unlocked but I got the OTA b343 Oreo and proceeded to install it, I tried to unlock the bootloader but it is impossible for me FRP UNLOCK, PHONE RELOCKED, try fastboot and ERROR FAILED, I wanted to get back the unlock code in DC_UNLOCKER and it is not possible so I am in B343 OREO, today return to NAUGAT by HISHUITE already being in b151 proceeded to unblock it with the code that did it before and the same error was failed and follows the RELOCKED boot manager, but not LOCK, even though it is a new firmware.
Forgive my English, use google translator.
Thank you
geregamboa said:
It all started with an error while in B330 oreo, try to install the latest version b343, and by mistake place the firmware of b151 naugat in the folder of HWOTA, without realizing I slipped in twrp and stayed in the logo, it was impossible to revive it by fastboot , the partitions had been totally erased, a technician revived it with a dongle box, installing everything from scratch. I am in b151 naugat and the boot manager unlocked but I got the OTA b343 Oreo and proceeded to install it, I tried to unlock the bootloader but it is impossible for me FRP UNLOCK, PHONE RELOCKED, try fastboot and ERROR FAILED, I wanted to get back the unlock code in DC_UNLOCKER and it is not possible so I am in B343 OREO, today return to NAUGAT by HISHUITE already being in b151 proceeded to unblock it with the code that did it before and the same error was failed and follows the RELOCKED boot manager, but not LOCK, even though it is a new firmware.
Forgive my English, use google translator.
Thank you
Click to expand...
Click to collapse
try this HWOTA link
Friend, that's the problem I could not unlock the bootloader, I already rollback by hishuite I'm naugat b151, but I can not get it to unlock, that's my concern
geregamboa said:
Friend, that's the problem I could not unlock the bootloader, I already rollback by hishuite I'm naugat b151, but I can not get it to unlock, that's my concern
Click to expand...
Click to collapse
you should know your unlock code and unlock again your bootloader.
Wrong forum
geregamboa said:
It all started with an error while in B330 oreo, try to install the latest version b343, and by mistake place the firmware of b151 naugat in the folder of HWOTA, without realizing I slipped in twrp and stayed in the logo, it was impossible to revive it by fastboot , the partitions had been totally erased, a technician revived it with a dongle box, installing everything from scratch. I am in b151 naugat and the boot manager unlocked but I got the OTA b343 Oreo and proceeded to install it, I tried to unlock the bootloader but it is impossible for me FRP UNLOCK, PHONE RELOCKED, try fastboot and ERROR FAILED, I wanted to get back the unlock code in DC_UNLOCKER and it is not possible so I am in B343 OREO, today return to NAUGAT by HISHUITE already being in b151 proceeded to unblock it with the code that did it before and the same error was failed and follows the RELOCKED boot manager, but not LOCK, even though it is a new firmware.
Forgive my English, use google translator.
Thank you
Click to expand...
Click to collapse
I think you are in the wrong forum, the mate 10 never came with nougat, this forum is just for the mate 10, so I would suggest that you search for the right forum and ask there.
revjamescarver said:
I think you are in the wrong forum, the mate 10 never came with nougat, this forum is just for the mate 10, so I would suggest that you search for the right forum and ask there.
Click to expand...
Click to collapse
Mate 10 lite came with nougat
The at&t version from México originally come with Android 7.1 NOUGAT in the versión C121B100
Si many latinoamerica versions has the same version.
Fot the relock problem you must do the same ateos for unlock, but you have to wait 7 o 14 says, i don't remember, but after that you should be able to reunlock your Huawei with the same code because it's the same serial number.
Wrong forum
GiuseppeAguilar said:
Mate 10 lite came with nougat
The at&t version from México originally come with Android 7.1 NOUGAT in the versión C121B100
Si many latinoamerica versions has the same version.
Fot the relock problem you must do the same ateos for unlock, but you have to wait 7 o 14 says, i don't remember, but after that you should be able to reunlock your Huawei with the same code because it's the same serial number.
Click to expand...
Click to collapse
I still think you're in the wrong place, haven't seen anything here even remotely connected to the lite version of the mate 10, I'd search and see if there is a forum for that phone. You should be able to unlock the phone again, unless of course there motherboard was changed (that hooking up to a dongle story by the technician is kind of suspicious as the hardware to do that repair is not a dongle and is very expensive)
I managed to unlock using dc-unlocker but I generated the same unlock number I already had, the strangest thing was that I paste and copy and unlock. I am confused because the codes are the same and with the first one it does not let unblock and with the second code if, in order and I already achieved what I wanted to thank you all.
Related
Hi all
I searched this, but I question here,
1 - When you unroot , put stock and update an ota, it blocks the bootloader?
2 - and the when unlocked, format all to factory?
3 - In what moment the bootloader is blocked? only when first unlock is done?
Thanks in advance, I have an honor 7 and I Know how it works, but this honor 8 L09?
1. probably
2. u can prevent factory reset if unlocked earlier
3. idk what the question means
LastStandingDroid said:
1. probably
2. u can prevent factory reset if unlocked earlier
3. idk what the question means
Click to expand...
Click to collapse
3 - well, the main question is if in every ota update , it locks the boootloader and when unlock, format all ...this is the main question
in honor 7, I unroot, apply the ota and root again with no problems
sorry for my english
deadko said:
3 - well, the main question is if in every ota update , it locks the boootloader and when unlock, format all ...this is the main question
in honor 7, I unroot, apply the ota and root again with no problems
sorry for my english
Click to expand...
Click to collapse
lock bootloader i can't tell, if it does u can unlock the bootloader and again, and straight after flash TWRP it won't wipe the internal SD
Hi. bought an al-10 from china which apparently is flashed. There are a few things not working on phone so apart from trying to get help from seller, i have attempted the flashing myself. i have gone thru a few threads and watched TK vid on flashing twrp and rooting and roni on unlocking bootloader. now, considering the device is flashed i understand the bootloader is still unlocked (in fastboot says phone unlocked). in dev options there is no OEM unlocking option. i cannot get lock state through the code in dialler. when i try to flash twrp, sending recovery OKAY, writing recovery FAILED <remote: command not allowed> so cannot really get to rooting stage
Thank you for the time.
ptwarecki said:
Hi. bought an al-10 from china which apparently is flashed. There are a few things not working on phone so apart from trying to get help from seller, i have attempted the flashing myself. i have gone thru a few threads and watched TK vid on flashing twrp and rooting and roni on unlocking bootloader. now, considering the device is flashed i understand the bootloader is still unlocked (in fastboot says phone unlocked). in dev options there is no OEM unlocking option. i cannot get lock state through the code in dialler. when i try to flash twrp, sending recovery OKAY, writing recovery FAILED <remote: command not allowed> so cannot really get to rooting stage
Thank you for the time.
Click to expand...
Click to collapse
And the device is? Did u use fastboot flash recovery recovery.img
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
And the device is? Did u use fastboot flash recovery recovery.img
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Hi.
Sorry device is honor 8 frd-al10.
It was fastboot flash recovery twrp_cn.img
I have just received a message from seller stating it was flashed with eu firmware. I have it as frd c900b120. Should i be using the image for FRD-L09 or FRD-L19 in this case ?
Thank you.
Hello, I debranded my phone, so I'm running L21C432B130 at the moment, but when turning it on it displays the you're unlocked and can't be trusted message in Red, before it was in orange, it doesn't bother me, but once I found out I can't update to B160 via OTA, I freaked lol... Is there a way to get that OTA to work, or something?
Could you please explain, how you debranded the phone?
Acoca said:
Hello, I debranded my phone, so I'm running L21C432B130 at the moment, but when turning it on it displays the you're unlocked and can't be trusted message in Red, before it was in orange, it doesn't bother me, but once I found out I can't update to B160 via OTA, I freaked lol... Is there a way to get that OTA to work, or something?
Click to expand...
Click to collapse
Hi,
i have the same issue since 2 Weeks. Thats not the only thing, i got the massage : "Verfication failed, cant be trusted"
Phone: L31 C436 B336 SingleSim -> Debranded from T-Mobile with EUROPE TOOL from "Sebastian"
I think its a problem with the OEM Info
I Tried:
1. Flash Stock with TWRP, ERecovery -> Failed, adb and dload methode -> MM 6.0
2. Flash on b336 with TWRP, E-Recovery -> Failed, adb and dload
Normal Recovery and Erecovery didn't worked on b336, b130 only message i get is: Failed with a !
Didn't tryed to flash the OEM because in the Forums some guys says the OEM's are Specific some guys says its not Specific didn't know which i trust.
Debrand method:
get the EUROPE Tool and flashed the Singlesim OEM L31 then flashed stock b130. Since i did that i get the issues. (bootloader was unlocked)
My Phone is atm at b336 with TWRP from Nougat not rooted and bootloader unlocked
I debranded my phone using the huawei tool, can't remember the name but it wasn't the green one that opens in cmd, it literally a program
I think it's a normal message since you modified the system. Try updating to a stock firmware so that you relock the bootloader, you should be able to get rid of that message
Acoca said:
Hello, I debranded my phone, so I'm running L21C432B130 at the moment, but when turning it on it displays the you're unlocked and can't be trusted message in Red, before it was in orange, it doesn't bother me, but once I found out I can't update to B160 via OTA, I freaked lol... Is there a way to get that OTA to work, or something?
Click to expand...
Click to collapse
After downgrade to mm that message gone but in fastboot say my bootloader is unlock..so that mean that message no make diference in bootloader status right??
Someone???
I can't upgrade via OTA, it won't let me... I'm thinking maybe installing meticulus TWRP and doing a system dump may help, I wipe the whole system and just restore the dump?
Anyone have an idea?
Hi, i have a big problem: my phone isn't starting up anymore. Before bricking my device, i was in b160(VNS L-21), then i decided to upgrade to Nougat. So i unlocked bootloader, flashed twrp etc.. Finally i got N working, after that i flashed Revolution twrp and ROM, everything fine. Then i decided to format data, just to get a "clean" ROM, but after this, my phone fell in bootloop and, i don't know why, i couldn't even get into twrp and if i try to boot into it, i just get stuck in the yellow text "Your phone is booting up..." forever. So i downloaded b160, extracted update.app and flashed system, boot, cust and recovery to try to get as stock phone was, but after that i couldn't boot into system: i just saw the yellow choices menu stuck with the same text "Your phone is booting up...", can't even see Huawei's logo. I tried to flash twrp for 6.0, but i couldn't boot into it cause it was replaced everytime by eRecovery. So i tried to install b160 from dload method and it worked but bootloader locked again and i don't have the password anymore, and after Huawei's logo there's just a black screen forever. I heard about some kind of "oeminfo.img" to flash before downgrading from N but i didn't do that cause i couldn't access twrp after formatting data. I tried to install via ota b100, b120, b130 without success, they all say incompatible firmware when i install them. I can just install b160 or b161 but they don't boot up. Please help me if u can, i'll really appreciate it
unlock you bootloader again !
flash revolution recovery b9
flash oem.info
dload b160 (Factoryreset, Bootloader locked)
Ron
RonPo said:
unlock you bootloader again !
flash revolution recovery b9
flash oem.info
dload b160 (Factoryreset, Bootloader locked)
Ron
Click to expand...
Click to collapse
I can't unlock bootloader again because i can't access system to get infos like imei etc, and i don't even have the code to unlock bootloader.. Btw, thank you for helping me
xDavi01 said:
I can't unlock bootloader again because i can't access system to get infos like imei etc, and i don't even have the code to unlock bootloader.. Btw, thank you for helping me
Click to expand...
Click to collapse
Try fastboot getvar all . Maybe it contains all the information you need
if not, dc-unlocker will do what you need. I've bricked my device and with their soft I've managed to write the full img. You should try only to unlock the bootloader service from them
You can look at the package of your P9 Lite. There should be a sticker on it with your IMEI.
Schlengge said:
You can look at the package of your P9 Lite. There should be a sticker on it with your IMEI.
Click to expand...
Click to collapse
Okay, i found it, but what about serial number and product id?
dondrog said:
Try fastboot getvar all . Maybe it contains all the information you need
if not, dc-unlocker will do what you need. I've bricked my device and with their soft I've managed to write the full img. You should try only to unlock the bootloader service from them
Click to expand...
Click to collapse
Thank you! Now i have IMEI and Serial NR, i just need Product ID. Is there a way i can get this?
Edit: I DID IT! YAY! I got bootloader unlocked, i used Huawei Product ID Generator, and typed "HUAWEI Y300-0000" instead of "HUAWEI VNS-L21" in Reformatting Lock Huawei's page, and it worked like a charm! Thank you for your help guys, you're the best
xDavi01 said:
Thank you! Now i have IMEI and Serial NR, i just need Product ID. Is there a way i can get this?
Edit: I DID IT! YAY! I got bootloader unlocked, i used Huawei Product ID Generator, and typed "HUAWEI Y300-0000" instead of "HUAWEI VNS-L21" in Reformatting Lock Huawei's page, and it worked like a charm! Thank you for your help guys, you're the best
Click to expand...
Click to collapse
for some reason that does not work for me VNS-31 :crying:
Hi guys, I will appreciate if someone can help me. The things is:
I erase system.img from recovery and I backup from XT1706. After I found a site with stock XT1700 rom I downloaded last version which is the S503 I used SP Flash Tools and everything goes well. But when I tried to unlock Bootloader again adb windows said: This operation is not allowed. I tried everything but I wasn't able to unlock Bootloader again. So I downloaded the first version (S116) and surprisingly I could unlock Bootloader. But I get no notification of OTA updates it says that phone has the last version which is not true. Any ideas of what could be happening here? Thanks of hand for you help.
If you downloaded the ROMs from http://motorolastockrom.com/motorola-moto-e3-xt1700 then I suspect the problem is the ROMs have locked boot loaders. I tried installing the S503 version and the S302 version and had the same problem as you. In the end I ended up installing an XT1706 firmware and was able to unlock the bootloader, but sadly it is the same release date and adroid patch version as the XT1700 ROM I was on to begin with (S124)
Hello, I recently purchased the T-mobile version of the 6T (bad idea) that had a locked bootloader, and tried to flash it to the international version so I can root the device. I followed this post in hopes of achieving it. The device will no longer boot. The screen quickly flashes with a Oneplus logo with "fastboot mode" underneath then I am met with this error: "Build version and HW is not match!". Is it completely bricked? Can I flash back to a T-Mobile OS?
If it is truly bricked I am curious if someone could explain why it may have happened. As in, has T-Mobile changed some the checks involved with flashing to the international version? Or was it because the device was running the latest Oxygen OS, is it impossible to downgrade this way? I am genuinely curious and want to take this as a bitter learning experience.
Thanks for your input.
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Pain-N-Panic said:
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Click to expand...
Click to collapse
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Did you get it all figured out? If not here's a semi detailed version of what I had to do with my tmobile 6t, because I had issues as well. Mainly my phone not showing up in msm tool. Only wanted to work after it had Android 9. Also I had little sleep the night I did this so I'm trying to recall the best I can.
Assuming your phone shows in msm tool at this point
Used msm tool to flashed older A9 ops https://androidfilehost.com/?fid=11410963190603895067
Boot in and enable adb and oem bootloader unlock
Boot to bootloader and unlock it
Flashed first A10 OOS https://androidfilehost.com/?fid=4349826312261819701
Flashed 10.3.7 to both slots with twrp https://androidfilehost.com/?fid=10763459528675591630
Flash rom
Flash Magisk
Profit
Some of this could be redundant, but my late night research and trial and error paid off.
GoldfishSnack said:
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Click to expand...
Click to collapse
Well I'm glad you were able to get it up and running. I highly suggest unlocking that bootloader as soon as you can....having an unlocked BL is key to getting out of a lot of bricked situations.