...
I hope u find this, i've also a bricked x+1
If anyone have this tool I need too!!
Thanks
Can you get into bootloader mode? Charge the phone and see if you can get into bootloader mode.
I'm on the same boat... Just got my Moto X 2014 bricked... Found the tool and files for the original Moto X, but not for Moto X 2014. I don't think they exist (yet).
---------- Post added at 05:08 PM ---------- Previous post was at 05:03 PM ----------
@JulesJam
I am (and I believe eveybody else on this post is) requesting the tool / files because our smartphones are bricked in a way we can't access the bootloader. The tool Junior asked on the OP is to repair / reflash the bootloader, which probably got corrupt, so there's no way to access it and flash anything through Fastboot.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
joker2mbr said:
I am (and I believe eveybody else on this post is) requesting the tool / files because our smartphones are bricked in a way we can't access the bootloader. The tool Junior asked on the OP is to repair / reflash the bootloader, which probably got corrupt, so there's no way to access it and flash anything through Fastboot.
Click to expand...
Click to collapse
Ok, yes, if you corrupted the bootloader than you obviously can't get into bootloader mode. But a lot of times people just don't know how to get into bootloader mode when they have a blank screen. So I was asking.
If your screen is blank when you turn on your device and you know the phone is charged, you can press and hold the power button for about 5 seconds, then immediately press and hold volume down and then press and hold power again and hold both for about 4 seconds then release. I have found I need to press and hold both volume up/down then while still holding press power and keep all 3 held down for 4 seconds and then release. I don't know why but pressing and holding all 3 seems to work better for me.
JulesJam said:
Can you get into bootloader mode? Charge the phone and see if you can get into bootloader mode.
Click to expand...
Click to collapse
The screen is only black and phone doesn't get to the fastboot. I've tried a number of ways.
When I connect to the PC, the device is recognized with the name QHSUSB_DLOAD.
When I connect to the charger, the green led flashes constantly.
Ive already have the .hex files
Junior Passos said:
The screen is only black and phone doesn't get to the fastboot. I've tried a number of ways.
When I connect to the PC, the device is recognized with the name QHSUSB_DLOAD.
When I connect to the charger, the green led flashes constantly.
Click to expand...
Click to collapse
The behavior I see here is quite the same. I tried to use the blankflash tool, but as you already discovered, it needs some device specific files (from the bootloader) and the ones available around just won't work with the Moto X 2014... Install the unsigned device driver on Windows is not difficult. The problem is to find these files, that should come directly from Motorola. Without them, we can't restore the bootloader, that is probably corrupted.
---------- Post added at 11:26 PM ---------- Previous post was at 11:22 PM ----------
dashiell_cano said:
Ive already have the .hex files
Click to expand...
Click to collapse
Did you manage to use the files you've found to fix your bootloader? I thought the needed files were like "singleimage_XXXX.bin"... Please let us know your results.
Thanks a lot!
Junior Passos said:
The screen is only black and phone doesn't get to the fastboot. I've tried a number of ways.
When I connect to the PC, the device is recognized with the name QHSUSB_DLOAD.
When I connect to the charger, the green led flashes constantly.
Click to expand...
Click to collapse
Has anyone looked at this process to see if some variation of it can be used to resurrect your device?
http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602
I am not familiar with the process used here to resurrect a bricked Moto X 2013:
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
However, I have a file emmc_appsboot.mbn for 5.0 for XT1096 (Verizon Moto X 2014) and from scanning the thread above, that may be a useful file.
I can access to the command system, but with the .bin file ive found i receive the "file to large" or "wrong version" message sometimes.
As you said we need the right .bin file.
dashiell_cano said:
I can access to the command system, but with the .bin file ive found i receive the "file to large" or "wrong version" message sometimes.
As you said we need the right .bin file.
Click to expand...
Click to collapse
do you know what emmc_appsboot.mbn is?
JulesJam said:
do you know what emmc_appsboot.mbn is?
Click to expand...
Click to collapse
As i know the mbn file Is the equivalent to the .hex file, am i wrong?
dashiell_cano said:
As i know the mbn file Is the equivalent to the .hex file, am i wrong?
Click to expand...
Click to collapse
Idk, but I have that file and it is for the aboot partition if anyone wants it I can upload it. But it is for the XT1096, I don't know if that matters or not. Do you want it?
Yes please, with your file, mine and the next files to come maybe together we can solve this puzzle
dashiell_cano said:
Yes please, with your file, mine and the next files to come maybe together we can solve this puzzle
Click to expand...
Click to collapse
https://www.dropbox.com/s/5bu79og4b3oqbug/emmc_appsboot.mbn?dl=0
---------- Post added at 05:07 AM ---------- Previous post was at 05:03 AM ----------
dashiell_cano said:
Yes please, with your file, mine and the next files to come maybe together we can solve this puzzle
Click to expand...
Click to collapse
Also read this:
http://forum.xda-developers.com/showpost.php?p=60635306&postcount=431
What is the emmc software flasher tool? Is it this?
http://androidxda.com/download-emmc-dl-tool
JulesJam said:
https://www.dropbox.com/s/5bu79og4b3oqbug/emmc_appsboot.mbn?dl=0
---------- Post added at 05:07 AM ---------- Previous post was at 05:03 AM ----------
Also read this:
http://forum.xda-developers.com/showpost.php?p=60635306&postcount=431
What is the emmc software flasher tool? Is it this?
http://androidxda.com/download-emmc-dl-tool
Click to expand...
Click to collapse
The flasher tool is a program that let you solve the missing recovery with the qualcomm devices instead of use command lines(its something like rsd vs mfastboot), you need 2 files, .hex file ( or mbn) and .bin file (the emergency recovery). You have the mbn (same as my .hex) we just need the .bin one.
dashiell_cano said:
The flasher tool is a program that let you solve the missing recovery with the qualcomm devices instead of use command lines(its something like rsd vs mfastboot), you need 2 files, .hex file ( or mbn) and .bin file (the emergency recovery). You have the mbn (same as my .hex) we just need the .bin one.
Click to expand...
Click to collapse
Is the .bin file something I can pull from a working device? Or is it inaccessible?
... I really dont know
dashiell_cano said:
... I really dont know
Click to expand...
Click to collapse
The Droid Ultra is very similar to the Moto X 2014, do you think any of these files may work?
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
maybe this:
MPRG8960_MOTO.zip
Related
Hi
Dear friends I have a big problem with FRP. I try a lot of methods but any one of them didnt work. I try:
1. By get in to mail or youtube but i get message that javascript is disable.
2. Get by web like before but i dont have any keyboard.
There is other metod to unlock this FRP? I bought phone a few days ago. In huawei service i must pay 50$
Hi! Try to downgrade the Android firmware to an earlier date.
but how, I dont have trwp even bootloader is locked olny i can in dial up *#*#2846579#*#* and then update but I dont know what i need to copy on sd card
djsobol said:
but how, I dont have trwp even bootloader is locked olny i can in dial up *#*#2846579#*#* and then update but I dont know what i need to copy on sd card
Click to expand...
Click to collapse
Download service ROMs here:-
https://androidhost.ru/
Instructions in zip.
Will work on stock phones.
I found a lot of ROMs but witch one will be good?
LLD-L31
djsobol said:
I found a lot of ROMs but witch one will be good?
LLD-L31
Click to expand...
Click to collapse
Well what model is your phone ?
LLD-L31 ( C434 ) is European.
Yes my country is important?
there is ADR, XAS, XVR what is mean this symbols?
So mine is LLD-L31 8.0.0.136 (C432).
Enter on http://androidhost.ru, and there search for the 8.0.0.125 (C432) firmware, it is the one with June patch, so I guess you can do the Talkback trick on it.
ok I'm downloading all 3 and witch one I should chose?
Upload the picture again.
ok
google
That three are not good.
Search for 8.0.0.125 one.
there arent other, could you tell me or sent a picture witch one i should download?
I will upload a link in a couple of minutes, I am on my phone now.
ok I'm looking forward to download it
djsobol said:
ok I'm looking forward to download it
Click to expand...
Click to collapse
Here's a link for B132 which should be early enough to allow the BL unlock exploit (should you need it) :-
https://androidhost.ru/6ps
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
djsobol said:
there arent other, could you tell me or sent a picture witch one i should download?
Click to expand...
Click to collapse
There are at least 15 to choose from.
ok i unpack it and copy dload on sdcard??
Where i can find tutorial or something like that
@aka.petteri give me elier ver
You know, you can always email Huawei and request your FRP key and just use Fastboot to unlock FRP.
i write to support but they wont help me because i should have recipte and give it to service and pay 40-70$ if I have recipte of corse. In other way they wont help me.
djsobol said:
ok i unpack it and copy dload on sdcard??
Where i can find tutorial or something like that
@aka.petteri give me elier ver
Click to expand...
Click to collapse
Copy complete Dload folder onto root of SD card.
Power off phone.
Hold all three buttons Vol + Vol- Power and forced update should start.
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
djsobol said:
i write to support but they wont help me because i should have recipte and give it to service and pay 40-70$ if I have recipte of corse. In other way they wont help me.
Click to expand...
Click to collapse
If you can prove ownership they will ( should) give you your FRP key, no need to go to a service centre at all.
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.59 and OOS v9.0.13 which is compatible with International and McLaren editions.
OOS v9.0.11 can also be used to convert a T-Mobile model into a fully fledged International model, more info here.
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download one of the drivers below and install.
Run MsmDownloadTool V4.0 and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
6T MsmDownloadTool v4.0.59 (OOS v9.0.13)
6T MsmDownloadTool v4.0.58 (OOS v9.0.12)
6T MsmDownloadTool v4.0.58 (OOS v9.0.11)
6T MsmDownloadTool v4.0.58 (OOS v9.0.6)
6T MsmDownloadTool v4.0.58 (OOS v9.0.5)
Driver
Alternative driver
Shameless plugs - OP referral link for any peops that would like $20/£20/€20 discount: OnePlus or PayPal donation link: PayPal.
Wow nice. Now to test this on T-Mobile!! Let the flashing commence
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
im tempted to run this today on the tmobile model. how high is the risk of hard brick? will it leave me without fastboot if it doesnt work?
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
apparently the flash to 9.0.5 in the other thread overwrites the modem anyway. its the criticals that dont overwrite. worst case im within my 14 days still, can alwasy return
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
strictlyphat said:
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
Click to expand...
Click to collapse
One of three things will happen.
One, it will recognize it as the wrong device and won't flash at all.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
Click to expand...
Click to collapse
Screw it. I'm gonna do this soon. Will report back
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Wanna find out? I'll probably test in a few, lol.
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Cuz I'm assuming it's the same as Samsung. One hardware multiple softwares.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Dark Nightmare said:
Wanna find out? I'll probably test in a few, lol.
Click to expand...
Click to collapse
Dude I will owe you one. Ur much braver than I. If my son falls asleep I'm trying to. PLEASE LET ME KNOW. And please let me buy u a beer lmfao
strictlyphat said:
Screw it. I'm gonna do this soon. Will report back
Click to expand...
Click to collapse
Guess I'll wait on your results...
Dark Nightmare said:
Guess I'll wait on your results...
Click to expand...
Click to collapse
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
strictlyphat said:
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
Click to expand...
Click to collapse
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Dark Nightmare said:
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Click to expand...
Click to collapse
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
strictlyphat said:
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
Click to expand...
Click to collapse
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.[/QUOTE
oof that sucks. thanks again
Click to expand...
Click to collapse
Safe flashing to anyone taking the plunge!
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
tried it for good measure, same error
iaTa said:
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.58 and OOS v9.0.5 and is compatible with the non T-mobile international models (T-mobile compatibility currently unknown).
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download the driver below and install.
Run MsmDownloadTool V4.0_factory.exe and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
MsmDownloadTool: https://androidfilehost.com/?fid=11410963190603846961
Driver: https://androidfilehost.com/?fid=24052804347798730
Shameless plug - my OP referral link for any peops that would like $20/£20/€20 discount: https://www.oneplus.com/invite#EC5BZVULJDUUO22
Click to expand...
Click to collapse
Oh my God you just saved my life brother. Thank you so much.
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
Sad days... Appreciate the risks you've taken tho!!
Hi guys I unlocked my bootloader etc and like everyone else who owns a E4 Plus I get the message "Orange state your device has been unlocked bla blah"
I was wondering is there anyway to remove/hide it? I already searched the forum and most answers were a "no".
But I just wanted to double clarify hence I started this thread.. I know the message only shows up on bootup but like everyone else I would prefer it not to be there..
any replies would be appreciated thanks.
My model is XT1771 Nicklaus
Cheers.
I flashed a bootlogo that covered it. There are several around, pick what you like.
koop1955 said:
I flashed a bootlogo that covered it. There are several around, pick what you like.
Click to expand...
Click to collapse
Could you link me to your boot logo or one similar?
I searched but cant find one specifically hiding the message.
Thanks
koop1955 said:
I flashed a bootlogo that covered it. There are several around, pick what you like.
Click to expand...
Click to collapse
That just apply for the Qualcomm variants, on nicklaus that warning is reported by lk partition on mtk devices, and cant be removed by just changing an custom logo
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
Cobrahaze said:
Could you link me to your boot logo or one similar?
I searched but cant find one specifically hiding the message.
Thanks
Click to expand...
Click to collapse
It cant be removed, at least that you hex patch the lk partition of the device, this message is reported by this partition, it doesn't load an image on boot, it just display this annoying message, and that its why it xant be removed
hetor99 said:
That just apply for the Qualcomm variants, on nicklaus that warning is reported by lk partition on mtk devices, and cant be removed by just changing an custom logo
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
It cant be removed, at least that you hex patch the lk partition of the device, this message is reported by this partition, it doesn't load an image on boot, it just display this annoying message, and that its why it xant be removed
Click to expand...
Click to collapse
Thanks for clearing that up for me.
My apologies for posting incorrect information. The differences between the E4 Plus versions continue to surprise me.
koop1955 said:
My apologies for posting incorrect information. The differences between the E4 Plus versions continue to surprise me.
Click to expand...
Click to collapse
I just got this phone for christmas, There are way too many versions of this phone, so confusion is going be a learning curve, what works on one version doesn't work on another.
So far that's the only downside I have found so far with this phone. Mine is the retail version, xt1775.
Can someone download this twrp and upload it to a mirror? It's for the Red Magic 3.
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEw...arentPath=/sharelink781715067-606770439204444
+6281281903288 contact me via whatsapp and i will share to you twrp file
tembokbesi said:
+6281281903288 contact me via whatsapp and i will share to you twrp file
Click to expand...
Click to collapse
OK at this point Ill try anything. I have my cell totally unlocked OEM an Bootloader an still have just a fastboot screen an little else no matter what I try and do.
I use whatsapp. Not sure how to add you or contact you through it?
The only thing i used it for was sending info to my boss
---------- Post added at 01:44 PM ---------- Previous post was at 01:43 PM ----------
Bryceicle1971 said:
OK at this point Ill try anything. I have my cell totally unlocked OEM an Bootloader an still have just a fastboot screen an little else no matter what I try and do.
I use whatsapp. Not sure how to add you or contact you through it?
The only thing i used it for was sending info to my boss
Click to expand...
Click to collapse
Edit: just found out how to add you
I already download twrp wait I share after some time
Any Twrp or EDL rom? Currently stuck in bootloop.
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