Related
To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Could you post what you did or tried to do that bricked it?
99 times out of 100 rebooting will fix the "waiting for device" problem, especially if the PC drivers are installed appropriately, but I'm guessing you already tried that. I'd do it a few times, why not?
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
soupmagnet said:
Other useful information would be....
What OS you are using
Whether you are using stock or custom rom
What versions of FFF and recovery you are using
When the incident occurred and the events that surround it
Your level of experience
How familiar you are with your OS
How familiar you are with command line interface
Your mother's maiden name (OK, maybe not)
You get the idea.
Click to expand...
Click to collapse
Win7 64bit Ultimate
Stock
It's a clean kindle with nothing on it that got bricked while I was rooting it, some how.
My experience is really only a 1 time root when i first bought it back in January.
Very familiar with my OS.
Average with command line interface
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
nchevaux said:
Assuming the kindle is powered down and unplugged from the computer.....press the power button as you normally would to boot the device. What happens? The more details the better. I'm still not sure how exactly you got in this situation. Obviously you were trying to root. With what....KFU or command line?
Click to expand...
Click to collapse
it stays on the kindle fire logo until i hard reset it.
I was using KFU when this happened.
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
soupmagnet said:
Go here
...and download FFF1.4
Mount your sdcard while in recovery and transfer the FFF1.4.zip from your computer. Install FFF1.4 in recovery (no wipe) and reboot.
As soon as you see the Blue kindle fire logo, hold the power button until you see options show up on the bottom. Use the power button to scroll through the options and select "Normal Boot"
Click to expand...
Click to collapse
how am I supposed to put it on the kindle... Did you not read my other posts?
It won't let me do ANYTHING to it.
Did you install the drivers from kfu with your kindle plugged in?
needhelpplease3 said:
how am I supposed to put it on the kindle... Did you not read my other posts?
Click to expand...
Click to collapse
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
needhelpplease3 said:
To make a long an annoying story short, I've bricked my Kindle, tried every way possible on this site to fix it, but nothing helped.
Click to expand...
Click to collapse
Don't make a long story short. The more information you can provide, the better.
I've tried all different programs and it all leads me to the same problem, it doesn't recognize my kindle.
It's not that my computer doesn't recognize it, because It's drivers were all correctly installed, and it doesn't give me errors. The programs are the ones that are not picking it up.
I've heard about it being in fastboot or something, but I've tried going that route, but the stupid thing would stay at waiting for device, forever.
I really need some help on this, because It's been bugging me for the past couple days.
Any help?
Click to expand...
Click to collapse
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
soupmagnet said:
Let me explain something to you, friend. When you sign up for XDA with a name like "needhelpplease3" that tells me that you are not here to be a part of the community and are for one reason and one reason only, you need help. A person such as yourself should tread very lightly when asking for help or you may miss out on what may be your only hope. I absolutely did read your other posts and I'm trying to help based on what I've seen. Your lack of information is making it rather difficult to pinpoint your problem effectively so you should, out of respect, be patient or provide some USEFUL information as to what your EXACT problem is. So, to be nice, I'll explain to you where you went wrong and how you can readdress the situation to get the help you need.
Don't make a long story short. The more information you can provide, the better.
We see 20 posts exactly like this every day and it hardly ever implies "It won't let me do ANYTHING to it."
Now, by "ANYTHING" do you mean the power won't come on? Or do you mean that the power comes on but you either aren't able to access recovery or don't know how? What happens when you try to power the device on?
Also, exactly at which point during the rooting process did your problem occur? Did you have a full battery when you started? Did you unplug the USB cable in at some point during the process?
You cannot expect us to effectively fix a problem that we can't see without going into GREAT detail with what you are experiencing.
I suggest we start over and try again, only this time with a better attitude and some more useful information.
Click to expand...
Click to collapse
Sorry, I've just been really agitated by this whole situation. I've asked another forum and got back with horrible answers.
To start all over again, this is what happened.
I had my kindle fire at 6.3, unrooted (only unrooted because of the update), and decided to why not root it again, just so it's updated.
I got all the necessities to root the kindle, the same things I used when I first got it, and started up the process.
At first, the drivers were giving me issues, but that got settled quite quickly.
Then when I started up KFU, I did the perm root, but it somehow got canceled in the middle of it, so I'm guessing that's what has screwed it up.
Now when I plug it into either my Wall or USB adapters, it doesn't work.
I've tried that hard reset way, where you hold down the power button for 30 seconds, and that didn't work either.
So I got fed up, and came here for answers.
Right now, it's basically a dead Kindle Fire.
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
soupmagnet said:
Based on your answers it sounds like you are having a "power on" issue caused by a failed bootloader install.
Unfortunately there is only one known way to fix a broken bootloader, the USBboot method, and it requires removing the back cover and creating a short at a certain location.
It's tricky but effective and has helped many users with the same problem. Read over these two threads to get an idea of what needs to be done.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?p=25624152
Click to expand...
Click to collapse
Great... I'll try it. I'll tell ya what happens. Thanks
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
needhelpplease3 said:
just got done doing the ubuntu way, with firekit.
Didn't work.
It just kept saying wait for device. + My Kindle was turning on and off.
Click to expand...
Click to collapse
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
soupmagnet said:
Just to make sure I understand correctly, your device was turning on and off while attempting the "shorting trick" or has it always been doing that?
Click to expand...
Click to collapse
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
needhelpplease3 said:
I didn't do the shorting trick. Doesn't seem like the safest thing to do, so i did the way without it and it didn't help.
Is my last option the shorting trick?
Click to expand...
Click to collapse
Stop! before you screw something up.
More to follow....
soupmagnet said:
Stop! before you screw something up.
More to follow....
Click to expand...
Click to collapse
You're confusing me.
More to follow?
When I asked you "What happens when you try to power the device on?", I'm looking for specifics, i.e. "When I press the power button, nothing happens and the screen doesn't come on at all", or "The screen comes on, but the boot logo flashes on and off", or "The screen comes on, but hangs steady at the boot logo".
It is very important that you make this clear from the very beginning because it will help us in not telling you do do the wrong thing and potentially causing serious harm to your device.
I'm getting conflicting symptoms from you and it is making helping you rather difficult. If your screen doesn't come on at all the only fix for that starts with the "shorting trick". When you say that your screen was turning on and off it makes me think that it was doing that all along, which would require a completely fix.
If I'm going to help you I need to know exactly what is going on with your device along with any changes it has made and when they happened.
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA
dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.
benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.
same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?
hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"
Hi all,
I have been reading through this forum and some other links trying to solve my problem, but I haven't managed to find the answer. There seems to be a lot of very similar issues though, which makes it all the more frustrating.
A friend and I got my HTC Desire to S-OFF and flashed a custom ROM onto it over two years ago, and it was working perfectly well. After a while I noticed that the phone got very hot with extended use, and often reset itself, which I believe is a fairly common thing. Then suddenly one time, it reset and got stuck in a bootloop. The HTC splash screen just came up for about 30 seconds, then a black screen, then the HTC splash again, repeatedly. I can get into HBOOT, but when I select RECOVERY, the HTC splash screen comes up and stays up. Also, seemingly randomly, whenever the HTC splash screen comes up, sometimes it decides to vibrate seven times, other times only once. I forgot about the phone after I upgraded, but now I'd like to get the phone up to working order to play around with.
As I said, this all seems familiar from other posts, but none of them solve my problem. I've tried reflashing various HBOOT and recovery images in fastboot as is often suggested, none of which change the situation. I've also tried flashing the recovery in HBOOT using the .zip version, which still changes nothing. I'm wondering if a hardware problem could explain the issues I'm having, following the repeaded overheatings, but I'd expect an error to pop up when flashing the recovery image.
I feel like the problem is either a serious hardware failure, or I'm overlooking something critical in the flashing process. I apologise if there is an exact post already open that solves this. Any hints that could help would be great.
Oops
Sorry, I meant to post this in the Q&A section, not here.
Guffmeister said:
Hi all,
I have been reading through this forum and some other links trying to solve my problem, but I haven't managed to find the answer. There seems to be a lot of very similar issues though, which makes it all the more frustrating.
A friend and I got my HTC Desire to S-OFF and flashed a custom ROM onto it over two years ago, and it was working perfectly well. After a while I noticed that the phone got very hot with extended use, and often reset itself, which I believe is a fairly common thing. Then suddenly one time, it reset and got stuck in a bootloop. The HTC splash screen just came up for about 30 seconds, then a black screen, then the HTC splash again, repeatedly. I can get into HBOOT, but when I select RECOVERY, the HTC splash screen comes up and stays up. Also, seemingly randomly, whenever the HTC splash screen comes up, sometimes it decides to vibrate seven times, other times only once. I forgot about the phone after I upgraded, but now I'd like to get the phone up to working order to play around with.
As I said, this all seems familiar from other posts, but none of them solve my problem. I've tried reflashing various HBOOT and recovery images in fastboot as is often suggested, none of which change the situation. I've also tried flashing the recovery in HBOOT using the .zip version, which still changes nothing. I'm wondering if a hardware problem could explain the issues I'm having, following the repeaded overheatings, but I'd expect an error to pop up when flashing the recovery image.
I feel like the problem is either a serious hardware failure, or I'm overlooking something critical in the flashing process. I apologise if there is an exact post already open that solves this. Any hints that could help would be great.
Click to expand...
Click to collapse
Might be an overheating issue. Try putting your phone in the freezer for about 10 minutes, with the battery taken out , then try to boot.
Hi, thanks for your response. I saw you posted a similar comment in the Q&A section.
I'll give it a go. I'll also try flash the RUU as you suggested in that same post if that doesn't work. How exactly does putting the HTC in the freezer help? I can understand if it was still hot from being on a lot, but it's been sat on a shelf for well over a year switched off.
Guffmeister said:
Hi, thanks for your response. I saw you posted a similar comment in the Q&A section.
I'll give it a go. I'll also try flash the RUU as you suggested in that same post if that doesn't work. How exactly does putting the HTC in the freezer help? I can understand if it was still hot from being on a lot, but it's been sat on a shelf for well over a year switched off.
Click to expand...
Click to collapse
Well, it takes a lot less time for it to heat from 24°C than from -10°C.
Hello.
First I am new to the forum and I hope it does not violate any rule.
I have a problem with the model HTC 820 HTC OPFJ400.Am specifically tried to work through it from what I knew but nothing worked: Recovery / Factory Reset
Let me tell you about the issue.
Now a few days, my father received an update on the phone and wanted to make it .When gave the update to start the phone suddenly went out, then tried to switch it on and do not know what that can no longer pressed between the phone and the only access three menus. I'll put some pictures to see which ones are three menus
Apparently not have enough posts to be able to put pictures but will leave 0034-632763952 WS number for those interested in pictures.
I looked left and right after tutorials but nothing helped.
I want to return it to its original factory state.
If anyone can help me with a step by step tutorial or more tutorials step by step to bring back to the factory settings.
Once again I hope you will not violate any rules and I apologize if I have violated.
Thank you for your time.
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.