Database Users

Stuck on Google logo - can't get bootloader, PC won't recognize

Before I start, I just want to say that I've looked at dozens of threads with similar issues and nothing has helped.
My Nexus 7 will only power on to the Google logo screen.
Things I have tried:
1) Getting to the bootloader/recovery -- tried using the official method (power and volume down) as well as every single combination of power, volume up, volume down and both volume buttons pressed at the same time. All over 10 seconds and as long as a few minutes. Nothing will get it go to the recovery or bootloader.
2) Connecting to PC. Yes, I've tried with several cords, numerous USB ports and even several computers. Not one will even recognize it. I've used Wug's Nexus Root Toolkit to install drivers. Downloaded images to flash. It will not recognize it either via Fastboot or ADB drivers. Nada.
3) Opening it up and checking connections, including the battery and other visible connections that could be unhooked and plugged back in.
4) I've let the battery drain completely and sit for a few days. Then recharged and same thing occurs. Will only go to Google logo no matter what combinations of buttons I've tried.
I've had it two years, so obviously it's past it's warranty period.
I've pretty much come to the conclusion that it's hosed and don't think anything will fix it. But I thought I'd try posting here, realizing all of the other posts I've read have at least been able to get it to the bootloader.
Any other suggestions????

If you can't get to bootloader...and windows won't see it...There's not much advice to give. Every fix involves fastboot pretty much....so you need bootloader menu and your PC seeing it.
You may be pickeled.

either your bootloader has been removed or volume down button is not working..
as i am a newbie. i dont have much knowledge so cant help further

Connect to your pc via usb cable, look under device manager on your pc. If lists yor Nexus an apx device, you are probably hosed. That means your Nexus has been completely wiped, bootloader, os, recovery, everything. Your only option would be an nvflash, but you would have had to already backup your nv blobs to be able to fix it. These blobs are device specific and need to be pulled from a working device. Google nvflash for more info.

[Q] Jiayu S3 semi-hard brick (NOT BY FLASHING), help needed

Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.

Bump..
Anyone?

bump

help pls, nexus 4 softbricked

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.

RSD Lite Flash Failure?

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

Finally! FRP bypass TB-X606F

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.