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.
Related
I have been waiting nearly two months for HTC to get on the ball and release the official version of Windows Mobile 6.5 so I could download it and see if it's worth using as my main phone OS. But they have been lazy and have yet to come out with it. So, I got impatient and began looking into the roms that were already available and how to flash my phone to get them to work. The first step I read that I needed to do was unlock my phone. However, I forgot what the text said at the top of the page (here's the link to the program I used, if that's helpful): http://forum.ppcgeeks.com/showthread.php?t=36062. So I proceeded to use the Diamond Unlocker (as that should have been a huge tip-off to me then, but this was my first ever unlocking experience, so I had no idea what I was doing) Now, my HTC Touch Pro 2 from Verizon won't even turn on. It won't go into a bootloader screen, absolutely nothing happens when I press power button, the reset button, or a combination of any of the buttons on the device.
However, when I plug the phone into my computer, a device does pop up: Qualcomm CDMA Technologies MSM. I can't get anything more than that, though. No software drivers will install, it does try very hard to find some though.
Any help, advice, tips, tricks, random guesses, would be greatly appreciated. Thanks for all your help.
Welcome aboard
try to reflash another ROM
have a deep read here
http://forum.xda-developers.com/showthread.php?t=550540
Good luck,
Buttons don't respond.
I can't get my phone to turn on or even go into bootloader mode. So, without that, I don't understand how I can flash a new ROM onto my phone.
And hello to you as well.
I did read that link, but none of the button codes worked, and my phone isn't responding to the Hard-SPL that I started when my phone was connected. It says that it cannot find the device and I need to resync it. But I start Windows Mobile Device Center and it can't find my phone either.
However, an interesting new development is that my phone, every now and again, starts charging when connected to my computer. The light turns orange, and my computer picks it up. But it does this for a bit, and then it changes back to nothing.
If you can't access the bootloader using any of the methods detailed here, then I hate to say it, but your device is probably bricked. It's really difficult if at all possible to recover when the SPL (AKA bootloader) is severely damaged or completely destroyed. There were some tools a while back to help recover from nuked SPLs, but AFAIK they aren't compatible with the TP2, and you have to be security unlocked, which I can pretty much guarantee you aren't.
Your best bet would be to take it back to the store and play dumb, saying that it "just stopped working" in the hopes that they'll give you a new one, but there are no guarantees it'll work. Best of luck
That's what I need to know
Thanks for the information. I just needed to know what to do. I can't access the bootloader or anything even similar to it, so I am just going to get it replaced and then be much more careful in the future.
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:
Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on
Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.
I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.
He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.
Can anyone help me with this problem?? I tried many ways but there isnt anything possible. The community either ignores me or gives me a simple answer. Can anyone just give me a suggestion of what i cant do?
You can't do anything with it by the looks of things, it's gone.
me too.....
On the same boat but mine is being recognized by my PC.
Same here... some extra info.. but still broken.
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
tacua said:
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
Click to expand...
Click to collapse
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Done that
mb_guy said:
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Click to expand...
Click to collapse
I had lurked this forums for 3 year now, and until now I signed up to post my experience. So yeah, I have looked on this forum and other sites for the correct KDZ. If you look careful on that post (as I did) that latest full LP version KDZ is 10h, which already have it for a while. However when this happened to my phone, it was already on 10n which is the version I expect to find somewhere to be able to recover my phone. Recently, I see that is available version 20e but that is already MM, I want to observe how it behave on the community before I decide to go there.
No matter what is the case, the phone was sent for repair. I think mine when under the worst case scenario of the so much mentioned bootloop. So much, that it even opened the bootloader and show me the fastboot prompt, although that the Canadian version is locked.
For my experience with the Nexus, they come with two bootloaders, the normal that can be updated locked and unlocked and a emergency bootloader that is available when the device is almost bricked and the normal bootloader is borked. Finally there is a low level manufacturer flashing that use the OEM SOC application to put the initial ROM. In the past I have been able to play with the Rockchip and the Nvidia Tegra 3, applications at that level. So those devices are simple "unbrickables". Low level Qualcomm (QHUSB_BULK) flashing is barely mentioned on the net, no process detailed, no application available so far that I can find.
My experience with LG so far is like buying a PC with installed OS, no recovery CDs, no website to download the recovery, no access to the BIOS, no "normal" human soul is allowed to create a full backup of the HD without going on a major hackaton with not assurance that what you get will work in future case of emergency. If something happens to the OS when you are out of warranty... you are royally screwed.
Guys try the oven method it may work. Some are saying it lasted 24 hrs others say its still active. It may be dangerous but worth a shot since no one else is taking action on this fix.
Also my phone was just rooted. At that time I wasn't trying to do anything with modifying but just using instagram.
1. This phone's been babied no damage.
2. Never rooted or any kind of tweaking, only basic usage.
Now it gets stuck on boot and even if I try to hard reset once I tap the button to get into recovery it just flashes the Google start up logo. I can never get to the "no command" part. Besides that it does nothing but turn on stay stuck on boot (Google logo).
same here :/ any updates?
its not a brick. if this issue is affecting several people, someone at xda will figure it out, or google themselves will notice and fix it. I contacted google about it and let them know that ive seen several users reporting the same issue. i'm also trying different things on my end, but without being able to sideload zips or get into twrp its difficult. I cant even tell if the memory is encrypted or not. and fastboot has no diagnostic tool for me to run a hardware test, however I cant see all of our devices working fine one day and randomly breaking the next...
---------- Post added at 05:10 AM ---------- Previous post was at 05:09 AM ----------
it seems the last update or two did something and flashing different boots and stock images is not overwriting whatever is wrong, almost as if it was an update to something that can't be rolled back. if thats the case we will need another update that corrects the issue, since we can't manually reverse it.
godkingofcanada said:
its not a brick. if this issue is affecting several people, someone at xda will figure it out, or google themselves will notice and fix it. I contacted google about it and let them know that ive seen several users reporting the same issue. i'm also trying different things on my end, but without being able to sideload zips or get into twrp its difficult. I cant even tell if the memory is encrypted or not. and fastboot has no diagnostic tool for me to run a hardware test, however I cant see all of our devices working fine one day and randomly breaking the next...
---------- Post added at 05:10 AM ---------- Previous post was at 05:09 AM ----------
it seems the last update or two did something and flashing different boots and stock images is not overwriting whatever is wrong, almost as if it was an update to something that can't be rolled back. if thats the case we will need another update that corrects the issue, since we can't manually reverse it.
Click to expand...
Click to collapse
so... Google knows about the issue, ok. But how will that help, to a whaetver person like me, that has NO google shops to RMA, or bring them to fix it to?
Are you saying that they will patch an OTA, so that we can sideload it? i can enter recovery mode, after letting the phone stay in Power Off mode a few hours. Tried resetting multiple times.
I have a similar situation.
Pixel XL on charge, went out for 10 minutes, came back, pick up phone, power button unresponsive...
I did have all the preps for rooting (OEM unlock turned on, developer mode enabled, USB debug etc...) because I was going to try some custom ROMs.
"fastboot oem unlock" returns "FAILED (remote: 'oem unlock is not allowed')"
My whole life is in that damn expensive paperweight... I am in serious trouble (medical reasons, daily notes stored on phone) if i can't even simply recover user data.
Any ideas? anyone? help... please
I'm on the phone with google software development
No luck. Toasted or repair. They said the mobo
Sorry to hear that. Just curious - how old the device was, maybe you have a manufacturing date? Have you used the genuine USB C PD charger, or used third party chargers? Just don't understand how motherboard dies so frequently for first gen.
Mine died this morning when I went to check the weather. An update had apparently installed overnight, nothing else was out of the ordinary. It froze and I hard powered it off. I haven't had any signs of life since. It is listed as "Qualcomm-HS-USB QDLoader 9008" when I try to plug it into my computer (no access, just listed as a connected device.) Mine was a 128gb variant, carrier unlocked, never rooted/etc., only used with official charger & usb cable. I don't have the mfg date unfortunately.
I hope any of that info can prove useful, even if just to help establish a scope of the affected devices.
C4rb0nf00tpr1nts said:
I have a similar situation.
Pixel XL on charge, went out for 10 minutes, came back, pick up phone, power button unresponsive...
I did have all the preps for rooting (OEM unlock turned on, developer mode enabled, USB debug etc...) because I was going to try some custom ROMs.
"fastboot oem unlock" returns "FAILED (remote: 'oem unlock is not allowed')"
My whole life is in that damn expensive paperweight... I am in serious trouble (medical reasons, daily notes stored on phone) if i can't even simply recover user data.
Any ideas? anyone? help... please
Click to expand...
Click to collapse
Did you try the more current "fastboot flashing unlock" command? That is the correct one.
The problem is that will erase your user data partition.
Hopefully your notes were taken in Google Keep? If so, you can read them on any computer you can sign into with your Goodle account.
jaytv said:
Did you try the more current "fastboot flashing unlock" command? That is the correct one.
The problem is that will erase your user data partition.
Hopefully your notes were taken in Google Keep? If so, you can read them on any computer you can sign into with your Goodle account.
Click to expand...
Click to collapse
Sure did. Tried everything. Nothing will connect to the phone - only things that return a successful response are some of the fastboot commands (getvar all, device).
And due to having friends and colleagues that kept telling me to turn off all the "big brother" type of backup options I have nothing.
I can categorically state that I have nothing to hide from all the officious types that would be watching my every key stroke or phone entry and I will be turning on every backup or recovery option in future, whether or not I go back to the fragile device of a Google phone is to be decided if I myself decide to push on from this point at all...