Related
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
It sounds like you're suffering from some sort of hardware failure. You need to send your phone in for repair/replacement.
The Unnamed Time Lord said:
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
Click to expand...
Click to collapse
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Same issue here...
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
then i shut it down, pulled the battery and then back, and restarted: the phone goes directly to that black backlit screen, i tried several times and tried recovery with no luck, so i thought my phone was messed up although i did have some haptic feedback, well in fact the phone was actually booting, but just not showing anything else than the backlit screen; i waited a minute or so to the booting completes (still shows nothing), then i lock/unlock the screen again and there it is, asking for the pin code.
I tried to go to the recovery again to try to wipe dalvik-cache, i know for sure it goes to recovery, but with a totally black screen, not even backlit this time; the trackpad is too sensitive in the recovery to just blindly navigate in the menu, so it is not useable at all.
Then i had the idea to go to Rom Manager, i reflashed the rom from my sd-card, and enabling wipe dalvik-cache, which worked (all through a black screen). After a few minutes i "felt" it rebooting (vibrating) but still back to that black backlit screen, and i locked/unlocked it again and back it was asking pin code...
I also tried to roll back recovery to 3.0.2.4, since i remember i updated it a few weeks ago, but still the same issue.
I don't know what else to do without accessing the recovery, i wanted to try another kernel, or remove the trackpad wake... is there a way to do it via a script? I guess it's what Rom manager does...
Next step will be a total wipe, but i need to make some room on my sdcard for backup purposes first...
If anyone has an idea to sort this out, i'm highly interested...
I'll try to get a logcat, maybe could give a hint
Edit: Virtuous sense 2.0.0 (used it with no issue since it came out, could it be a hw issue?)
Edit2 : attached logcat
Is the pin screen differant than the usual one ie white number keys? If it is that's the sim lock screen you need to call the carrier to get the code or find out the default. Or just get a new sim lol
nah it's the 4 digit pin code, i didn't lose it btw, it's still working and i can use the phone, but i have a black backlit screen whenever i want to wake the phone, and thus when i receive a phone call, i don't know who it is and i blindly press/swipe the screen to answer, because if i want to use the same trick of locking /unlocking, it doesnt work as the lock button is also used to reject a call...
Maybe rip and reinstall the phone app?
asim0 said:
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
Click to expand...
Click to collapse
I have the same exact problem as this EXCEPT, it's intermittent. Sometimes when I wake the phone I get an all black but backlight screen, and other times it's fine. I'm on CM7.1.
But a superwipe and reflash will probably fix it. Also don't restore system data on TB
I know i still can use wipe data + cache + dalvik through rom manager, and i always used to superwipe before switching roms, but how can i do that now when the recovery is all blacked out?
can anyone guide me to a script or something i could do while the phone is active, to tell him to reboot to recovery and flash that superwipe?
anyway i'll try the regular wipe and keep the thread updated
---------- Post added at 02:42 PM ---------- Previous post was at 02:35 PM ----------
SuperDave81 said:
EXCEPT, it's intermittent.
Click to expand...
Click to collapse
On my side if i leave the phone locked more than 30 seconds, it happens 100% of the time; also I noticed that now the backlight blinks 2 or 3 times (1 second blinking) when locked, first a few minutes after locking, and then randomly, about 3 or 4 times per hour; I guess it's getting worse;
I've read on another thread that it could be video cable getting loose, but since mine is still under guarantee, i won't open it right now just to check, if i can't fix by wiping / superwiping (when i know how to), i'll use that guarantee, which is one month left (lucky me)
EDIT: one other thing that makes me think it's no hardware, when the black screen appears because of a phone call or a message, the ringtone and notification sound are both half as loud as they should be, this is all really strange
after backing up my data, i reflashed the rom via Rom Manager, and I wiped data and cache (which equals to factory reset) this time: the first screen that should show the pin code numpad was already a black (backlit) screen!!
Also, thinking about it, i realised that the "flash rom from sdcard" menu in Rom Manager is in fact "Flash ZIP from sdcard": the zip doesn't have to be a ROM!!
So I tried flashing a new kernel this way, also some framework modifications (extended settings, removed TP wake, etc...) they all install Ok, but still this black screen...
Also I was about to flash SuperWipeG2.zip this way, but if it doesn't fix my problem, I will be stuck with a blacked out recovery, as SuperWipe wipes everything including /system; so if anyone has an idea to tell Rom Manager to flash two zips (Superwipe then Rom) i'll be willing to try, or a script to do that;
Maybe i'll have a look of the scripts in Superwipe and in the rom, and put both zips together... don't know if it's possible?
Maybe I'll try the Superwipe alone if I can get a spare phone, just in case...
Other thing:I used the phone's gps for more than 5 hours with the screen lit, and it never flickered even once; so it's hard to believe it's a screen connection issue...
Just to keep this updated, everything i did, including superwipe didn't change this issue, so i sent it back to the technical support (under guarantee) and I got it back today; the report that came with it says the screen has been replaced; so it was hardware finally...
Hi, i have same problem.. Black screen in recovery and during the boot. When the system boots, screen is OK. Sometimes i have also blackscreen when I want to use HW keyboard. I tried 4ext, reflash older versions of CW but still the same. I can see a screen through Android Screen Monitor and I can cotrol it. But phone is blak, only backlight. Can somebody say, how to solve this issue?
So, for other, if you cant see screen, you can use Android Screen Monitor for Windows and connect phone through USB and see a screen.
G1ForFun said:
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Click to expand...
Click to collapse
WAIT one minute... they don't care? where was I when this meeting took place?
I had this issue as well on a spare G2 I had.
The screen was just black but you could tell it was lit, hardware keys were lit as well.
The phone was actually my brothers and it rooted w/ CM7.
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
I never attempted to get it replaced and kind of wish I did now if they don't care about the device being rooted.
I purchased my G2 before he had his, and it's never had the issue so not sure what to think of it.
Saintfyre said:
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
Click to expand...
Click to collapse
I think I have similar issue, can you post where you found those instructions?
Thanks in advance!
http://www.youtube.com/watch?v=u-dR8CHEGjY&feature=youtube_gdata_player
Sent from my HTC Vision using XDA Premium App
I used the same tutorial to change the LCD but after I put the new its just the backlight but nothing else... I will give it another go maybe and have a look again at those ribbon cables! I guess...
---------- Post added at 10:59 AM ---------- Previous post was at 10:09 AM ----------
I found on ebay: HTC-Desire-Z-T-Mobile-G2-A7272-Slide-Flex-Cable-Ribbon
or I found also with the chassis for a bit more.
Thinking to buy this, it would be great if anyone could confirm that it would help "my condition" ?
THanks in advance!
In terms of cables, yes the flex cables are what you want.
Sent from my T-Mobile G2
Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google (Call us at 0800 328 6081) and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
I include a picture of the N7 display after the unsuccessful 4.1.1 update.
Image https://docs.google.com/open?id=0B3oSwFvF1cmebXE4S2lvZlNlU0E
Cab
Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/
Looks like a defective unit. Not sure what pirates have to do with it.
Via my HTC Rezound
CrazyPeter said:
Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/
Click to expand...
Click to collapse
Thank you for being a productive member of this community, xda would not survive without you.
Sent from the matrix. (or my phone)
Not a good sign that it's doing it in fastboot mode. You can try leaving it in fastboot mode to drain the battery then plug it in and try again. Or, search for the instructions to reapply the stock 4.1 image. If those don't work then RMA it.
That looks very familiar.
A few minutes after the update (which I installed about 10 minutes in to receiving my new Nexus 7) I immediately had a total screen lockup/crash with lovely multicolours.
After that, any subsequent reboot/factory reset, the lockups continued and became more an more frequent until after just a day the device was completely unuseable.
I don't think the update caused it. I think it's factory defective and probably related to a messed-up Tegra 3.
Thanks for the feedback guys - I'm gonna RTM it as advised. A good unit shouldn't go wrong at all when just out of the box with no 'normal' or 'strange' apps added. It just had pure google stock on it.
cabello123 said:
Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
Cab
Click to expand...
Click to collapse
Ok, I was about to post this very thing. Mine went red. Bright red. Nothing worked. Took it back to the store and it turned on fine and looked good...until the manager took it and flexed it a bit. Then, bam. Everything flickered and turned red.
So now I have new one (N7 16gig) and its working great. But the alert comes on telling me to upgrade to the 4.1.1. No way in Hell!! It's an hour drive back to the store to get another.
So what's the solution. Anyone else have this happening?
That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.
jonnyg1097 said:
That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.
Click to expand...
Click to collapse
I was not telling people to beware of upgrading. I was asking if others had experienced this.
cr2crf said:
I was not telling people to beware of upgrading. I was asking if others had experienced this.
Click to expand...
Click to collapse
So I finally updated the os to 4.1.1 Success. Hoping this little tab keeps going. The more I play with it the more I am glad I got it and not a 10 incher
Were these affected units stock unrooted? As a general rule you always want to revert back to stock unrooted before applying any OTA updates.
Hey guys,
I am having 2012 wifi 8GB N7 for more than yr now and have recently started getting irritating problem making it unusable.
Its behaving as if its power button is continuously pressed even when i am not touching the tablet or sound / power buttons. Its operating on its own to restart, bring power menu in every situation i put it in, like in system standby condition, powered down condition or in bootloader or even in CWM recovery. Its operating function corresponding to power button.
Tablet is out of warranty so i am trying to troubleshoot and fix it myself (as far as i can) and but getting any clues from online available material too. Also out of warranty repairs are costly / worthless if service guy decide to change its PCB.
If anyone has faced similar issue/ got solution/ got it fixed from service guys, please suggest me what can be done. Is it a software issue or hardware issue like.
So far I have tried factory roms of 4.2.2, 4.3, CM versions and AOKP versions in rooted, non rooted, bootloader locked unlocked conditions. And from my understanding its not related to any roms. Heck it shows this erratic behavior even in bootloader mode or in CWM recovery.
Can there be anything which service guys do as far as software is concerned which we cant do, so that i can give them to fix it?
Looks like a hardware issue. The internal part of the button may be loose.
Sent from my AUXUS Nuclea N1 using xda app-developers app
Ain't nobody faced such issue ever? Please guys i need some inputs.
So far i tried disconnecting power/ volume button strip/ cable from motherboard and let it idle for sometime. Even tried booting with that strip removed, but it didnt solve the problem. So my thinking of this strip being the culprit is wrong (from my understanding).
Thought of giving an update to this issue..
Dismantled N7 completely taking help of youtube videos. Booted back up and problem persisted but with extreme low frequency. i.e. power command executed on its own after a long time. So used tablet for half and hr, updated it to 4.4.2 which was not possible in the condition it was in before. Later problem aggravated to initial level again. i.e. continuous restart, no operation possible.
So left tablet in powered off condition for a day. Switched it on again. And could use it for same half an hr without facing any problem. After that problem started troubling again.
If anyone can think of resolution, would appreciate assistance.
Thanks.
Another pleasant update.
Tab was lying unused for months with battery fully discharged. And later when i checked at random without even expecting any change in its condition..... it started perfectly.
And its working without any issue now. Hope this will help someone else facing problem.
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?
razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.
Hi,
After Xmas I made factory reset with TWRP and I made an upgrade to CM13.(6.0)
It was working fine.
When I was trying to make next daily update, after reboot, screen became black and nothing shown up.
I was trying a lot of things since that moment.
When I was going back from service point (I really want to sort it out) when they told me it is probably LCD broken (i have broken glass, but 1 year ago, so I do not believe it can be screen),
when I take phone out I spotted that keys are highlighted so I swiped and it locked out and shown screen! it was working perferctly fine,
so I decided that it is best moment to flash newest CM to solve issues, but after reboot screen was black again.
I can enter download mode so it is visible in Odin, but screen is black in every mode.
There is only quick flash on screen when turning on and also really short moment of Samsung Galaxy logo which becoming dark quite quickly.
I flashed stock rom(5.0), but nothing changed, despite of that I know phone is turning on somehow because I hear music on turning on...
Can someone help?
I really doubt that it can be hardware issue.
Can it be something with BL ? How can I solve it...?