Related
So, I had reformatted my phone via recovery mode. I did this not knowing samsung would force me to put in my samsung account info when turned on for the first time... I had actually sold it to a friend, thinking he would just sign in through his account. This caused an issue and it needed the original samsung account of the previous owner (which is me). I put in my information and it just says "processing failed". I had changed my password, made sure it was the correct information and it all was but it never worked and came up with the same error.
So what I am looking for now is a completely fresh install of a either lollipop for the, specific "g900aucu3boc4" version of the S5. Anything to bypass that ridiculous error and literally start fresh, like a brand new phone would. I will even accept 4.4.2 if available. Anything to help me, because I have sold this to my mate and he has STILL not got the phone after about 3 weeks... I really hope you guys can help, will mean a lot!
Thank you all! :good:
TheAndreYounes said:
So, I had reformatted my phone via recovery mode. I did this not knowing samsung would force me to put in my samsung account info when turned on for the first time... I had actually sold it to a friend, thinking he would just sign in through his account. This caused an issue and it needed the original samsung account of the previous owner (which is me). I put in my information and it just says "processing failed". I had changed my password, made sure it was the correct information and it all was but it never worked and came up with the same error.
So what I am looking for now is a completely fresh install of a either lollipop for the, specific "g900aucu3boc4" version of the S5. Anything to bypass that ridiculous error and literally start fresh, like a brand new phone would. I will even accept 4.4.2 if available. Anything to help me, because I have sold this to my mate and he has STILL not got the phone after about 3 weeks... I really hope you guys can help, will mean a lot!
Thank you all! :good:
Click to expand...
Click to collapse
You have active the "REACTIVATION LOCK" on setting ,after that when u will reset your phone then it will ask for the account .i have done once and also faced a same problem,there is method to bypass that just search on google for that it will work.sorry but i actually forget the process.
---------- Post added at 12:31 AM ---------- Previous post was at 12:26 AM ----------
leoishwor10 said:
You have active the "REACTIVATION LOCK" on setting ,after that when u will reset your phone then it will ask for the account .i have done once and also faced a same problem,there is method to bypass that just search on google for that it will work.sorry but i actually forget the process.
Click to expand...
Click to collapse
This is the process. Hope it will help u
https://youtu.be/OCZpUcnp6Cc
I had rooted my H811 but ive had problems with my phone contacted T-Mobile and they are going to replace my phone but i had flashed the 81110n kdz i got no unlocked bootloader warning but once it updated to 20i the warning came back is there any way to relock the bootloader or pull the warning help plz
Doubt it will even matter
Sent from my LG-H811 using Tapatalk
Please help....
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
DrakenFX said:
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
Click to expand...
Click to collapse
Worked ty vm @DrakenFX
Im sorry, but I too have the dreaded keyboard problem with the LG G4 and need to send it back for repair. Mine came with unlocked bootloader, and it shows on the LG screen where it gets stuck. I have managed to get it to reboot temporarily by putting it in the fridge for like 15 mins. But how do I get to the screen above so I can remove twrp and relock the bootloader?
i tried it for my h815 and it didnt worked
FAILED (remote: unknown command)
finished. total time: 0.004s
DrakenFX said:
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
Click to expand...
Click to collapse
would you do a video of it.? show us?
---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------
Rich7597 said:
Worked ty vm @DrakenFX
Click to expand...
Click to collapse
or would you??
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
maikalwolf said:
Im sorry, but I too have the dreaded keyboard problem with the LG G4 and need to send it back for repair. Mine came with unlocked bootloader, and it shows on the LG screen where it gets stuck. I have managed to get it to reboot temporarily by putting it in the fridge for like 15 mins. But how do I get to the screen above so I can remove twrp and relock the bootloader?
Click to expand...
Click to collapse
so what happen to yours ??? what you did? did you fixed? relock it.? if you did relock it would you make a video of it..?
raptorddd said:
would you do a video of it.? show us?
---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------
or would you??
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
so what happen to yours ??? what you did? did you fixed? relock it.? if you did relock it would you make a video of it..?
Click to expand...
Click to collapse
So I kept trying to do the freezer trick over and over again until I noticed that it actually had to be in the freezer the 20 mins just to start!! If it did not it would not boot at all. It was not a battery problem, it just stopped unless it was cold. I took a chance on sending it in since it was warrantied still, and crossed my fingers that they would not do the freezer trick at the factory. They did not and a few days later I checked and it was in their repair qwe. Keeping my fingers crossed until I saw that the resolution was "Replace motherboard" Reason "bent motherboard". I know the bent mobo was BS. But hey what ever it took right? A few days later it was in the mail and my son has been using it perfectly well since then with that same battery and another he purchased! They did take the protective glass screen saver off for some reason. So Bonus a practically new phone and I still got some warranty left until Oct of this year!
maikalwolf said:
So I kept trying to do the freezer trick over and over again until I noticed that it actually had to be in the freezer the 20 mins just to start!! If it did not it would not boot at all. It was not a battery problem, it just stopped unless it was cold. I took a chance on sending it in since it was warrantied still, and crossed my fingers that they would not do the freezer trick at the factory. They did not and a few days later I checked and it was in their repair qwe. Keeping my fingers crossed until I saw that the resolution was "Replace motherboard" Reason "bent motherboard". I know the bent mobo was BS. But hey what ever it took right? A few days later it was in the mail and my son has been using it perfectly well since then with that same battery and another he purchased! They did take the protective glass screen saver off for some reason. So Bonus a practically new phone and I still got some warranty left until Oct of this year!
Click to expand...
Click to collapse
did you send it to LG ot TMO.?
great at least you have a working phone, thats what you paid for anyways..
did you unlocked bootloader? i wouldd like to unlock it. but same reason warranty... so i was thinking since i saw this post that it can be relocked but theres no video of it... like unlock it, then if i get bootloop. flash the modded KDZ relock it, then flash stock and send it for repairs... could it be done?
raptorddd said:
did you send it to LG ot TMO.?
great at least you have a working phone, thats what you paid for anyways..
did you unlocked bootloader? i wouldd like to unlock it. but same reason warranty... so i was thinking since i saw this post that it can be relocked but theres no video of it... like unlock it, then if i get bootloop. flash the modded KDZ relock it, then flash stock and send it for repairs... could it be done?
Click to expand...
Click to collapse
I bought it unlocked, it turned out to be one of the models with the bad motherboard. The previous owner directed me to here so I could re-lock the boot loader. I got to the window several times but it would not stay long enough for me to try re-locking it. That's why it was nice that the phone's mobo was bad enough that it just stopped booting up! I took a chance. If it had booted and they would have seen the un-locked BL they could have told me tough luck. But I have read in many forums that LG is pretty good about this issue with the bad models. So it's a roll of the dice and lucky for me either the phone did not boot up for the Tech who handled my phone, or he saw what was going on and went ahead and switched out the mobo despite seeing the first screen screaming "unlocked bootloader!"
maikalwolf said:
I bought it unlocked, it turned out to be one of the models with the bad motherboard. The previous owner directed me to here so I could re-lock the boot loader. I got to the window several times but it would not stay long enough for me to try re-locking it. That's why it was nice that the phone's mobo was bad enough that it just stopped booting up! I took a chance. If it had booted and they would have seen the un-locked BL they could have told me tough luck. But I have read in many forums that LG is pretty good about this issue with the bad models. So it's a roll of the dice and lucky for me either the phone did not boot up for the Tech who handled my phone, or he saw what was going on and went ahead and switched out the mobo despite seeing the first screen screaming "unlocked bootloader!"
Click to expand...
Click to collapse
you were lucky only a few of them have been repair after unlocked bootloader..:good:
i have heard some complaint from other users that theirs were denied. not unlocked, but he assumes they LG tought it was unlocked because he says that when you request unlock.bin you must place your imei or serial number so they have it on record....
so you planing on unlocking this ?? HAHA if you do. i would like to see someone post a video or relocking and that it works..
No I will not be unlocking it. My son has the phone and wants to keep it locked in case. Like I said he is still under warranty.
maikalwolf said:
No I will not be unlocking it. My son has the phone and wants to keep it locked in case. Like I said he is still under warranty.
Click to expand...
Click to collapse
yeah makes sense, better have it under warranty.
DrakenFX said:
To lock the bootloader back is as simple as unlocking it, just follow the next steps and you'll be good to go :
Code:
adb reboot bootloader [b] (this reboots to bootloader)[/b]
fastboot oem lock[B] (this wipes all data)[/B]
P.S. This process may or will erase ALL DATA from Internal Storage.
Click to expand...
Click to collapse
This process will remove my all data like Images, Video, contacts etc.... or will wipe out my complete phone including OS files??
Hi Folks,
I flashed NightOwl onto the spare N7000 because we needed it while another phone was being repaired.
All was well until my wife changed the pattern being used in the pattern lock (trying to keep the kids out). Now she can't remember the pattern, and there are photos on the device she wants me to recover.
I've done some surfing, found a nice 'howto' youtube showing which files to nuke to remove the pattern lock altogether, but my problem is that once connected to ADB my attempts at getting su access to remove said files are denied. Apparently I don't have root??
Anyhoo - i'm looking for suggestions - what's the best way of getting through the pattern lock, or getting contents out of the phone so i can wipe, flash and start playing again.
Help?
Cheers,
t
try to ask at the rom-thread. bauner might help!?
---------- Post added at 01:50 PM ---------- Previous post was at 01:47 PM ----------
just reinstall the rom !?
timness said:
Hi Folks,
I flashed NightOwl onto the spare N7000 because we needed it while another phone was being repaired.
All was well until my wife changed the pattern being used in the pattern lock (trying to keep the kids out). Now she can't remember the pattern, and there are photos on the device she wants me to recover.
I've done some surfing, found a nice 'howto' youtube showing which files to nuke to remove the pattern lock altogether, but my problem is that once connected to ADB my attempts at getting su access to remove said files are denied. Apparently I don't have root??
Anyhoo - i'm looking for suggestions - what's the best way of getting through the pattern lock, or getting contents out of the phone so i can wipe, flash and start playing again.
Help?
Cheers,
t
Click to expand...
Click to collapse
You can reset the phone from recovery, it's won't affect files on the phone.
You will only lose all third-party apps and all app related settings.
Hi!
I'm from Brazil and I bought a Moto G6 XT1925-3.
I want to unlock bootloader but the option OEM Unlock is greyed out on Developer Options.
I tried RSD Lite with many firmware available on https://mirrors.lolinet.com/firmware/moto/ali/official but none worked.
Does someone have a tip?
Thanks!
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
juicypoot said:
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
Click to expand...
Click to collapse
I already tried everything that is possible!
I flahed retail firmware through RSD Lite and nothing happens: allow oem unlock greyed out.
Maybe your OEM is already unlocked. Try running this command: fastboot oem device-info in fastboot and see what it says
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
adrianogoes said:
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
Click to expand...
Click to collapse
Still waiting here. How much time did you wait?
You can also try to delete user 999 and oem option should reflect under dev option.
bhati2710 said:
You can also try to delete user 999 and oem option should reflect under dev option.
Click to expand...
Click to collapse
What do you mean? Please explain
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
bhati2710 said:
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
Click to expand...
Click to collapse
Thanks for replying, but this didn't work. I tried one year, one month, 7 days before and after and it still is grayed out :crying:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
WoKoschekk said:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
Click to expand...
Click to collapse
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
mrsiri said:
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
Click to expand...
Click to collapse
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
WoKoschekk said:
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
Click to expand...
Click to collapse
The text is "connect to the internet or contact your carrier". I didn't flash the boot.img, but booted it. Like when you boot TWRP, but in this case it was the original stock boot.img
My bootloader says "flashing_locked", so it is not fully unlocked. And I can't unlock it without enabling the "OEM Unlock" Button ?
Yes, you have to wait.
WoKoschekk said:
Yes, you have to wait.
Click to expand...
Click to collapse
In the end I sent my device to a repair service. Thanks for the help, but I can't rely on waiting 7 days and assuming the button will re-enable itself. I need it fixed as soon as possible.
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
WoKoschekk said:
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
Click to expand...
Click to collapse
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
mrsiri said:
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
Click to expand...
Click to collapse
Yet the itch of simply waiting will now stay forever
mrsiri said:
Yet the itch of simply waiting will now stay forever
Click to expand...
Click to collapse
As soon as the bootloader is unlocked you won't have that trouble anymore.
WoKoschekk said:
As soon as the bootloader is unlocked you won't have that trouble anymore.
Click to expand...
Click to collapse
Good and bad News!
The repair service couldn't fix the problem so I wasn't charged for it.
The bad News is I'm back at the same state
This time I'll wait the 7 days.
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