Posted recently as my Nexus 7 seemed to be bricked. It seemed hopeless as it was a competition prize and i had no receipt of purchase and it seemed that the factory warranty had run out. nVidia the competition sponsor I guess bought a shed load of them and then handed them out later.
Anyhow, after seeing repeated demands that I use the original charger (which was a US charger and as such not compatible with 240V power in the UK) I finally decided to try it. I remembered that i had bought a transformer for a guitar effects pedal so I plugged that in and the charger into that and then the Nexus 7. Still no joy. However I decided to leave it connected and let it charge over night and the whole of the following day.
This evening I forlornly tried to boot the unit and HURRAH! I got the Google logo.
I waited for the animation to start for Android....
And I waited.....
And I waited a bit more....
Nothing. It seems stuck. I then powered it off by holding the power button and it turned off, only to immediately turn on and stop at the Google Logo. The only way to stop this was to get into fastboot mode (Power and volume down pressed) and cycling to power off and hitting power again to execute.
So I thought I could get somewhere.
However I cannot get it to go properly into recovery mode. I get the bootloaded screen where I can restart the bootloader (which does just that), power off (which also works correctly), Start (locks at Google Logo) or recovery mode (which also locks at the Google Logo)
I cannot get to the screen with the image of the Android with the red triangle and the exclamation mark.
The bootloaded screed says the following:
FASTBOOT MODE (red text)
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d2d422357f20b
SIGNING - not defined yet
LOCK STATE - LOCKED
I have the SDK loaded and I cannot get the "Fastboot devices" to work. I previously sideloaded KitKat onto it so all the drivers are installed. I cannot get my PC to see that there is anything plugged in to the USB port. I think i need to get to this screen so that I can initiate a total system restore don't I?
Also the system heats up like an oven when it is locked at the Google logo.
I have repeatedly tried to get the drivers installed and have yet to get the PC to recognize the device. This is really wierd as I had used the adb to sideload KitKat onto the device.
Shortly after the sideload and a small 1.5Mb OTA update it went on the fritz. It would do absolutely nothing. After an extensive charge on the original 2A charger I can get it into Fastboot. However the fastboot sometimes freezes and I cannot get into Recovery Mode. Whenever I try to hit the power for recovery I get the Google logo and that's it. Have tried numerous presses of Vol-up and Power but no use.
It seems that there is something that the unit is trying to process and cannot get past that point. What can I do? I seem to be in driver hell. I am totally Stock. When the system was last operational USB Debugging was switched on. I don't care if I have to wipe it flat, I just want it working again.
Help please!!!!!!
Related
So to answer the first question, yes I followed the stickied guide up top, and yes, it successfully flashed the bootloader, wiped all data, and flashed stock ROM all to success. It appears my case is unique. I was told that it could be the battery connection, so I've done no fewer than half a dozen times of taking the back off, resetting the battery connection, and closing back up. It does not appear to be the battery.
I am stuck on the fastboot screen, the one where the android is lying down and blue squares project from an body. It shows me the controls I can make with the volume switches and the selection choice of 'Start'... but I cannot do anything. Before I went to flash I could move through the selection with Vol Up ONLY, but now I cannot even do that. Here's all the mode says:
Code:
FASTBOOT MODE
product name - grouper
variant - grouper
hw version - er3
bootloader version - 4.23
baseband version - n/a
serial number - ###############
signing - not defined yet
LOCK STATE - UNLOCKED
I've pretty spent the past twenty four hours on google searching through all the threads I've seen. They are either all dead, or most of them found the sticky fixed their problem. Has anyone heard of it coming to this?! All I can do is access fastbook VIA a DOS prompt and do fastboot commands, and if I disconnect the tablet from my PC, it'll remain in this mode with the screen on until the battery dies. Charging appears to charge the tablet, but again, no controls work. And yes, the buttons were set properly when I closed my tablet.
Anyone?
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
...Awesome... said:
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
Click to expand...
Click to collapse
I'm just trying to boot up! I don't know what happened, but I haven't been able to use it for school all week!
I cannot boot into the OS. Any time I plug this device in it sends me to the fastboot screen with no controls.
OK I just flashed CWMR 6.0.4.3 and it did not fix the problem.
Any other ideas?
I just repeated all the steps again to see if any of them failed before, they have not worked. So recap:
Stuck in fastboot mode
Android will not boot
Loose battery connection is not the problem
I am able to access fastboot on my computer
I have followed everything from the sticky (wipe everything, flash bootloader, flash image)
I have flashed a new recovery
I am still stuck in fastboot
I cannot control options in fastboot with the volume and power buttons
I can only access fastboot by charging my tablet
The only way the tablet will power down is when it completely depletes it's battery
As far as I can tell, nothing was wrong with the tablet when it was functioning
This happened when I went to charge my tablet, presumably when the battery ran flat running android
If I charge too long the tablet gets fairly hot.
That's about all the information I can provide. Is there anything else I can try? Please, I need a tablet for school and I cannot afford a new one!
hi all,
i had the nexus player with me and installed cm12.1, everything was working fine, i had it at the hotel i was staying at. no issues whatsoever. but after i unplugged it and brought it back home, i plugged it back in and it just bootloops on the google logo. the bootloader is unlocked.
i tried pressing the reset button while powering it on, but no luck, the leds dont flash quickly to enter fastboot.
ive tried also keeping the reset button pressed again while powering it on, and eventually the led will blink slowly. i then let go, but then it just brings up the google logo again and will bootloop. tried plugging it into the pc while doing this as well, but adb doesnt detect it either.
pretty cant get into fastboot mode or even the recovery mode. any hints or tips i should try? i dont want it to be dead after just 4 months of usage.
Lol I did the exact same thing in pretty good at getting out of a brick but the nexus player is pretty low on my list its actually been like this for about two months now and I haven't touched it
While the LED is blinking slowly have you checked to see if the device is enumerating over USB at all. I believe slow flash indicates recovery mode. Do you ever see Andy with an exclamation mark?
Sent from my D6503 using Tapatalk
well I was able to get it back up and running by plugging it into my pc and messing with the drivers a little bit, then I used fastboot to flash the stock firmware again and now im putting a custom recovery back on it, all in all its pretty easy to fix so its definitely not dead for good. Sorry im not great with tutorials
howd you end up recovering. i want to get it back up and running. perhaps i can try another pc.
when the led flashes slowly, i have the hdmi cable plugged in, but it just bootloops, never gets to to the android recovery mode. first time ive had a bricked android device.
kewvention said:
howd you end up recovering. i want to get it back up and running. perhaps i can try another pc.
when the led flashes slowly, i have the hdmi cable plugged in, but it just bootloops, never gets to to the android recovery mode. first time ive had a bricked android device.
Click to expand...
Click to collapse
Boot into the bootloader by unplugging the nexus player and then hold the button on the bottom and plug it in. Let the button go when you see the google logo. Then just use fastboot to flash the stock firmware.
Hi guys,
I had Pure nexus rom installed:
http://forum.xda-developers.com/nexus-4/development/rom-pure-nexus-project-layers-t3237366
and everything worked fine for weeks. Yesterday I noticed that my nexus 4 is using battery too much, without any reason.. Then my phone turned off, try to restart but it was stuck on google logo. At that point there was 20 or 30% battery left. I boot it to recovery, wipe everything and tried to restore factory settings, cos I didnt have any backup on phone. But again it was stuck on google logo.
So now I cant boot it cos there's no system installed on it, basicaly there is nothing on my phone. I tried Nexus Root Toolkit, but my pc dont recognize my phone, when I boot to recovery it's still the same, so I cant install drivers..
At this point, I have no idea what to do.. Can anyone help pls?
Thx
Can you get into fastboot? Are you using Win7? Tried different USB ports and cables?
audit13 said:
Can you get into fastboot? Are you using Win7? Tried different USB ports and cables?
Click to expand...
Click to collapse
Thx for quick reply !
Yes, I'm using win7 64x, I tried all usb ports and 3 different cables and nothing. I can get into fastboot and recovery, but pc still don't recognize anything..
i am currently under the same situation
only difference is i can still fastboot and flash a recovery (twrp for that matter)
afterwards, when booting to recovery - i can install a rom
once the rom is installed, reboot does not boot into the ROM and instead just displays the google logo - then vibrates a little - then the screen turns off
I just tried on 2 other win7 pc's, still nothing.. Nexus root toolkit just can't establish adb/fastboot connection..
edit: other thing I tried is to copy ROM file on usb stick, and then connect usb stick with micro usb cable to phone, and when I'm in recovery (twrp 3.0.2-0) there is just ''internal storage'' option.. Is that normal, should twrp see external USB drive? Cos I'm thinking that maybe something is wrong with usb charging port (I replaced that board month ago).
Hi,
I have a similar problem:
I had my mobile in working condition and once when upgrading the OS to 5.0.1, it downloaded the OS and was upgrading. During that process, the charge got over and hence the phone was shutdown. There after, it was not proceeding further from Google screen when trying to reboot. So, i thought battery is dead and replaced the battery with a new one. Now, i am getting the following problem:
The phone doesn't turn on(not even getting GOOGLE screen now). But, If I keep holding power button and Volume down button and try to insert the charging cable immediately then i get the boot menu but it wont stay there for even a second and goes to GOOGLE logo screen and gets shut down. Please help me with this.
Hi guys,
I menaged to fix the problem, my problem was charging port (smal L shaped board) that I replaced month ago. That's why there was no connection.
I got another one this morning from ebay, and Nexus Root Toolkit established connection immediately.
guruhg said:
Hi,
I have a similar problem:
I had my mobile in working condition and once when upgrading the OS to 5.0.1, it downloaded the OS and was upgrading. During that process, the charge got over and hence the phone was shutdown. There after, it was not proceeding further from Google screen when trying to reboot. So, i thought battery is dead and replaced the battery with a new one. Now, i am getting the following problem:
The phone doesn't turn on(not even getting GOOGLE screen now). But, If I keep holding power button and Volume down button and try to insert the charging cable immediately then i get the boot menu but it wont stay there for even a second and goes to GOOGLE logo screen and gets shut down. Please help me with this.
Click to expand...
Click to collapse
That looks like a stuck power button.
Try just holding the volume down button and plugging the charger.
If you see the fastboot screen, you have a stuck power button.
Just experienced this issue on a Nexus 5 and I was able to recover from it by "massaging" the power button for a while.
So I pulled out my XT907 to test a new cable I have. The port on the phone has been damaged and it won't charge and won't be recognized by my PC. The port stopped working ages ago during a reset to stock using RSDlite. So when the device tries to boot, it goes straight to the fastboot screen and tells me there was a flash failure. This screen also tells you if you have a USB cable connected. Heres where I am confused. According to this screen, when I plug in a cable, the device registers it as being plugged in (or not plugged in), but the PC won't say anything. Since then I thought I also lost TWRP as a result of the flash failure. Today I found out I was very wrong. I got the device to boot to TWRP without issue, the red Motorola logo even appears at boot which hasn't happened since RSDlite failure. From there I went to the file manager and discovered the whole system is still there. So I am confused as to what is really happening here: 1) Either the USB port on the phone works or it doesn't, depending on what you believe (the phone or the PC) 2) If RSDlite did fail, as fastboot says, how would I even be able to boot to TWRP? 3) Given number 2, if the flash really did fail would it cause the device not to be recognized? 4) Also given number 2, the logo shouldn't even appear period. EDIT: 5) With the device powered off and I plug it into an outlet or my PC, it will power on into fastboot and also says USB connected.
So I decided to dig out the phone and play around with it. I can still get into TWRP so I managed to flash system and boot. Here's the weird part. I thought the phone wouldn't charge. I was wrong. It charges on almost every cable, but my PC will not recognize it in AP fastboot or TWRP. I had forgotten about the 3 button trick, volume up + volume down + power brought me to the recovery menu. I just let it sit there for the few seconds it stays and suddenly the red logo appeared...and the phone booted...normally. So it does charge, but adb or fastboot is a no go. Looks like if I keep this phone, I'll be flashing what I can or am able to with TWRP, on an external SD card if I can't download it to internal.
So it appears only the AP fastboot partition is damaged...every time It boots to it (if I didn't intentionally do it) it says "fastboot flash failure". So since I can't use RSD lite, what are my options?
So the only thing that was damaged was AP fastboot and anything beyond that, including 'charging mode' (thanks for that trick @sd_shadow though it didn't work). For a couple years I thought the clip inside the charging port on the phone was too badly damaged to take a charge or be recognized by my PC. So with intentions of fixing it myself, I put it in a drawer until such time. I knew there was some hope in salvaging it despite the 'flash failure' because every cable I tried, would only charge the phone so no PC means no RSD Lite. I was convinced TWRP would save me and I would find a way to flash everything I needed, but was only able to get as far as the boot.img and system.img. So last night I started to play around with the phone after having plugged it in and noticed the green light in the upper left corner turned on. I spent a few hours flashing and reading and flashing some more before I found another post by @sd_shadow referencing to three buttons, press and hold in this order: volume down, volume up and power. That got me to the stock Motorola recovery screen, which only hangs around for abut 10 seconds, so you have to be quick at selecting an option. I did not select an option, and much to my surprise the phone booted all the way and properly. And that was the only issue. I still had TWRP too. However anytime I needed to reboot, it would go straight to the AP fastboot screen. The 3 buttons bypassed that.
I looked inside the charging port on the phone as I had many times before, and noticed what looked like a piece of foil stuck inside of it. I tried to dig it out but I just managed to push it between the crack in the clip. I plugged it back into my PC and I was even more surprised when it made the familiar connect sound. So I assume that piece of foil was actually a pin, and I managed to seat it just right that the phone charges, is recognized by my PC and i was able to SUCCESSFULLY recover using RSD Lite. We're back in business
After trying tons of different methods to bypass FRP on this TB-X606F without any success, I was FINALLY able to bypass it. I was not expecting this to work, so I wasn't documenting or taking screen shots. I typical solutions with sp_tool I was unable to get to work.
Was tested on
TB-X606X_RF01_220613
TB-X606X_USR_S300673_2206131545_V9.56_BMP_ROW
I only set the location of the 3 files as shown in the screen shot. Nothing else. Pressed "download"
Connected to computer while off, did not do anything initialy. Believe I pressed power + vol up or power + vol down and sp_tool immediately started the download, took maybe 30 seconds, green check mark when done.
https://imgur.com/AvdFpFs
uploaded: https://anonfiles.com/B382E8ncze/TB_X606F_FRP_Bypass_Verified_April_2023_Full_7z
hope this helps someone.
Edit: I did have the vcom drivers installed from here: https://www.getdroidtips.com/install-mediatek-mt65xx-usb-vcom-drivers/
Initially I was having a hell of a time trying to get it to boot into the correct mode. I was briefly able to see it connect with the vcom driver and com port, when sp_tool would attempt kinda sometimes to start, but would always fail.
Also make sure battery is 100%
Edit 2: During my initial resetting (tried the obvious first, wipe data/factory reset in recovery. Then used lenovos recovery tool which I had read would erase FRP. It did not, and also updated me to the newest version). I bought this tablet "new open box" on eBay, on the cheaper end, seller failed to mention was FRP locked. I figured ehhhh, easier just to flash it than start a case, send it back, etc etc... When I messing with SP flash tool, I was being slightly dumb and had a battery with maybe 30% charge, which didn't matter, since I knocked the tablet while it was attempting to start to do things and it became unplugged. Not sure if SP flash tool was doing anything, task manager showed it seemed like it was, but the program was mostly frozen and not giving me any info. Kept charging it up on the wall charger, but all I could get was a solid red light, no attempt to boot, and windows claimed unrecognized device. In hindsight, I'm wondering if I did not have the vcom drivers installed at the time, or correctly installed them (could have had a conflict, dunno) I was actually just going to RMA it since it looked nice and bricked. Left it on a charger for a week, was busy and just kinda forgot about it. I went to grab it the day I posted this and saw oh... 100% charged battery icon...... that's new... Turned it on, and I was back at the initial setup still FRP locked.
I also do not think that with the tablet off and plugging it in with with Vol Up an Down buttons pressed is correct. I haven't had that do anything for me. Cable aside, Power + Vol Down will get you into fastboot, Power + Vol Up *sometimes* would get me into recovery? It seemed pretty hit or miss. Tried a download mode jig, no dice, tried (forget what the name of it is...) a FRP/Boot/Programming cable thing, no dice on that either.
Again, I hoping this helps someone. I tried everything to get FRP bypassed, even shady shady "tools" and blatantly out of focus click bait virus linked YouTube videos.