Greetings all, I hope you can help me. My son imported a sim unlocked Claro version Razr i from Puerto Rico to use on AT&T. Well he got impatient and tried to root the 4.0.4 ICS firmware on here using one of the tutorials but he did not unlock the bootloader first. Now it is stuck in fastboot and I cannot flash a boot img to fix it. I tried to unlock the bootloader via Motorola's website but it says this phone is not available to unlock. Please help me out as he has a brand new bricked phone right now. I hope it can be fixed or it is a hard lesson to learn. Thank you all in advance.
Hi, have you tried hard-resetting the phone? You probably have, but I have to ask.
On the RAZR i, hold the volume down button and the power button together for about 10 seconds, then the phone should shut down and you can release those buttons. That should get it out of fastboot mode. I'm hoping that you could get it into recovery mode from there. Have you tried recovery mode? It will depend which version/level of Android the phone is on Android 4.0 Ice Cream Sandwich or Jelly Bean 4.1.
AW: [Q] Bricked Razr i with locked bootloader tried to root
You need the right boot.img for your current Firmware. It's pretty easy to solve.
fastboot flash boot boot.img.
The worst part is to find the right Firmware for your device. It has to match your region (Latam i guess)
Gesendet von meinem XT890 mit Tapatalk 2
Apologies for the tiny off-thread comment, but HSD-Pilot I tried to PM you and it is disabled. I recognise that you're a busy person. If you do have a spare minute, could you take a look at this thread, any ideas you may have would be greatly appreciated:
http://forum.xda-developers.com/showthread.php?t=2185954&page=2 :good:
AW: [Q] Bricked Razr i with locked bootloader tried to root
SharpnShiny said:
Apologies for the tiny off-thread comment, but HSD-Pilot I tried to PM you and it is disabled. I recognise that you're a busy person. If you do have a spare minute, could you take a look at this thread, any ideas you may have would be greatly appreciated:
http://forum.xda-developers.com/showthread.php?t=2185954&page=2 :good:
Click to expand...
Click to collapse
I'm aware of this problem, an user of our German Forum is searching for an solution, too. But i got no idea how to get into Fastboot, when the phone doesn't react. I got no chance to test it with my device, because i'm not willing to hard brick it
What i can tell you is that all these Problems are caused by an kb big file called gpt.bin (Bootloader). Take that out of an ICS Fastboot, together with the motoboot and you're safe to flash back from JB to ICS with RSD. (with an unlocked Bootloader of course)
Gesendet von meinem XT890 mit Tapatalk 2
Yesterday, my brother asked me to unbrick his Sony phone. It had an almost identical situation. However, I unbricked it! With the Sony phone, fastboot was not accessible while bricked, so I used 'flash mode' (green LED) and used an .FTF file to relock the bootloader, then fastboot became active again.
The .FTF file looks like this: http://forum.xda-developers.com/showthread.php?t=1924221
Is there nothing similar with RSD lite? We could enable fastboot by using flash mode, but I haven't seen this on Moto yet.
AW: [Q] Bricked Razr i with locked bootloader tried to root
From what i know the complete Bootloader is messed up. Usualy RSD won't let you downgrade the Bootloader. But after it's unlocked it works and i got no real idea how it effects the Device. I mean there's no error by downgrading it, from what i've read (like preflash validation error or similar).
So in my opinion the ICS Bootloader doesn't play well with the updated secure Levels of the other Partitions or they changed the adress / path to them. But i'm no Dev, just an usual Crackflasher. So i might be totally wrong
I know that Service Centers change the complete Motherboard after you send it in. So i guess there's no easy solution.
The unbrick tool seems to be working once, but after you try to flash an new Firmware you stuck with this damn Service Error.
Gesendet von meinem XT890 mit Tapatalk 2
Related
So i flashes the official austrian firmware(hutschison) and if I enter adb reboot oem-unlock it goes to the bootloader but then shuts down itself. so i end at battery loading anim and BL is still locked anyone encountered the same problem ?
Sent from my LG-P880 using xda app-developers app
Yes, i got the same problem, the only diffrence is that i have flashed EUR OPEN rom. but mij bootloader is 232-10
at least i am not the only one.. Anyone with austrian firmware unlocked the bootloader ?
Sent from my LG-P880 using xda app-developers app
well, my provider is not hutchison but im also in austria and using euro open version which works without problems. there is no need to use the austrian firmware when you dont have hutchison
Gesendet von meinem LG-P880 mit Tapatalk 2
but i have hutchison. and its branded
as far as i know theres no way to debrand it without the shop
Sent from my LG-P880 using xda app-developers app
you only have to flash euro open and it's unbranded.. !
i'm also from austria, v20a 232-10 bootloader.. hope there will be a way to unlock that sh*t!
these days i'll probably try to flash various versions, with and without sim card, hope to get another bootloader to unlock it !
or probably we have to wait for offizial hutchison firmware update v20x...
did you get it unlocked ?
Sent from my LG-P880 using xda app-developers app
my experience to unlock it
first I flashed the official europe open firmware. I tried to unlock it and get the LG security denied error(official method)...(I did a clean install every time)
now I am on the official has/hutchison(austria) firmware. I tried to unlock too. with the official procedure I got just the LG logo and then the battery charging logo.
then I tried to unlock it with this commands: "adb reboot-bootloader"....I just got the Lg logo. then I typed: "fastboot oem unlock"...my pc wanted to install the fastboot driver. I installed it. I tried it again. "adb reboot-bootloader"---}Lg logo---} then I typed: "fastboot oem unlock"......on the display I had the option to unlock the bootloader or not. I choose to unlock it. at the cmd was to see: bootloader is unlock now. after that I removed the usb-cable and the battery.
but in the hidden menu stays: it is locked
if I repeat this commands I get the message that it is already unlocked...
I mailed to the carrier (3drei) if there any official way to unlock it because I read that it depends on the carrier if it is unlockable or not. they wrote my back that the give no support for this I should contact LG....
by the way. for me is the europe open firmware better than the hutchison austria firmware...
I can't even install a ROM to get the EUR-XXX version. I flash the open eur version but it still says 232-10. With or without sim card... What can we do?
Unbranded official Slovak distribution ... same 232-10 cant unlock tried fastboot unlock but in hidden menu still "locked"
we dont have many options
1. LG releases a update where they fix this sh**
2. we find a way to flash to EUR-XXX
3. A dev implements a bootloader bypass.
4.If we have the encrypting script of the .dz files we could flash it via lg flash tool i think
Sent from my LG-P880 using xda app-developers app
I have a 232-10 as well, only a month old or so its unbranded bought from DiTech (big PC and PC Part suppler) in Vienna.
And I'm also eagerly waiting for an unlock.
This is so unfair policy from "Life's Good" ....
DavidXanatos said:
I have a 232-10 as well, only a month old or so its unbranded bought from DiTech (big PC and PC Part suppler) in Vienna.
And I'm also eagerly waiting for an unlock.
Click to expand...
Click to collapse
also got my phone from ditech in vienna, but i was able to unlock
Gesendet von meinem LG-P880 mit Tapatalk 2
I'm also having a big problem with this bootloader. Tried all the written methods that are described here and it's still locked. I can't understand why I always get a status in CMD -> Bootloader is unlocked now but when I go into hidden menu, it is not. (Not even a little bit logical to me) My phone is unbranded with a rooted 20a EU official JB installed.
gordon0001 said:
also got my phone from ditech in vienna, but i was able to unlock
Gesendet von meinem LG-P880 mit Tapatalk 2
Click to expand...
Click to collapse
Did you also get the ASWSWH (232-10) model?
or the ADEUWH?
I'm asking because according to geizhalts and the sticker on the box (printed by ditech) it should be an ADEUWH.
So i guess they got an other charge in and did not notice the change.
If you have the ASWSWH (232-10) how did you unlock?
scarfaceq said:
I'm also having a big problem with this bootloader. Tried all the written methods that are described here and it's still locked. I can't understand why I always get a status in CMD -> Bootloader is unlocked now but when I go into hidden menu, it is not. (Not even a little bit logical to me) My phone is unbranded with a rooted 20a EU official JB installed.
Click to expand...
Click to collapse
the output on cmd happens before the phone gets really unlocked.. I dont now why they implemented fastboot so ?
Sent from my LG-P880 using xda app-developers app
Sorry to take this a bit off topic, but what is the output you guys get from this command:
adb shell cat /sys/firmware/fuse/odm_reserved
I get this:
0x0000000000000000000000000000000000000000000000000000008000000000
Some people are speculating that having that result means that you have flashed the beta and made your bootloader unlockable.
I have never flashed the beta and have a 268-01 branded phone. I'd like to prove that hypothesis wrong.
Cheers
Sent from my LG-P880 using Tapatalk 2
I never flashed any beta just now (today) the original 20a for my phone with the officual LG tool
when I type
adb shell cat /sys/firmware/fuse/odm_reserved
I get this:
0x000000000000000000000000000000000000000000000000 0000000000000000
EDIT:
I just looked again and now it says
I get this:
0x000000000000000000000000000000000000000000000000 0000008000000000
So its changes, I have a 3 sim card in the device.
Can it be that shortly after the update the firmware locks the bits if one has the wrong sim card?
DavidXanatos said:
I never flashed any beta just now (today) the original 20a for my phone with the officual LG tool
when I type
adb shell cat /sys/firmware/fuse/odm_reserved
I get this:
0x000000000000000000000000000000000000000000000000 0000000000000000
EDIT:
I just looked again and now it says
I get this:
0x000000000000000000000000000000000000000000000000 0000008000000000
So its changes, I have a 3 sim card in the device.
Can it be that shortly after the update the firmware locks the bits if one has the wrong sim card?
Click to expand...
Click to collapse
That would be very strange, but who knows! What you are saying is similar to other reports in other threads! Is your bootloader 232-10? Thanks for helping btw
EDIT: did you do anything between the readings, like, attempting to unlock your bootloader?
Sent from my LG-P880 using Tapatalk 2
I have a motorola X with unlocked bootloader, but the flash another ROM, remains intact the stock ROM. So when I try with a custom recovery also remains the stock recovery.
I want flash my phone since all process stops, and sometimes off by itself.
Thanks for any help and excuse me my english.
Model: Moto X 1053 Nextel México.
I dont think that the bootloader of your phone is properly unlocked... From what i understand your post is saying that whenever you flash anything the whole mobile doesn't takes any affects... So still it must be Write Protected... AFAIK... Do this test and make sure that your Boot loader is completely unlocked...
Power off your phone
Wait for 5 Seconds
Press and hold power button and volume down button simultaneously for 4 seconds then release those buttons...
And look out for a yellow line or a any other white line saying Device Status Code
If your bootloader is properly unlocked it must say: Device is unlocked: Status Code 3
If it gives you any other status code... Then your Boot loader might be relocked thats why it must be saying bootloader unlocked on the startup by which i assume you are saying bootloader is unlocked... Checkt these out and tell us... We are always here to help others android owners..
Good luck..
Sent from my ghost using Tapatalk
whizinc said:
I dont think that the bootloader of your phone is properly unlocked... From what i understand your post is saying that whenever you flash anything the whole mobile doesn't takes any affects... So still it must be Write Protected... AFAIK... Do this test and make sure that your Boot loader is completely unlocked...
Power off your phone
Wait for 5 Seconds
Press and hold power button and volume down button simultaneously for 4 seconds then release those buttons...
And look out for a yellow line or a any other white line saying Device Status Code
If your bootloader is properly unlocked it must say: Device is unlocked: Status Code 3
If it gives you any other status code... Then your Boot loader might be relocked thats why it must be saying bootloader unlocked on the startup by which i assume you are saying bootloader is unlocked... Checkt these out and tell us... We are always here to help others android owners..
Good luck..
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. This is the screenshot of my device.
h ttp://i.imgur.com/vENGkWY.jpg?1
cer0n said:
Thanks for your help. This is the screenshot of my device.
h ttp://i.imgur.com/vENGkWY.jpg?1
Click to expand...
Click to collapse
Okay so i saw the screenshot.. Its properly Bootloader Unlocked..
Now the chances might be that your stock recoverry is either corrupted or damaged because your phone's factory reset is not working.. Flash the stock firmware of your phone through RSD LITE... Flash the 4.4.4 version and dont donwgrade... And after flashing the stock firmware... try flashing recovery again. Find the stock firmware of your device according to your model... find the model code at the lower back side of your phone its really tiny so you to have twist the phone to make it visible...
Sent from my ghost using Tapatalk
whizinc said:
Okay so i saw the screenshot.. Its properly Bootloader Unlocked..
Now the chances might be that your stock recoverry is either corrupted or damaged because your phone's factory reset is not working.. Flash the stock firmware of your phone through RSD LITE... Flash the 4.4.4 version and dont donwgrade... And after flashing the stock firmware... try flashing recovery again. Find the stock firmware of your device according to your model... find the model code at the lower back side of your phone its really tiny so you to have twist the phone to make it visible...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
I don't find the firmware of moto x Nextel México.
I've read in the web that has not released any firmware Nextel Mexico for moto X.
Is there any other solution?
Thank you
cer0n said:
I don't find the firmware of moto x Nextel México.
I've read in the web that has not released any firmware Nextel Mexico for moto X.
Is there any other solution?
Thank you
Click to expand...
Click to collapse
Which model is your moto x? I've seen nextel firmwares on file factory before... tell me the model of your moto x..
Edit: Sorry i forgot you mentioned above its a XT1053 nextel.. Wait for a couple of hours i have all links of stock firmware sites on my pc.. As i get back home.. I will try find a firmware for you.
Sent from my ghost using Tapatalk
whizinc said:
Which model is your moto x? I've seen nextel firmwares on file factory before... tell me the model of your moto x..
Edit: Sorry i forgot you mentioned above its a XT1053 nextel.. Wait for a couple of hours i have all links of stock firmware sites on my pc.. As i get back home.. I will try find a firmware for you.
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Motorola X 1ra Generación (2013), Nextel México.
Ok, thank you!.
cer0n said:
Motorola X 1ra Generación (2013), Nextel México.
Ok, thank you!.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-newbies-how-to-revert-to-stock-t3104208 follow this thread this will help you for sure.
Hi everybody, i was wondering if you know where i can download stock rom for my P10 cell phone. I tried to put this rom VTR-L09C605B151 to my phone and now it stuck in huawei logo. (this rom is for latin america ,im from Chile Movistar company)
the original version of the rom installed in my phone was the VTR-L09C521B101, if anybody knows where I can download the full firmware please help!!
the phone have only 2 weeks of life.
PD: I justo took it to Service, but they said that this problem is not covered by warranty.
any help would be higly appreciated.
thanks!!!!
How did you flash the firmware?
Flashed with adb. I have extracted the boot sytem and the other file and flashed boot first then the others. I can enter now in bootloader mode.
Enviado desde mi SM-J700M mediante Tapatalk
Right now i don't have the exact names. Let me reach home and I will post.
Enviado desde mi SM-J700M mediante Tapatalk
You can use firmware finder to download ur original firmware and use this tool to flash firmwares since u have unlocked bootloader https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I will try that. In case the original rom was not found. How can I proceed?
Enviado desde mi SM-J700M mediante Tapatalk
fmm1977 said:
I will try that. In case the original rom was not found. How can I proceed?
Enviado desde mi SM-J700M mediante Tapatalk
Click to expand...
Click to collapse
It's there but not full, maybe rebrand to other region.
thanks for the help. Right now I have sent the phone direct to huawei's service, so I will wait 2 days and see what happened. Stay tuned!
Maybe this will come in handy
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L09C521&firmware_page=0
Hello, I finally did not fix the phone, because they tell me from huawei that you can not put an official rom, that the only way to fix it is by placing an unofficial rom. I do not know if it will be true or not. The truth is that my phone has become a beautiful paperweight. :crying: Please, I need your help to revive my phone.Do i need to wait until official rom comes out full? And apply adb just as I did before? Extracting the files and uploading them to one ?. Any help is welcome. Thank you all!
I have another question, is there a way to put a full rom but another version with other method?
because before brick my phone I have flashed in this order:
boot.img
recovery.img
system.img
from the VTR-L09C605B151 version.
I dont know what means C605B151, I dont know why it didnt worked, because this rom is for latin american.
or what if I install TWRP then update the rom?
I've just done mine with dc phoenix cost about £35 by the time I sussed it but all working now as I'm typing on it and mine was stuck on boot screen but able to get into fast boot
well, finally im trying to rebrand my phone to VTR-L29 eu version, but Im having problems with bootloader.
Right now my bootloader says relocked and FRP lock. tried with fastboot oem relock and unlock and nothing happens.
what can I do now?
u.u
Hi again, the thing is that my phone shows Phone relocked, but adb shows to me that bootloader is unlocked, if I try to unlock again says remote command not allowed.
Anybody knows why it shows like this?
thanks!!
Finally!!!! my phone was restored and is back!!!
I have used the funkyhuawei rebranding method (since it was impossible to unlock my phone) they have a method that you can rebrand with locked phone. Paid 46 dollars but it was worth!!
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631
Personally, today I received the update of the "December 2018" Security Patch from my Mi A2 (Already with the Pie), but after "extracting the files, updating the apps" and request to reboot, my cell phone does not exit the ANDROID screen anymore ONE.
It stays on this screen until it turns off again (automatic).
Did someone else do that?
Do you know how to correct this error ??
Thank you!
Do you have unloked bootloader?
Odesláno z mého Mi A2 pomocí Tapatalk
Pero55 said:
Do you have unloked bootloader?
Odesláno z mého Mi A2 pomocí Tapatalk
Click to expand...
Click to collapse
I have already tried to access recovery, as well as reboot the bootloader through the fastboot, but nothing. He either enters the Fastboot, or stands still on the Android One screen.
I can not unlock Bootloader because it has no way to enable usb debugging and disable oem locking since it does not access the system.
Im in the same exact situation. Got the update and phone gets stuck at boot screen.:crying:
You have to enter Edl mode and flash rom with mi flash. I had the same problem and solved it. this is the only way for the lock bootloader.
https://youtu.be/i3OU4DOd7aY
https://en.miui.com/thread-3524265-1-1.html
Odesláno z mého Mi A2 pomocí Tapatalk
ewertombarbosa said:
Personally, today I received the update of the "December 2018" Security Patch from my Mi A2 (Already with the Pie), but after "extracting the files, updating the apps" and request to reboot, my cell phone does not exit the ANDROID screen anymore ONE.
It stays on this screen until it turns off again (automatic).
Did someone else do that?
Do you know how to correct this error ??
Thank you!
Click to expand...
Click to collapse
I have just received this OTA and now I don't know if I should install it, were you root user or did you have modified the software? Mabye a Magisk module not being deactivated/uninstalled before the OTA caused your bootloop...
Doing this wont void the warranty?
i have the same problem but my bootloader is unlocked. i dont want to lose my userdata, what should i do?
coree said:
i have the same problem but my bootloader is unlocked. i dont want to lose my userdata, what should i do?
Click to expand...
Click to collapse
Have you got TWRP or any other custom recovery installed? If not, install it and copy your data from there to your PC, then flash again all software partitions and when you reboot your device, restore the backup. It should work...
If not, you can try the experimental way and flash again all the partitions except userdata, but I'm not sure this way will work...
once i unlocked the bootloader i didnt do fastboot unlock critical. but i need it to flash the partitions. if i do it know will all userdate be erased?
coree said:
i have the same problem but my bootloader is unlocked. i dont want to lose my userdata, what should i do?
Click to expand...
Click to collapse
Just use flash_all_except_data script. It worked for me with extracted ota payload, and you can now use full fastboot 10.0.2.0 image - link is available.
---------- Post added at 07:23 AM ---------- Previous post was at 07:19 AM ----------
coree said:
once i unlocked the bootloader i didnt do fastboot unlock critical. but i need it to flash the partitions. if i do it know will all userdate be erased?
Click to expand...
Click to collapse
Unlocking will wipe all userdata. This is why I always unlock everything right after buying the phone.
Same problem here
I also got the exact same problem: stuck in androidone screen, with a locked bootloader. I did not want it to open it myself to avoid losing the warranty, so I have sent it back to the seller (eGlobalCentralUK), they should be able to fix it easily...
I find it very disturbing that Xiaomi has not been helpful giving a solution (they just kept referring me to the seller) , even though they are clearly to blame...
Same problem for me too. I'm struggling with it for four days with it.
Sending the phone back is my last resort, I prefer a DIY solution.
Unlocking the bootloader is the problem at this moment. When it is unlocked I can reflash the stock android ROM again and hopefully the phone will work again.