Database Develop

[Q] S-On (Re)Locked Stock GPe Bootloop Discussion

Shall we have a centralized place for discussion (or better, solutions) related to the bootloop issue happened on HTC One GPe? Apparently I'm not the only one in this situation, and having a single thread will help others to find the solution more easily.
The problems are basically having a soft bricked GPe and only bootloader is accessible. The GPe device is real, S-On, locked or relocked, with stock firmware of OS-3.58.1700.5 and HBOOT 1.54, but without a working rom.
1. flashing the GPe RUU by graffixnyc from this thread won't work because of the signature verification failure, which makes sense since it's not signed by HTC (the firmware.zip flashes through because it's signed by HTC).
2. fastboot oem unlock does not work and shows the following error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
3. fastboot flash unlocktoken Unlock_code.bin fails silently, i.e. the confirmation screen does not show up on device.
4. trying s-off the device is not feasible without a working rom and unlocked bootloader.
5. fastboot boot <custom_recovery>.img fails for both CWM and TWRP:
Code:
downloading 'boot.img'...
OKAY [ 1.123s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.123s
6. fastboot erase cache and factory reset does not help.
Any other options so we could have a try? @nkk71 @SaHiLzZ

Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.

SaHiLzZ said:
Thank you for creating this thread. The same issue is happening for converted devices with relocked bootloader as well.
I'm out of options as neither fastboot oem unlock nor fastboot flash token unlock.bin are working, and without these not much to do.
Click to expand...
Click to collapse
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.

This seems to be happening more and more. I'm in the same boat. Tried to update a GPe HTC One and got stuck.
I have contacted HTC support as stated in this thread:
http://forum.xda-developers.com/showthread.php?t=2492469&page=5
They we able to help get his up and running. Hopefully they can help me out to with out the need to pay extra charges.
I will update on the progress, but seeing as we are entering the weekend, it will probably only be next week.
I miss my phone

Thanks for the thread and the clear summary. I have exactly the same issue with my stock Gpe and am anxiously waiting for a solution.
Sent from my Nexus 7 using XDA Premium 4 mobile app

joe7wu said:
It seems like some mechanism has been changed in the latest firmware that prevents the original unlocking method.
Click to expand...
Click to collapse
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.

mderksen said:
Create a new unlock_code.bin file using htcdev.com. This worked for me. I tried to use a unlock_code.bin file which i used when using Sense. This older bin-file didn't work so i tried to create a new one. This worked for me and my bootloader is unlocked now.
Click to expand...
Click to collapse
I think he is talking about the method on the device, not from HTC Dev.
On the device, using "fastboot oem unlock" or the HTC Dev method dosent work.
As stated above the first returns an error and the .bin method shows a success message, but nothing actually happens.
This is my situation anyways.

Any one with locked, not relocked bootloader having the same issue. Wonder how Google will fix this..

+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist

I am also having the same issue on my google play edition. S-On. I reflashed a stock recovery image so I could update to stock ROM. Now, I am stuck in a bootloop. I cannot reload any kind of custom recovery (I say that I can't. When I do, the phone will not boot into recovery. It just jumps to the Google screen, attempts to load the OS and then restarts). I AM able to unlock and relock using fastboot oem unlock and lock. I've attempted to reload the firmware and it seems to work (via cmd loading), but the loop process begins again. I attempted to flash a 4.3 firmware I found, but received the blue screen of nothingness when I did.
I'm lost. Possibly only solution is sending back in for repair. I just got the phone and this is annoying as heck..

alcaloide_ said:
+1 I'm having the same problem
Edit: They should make this a sticky thread for as long as the problem exist
Click to expand...
Click to collapse
Yeah, a sticky thread will help a lot. Anyway, I'm still waiting for those people who got in touch with HTC and see how it goes. A bit worried about the fact that I'm in Canada and a friend in US bought this phone for me. Not sure how the custom support will be like in my case.

So, a thought just occurred to me - i haven't updated any of my tools for fastboot since i originally unlocked the system a few months ago.
I am not currently at home, so i cannot check on this, but perhaps this will help others....
The current sdk tools version is 22.3 : http://developer.android.com/sdk/index.html
Could perhaps updating these tools help us re-unlock our phones?
If someone checks and tries this, and then the fastboot oem unlock command, let me know if it is simply a windows software thing.

OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...

AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Hope this helps somebody...
Click to expand...
Click to collapse
Interesting. I chatted with an HTC rep this morning and I am sending the phone to an HTC repair facility in Houston. I wish Google would just do an exchange. DId they give you a hard time? Should I just call them and ask for an exchange?

They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.

AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Thanks! I assume it is a one year warranty? My issue is that I bought it used. I wonder if they will give me a hard time about that.
---------- Post added at 03:48 PM ---------- Previous post was at 03:34 PM ----------
AmirH said:
They didn't give me a hard time at all. They were actually pretty cool about it.
They tried to help me out, they saw they couldn't, so they said they would send me a new one. I even went as far as telling them that I was playing around with it trying to unlock and flash 4.4(not too specific of course), and that they should just give me a flashable zip to use because I could get it into RUU mode.
I'm not sure if it makes a difference but I bought the phone in August. So i guess the only real question is, is if you still have warranty.
Click to expand...
Click to collapse
Well, i just got off the phone with them. I'm glad you had more success than I! The lady said she could not identify a troubleshot and, since I did not buy from them under my account, they couldn't help me.

AmirH said:
OK so I emailed HTC, they told me that because the phone was issued from Google, it was Google who was in charge of the warrenty. They gave me the Google customer care number "Google’s US hardware support number: 1.855.836.3987 they are open 24/7." just in case anyone needs it.
I just got off the phone and after talking with them I got the impression that they are aware of the problem but that there is currently nothing that they can do to fix it.
It seemed as though he was hinting at a fix in the future, possibly a flashable zip, but I dont know.
Anyways he had me go into recovery mode, and do a factory reset. I didnt even know I was able to do this. Unfortunately it didn't help.
At the end we had to set up an RMA. They are sending out a phone and then I will need to return mine.
Being currently in Israel they were unable to send it here, so they are going to send it to the US, and they I will send mine back from here.
Kinda sux, I was hoping for a quick fix.
Click to expand...
Click to collapse
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).

elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
I would give it a shot

elisaw99 said:
Huh. Interesting. Maybe i just need to call Google. I did try factory reset, but that didn't work. Probably best to do what you did and just ask for a new one to be sent, if they cannot resolve. I did buy it with my google account, so i might be in luck (I probably about when you did, around August).
Click to expand...
Click to collapse
Let us know how it goes! II will be sending mine to HTC tomorrow

I just got off of the phone with Google. Rep indicated that many have been going through this problem. They are sending out a new phone right away and I will send mine back upon receiving the new one. Bought the phone in July from Google Play Store. Great customer service!

[SOLVED] Moto X xt1052 Stuck in Fastboot

Hey ,
seems like you guys are my last chance. I will try to explain my situation:
So today I was just messaging when suddenly some process.google.media (cant recall exactly) error was spamming my phone. I restarted the phone and then the problems started happening. The moto X was stuck in the boot screen.
I read that i should install TWRP and factory reset. So after doing that I was pretty much stuck in recovery.
Whenever i turned the phone on, It was immediately booting the TWRP.
So I thought fine, I will probably have to install a ROM, so it can actually boot something.
I went for the xt1052 Lollipop 5.1 untouched EU version of the forum. Still It somehow didnt boot.
Next I came across the following youtube video: youtube /watch? v=ne46LQ3n7nA
(cant post url)
Followed all the instructions in the video and it actually got my phone to work.
I thought that now everything would be just like when I bought my phone.
So I installed the official lollipop update which popped up on my screen.
And now Im stuck again...
Im sitting in Fastboot Mode and get the following error:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
Dont know how many threads I read by now on here to find a solution but I cant find any..
I installed RSDLite, but Im not sure which version to use to flash now.
Tried two zip folders, but apparently the xml file was missing.
Im kinda scared to use the wrong zip anyways and screw my phone completely if it isnt already.
Id really appreciate any help since im currently clueless.
Thanks boys!

downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
This is likely your problem and the result of flashing a lower version onto your Moto x. I would start looking how/if you can recover from a downgrade.

I might add some additional error description to make ppl find this thread in the future :
Stuck in bootloader - Fastboot - cant enter recovery - when choosing any options from fastboot: Load kernel (boot) failed
-----------------------------------------------------------------------------------------------------------------------------------------
Alright seems like i got it working again.
Since this forum helped me so much I want to contribute something to it by giving u guys my solution.
So I stumbled across alot of threads with @KidJoe replying. He really knows his stuff, when it comes to the MotoX.
I dont know how to quote off of other threads, but this quote of KidJoe got me on the right track:
" GPT.BIN is the partition table. Its important. When GPT.BIN and MOTOBOOT.IMG are mismatched from the rom on your phone you could brick when taking an upgrade.
In most cases, the GPT.BIN has matched from model to model when on the same rom (i.e. GPT.BIN from XT1060 4.4.4 rom has matched GPT.BIN of XT1053 4.4.4 rom).
However, try Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and see what happens. "
Alright so, here is what I grasped:
before things went bad for my phone, I was already on lollipop. Following the youtube video I downgraded it from 5.1 to 4.4.4.
While downgrading I already noticed that some commands failed, which was the gpt.bin stuff.
So after my phone was working on 4.4.4 and I used the Motorola Upgrade to 5.1 , there must have been a problem with the gpt.bin and motoboot.img , just like KidJoe said. Hence why I got stuck in Fastboot.
As I said in the first post, I had to find the right image for my phone.
In the Fastboot mode I saw that I was on 30.BE, and from what I understand that means im on lollipop and since I cant downgrade, I had to find the right lollipop version for my device.
Im also german, so I found this version:
XT1052_GHOST_RETDE_5.1_LPA23.12-15.5_cid7_CFC.xml.zip
KEEP IN MIND, my problem was having the wrong version all along, so you have to find the right version for your smartphone, dont make the same mistake I did!
I found my file on filefactory through this link here:
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
(EDIT: I recommend using something like jdownloader to manage the download)
After I had the right version, I used rsdlite, chose my new file and my phone was working again.
However, I noticed that even tho my phone was working, the rsdlite actually failed somewhere between the lines. (I think it was step 7 or 9)
I was really happy to see my device boot up again, but wasnt happy with those errors and followed this link:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Option 5.
Now finally all the commands went OKAY in my cmd window.
After the motorola took some time to boot up again, I performed a factory reset via settings.
Just to make sure its fine and it seems like it is.
To end this thread off, I hope KidJoe will read this post.
Big thanks to you, your the man!
And even tho on some posts you came along a bit harsh, which really got me worried my phone would be completely dead, I wish you a nice christmas time dude!

Moto X Dev Edition stuck in fastboot

I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead

RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?

Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.

i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.

varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s

I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.

OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.

I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.

PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.

Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.

RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8

@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!

PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.

Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend

Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?

RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!

RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..

Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob

Huawei P10 Lite Bricked? Need help please.

Hello all,
First of all I looked for a (sub) forum for the P10 Lite, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my P10 Lite (WAS-LX1A model)...
The phone is running the stock B102 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last saturday (June 24, 2017) there was an OTA update to B131 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B120, B123 and B131 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Tried all I can think of on 2 linux machines and 1 Windows 7 machine, all 64-bit, allthough 1 of the linux machine is multi-architecture so it runs 32-bit too (not related to this issue, needed 32-bit for WINE). This just to rule out an issue with my machine. All 3 machines act exactly the same though which makes me (strongly) believe the issue resides on the phone.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Info:
- phone: Hauwei P10 Lite, model: WAS-LX1A, firmware: WAS-LX1AC432B102
- (main) laptop: HP Probook running Arch linux (64bit), uname: "Linux probook 4.11.6-3-ARCH #1 SMP PREEMPT Thu Jun 22 12:21:46 CEST 2017 x86_64 GNU/Linux".
- Android SDK version 26. Package named: "aur/android-sdk-platform-tools r26.0.0-1 (1155, 9.20)" Which can be found on Arch's AUR. (I am aware I need to run fastboot as "sudo", fastboot cannot do anything without sudo priviledges).
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".

OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with DC-Phoenix tool, just flash stock firmware you had on the phone.

MobileTechArena said:
OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with <snip> cannot post URL's yet <snip> tool, just flash stock firmware you had on the phone.
Click to expand...
Click to collapse
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?

GuessThisIsMe said:
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?
Click to expand...
Click to collapse
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.

MobileTechArena said:
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.
Click to expand...
Click to collapse
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).

GuessThisIsMe said:
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).
Click to expand...
Click to collapse
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this REDLOTUS tool to bypass eRecovery and flash firmware.

MobileTechArena said:
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this <snip> tool to bypass eRecovery and flash firmware.
Click to expand...
Click to collapse
Ok, l did get the right firmware (EU region), so that wasn't the issue.
Tried the REDLOTUS tool (thanks for that link btw, seems like a promising project), but alas it doesn't seem to work for me.
Got node js/npm installed just fine, it works, manages to get the firmware and everything, listens for HiSuite and manages to point HiSuite to local host to look for firmware there (like it should according to REDLOTUS' Readme).
Unfortunately, HiSuite doesn't give me the option to update firmware, only the systemrecovery button isn't greyed out, and systemrecovery tells me my device isn't supported. I can see on my phone's screen "rescue mode enter..." when I select systemrecovery in HiSuite, but nothing else happens.
Seems like REDLOTUS might work for me once the author manages to get it to work with eRecovery instead of HiSuite (apparantly that's being worked on atm).

hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english

Radnaksi98 said:
hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english
Click to expand...
Click to collapse
If your phone reads "PHONE Unlocked" and "FRP Unlock", then lucky for you, you don't have anything near my problem.
First of, if you do a: 'fastboot devices' command, does it show your phone?
Can you tell me if the following commands work, and what they return?
- fastboot oem get-bootinfo
- fastboot oem get-lock-state
- fastboot oem lock-state info
If you run Linux you'll need to "sudo" the fastboot commands.
You have enabled ADB-debugging on the phone right?
Edit: Can you still get into the stock recovery? To get there first turn the phone completely off. Then hold Volume Down (-) and Power buttons till you see the Huawei logo, then release both buttons. From stock recovery you could try a factory reset (DO NOT DO THIS IF YOU HAVE TWRP INSTALLED!!!).

hi, the phone shows me "FRP Unlock", but when i've done all the commands u gave me and there's an FB Lockstate on: LOCKED
Idk what it is
EDIT: ADB-debugging isn't enabled because i can't boot the phone, and when it started to bootloop that was when i've unlocked the bootloader and someone told me to factory reset the phone, so i think the ADB-debugging isn't enabled anymore
EDIT2: Stock recovery is working

does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help

Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
You can find a full TWRP backup of the B102 firmware in the thread called -> Root p10 "lite" , on page 11 user: stefanwe92 posted a link to it.
Good luck!

Thank you for answering me !
But i've the LX1A, so can i use it ?

Radnaksi98 said:
Thank you for answering me !
But i've the LX1A, so can i use it ?
Click to expand...
Click to collapse
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:

GuessThisIsMe said:
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:
Click to expand...
Click to collapse
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !

Radnaksi98 said:
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !
Click to expand...
Click to collapse
command: "fastboot oem get-build-number" should tell you exactly which firmware your phone is running.
Congrats on your success!
Regarding your English, it seems just fine to me, I understand you well. And for sure it's better than my French (dropped that subject as quickly as I could in high school ).
Hope to hear from you soon, with a working phone!
Sleep well, btw I live in the same timezone as you (I'm Dutch).

Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved

GuessThisIsMe said:
Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved
Click to expand...
Click to collapse
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:

Carkai said:
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:
Click to expand...
Click to collapse
Agreed!
Nice people those Irish, some of them like their whiskey a bit too much , but all of the Irish folk I've met in my life have been nothing but kind human beings.
Knew one Irish lad who thought nothing of starting to drink at 8 in the morning, I tell you the drive back home was very interesting (and not at all dangerous :silly.

Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
I have a identical problem... my phone is stuck in "Huawei eRecovery" screen. Same situation that you had reported (connection fail).
I found a solution to enter in FASTBOOT & RESCUE MODE and i posted in:
https://forum.xda-developers.com/general/general/solution-huawei-p10-lite-alternative-to-t3637311
I also have a TWRP backup... but my problem started when i used it to restore my phone. So i believe that it will not help you. But if you want I can send it to you. My model is a WAS-LX1A (Portugal).
Have you found a solution to your problem?

[Given up] Semi dead Lake

Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!

y5r43l said:
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!

y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
Try the unlocking code again

sd_shadow said:
Try the unlocking code again
Click to expand...
Click to collapse
It won't allow. It asks to enable OEM Unlock under Settings -> Developer Options.
Thanks for the answer!

y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7.
Sent from my ali using XDA Labs

Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!

pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files

Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.

pastorbob62 said:
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
Click to expand...
Click to collapse
This was his way of knowing that, you and i, we have been here for a long time, i learned this years ago, now he knows it

Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.

y5r43l said:
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
Click to expand...
Click to collapse
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!

y5r43l said:
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
Click to expand...
Click to collapse
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on

darkherman said:
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
Click to expand...
Click to collapse
Hi, darkherman,
thank you for you reply.
Unfortunately it won't work as according to documentation: "Make sure you enabled adb debugging on your device(s)."
I have to boot the system to enable it in Developer Options.
Thanks anyway!
Is there a way to bypass the Google Wizard and boot the system without logging in?
About the warning on startup I've read somewhere that's not possible because of some var value obtained from:
Code:
fastboot getvar allCODE]
Don't remember exactly what var, but its value may be 0, 1 or 2 that means locked, unlocked and relocked (not necessarily in this order)
-- runnig the above command I saw some variables such as securestate, verity-state and iswarrantyvoid than may mean something.
But, as far as I know, we have no command such as "set-iswarrantyvoid false" or "set-verity-state 1" or something like that.
Maybe this could be done by replacing/updating the firmware if possible, but I think it doesn't worth the risk of making the device irreversibly bricked.
Thanks again for your reply.

It seem there's no way to rescue it.
Gonna just give up and throw it away.
Thanks for those who tried to help!

y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse

KtownJeff said:
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
Hi, thank you for your reply!
I really never have took apart a phone nor know about test point shorting so this is not an option for me. I could even try to do it but probably won't be able to mount it back.
It's a no carrier phone, but in my country, there's no so easy return policy that I know of, unfortunately.
The bypass won't work because the second pass, "Connect your Motorola Moto G7 Plus to your Wi-Fi", as I think this is the biggest problem, I cannot connect to Wi-Fi. I also tried the method suggested by @darkherman throught gnirehtet with no success.
Click to expand...
Click to collapse