Develop Bugs

AT&T Tab Black Screen/White Line During Bootup Fixed

I took my stock AT&T tab and wiped it then flashed Roto JME-4. When I rebooted, I had a black screen for about 60 seconds, with a skinny white line, and I could hear the samsung music. After about 1.5 minutes, I pressed the power key, and screen went totally black - no line. Then I pushed power again, and everything was normal after that, unless I rebooted.
Anyway, here is it fix:
1) go to http://forum.xda-developers.com/showthread.php?t=899196 and download the jj4bootloader.zip file
2) use odin to flash the unzipped jj4 file. It goes in PDA and nothing else in any options.
3) upon reboot, you will have a 100% normal startup with logo and music.
I used the Bootloader Patch app to check this, and it reports it is safe, and that I can flash anything.
Thanks to Roto, Chain Fire, and alexnoalex

Ok, so, just to be sure I'm not going to break my Tab, doing this ONLY changes/fixes the boot animation etc. (get's rid of the AT&T stuff, and puts in the Samsung stuff).
To be clear, I just flashed Roto's latest Euro firmware (Baseband P1000XXJMA, Build FROYO.XXJME), so performing this fix won't affect/change ony of this stuff right?
If I have to re-flash everyting from scratch, then it's really more trouble than it's worth (Blank screen at bootup? Big deal... It's just at boot right? Everything else works perfectly!)

I wish rotohammer and other rom devs would include this information clearly in their initial posts. Took me awhile to find this fix but it works well. This is also important because you can't see the recovery screen without it.
Sent from my GT-P1000 using Tapatalk

Jade Eyed Wolf said:
If I have to re-flash everyting from scratch, then it's really more trouble than it's worth (Blank screen at bootup? Big deal... It's just at boot right?
Click to expand...
Click to collapse
This is just a quick 30 second flash thru odin, it only repairs the black screen, and doesn't touch anything else!
The developers took out the sound and logo to make the rom file size correct.

That's just the answer I was looking for! Thank you good sir!

Glad I could help.

Hello, I have the same problem but I cannot flash the zip file because my computer doesn't detect the tab when I'm in download mode. I tried updating the drivers and software and it still doesn't want to detect it. I cannot get into recovery mode because of the black screen/white line. Do you know what I can do to get my computer to detect my TAB? I tried searching the forum but could not find any info that helped. Any help is much appreciated. Thanks!
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build Froyo.XXJMA

Are you using windows xp, or 7? Put the tab in download mode before you connect to the computer. Is your tab set to usb debugging mode?

I used Win XP, Windows 7 x64 and x86, non of them worked. They can detect my Galaxy S I9000 phone but not my TAB. Yes, I tried it with both debugging on and off, it still doesn't work. Could it be the kernal's fault? Maybe the cable? It will charge the TAB but for some reason my computer won't detect it.

Try different usb cables and ports on the computer.

I tried a different wire and usb ports and it's still not working. I just realized the TAB is not charging anymore. It doesn't make the charging sound when I plug it in. Figured out it's not the cable because it worked on another TAB. Could it be the firmware or kernal?

Not charging when plugged in the computer, or in the wall outlet? Plug it in the wall for at least for hours to get a full charge.

It charges if I plug it into the wall but its very slow like when you charge it via usb. Im using the original charger and cable. There is an x next to the charging/lightening icon on the top when I plug it into the wall and computer.

Just let it charge all night. Be sure its off when charging.

What's the point of having it fully charged? How will that help? My computer still won't detect it even if it's fully charged. I need help to get my computer to detect it so I can restore the original firmware.

I have seen five problems like yours, and after a complete charge, then reboot the phone into download mode, the problem cleared up. They used a different usb port also.
Go to windows update and update your pc.
Look a few threads further down named «help help help»

Ok its currently 50% now. Ill let you know once its fully charged. Thanks for your help so far.

Its 100% and my computer still doesn't detect it. Now what?

Did you have a chance to see the thread “help help help"?
This will sound crazy, but double check your cable - recently someone had the same trouble, because they had dust in the cable connector.

I cannot see the thread you're referring to.
Yes, I did tried a different cable and it's still the same.

Hard bricked... without a good reason!

I've owned my SGII since release, went through a few roms, never had any issues. I have been running liquidsmooth for a month or two, without much issue. Although, lately stablity has dropped off a little. Nothing bad, just a freeze every few days and other minor hiccups.
Then something bad happened.... Last night I was using the phone and it turned off. Then it wouldn't boot. Battery pull, and rebooted but no joy. Then I booted to recovery (TWRP, but I'm not sure which version) and found that it said something along the lines of "E: could not mount /system", along with lots of other similar failure to mount messages. Oh well, I guess I'll just wipe it and flash something new. Any attempt to wipe would hang and then the phone would turn off after a few minutes.
Then I went to flash the stock setup from odin (using the howto from the dev section) , but it too would fail every time. I even tried different builds from samsung's official roms, but they all would fail to install on the phone. I read every thread I could find, and the next thing to try seemed to be an emergency recovery through Kies. That also failed, except it left my phone hard bricked. I can't get into download or anything, nothing shows in the device manager, just completely dead... I made a USB jig, but no luck there either.
I'm completely frustrated... I don't know what to do now... Buy a MB from ebay? The phone was flawless before all this. Any suggestions? I'm using a blackberry pearl for now, I can't let that happen.

Have you tried the Jig on another Samsung phone so you know the one you made physically works?
Some people have managed to get into DL Mode by pulling the battery, SIM, SD, etc. For 5 - 10 minutes then connecting it to the pc with Odin running b4 inserting the battery to enter DL Mode.
Otherwise mobiletechvideos has a really good reputation and turn around time for JTag service.
There is a chance its a hardware problem, and hopefully another member on here can shed some light on the possibility of it being a HW issue or not..
Cheers,
Chris

Thanks for the suggestions. I don't have another samsung phone to try the jig with, but I'll see if I can get a friend to let me hook up this crazy looking thing. I got the resistors set up to 299K, hoped that would be close enough, but perhaps not.
I tried that plug-first-battery-second trick to get into DL mode, but that's not working either.
I looked at the jtag service too, but my fear is that I have corrupted memory. In that case, I wouldn't get a refund if I still couldn't get to a fully healthy boot. It seems odd though... not like it's a common trend for this particular model (that I've seen).
Just seems so strange that it happened for no apparent reason... before it was hard bricked I was able to USB mount the internal storage and access and transfer almost all the contents, except for one folder. I wonder if that one part of the memory caused all the problems?
Again, thanks for the suggestions. I'll keep plugging away at anything that might help, and in the mean time I guess I'll keep my eyes out for broken phones or some way to salvage a board.

If im not mistaken, a hard brick should show up in you device manager as the board itself when connected.
Does anything show in you device manager when its connected? And have you tried using a different PC which has never had Kies installed on it, where you just install the drivers for the T989?
Odin tends to fail at the modem or due to the presence of a .PIT
I got myself out of a brick which started over the a very similar issue, but due to a bad flash.
After 5 hrs of getting nowhere (I was using a Jig) I would get Odin to recognize the phone (My Screen was NOT displaying the DL Mode screen, It was going into DL Mode but other than Odin recognizing it, there were no signs of life!) after enought tries but flashing to stock would fail. I ended up taking a shot at flashing the stock kernel using 512.Pit from a T959, Reflashing the same Kernel, then flashing recovery. I don't advise anyone do this as that PIT file is NOT for a T989, and it may have been BS luck not the use of that PIT file that did the trick.
But I did get it back running %100

Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.

This happen to me before, I just cleared cache and Davik then rebooted recovery then flashed another Rom.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Unfortunately for me, since data, cache, and system couldn't be mounted, I couldn't successfully clear them.

KLR Rico said:
Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.
Click to expand...
Click to collapse
I would put the jig in with the battery and everything still removed, and alot of trial and error trying things like battery first then connecting the cable with Odin always being already running. Then doing the reverse, etc.
When I did get Odin to recognize the phone, one thing I learnt is when it would detect, it only ever happened after having killed and reopened Odin. I have no explanation on why using "End Task" after each attempt to connect and opening Odin again made a difference but it did.
Have you had a look at the QPST thread? I would ask one of the members contributing to it about why you would or would not see the board. And you could always try installing the boards drivers manually, or enable "Show hidden devices" in your device manager.....
Did you contact the guys at mobiletechvideos and explain the details?
You were able to boot to recovery, so it sounds partition related. But I would try just to flash the stock UVLH1 kernel and recovery with Odin vs full stock rom if you do get it to detect. And if it does detect with Odin eventually do not let it reboot or loose power. Just Kill Odin, unplug the cable if you need to, Start Odin again and reconnect the cable. Once in DL Mode it will stay in DL Mode as long as you have the reboot option in Odin unchecked, etc.
Also if you can get the battery charged fully somehow, your best shot is with a fully charged battery.
Chris

[Q] [Help] How to fix SGT 3 10.1 (WiFi) not turning on

Hey guys, My Samsung Galaxy Tab 3 10.1 (Wifi) Won't turn on anymore. Don't even charge! My brother was playing minecraft until my Tablet's life reach 0% (Died). Then I charged it, It's still charging after 30 mins of charging I turned it on then the SAMSUNG GALAXY TAB 3 logo appear (Start-Up) but it fails like it shutted down. I tried charging it again but it wont charge anymore nor turn on, I'm not using any ROM but i rooted my SGT 3 10.1
Anyone knows how to fix this? Please help asap!

Try different charger, usb cable, leave it for a while then try charging it, plug it into computer usb port or plug out sd card then try
Sent from my SM-T210R using Tapatalk

Ripshock said:
Try different charger, usb cable, leave it for a while then try charging it, plug it into computer usb port or plug out sd card then try
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
Okay, Gonna try those now and hope something will fixed this. I'll reply if it works or not soon
Edit :
Be right back in 2 hours to check everything.
Edit Again :
My Tablet is fixed now, Thanks dude.
What I did is stopped charging for 10 minutes then i charged it using PC/Laptop then waited 1 hour, then charge it on normal then it started to charge and turned on. but again, stuck on SAMSUNG GALAXY TAB 3 logo then shut down....

None of those works. Any other idea?

I would do the process over again. But do not start the tablet. See if you can get into recovery mode (Vol+ / Power) or download mode (Vol- / Power). If that is successful then leave it there for awhile. Power off and try again. If good, then I would reload the OEM Rom or a backup that you may have. But I would not try powering the unit again. There might be a corrupt file caused by the initial improper shutdown.

It got even Worse, I tried to do the process again but it DOESNT turn on or Charge anymore. I waited 1 hour then charge, still, charge 2 hours, still. What to do now? Theres no helper here on our village except me so please help me

If your device is not charging then I wonder if it is the charger and not the device. I don't think the battery could go bad that fast. I could be wrong, but I don't think. So that leads me to believe that your charger possibly is not working like Ripshock mentioned.
Is the charger the OEM that came with the Tablet?
If not, can it produce 5vdc @ 2 amps?
What about the USB cable, is it OEM that came with the Tablet?
If not, is it wired correctly and can it handle 2 amps?
Regardless of how you answered the questions, I would seek another source for charging. I don't think the PC will charge. I don't believe the USP ports are setup to handle that much current. I could be wrong, but again, you might seek out another source for charging.

UPC won't charge tab. It has to be plugged into an eletrical outlet
Brian D said:
If your device is not charging then I wonder if it is the charger and not the device. I don't think the battery could go bad that fast. I could be wrong, but I don't think. So that leads me to believe that your charger possibly is not working like Ripshock mentioned.
Is the charger the OEM that came with the Tablet?
If not, can it produce 5vdc @ 2 amps?
What about the USB cable, is it OEM that came with the Tablet?
If not, is it wired correctly and can it handle 2 amps?
Regardless of how you answered the questions, I would seek another source for charging. I don't think the PC will charge. I don't believe the USP ports are setup to handle that much current. I could be wrong, but again, you might seek out another source for charging.
Click to expand...
Click to collapse

tones160 said:
UPC won't charge tab. It has to be plugged into an eletrical outlet
Click to expand...
Click to collapse
As I suspected, but I thought I read somewhere that the PC can be setup to do just that on the USB port. Key phrase is "thought I read".

Nah. For some reason the tablet can't charge and transmit data through the cable at the same time unlike our phones and other devices. Personally i think it's stupid that it won't charge but hey that's how they were made lol. I use a very good cable too.
Brian D said:
As I suspected, but I thought I read somewhere that the PC can be setup to do just that on the USB port. Key phrase is "thought I read".
Click to expand...
Click to collapse

Well, I have been to this situation more than once (Galaxy Tab 3 10.1 and Galaxy Tab 2 7.0, which are both family tablets). Do a "force boot"
Steps:
1.) Leave it there for, like, 4 hours or while it is charging do step 2.
2.) Now, press the power, volume up, volume down and home button together, until the it boots up completely
3.) Charge the tablet again..
Easy as that.. If that does not work, remove the battery inside (You need to have proper tools and a hand that can search youtube)
or, even if that does not work, your brother may have screwed something up (Either by dirty flashing another ROM or by doing some dangerous system modifications).. Your last hope is the repair shop (If you have warranty, send it back to a SAMSUNG REPAIR SHOP and act dumb, they will fix it for you, free of charge.)

I am not 100% sure here, but I don't think pressing the home key while using the power and vol keys will do anything. I believe that to be a process found on some of the other Samsung devices, but not the P5210. I personally have not tried it and I really don't want too knowing right now that my machine is working just fine. Would hate to do something that I cannot reverse.

- Mᴏʀᴏɴ - said:
Well, I have been to this situation more than once (Galaxy Tab 3 10.1 and Galaxy Tab 2 7.0, which are both family tablets). Do a "force boot"
Steps:
1.) Leave it there for, like, 4 hours or while it is charging do step 2.
2.) Now, press the power, volume up, volume down and home button together, until the it boots up completely
3.) Charge the tablet again..
Easy as that.. If that does not work, remove the battery inside (You need to have proper tools and a hand that can search youtube)
or, even if that does not work, your brother may have screwed something up (Either by dirty flashing another ROM or by doing some dangerous system modifications).. Your last hope is the repair shop (If you have warranty, send it back to a SAMSUNG REPAIR SHOP and act dumb, they will fix it for you, free of charge.)
Click to expand...
Click to collapse
Yep, I did those steps. and it's turning on now. but i cant start it up. When I open it, it goes to TWRP mode. This happens when I wipe all my phone cache,dalvik,etc (everything) then when i restarted the system it says "no OS installed, still continue?" I choose yes, then it said "your tablet's root could be corrupted, want to install a fresh new one?" I choose yes then my tablet restarts but on TWRP again, I install a rom named Pimpdroid then restarted the tablet, still the same (Always go to TWRP mode even i'm not press power+up volume+home bottom together) Just the power button but it goes to TWRP mode, i tried installing other roms but its still the same. If you can't understand properly due to my poor english. I can make a video on it if u r willing to help me. I really need help guys since theres no repair shop here its just an island!

Does anyone experienced this problem already? or does anyone knows how to fix this problem? Help me please

RazerKnight17 said:
Yep, I did those steps. and it's turning on now. but i cant start it up. When I open it, it goes to TWRP mode. This happens when I wipe all my phone cache,dalvik,etc (everything) then when i restarted the system it says "no OS installed, still continue?" I choose yes, then it said "your tablet's root could be corrupted, want to install a fresh new one?" I choose yes then my tablet restarts but on TWRP again, I install a rom named Pimpdroid then restarted the tablet, still the same (Always go to TWRP mode even i'm not press power+up volume+home bottom together) Just the power button but it goes to TWRP mode, i tried installing other roms but its still the same. If you can't understand properly due to my poor english. I can make a video on it if u r willing to help me. I really need help guys since theres no repair shop here its just an island!
Click to expand...
Click to collapse
When it asked to reinstall the root, say NO. Then power off the unit. Do not try and run the tab at this time. There is no OS. Start the tab in download mode. Connect to PC and start ODIN. Load the OEM Rom. This is the only way to get things back to normal unless you have saved a backup. If you have a back up, then start the tab in recovery mode (TWRP/CWM) and restore from backup.
I would recommend NOT installing Pimpdroid or any other rom until you have a fully operational tablet again. Best to always start from a fresh OEM Rom.

What is OEM Rom? and where can I download it?

OEM = Original Equipment Manufacture
OEM Rom is the firmware that was developed by Samsung and is the only official Rom for your device. All the other roms that are developed here are done so with caveats placed on them. Mainly that the roms can damage your device or brick it (cause it to fail completely).
Original firmware (OEM Rom) can be found here. In the search window just enter the model number of the device you have. In this case that would be P5210. It will take several hours to download the rom as it is huge, on the order of 1.9GB. Just be patient. It is always a good idea to have the OEM Rom safely tucked away on you computer for situations like this.

Brian D said:
OEM = Original Equipment Manufacture
OEM Rom is the firmware that was developed by Samsung and is the only official Rom for your device. All the other roms that are developed here are done so with caveats placed on them. Mainly that the roms can damage your device or brick it (cause it to fail completely).
Original firmware (OEM Rom) can be found here. In the search window just enter the model number of the device you have. In this case that would be P5210. It will take several hours to download the rom as it is huge, on the order of 1.9GB. Just be patient. It is always a good idea to have the OEM Rom safely tucked away on you computer for situations like this.
Click to expand...
Click to collapse
It's just like a rom? after downloading ill just install it like other roms?
and, Which country firmware should I download? There are tons of Country but the same rom

You will download the version for your country. I have no information about your whereabout. So you will have to find the rom for your country or region of the world.
You will need to extract the MD5 file from the zip and place it on your computer. Once extracted, you will open ODIN and load the MD5 file into the PDA slot and upload it to your device. Don't worry about the SS_DLL file. It will take some time to load into ODIN and then some time to load into your device. Do not stop the upload or interrupt. Once loaded, you will then restart your device and configure it like it was brand new out of the box.
The standard recovery will be loaded also. If you desire to load TWRP or CWM, you can if you want. You can also root the device. But I would not recommend loading any of the other roms until you get a better understand of what that rom does and how to load it. There are many posts on XDA that tell you how to load an OEM (stock) Rom. Just do a search for them. No need to be redundant here.
Just be careful.

Brian D said:
You will download the version for your country. I have no information about your whereabout. So you will have to find the rom for your country or region of the world.
You will need to extract the MD5 file from the zip and place it on your computer. Once extracted, you will open ODIN and load the MD5 file into the PDA slot and upload it to your device. Don't worry about the SS_DLL file. It will take some time to load into ODIN and then some time to load into your device. Do not stop the upload or interrupt. Once loaded, you will then restart your device and configure it like it was brand new out of the box.
The standard recovery will be loaded also. If you desire to load TWRP or CWM, you can if you want. You can also root the device. But I would not recommend loading any of the other roms until you get a better understand of what that rom does and how to load it. There are many posts on XDA that tell you how to load an OEM (stock) Rom. Just do a search for them. No need to be redundant here.
Just be careful.
Click to expand...
Click to collapse
Well, This is pretty weird. There's no Philippines (Which is my country) OEM rom and on the Tablet, it wont go to Recovery mode or Download mode. because when I charge my tablet it automatically opens then go to TWRP. When i turned it off it goes to normal charging. Then when I try to open it using this (Power button+volume up+ Home) it still goes to TWRP mode. How to fix this?

Need help. accidentally wiped os after flashing recovery and now have trouble

So I have had this device since February and finally decided I wanted to Unlock the bootloader, install a custom recovery and get some cool new roms on it. I have the GPE by the way.
Anyways so I unlocked the bootloader and flashed TWRP and then rooted the device by flashing a zip file for root. I assumed the tablet got rooted so I then decided to try the multi window hack and flashed that. Well it caused some apps to corrupt (the phone app in particular) and they would keep crashing preventing me from doing anything. I decided to go back into recovery and try to do a data and cache wipe but that did not help. Eventually I wiped the entire OS which was a mistake. I was still able to get into recovery mode but I have no SD card to load up with a rom to flash and it was late to go buy one. I also tried ADB through the recovery mode that did not seem to work.
I did some searching and found out that I could download the LGMlauncher and it could get me back to stock but to use that I needed my serial number which is on the box (which I had at the office). So I plugged it in (and got the little battery icon) and a few hours ago went to the office to get the box. I tried the LGMlauncher and it keeps on crashing while trying to update and now I am not able to get into recovery mode. What are some other steps I can take to try and recover it?
Thanks.
Edit: I tried the LGMlauncher again and it said my battery was low so I plugged it back in. is there a trick to charging it while it is off? I assume that could be why recovery mode wont work.

Hi, if you have twrp recovery and it is working you can install your missing system by following this post
http://forum.xda-developers.com/showthread.php?p=53744333
Good luck
Sent from my LG-V510 using Tapatalk

schalmers said:
Hi, if you have twrp recovery and it is working you can install your missing system by following this post
http://forum.xda-developers.com/showthread.php?p=53744333
Good luck
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
Yeah It appears as though the battery was not charging even though I had plugged it in and now it is dead. I cannot seem to get it to go into recovery or anything. Is it safe to say it is bricked?

When my HP Touchpads battery was to low to take a charge from the wall charger, the only way it could get enough charge to be able to use the wall charger was to trickle charge it from my computer usb port for a couple of days.

Jubeldum said:
When my HP Touchpads battery was to low to take a charge from the wall charger, the only way it could get enough charge to be able to use the wall charger was to trickle charge it from my computer usb port for a couple of days.
Click to expand...
Click to collapse
Yeah it has been plugged into my PC for a few days and nothing.

Bootloader unable to boot ROM, recovery. Computer not detecting fastboot presence

My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.

zakoda said:
My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.
Click to expand...
Click to collapse
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:

dominoeflux said:
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:
Click to expand...
Click to collapse
I have mentioned in my post: It is not a driver problem

zakoda said:
I have mentioned in my post: It is not a driver problem
Click to expand...
Click to collapse
if its not being detected in fastboot mode, than that means it's a driver problem since the same thing happened to me. you have to manually install the fastboot driver for fastboot mode. I've read your post and I understood exactly what you were talking about. have you even tried to check the driver? have you tried flashing back stock? if you've checked other computers that you have mentioned and it's still not detecting it in fastboot mode with the other computers, than the driver for fastboot mode needs to be updated manually, seeing that if it was detected by the other computers that you have, you wouldn't be asking for help right now because your device would already be up and running. hey i'm just trying to help u here. it doesn't hurt to double check your driver. I may be a junior member, but I know plenty seeing that I've been through the same situation myself. if it's not the driver as you say it's not, what version TWRP were you running and did you restore a backup with the EFS checked?

Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.

zakoda said:
Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.
Click to expand...
Click to collapse
In the most country, the warranty is 12month so maybe gone because now it's 21th of december