Develop Bugs

[Q] LG Optimus G Stuck On LG Screen Need Help.

I was making a TWRP Backup when all of the sudden my phone just randomly turns off. I grabed my phone and it was really hot. Tried turning it on, but nothing happened. Then I connected it to the ac adapter and it turned on, but it would go to the LG logo, the screen turns black then it restarts. This does not stop unless I unplug it. I had previously made two backups before and nothing like this happened, but this time I enabled conpression<-------- This must have been what caused this. All I want to know is if this can be fixed or not. If it could be fixed I would be so happy if somone could tell me how to fix this. THANK YOU. P.S. THIS PHONE IS A BEAST. D

cgtrr34 said:
I was making a TWRP Backup when all of the sudden my phone just randomly turns off. I grabed my phone and it was really hot. Tried turning it on, but nothing happened. Then I connected it to the ac adapter and it turned on, but it would go to the LG logo, the screen turns black then it restarts. This does not stop unless I unplug it. I had previously made two backups before and nothing like this happened, but this time I enabled conpression<-------- This must have been what caused this. All I want to know is if this can be fixed or not. If it could be fixed I would be so happy if somone could tell me how to fix this. THANK YOU. P.S. THIS PHONE IS A BEAST. D
Click to expand...
Click to collapse
Can you boot into recovery and restore a previous backup?
Sent from my LG-LS970 using Tapatalk 2

cowfodder said:
Can you boot into recovery and restore a previous backup?
Sent from my LG-LS970 using Tapatalk 2
Click to expand...
Click to collapse
It does not let me go into recovery, the screen goes black then restarts. All I can do is go into fastboot and Download mode.

cgtrr34 said:
It does not let me go into recovery, the screen goes black then restarts. All I can do is go into fastboot and Download mode.
Click to expand...
Click to collapse
Likely bricked. Do you have flashing notification and capacitive lights? Have you LGNPST'd? If yes to both of those questions, you're in the same predicament as I was and hopefully you have insurance, because your phone is fried.

xboxfanj said:
Likely bricked. Do you have flashing notification and capacitive lights? Have you LGNPST'd? If yes to both of those questions, you're in the same predicament as I was and hopefully you have insurance, because your phone is fried.
Click to expand...
Click to collapse
I do have flashing notification and capacitive lights. But I don't know what LGNPST is.(sorry I'm new to this) this is my first android phone

cgtrr34 said:
I do have flashing notification and capacitive lights. But I don't know what LGNPST is.(sorry I'm new to this) this is my first android phone
Click to expand...
Click to collapse
Sounds like you are toast. Take it to Sprint and have em swap it out for ya. Hopefully you either have insurance or are within your 14-days to return it.

xboxfanj said:
Sounds like you are toast. Take it to Sprint and have em swap it out for ya. Hopefully you either have insurance or are within your 14-days to return it.
Click to expand...
Click to collapse
Will they swap a rooted and unlocked phone?

cgtrr34 said:
Will they swap a rooted and unlocked phone?
Click to expand...
Click to collapse
Sprint's policy on root is to document it but not do anything about it, so they would swap it. If you're worried, I can help you restore stock firmware.

xboxfanj said:
Sprint's policy on root is to document it but not do anything about it, so they would swap it. If you're worried, I can help you restore stock firmware.
Click to expand...
Click to collapse
How could I restore it to stock firmware. And also thank you for replying back and helping me out

cgtrr34 said:
How could I restore it to stock firmware. And also thank you for replying back and helping me out
Click to expand...
Click to collapse
I will PM you about that since it is against forum rules and perhaps laws to post copyrighted stuff here.

xboxfanj said:
I will PM you about that since it is against forum rules and perhaps laws to post copyrighted stuff here.
Click to expand...
Click to collapse
OK thank You so much!

cgtrr34 said:
I was making a TWRP Backup when all of the sudden my phone just randomly turns off. I grabed my phone and it was really hot. Tried turning it on, but nothing happened. Then I connected it to the ac adapter and it turned on, but it would go to the LG logo, the screen turns black then it restarts. This does not stop unless I unplug it. I had previously made two backups before and nothing like this happened, but this time I enabled conpression<-------- This must have been what caused this. All I want to know is if this can be fixed or not. If it could be fixed I would be so happy if somone could tell me how to fix this. THANK YOU. P.S. THIS PHONE IS A BEAST. D
Click to expand...
Click to collapse
WTF!!!!! I just bricked my phone in less then 24 hours of owning it. I just rooted and unlocked it and right after making a TWRP Backup and rebooting my phone wouldn't turn on and it was HOT AS HELL!!
I got it exchanged at Best Buy but now im scared to do anything with it.

shook187 said:
WTF!!!!! I just bricked my phone in less then 24 hours of owning it. I just rooted and unlocked it and right after making a TWRP Backup and rebooting my phone wouldn't turn on and it was HOT AS HELL!!
I got it exchanged at Best Buy but now im scared to do anything with it.
Click to expand...
Click to collapse
Same happened to me. The phone overheats in recovery, so do what you need to do and then get out of it.

xboxfanj said:
Same happened to me. The phone overheats in recovery, so do what you need to do and then get out of it.
Click to expand...
Click to collapse
Im on the new phone and Im using clockwork and all is fine so far. I definitely suggest guys stop using twrp.
Sent from my LG-LS970 using XDA Premium HD app

Restore to stock when stuck at LG logo screen
xboxfanj said:
I will PM you about that since it is against forum rules and perhaps laws to post copyrighted stuff here.
Click to expand...
Click to collapse
Would you please help me out to restore to stock from a stuck LG logo screen? I can't even boot into fastboot or recovery. I tried LGNPST number of tries with different .bin files with no luck. I also tried a lot of diff things, too. Please email me at [email protected]. Thank you very much!

phatjulie said:
Would you please help me out to restore to stock from a stuck LG logo screen? I can't even boot into fastboot or recovery. I tried LGNPST number of tries with different .bin files with no luck. I also tried a lot of diff things, too. Please email me at [email protected]. Thank you very much!
Click to expand...
Click to collapse
I suggest you TEP it.
Sent from my LG-LS970 using xda premium

phatjulie said:
Would you please help me out to restore to stock from a stuck LG logo screen? I can't even boot into fastboot or recovery. I tried LGNPST number of tries with different .bin files with no luck. I also tried a lot of diff things, too. Please email me at [email protected]. Thank you very much!
Click to expand...
Click to collapse
Pull battery using a torx t5 screwdriver and phillips #00 if you don't have insurance.

xboxfanj said:
Pull battery using a torx t5 screwdriver and phillips #00 if you don't have insurance.
Click to expand...
Click to collapse
What's the purpose of pulling battery out? Just a try? I'm gonna have to get it from Fry's tomorrow and try that first.

phatjulie said:
What's the purpose of pulling battery out? Just a try? I'm gonna have to get it from Fry's tomorrow and try that first.
Click to expand...
Click to collapse
Because your phone doesn't know if it needs to be in charging mode or booting. Pulling battery will fix it.
Sent from my LG-LS970 using xda app-developers app

I had a similar problem as you. Upon getting the phone I rooted and used the FreeGee app from the Google Play store to unlock the bootloader. Everything seemed fine and dandy, until one day when I let my phone's battery drain completely. Pluggin it in to a wall charger resulted in the failed boot where the LG logo flashes before going to a blank, but backlit screen. Luckily, the first few times this happened, through a combination of quickly plugging and unplugging the usb cord and holding the volume up+power button, I could get it into recovery (TWRP). Then a simple cache & dalvik cache wipe, and the phone would boot up as if nothing ever happened. Very strange.
Well yesterday this happened again, however, this time there was no getting the phone into recovery. My previous methods of button mashing and plugging and unplugging weren't working. So, I decided to bite the bullet and use LGNPST to get back to ZV7. Now, like you mentioned, this failed boot would automatically happen, without pressing the power button to turn it on. So it was difficult to get the phone to stay off. I found that with the phone unplugged, if you continue to press the power button until the blank backlit screen turns off, AND continue to hold the power button for an additional five seconds, the phone would stay off and not auto power on into the failed boot.
Once I was able to get the phone to stay off, I pressed the middle of the volume key to depress both volume up and down, and then plugged a usb cord that was attached to my computer. This powered on the phone into download mode. Following the LGNPST guide I was able to get to around 67% complete before my phone turned off and an error message flashed on the computer screen telling me to power cycle the phone and reconnect. Well, the whole 67%/85% LGNPST failure is apparently common and not indicative of an actual failure; HOWEVER, my phone became completely unresponsive. It wouldn't power on at all. It didn't matter if the usb was unplugged or connected to the computer or wall charger. So, I was forced to unplug the battery. I followed this tutorial and successfully disconnected and reconnected the battery cord, and the phone shot back to life. It even booted up into the factory stock ZV7 rom. I guess that LGNPST was successful. It looked like I was on my way to returning my phone to breezy's deodexed ZV9 stock rom that I was previously running.
I went ahead and re-rooted, ran the FreeGee app again, and rebooted into recovery. Then I made a backup and attempted to flash my new rom. Now, I think this is where I royally screwed up. I was pleasantly surprised to see my screen layout and all of my settings still intact after LGNPST back to ZV7 and thought I could just wipe the caches and ignore the factory reset and system wipe before flashing. Perhaps it was this, but part of me also thinks there might be something wrong with my battery draining extremely fast in recovery.
I proceeded to flash and all seemed good, but rebooting resulted in the LG logo failed boot that we have already discussed. So, I went ahead and repeated the LGNPST-re-root process numerous times (switching to the freegee 0.5 batch file instead of the app). Everytime after the first initial restore, I could never get my phone to enter recovery. As soon as I rebooted after using freegee, the phone would be soft bricked again. Sometimes I would get the LG logo thing, other times I would get the dreaded alternating flashing red notification light and soft keys. A battery pull was usually required in these circumstances before I could get back into download mode to start all over.
I was about ready to give up when I took to the LGOG irc channel. That's when Xboxfanj stepped in and helped me out IMMENSELY. Over the course of several hours, he walked me through flashing some partitions in ADB. At times it seemed like there was no hope and that I should have just returned the phone, but he failed to acquiesce, we pushed forth trying a couple of other bootloader options. The new bootloader appeared to have fixed the phones erratic behavior with powering on and off, but I had no rom to boot into and no recovery. Xboxfanj recommended using fastboot to flash over a recovery. Once in the new bootloader screen my Windows XP machine detected new hardware and wanted some drivers. I attempted to use the [ADB/FB/APX Driver] Universal Naked Driver 0.72, but XP indicated that I was missing 'winusbcoinstaller2.dll'.
I grabbed winusbcoinstaller2.dll from here and all was good. Fastboot recognized the phone, I was able to flash recovery and subsequently boot into recovery. From there I reformatted the system, wiped data/factory restore, wiped cache, wiped dalvik cache, and flashed breezy's ZV9 deodexed rom.
Fortunately, after around 7 hours, I am happy to say my phone is back to being rooted, unlocked, and running ZV9. It powers on and off properly and can get into recovery without a hitch. I'm still curious what will happen if I let my battery drain completely. Perhaps I'll try it some time this week. I'll be sure to post back here if/when I do that. All in all, it was a harrowing, but educational experience.
Anyway, just wanted to give a big THANK YOU to Xboxfanj! You really are the man :good:. Thanks for your patience and determination.

[Q] Screen flickering / Bootloop -> Is my Nexus dead? Data recovery possible?

Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.

Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery

Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?

BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?

Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.

you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.

Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?

BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.

BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.

beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems

BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link

[Q] [Bad Update] Nexus 7 came in today, tried to root...

Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
UPDATE: So it wasn't bricked it, as I was able to return to the home screen. After a day of using it though, with the Nexus being buggy (freezing and crashing), it just died. I can't boot it or anything. It's plugged in, but nothing's happening.

Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Download factory image and do a factory restore:
https://developers.google.com/android/nexus/images#razorjss15q
I personally don't like toolkit. Recommend to root it yourself step by step.

I, being very technically unsavvy, have no idea what to do with the images.

Alright, here's the good news. You haven't bricked your nexus. You can and will fix this yourself, without a tool kit.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2379797
Then read it again and again until you understand the steps to fix your tablet. I was in your shoes once, years before toolkits were available and I learned how to fix worse problems then you have currently. Take your time.

Desperate User said:
I, being very technically unsavvy, have no idea what to do with the images.
Click to expand...
Click to collapse
Great user name given what you just posted

Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Same thing happened to me a month ago. Most important thing, don't freak out. Hold power for 20sec to hard reboot, then as soon as google logo appears hold down volume button to enter bootloader screen. From there you can do anything

http://forum.xda-developers.com/showthread.php?t=2391301

Did you boot into the phone after you unlocked the bootloader but before you tried to root? Do you have a custom recovery installed?

doe you have a custom recovery?
if so check if you still have your internal storage, i had the same problem as you but there is a bug going around when u unlock your bootloader your internal memory is wiped see this threat for feather explaining: http://forum.xda-developers.com/showthread.php?t=2380913
In my case i booted to fastboot and did the command fastboot -w and then it created new user partitions and then i could flash the stock image and then it worked again
Hope i helped u

No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't

hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app

HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't know, maybe you should make your own thread rather than hijack mine.

Desperate User said:
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
Click to expand...
Click to collapse
owh, does it al least charger when u plug it in?

silvan g said:
owh, does it al least charger when u plug it in?
Click to expand...
Click to collapse
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.

Desperate User said:
I can't tell. The damn thing doesn't respond to anything.
Click to expand...
Click to collapse
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down

HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Click to expand...
Click to collapse
If you're not rooted, it's just a stock update. There isn't any more risk than there is for any stock version, and you shouldn't lose data. If you buy a Nexus 7 2013 a few months down the line, after current stock with JWR66N is sold out, I believe it'll come with that update out of the box.
Desperate User said:
I don't know, maybe you should make your own thread rather than hijack mine.
Click to expand...
Click to collapse
I understand you're frustrated, but that was a little rude...he's just trying to get help, just like you.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Click to expand...
Click to collapse
Unrecognized in ADB or fastboot? Can you get into bootloader (boot while holding power and volume-down)? If you haven't tried fastboot while the phone is in the bootloader, and you can get into bootloader, try "fastboot devices." If you can do that, download a custom recovery and flash it from fastboot. Then format data and reboot.

silvan g said:
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
Click to expand...
Click to collapse
Done and nothing

Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img for the LTE or fastboot boot openrecovery-twrp-2.6.0.0-flo.img for the WiFi version.
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.

Guhrasoh said:
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Click to expand...
Click to collapse
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.

Desperate User said:
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Click to expand...
Click to collapse
How long has it been charging? I'd give it a couple hours, then try the bootloader again.

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!

Motorola G6 Play (Boot loop)

I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy

Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately

Thanks for the reply, please can you put a link to your guide?

Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928

Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.

Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops

sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?

Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?

The phone was bought direct from Amazon so in my mind a generic model to take any SIM.

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.

I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it

Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?

ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?

Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it

Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a

ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..

Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted

I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.

Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant