Related
I'm currently stuck in a boot loop, with no way to access my rom or recovery. I can only access bootloader. The boot loop began happening soon (around 2hrs) after flashing MIUI; The rom was running, and out of nowhere it just began cycling. Any ideas on how I can get out of this boot loop?
Edit: I'm no longer in a boot loop after installing a different full system PC36IMG.zip. Instead after the initial splash screen my evo goes black and vibrates 5 times, then my green LED starts flashing. It stays this way until I remove the battery.
So far I have tried:
Flashing RA's recovery image using fastboot. (The flash was successful)
Using RA's recovery PC36IMG.zip. (The installation was successful)
Using an RUU file renamed to PC36IMG.zip (The installation was successful)
Using a Sprint Lover's file renamed to PC36IMG.zip (The installation was successful)
For all of these the process of installing and flashing went fine. Yet when I would turn on my phone it would just go right back into the boot loop.
*I've been editing this post as I've tried new things, so you don't need to read through the thread to help me.
Anyways I'm at my wits end here, pretty worried, and phoneless, so any help would be amazing.
Have you tried ADB from bootlaoder or fastboot. May be able to get recovery that way.
I'm trying to do a bit of research, but am a little confused on what adb is. It's part of the android sdk? I can't seem to find it, or know how to launch it. Is there a thread somewhere that covers it? I'll keep doing my research, thanks for the tip.
Its a command terminal but if you are not familiar with it you probably wont get it right away! I am just starting to learn this myself. VERY VERY useful tool though! Here a link.......
http://forum.xda-developers.com/showthread.php?t=502010
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
thanamesjames said:
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
Click to expand...
Click to collapse
Jeez sounds like you have a better grasp on this than me already! LMAO
haha, well i'm not too sure. Have you gotten you're evo to be found? Right now while using adb, I'm just told "device not found." All my drivers should be properly installed because I had to install them when I used unrevoked. So I choose fastboot on my evo, and then it shows up on my computer as "android 1.0" under devices and printers... but adb doesn't find it.
I was told to get rid of my drivers and re install the recommended ones before starting. It recognized mine right away. YouTube also has nice how to videos on ADB.
Is there any way you can point me to the recommended drivers? I think that second link you gave me is the same as the first also.
Edit: Every single guide I see on the internet about adb, says use debug mode within the actual rom. However I'm obviously not in a rom, i'm in bootloader, and for the life of me can't get adb to find my phone.
Edit2: Ok, so maybe I can only use fastboot. Right now when trying fastboot it just says "waiting for device," even if it didn't say that, what would i need to do to get on the road to recovery?
So I'm starting to get scared. At first I figured this was something I could fix... and now I'm not positive it is. I've used fastboot from terminal, trying to flash recovery and it says "FAILED (remote: not allowed)" I'm starting to get desperate, does anyone have any ideas?
I'm sorry to bump this, but I'm really struggling here... because I'm phoneless and all , I worked at this for 5 hours last night from 9-2, and now I'm at it again... and very worried. I've read that theres almost no way to completely brick your phone, but I'm starting to feel like I did. It seems like no matter what I flash it just keeps boot cycling. Thanks for the help.
go to the bootloader and ruu it
I have... I took the ruu file and renamed it PC36IMG.zip, went into bootloader and it went through all the steps with "OK"s, rebooted, and went right back into the boot loop.
Specifically I used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip" from here,
http://goo-inside.me/evo/stock/RUU/
Is there a specific number version of RUU I should try? I just tried the most recent.
You have to use the ruu that matches your radios/software etc. How did this boot loop start? Give us all your phone info, rom, hboot version, radios etc.
Sent from my iphone slayer 4G
I flashed a CM7 nightly, from CM, about 2 weeks ago. Yesterday, still using the same nightly (build 1 or something) my phone seemingly out of nowhere rebooted - I wasn't even using it at the time. When it went back into CM7 it acted as if I had never linked a google account to my phone. The first thing that came up was the android google apps screen. Anyways, I decided I wouldn't stick with CM7 until at least an RC was out, so I wiped data, cache, and davlik and flashed MIUI. I used it for about two hours, didn't do anything out of the ordinary, and once again seemingly out of nowhere it rebooted... except when it did it went into a cycle and never reached MIUI, and wouldn't go into recovery, I could only access bootloader.
Anyways, I'll tell you what bootloader says my phone versions are, but I do believe the info all changed this morning when I flashed the ruu file.
SUPERSONIC EVT2-3 SHIP S-off
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Check your pm
Sent from my iphone slayer 4G
Are there any other thoughts on how to get on my feet?
In addition to booting an RUU file as PCIMG36 I've also tried a Sprint Lover's image as PCIMG36. Even though both installed properly, my phone still staid in the boot cycle afterwards for both.
I've been suggested, and have seen other users suggest on other threads, to try adb commands, but I don't know if i can access adb while the phone is in bootloader. I have however accessed fastboot, are there any commands that might help me? If not, can I use adb while in bootloader? Thanks.
Well I tried a new PC36IMG.zip file and I'm no longer stuck in a boot loop... instead as soon as the HTC EVO 4G splash disappears my phone goes black and vibrates 5 times, and my green LED flashes.
Good? Bad?
This would be the 300th something thread I've read on this subject and this is exactly were I'm at with my EVO minus the last post... I was using warms2p2 with the hdmi kernal everything working fine then I went to change my notification ringtone and bam went into boot loop and never came out. SOOO! it would be nice to save this unit... any help forum members would be great I've tried every RUU out there from fastboot from sd card nothing.
Very intesting that this thread ended this way... please share if you think you got this whooped. Thank you in advanced.
Love the revival of old threads...but did you try changing the kernel?
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip 3.70 RUU, just rename to PC36IMG and flash in the bootloader if you want to run the RUU.
I would be so greatful if someone could help me, I think I have really messed up.
Coles Notes: I flashed the 4.0.4 image to my System partition which I am pretty sure should have gone to the boot partition now... Holy **** I'm dumb.
Anyways now my phone is just stuck saying Google. Anyone who can point me in the right direction of even a System image I can flash over top I would be so greatful.
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Moleculor said:
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Click to expand...
Click to collapse
Not a dumb newbie, checking if bootloader still works is a good idea
@OP: If you can get in the bootloader, your best bet would be unlocking, installing CWM and then flash a ROM through it.
You can also flash the stock ROM via the GNex toolkit.
Just read the guides and information here in the forums, it seems confusing at first but is really simple once you get used to it.
Good luck!
Thank-you for your quick response. I have CWM installed and can get into the bootloader. the problem now seems to be I cant get the device to show up in windows I always get <waiting for device> when going to flash it. Any ideas? I have been searching the forums trying to find an answer but nothing so far seems to have worked.
Another dumb newbie thing, but when you plug the phone in to the USB port on your computer, does your computer show the phone as having connected (ala the ADB driver in your Device Manager in Windows)?
If not, double check to make sure your ADB drivers are installed. I doubt they aren't, seeing as how you were flashing stuff earlier (from your computer, right?), but it's a wild guess anyway.
Thanks to everyone for the advise. Yes I could see the drivers and they were working perfectly according to device manager. However I guess it was stuck outside of debug mode?
Anyways from the boot menu the program was able to detect it, flash 4.0.4 to the phone, and then I was able to install the canadian radio without issue (hence the reason why I did this in the first place, we are stuck on yakjuux with 4.0.1).
Thanks again to everyone, great learning experience.
Sure thing!
Glad it worked
As a future reference, the "Boot Menu" is actually where you need to be for flashing via PC. The commands won't come through if you're in recovery.
Make sure to make an Android right now!
You enter CWM Recovery, go to backup and restore and then hit backup.
In case your phone ever messes up while you're not close to a computer, you can just boot into CWM and hit "restore", it's as easy as that.
I always have 2 recoveries on my phone just in case.
So, hey guys, i've used this site a lot in the past, but now i need some help / advice, so i've registered. The following isn't going to be pretty but i'll explain it as best as i can.... infact, i can paste the email i sent to Sony asking for advice, it was this morning, i don't know if they operate or care
Hello people at Sony, my stupid head appears to have bricked my Xperia Arc S Android phone, it was still under warranty until i decided to unlock the bootloader, then i was having trouble restoring it back to stock android, this resulted in me trying to lock the bootloader. But alas, nothing now happens except a lonely green light flashing every so often, if i hold down menu, a blue light appears, which is charming, but then it dissipates and im left lonely again. With just a bricked phone and little dignity.
What are my options, by rules, it's void of warranty, can it be fixed? Can i pay for it to be fixed? Will my Natwest Insurance cover it on the grounds of Accidental damage (My stupidity) and Breakdown due to electrical fault, that being, no electrical softwareness is been transitorized.
I decided to go custom due to the wait for the Xperia update for my phone, out of the 273 S-I variant versions of the Arc S, 246 have gotten the update, but not mine, months had gone by, day turned to night, night turned to day, and i got desperate, i decided to root... for the first time. (And now last)
What i did learn, apart from technology will rise up and defeat us all, is JellyBean works very well to some degree on this phone, HOWEVER, the lack of Flash player caused bad results when playing content, im not sure what piece of code on the JellyBean CM10/Paranoid Android release was rendering it, but if you can get past the lack of flash for this and render images in its mobile bravia engineness then it will work a treat, and i mean it, it really did run well, obviously it was customness, but i digress...
Can anything be done? I do so love my Arc S, and just so you know, if it can't be repaired and I have to change phones, it will still wear the brand logo... Sony Ericsson... and if its your newer phones, that lack Eric's Son, i shall scribe his name proudly across the top with a sharp implement with pride. (With the care of an Adult, or someone equally minded)
Thank you lovely people over at Sony.
Stuart Herrington
Click to expand...
Click to collapse
So, basically it doesnt boot, apart from it does vibrate with button holds and the LED flashes. I tried flashing it with flashtool and stock ROM, but flashtool came back saying it needed unknown sources and debugging mode activated, which makes me think, it could be salvagable and not bricked, however how can i change those settings if i can't get into the phone itself, is there a bypass?
On a side note, i can Hold Menu, plug the phone into my computer and it goes into blue light mode, i cant remember the term for this
but its what i was using for flashboot, you reckon i could flashboot out of this? I was trying so many different methods to try and custom rom my phone that everything got confusing, which was best to use etc, and on another note the phone never booted when i tried to relock it, so im unaware if it finished, it didnt boot at all, and this is the point im at now.
Fortunately i picked up a Xperia U for £135, second hand, actually cheaper than my Arc S second hand, crazy really, but you can see why with the size difference and a couple of small spec differences.
Any help would be appreciated. This isn't obviously the best situation but i'm wondering if anyone has encountered this stupid mistake i've cast upon myself XD
Thanks in advance.
Wait...
I've checked the fastboot status of my phone using Flashtools, and it says my phone needs to be rooted first... hmmm it was rooted, maybe it got undone with the bootloader thing, i guess i can try but i can't access the phone to debugg or allow unknown sources.
Hi Stu15,
The fact that you can boot holding down the menu button is good.
You can probably flash a custom kernel onto your phone this way using the following command.
Code:
fastboot flash boot boot.img
If you have a rom that you want to use, then it usually comes with a custom kernel (called boot.img most of the time) inside the rom's zip file.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
So what you do is copy the rom to your sd card (just plug the card into your computer to do this).
Then flash the custom kernel that came with the rom.
Then boot into CWM and flash the rom (you should clear the cache and the dalvik cache before flashing the rom).
If you don't have a preferred rom, then have a look at this thread - http://forum.xda-developers.com/showthread.php?t=1653188
It has lotd of helpful links, near the bottom of the 1st post are a few roms you can try.
I hope that you come right.
Take care,
Hotfingers
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
stu15 said:
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
Click to expand...
Click to collapse
cool, well done. :good:
So i think i overlooked something while using "low effort root". I though the steps just fine, but at the end i overlooked where itsaid to wait for the phone to reboot then type "LEAVE" to exit. Well i just left. I know, im a noob,but ive done this before using "rockmymoto" on my droid maxx. (which to me seemed more difficult)
Anyway, im stuck in "download mode". I can remove the battery and attemp to boot, which gets it stuck at the boot screen. I can even boot up into stock recovery, but none of the options do what they're supposed to. (factorty reset doesnt evev work.). Ican still boot into "download mode".
I think i might be stuck somewhere btween stock and root.
My appologies if this isnt the right forum in whick to discuss this, is there a way to fix this issue?...................................Ive also searched elsewhere , askung is last resort for me.
Thank you in advance.
Moto G7 Play(MetroPCs)"Bad Key?"Problems-WARNING-I'm a beginner to smartphone repair!
Okay.
First, hello. Hope everybody is having a nice day. If I hope it gets better.
Second, I don't know much about smartphone flashing, locking, unlocking, backflipping, holahopping, or anything else.
Now, I understand computers just enough to build my own for gaming and editing or messing with Linux, Windows, etc. However, smartphones are relatively out of my comfort zone.
Anywho, I'm looking for better compiled and straightforward information and most likely help with this smartphone called a Moto G7 Play.
So, I got this smartphone a week or two ago from Walmart clearance, and it has been running fine. *Except* Every, single, time I cut on this phone it used to say, "N/A". I had no idea(and probably still don't) understand anything about it and decided to look into it. Turns out this phone has an "unlocked bootloader" meaning it can be "rooted" and "custom rommed". This similar to installing Linux on a Windows PC or one of the Google Chromebooks. right?
Anywho, I did take it back to the Walmart section and left it with them for two days where they said they would "fix it" only to give it back and them saying "Igot no idea". It's absolutely fine for them not figuring it out cause I've gone in and fixed there computers, some broken televisions, and alot of there forklift equipment.
Back to the topic at hand, I decided to try and fix this small issue only to dive headfirst into an unknown field of electronics beyond my education. So, I learned about Developer Options, ADB and Fastboot, Custom Roms(which I'm okay with not doing right now in life), and how to renable the bootloader.....
....Turns out. The Moto G7 Play happens to be pretty difficult to flash or reflash because of "stock firmware" which is supposedly unprovided by Lenovo/Motorola. And, when trying to finds ways to renable the bootloader, turns out many others had this problem and I discovered this site. Anywho, I found this post saying to use this program called "LMSC" or "Lenovo Moto Smart Assistant" and it said that all I need to do is follow the programs instructions and the Moto G7 Play would be fixed.
So, I used this LMSC and used the "rescue" function which is supposed to bring the phone back to it's original factory state. And, this would've been great.....if it actually worked. BUT, it didn't. And now, the Moto G7 Play will cut on saying "bad key" instead of "N/A" and of course it still has a "unlocked bootloader".
I know very little on "ADB/Fastboot". So, I've been using it and only learned of "adb devices", "adb reboot bootloader", "fastboot devices" and "fastboot oem lock". Each time I do this, the *bootloader* is still *unlocked*? and the *bad key* is still on every, single, time.
So, if anybody could please describe to me or help me in any way on this Moto G7 Play(MetroPCS Model: XT1952-6)....
1.) What is "bad key", and how do I fix "bad key"? Or, remove "bad key"?
2.) Is having a "unlock bootloader" a bad thing? If so, how do I fix it?
3.) I have tried entering "Recovery Mode" on the Moto G7 Play and each time it says "No command". I assume that this is also bad and wondering. How can I fix "recovery mode" and get passed "No command"?
I would be very grateful to anyone who can spare any part of there time in helping a fool like me understand these problems. I see a lot and I mean A LOT of individuals experiencing and asking similar based questions to mine. Yet, I have no idea what each person goes on about considering I've never done any of this before. Nothing wrong with others wanting to fix or customize phones that still have good use in them. I am still updating and upgrading PCs all the time around many school districts and even do local builds of PCs for others in editing and gaming. I understand when OEM providers lock units( or in a phone's case, devices) in order to make sure the user can't bridge off there own path by customizing or enabling features not covered under their limited warranty policy(my nicest way to put it). I am just looking for either information or help on this smartphone which seemed great and was even *unopened* yet was sent straight to clearance for "unknown reasons"(which is problems that came with the phone). I can't send the phone back to Walmart. I can't get help from Motorola or Lenovo cause I'm somehow the one who "damaged" the phone. So,....I need help, please. And, thank you
Right "Bad Key" can be ok. have you left it 2 minutes to boot? In recovery you may get bad command on stock. That's fine and normal as well. Just hold power then click the volume down and it should pop into recovery, but you shouldn't need it. If you want to try custom roms take a look at @Linuxassassin 's guide on the forum "How to install android 10"
00p513 said:
Right "Bad Key" can be ok. have you left it 2 minutes to boot? In recovery you may get bad command on stock. That's fine and normal as well. Just hold power then click the volume down and it should pop into recovery, but you shouldn't need it. If you want to try custom roms take a look at @Linuxassassin 's guide on the forum "How to install android 10"
Click to expand...
Click to collapse
So, "bad key" is ok? I don't know? Reminds me of the days where the first Xbox I thought had a bad CMOS battery and the timer could never work, so I always had to reset the time/date on everytime only to figure out until it was too late that it was a capacitor meltdown.
I'm just worried about the "bad key" one day crashing the entire phone's stock firmware and Android OS. Ya know?
I personally don't understand what "left it 2 minutes to boot".
I can still get to the bootloader by pressing the power button and volume down. Once I'm in the bootloader, I get on over to the recovery and I tried your method back then and again just know(for re-curiosity), but it wouldn't work.
A while back, I found also other ways of trying to get into recovery mode by holding the volume up button the pressing power button. Pressing the power button for 10 seconds then volume down. Pressing the power button for 10 seconds then volume up. Pressing the volume down for 10 to 15 seconds then pressing the power button. Pressing the volume up button for 10 to 15 seconds and then pressing the power button.
Each method couldn't get me into recovery mode and even before using the LMSC I couldn't ever get into recovery mode by those same methods said before. And, I'm surprised that it has a locked recovery mode on stock. But, it has an unlock bootloader? That happens to be something that I don't know about and would like to find some info on.
I also checked out @linuxassassain guide on how to install android 10. I don't know much about custom roms and, personally, I own a Nokia 6.1 as a work phone(cell phone and home phone on my AT&T carrier) and it has Android 10 cause it runs Android One.
However, that is my cell phone. And, Android One is great in that I don't mess with too many settings and I get constant updates that are sent out and help the phone run as my daily cell phone.
Plus, I notice that I use my Huwaei Y536A1 Fusion smartphone as my daily device(I own two now thanks to my father upgrading his cellphone too). I use it to listen to music, watch videos, etc. All the while, the Huwaei runs Android 4.4.3 KitKat, and I'm happy with it. When set up correctly in the settings, the phone can last just as long as the Nokia6.1 and Moto G7 Play in battery life when watching a YouTube playlist for almost 8 hours. It's crazy how this old phone can work so easily.
I decide to try and upgrade to this Moto G7 Play and that's when the "N/A" issue along with me using the LMSC to "rescue" the phone only to get "bad key".
So,....I'm pretty stupid in trying to fix this Hahaha XD
Either way, I'm ready to completely mess with the phone if need be cause it cost me only $30. I'm just wanting to fix this strange "bad key" issue now also with not getting into "recovery mode". And the "unlocked bootloader"(I don't know if this is an issue)? I can get into recovery mode on my Nokia 6.1 and Huwaei Y536A1 Fusion easily, just don't know why with this Moto G7 Play. Weird?
Yet, the Moto G7 Play still powers on and runs like it always does. I go into Settings>System>Developer Options and still find "OEM unlocking" greyed-out and saying "Bootloader is already unlocked" everytime since the day I bought it. It's just weird?
Anywho, flashing into Android 10 is kinda a "no go" considering "TWRP", I believe it's called?, has no official flash on Moto G7 Play which should be called "Channel", right? I would have to do something called a "dirty root" as described by another user to install something called "Magdisk", right? , And then flash a custom rom like Android 10 which all of this as I'm noticing in each forum seems to be a great hassle among many users. However, I'm only describing what I'm reading/seeing and considering the experience I'm having with this Moto G7 Play. I'm not too confident flashing it just yet.
So, still the questions do apply in that....
1.) I would still like to find a way to remove "bad key" whenever I boot up. Even if the "bad key" happens to never be removed from the stock firmware, but from the bootup screen at least. I don't know if this will require a "root" to happen for it, but I'm willing to try. Yet, I don't think it'll work considering I have no idea how to do it for this exact Moto G7 Play(Model: XT1952-6 by MetroPCs) and many others on this XDA platform can't seem to do it either.
2.) It seems the "unlock" bootloader" is not going away even if I use the "fastboot oem lock" on the Moto G7 Play. The bootloader shows it's unlocked and the developer options shows it's OEM unlocked. Which is weird cause I never unlocked it, and it came *unopened* by MetroPCs on a pallet that a Walmart employee and friend found a note on it saying for it "Goes onto clearance". So, I believe that there is a much, MUCH deeper rooted problem considering the "N/A" at the beginning of the bootup and now "bad key" at the bootup. I'm just wondering if the "unlocked bootloader" happens to be an issue".
3.) Same as "bad key" and "unlocked bootloader", I still got no idea on how to get into "recovery mode" I've heard from the Walmart employee that getting into "recovery mode" is important considering it could help me repair. I can't access it by volume and power button presses. And while typing this, I'm starting to try the fastboot methods yet still show up with the same issues in that all I get to is "No command". I'm still *highly unfamiliar* with "ADB/Fastboot" and I know of the many albeit confusing-to-me tutorials guide on these XDA Forums. I have only looked up ways for the Moto G7 Play by MetroPCs methods into getting into "recovery mode" yet to avail.
Will still say, thank you for the reply and sorry I type way, way, WAY too long. I'm just trying to cover all the basis on this Moto G7 Play by MetroPCs and it's current state. I thought I would go here as a last resort to see if I could get info and/or help on this smartphone. Plus, if anybody has future issues like I do, hopefully, I can leave a more coherent guide for others who are beginners(and I mean actually beginners) like me to find a better and easier way to comprehend the issue with there Moto G7 Play.
Thank you and hope you have a nice day.
You can replace the bad key screen with a logo.bin, which can be flashed with fastboot. I have attached a black Google logo that can be flashed with fastboot. You will have to unzip it first. Then enter bootloader (turn phone off. hold vol down + power when starting up) Then open a terminalo/command prompt window and enter the following commands:
Code:
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
This will flash it to both slots on your device.
Any questions feel free to reply again
Hello. This is still me. EmileLonghart. Forgot my password. Hehehe....I'm stupid.
Anywho, I actually already did put a new logo.bin file on it XD.
I kept researching and tried the Magisk to root with a patch file. It bricked it, but turns out LMSA's Rescue function can reflash the stock firmware(with the "bad key") on it again as a way to always rescue it.
So, then I tried each and every stock firmware from mirror.lolinet, used all the boot.img files, did another form where I typed out each fastboot command imaginable from the same mirror.lolinet stock firmware, tried to use the mirror.lolinet stock firmware in the LMSA, AND tried renabling the "recovery mode" each and every time or "unlocking the bootloader".
Needless to say, nothing worked for too long. But, I flashed it back on the stock firmware provided from LMSA, and I'm back to where I was with "bad key" again. I essentially bricked or froze this phone so...many...times! But that LMSA program is awesome by the way. I don't care what anybody says. That program always revived the phone after me constantly putting it into cardiac arrest XD.
Either way, I did discover a few things for me personal that might be useful for others and about my Moto G7 Play phone and what was exactly wrong with it.
1.) LMSA is the best to revive a bricked phone even if it says "bad key" or anyhting else.
2.) LMSA can flash other stock firmware from others on there program. Pretty cool
3.) With the Magisk patch firmware, I was able to enter the recovery mode before all the text turned to white bars then died(LMSA came to the rescue for that one too).
4.) I finally learned on my own thanks to trying to unlock the bootloader that the "recovery mode" was "corrupted" from what I guess was MetroPCs. Whoever used it before, unlocked the bootloader THEN they flashed stock firmware back onto the Moto G7 Play(Model:XT1952-6) without ever "relocking the bootloader". This is what gave the "N/A" as the first logo. When I flashed LMSA, "bad key" was displayed cause it is finally telling me that something on the flashed firmware is off which is actually that the bootloader is "unlocked" and canNOT be "relocked".
Hope this makes sense.
5.) I discovered the "logo.bin" a while ago before doing ANY of the other stuff I was doing. Turns out, you need to type in "orange" into the bottom left corner of the *MotoBootLogoMaker* program(which you'll need to use in order to change the bootloader exactly on this Moto G7 Play. I tried doing it without the program and...yeah...that bricked it too XD.
But, yeah. applying a new logo also will not remove the "bad key". I tried covering it up with many different logos. Annnnnnndddddd, yeah no. Didn't work. Only the MotoBootLogoMaker program worked, but I''ll try yours too. Future me speaking, "bad key" is somehow still there. Like a tree through a windshield, it's persistent and unavoidable that "bad key" XD.
So, this is all I've learned. I'm surprised I kept going despite bricking my phone hundreds of times. I've been using it since 5:00pm Us Central Time and it's now 9:57pm. It's at 63% and runs just fine with the custom logo.bin that still keeps putting the "bad key" in the corner in white text on a dark background or black text on a bright background(remember to type and replace "orange" in MotoBootLogoMaker to change the logo.bin in a or b).
At least I've learned A LOT from all the passionate, helpful individuals on this XDA Forums like youself. I think I managed to find your post I believe on this Moto G7 Play Forums. You also brought up the Xbox root and unroot functions when describing the a and b sections with regular mode and recovery mode by flashing Magisk patch file, right?
Anywho, I'm very grateful for everyone on these forums working with others and providing info for enthusiast, repair, and plain curiosity. Of course, even though I put a post to ask for info or help, I managed to do everything the *hard way* by myself. And on each failure, I learned more and more on how and what to repair and what wasn't repairable on the Moto G7 Play. My model has a very "bad key" source code that by the time I tried to repair the "recovery mode" by "relocking the bootloader". I would only end up bricking the Moto G7 Play and paying only $30 for this phone essentially made me say to myself 'You know what? If it dies cause I'm trying to fix it, then it take that brick to the head like I did back in boot camp."
I just want to say, 'Thank you' to everybody on this forum for what y'all do and helping others. I still wish and would like say that the XDA Forum still needs to be better in making a coherent guide that should be simpler and without having to go to hundreds of multiple links explaining something that should take like 5 minutes or less. Like everybody talks about the ADB and Fastboot programs as though if like 'You completely understand this complicated Command Prompt that is only explained as well as the nervous system of the human body. You know? Like how to make rockets that only the government decorated with a bouquet of heavenly fried chicken legs by Gordan Ramsey. It's as simple as that." If nobody understands sarcasm, I'm essentially saying that it's better to be clear and concise then straightforward and confusing. Still, great work and everybody is being very, VERY helpful and I'm extremely grateful. It's just that communicating these technical terms that are constantly changing is difficult for beginners only looking for ways to repair there phones or understand functions or programs.
I hope that communications like creating a bulletin board of repair guides or other guides could be on the top of the forums for those looking for better comprised ways to use programs on there phones.
For you, I just want to say, 'Thank you so much for your help.' You have been very patient with me and I am extremely grateful for all your help. I'll continue to look into the "bad key" logo.bin and try to find a better way to cover it. I did use yours and I'll keep trying others. Who knows? Might find an awesome pictures to put on the logo.bin. So, thank you and I hope you have a wonderful day...or night...I don't know your timezone. I hope you have a good day(Ther. I cheated XD )
Bad key or the long string of numbers can be changed to N/A by removing the boot.img signature. Unpack it, look in the split-image folder, delete the files with avb and sig in the names. There should be two total. Repack and flash.