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.
Related
Hi folks, This is the first time I need help from this excellent forum.
Something weird happened. I was updating apps from Google Play and when Titanium (Pro version), came up my phone crashed. I'm not a total noob, Unlock, Root all of my phones. No I never flashed other ROMs
I've tried everything to unbrick my phone (Nexus 4, 5.1.1., unlocked and rooted, factory ROM).
Now my PC doesn't recognize my phone, it's stuck on boot screen, can't boot into recovery, (error 10), no Fastboot, no download mode, I can't do anything. I've unbricked my phones many times before. Can't install MTP device driver including other drivers. This one has me stumped. Been at this for 4 days.
Can't sideload. Power and other buttons don't work to boot into Recovery, Fastboot etc,
Obviously, can't do a "battery pull" on Nexus 4. Tried the 15-second power button trick to simulate battery pull and other button tricks. Can someone help?
I've searched the web for days, tried all the tricks.
Can someone help?
Cheers!
What buttons are you using for fastboot mode? What when you power it off, then while pressing volume down button, press the power button?
Nitin
Thanx for replying Nitin
nitin.chobhe said:
What buttons are you using for fastboot mode? What when you power it off, then while pressing volume down button, press the power button?
Nitin
Click to expand...
Click to collapse
That's the thing. I've tried all the button combos. The problem is my PC doesn't fully recognize my phone so I can't access or push fastboot or ADB. It shows up in device manager but that's it, nothing else. The phone goes only as far as the boot animation and stays like that for days. I've soft bricked my other phones before but was able to repair them.
I get fastboot not found, ADB error 10. I've never seen anything like this. I also get an MTP driver error.
It got bricked by a Playstore app update then when Titanium backup pro came up, that's when it crashed???
I have a Nandroid backup on my pc but it's useless.
Thanx, I hope someone can figure this out. I'm running stock ROM, 5.1.1, unlocked and rooted.
I'm using Nexus Root Toolkit but can't push fastboot or ADB, because, like I said, it doesn't show in my computer???
Nomad5000 said:
That's the thing. I've tried all the button combos. The problem is my PC doesn't fully recognize my phone so I can't access or push fastboot or ADB. It shows up in device manager but that's it, nothing else. The phone goes only as far as the boot animation and stays like that for days. I've soft bricked my other phones before but was able to repair them.
I get fastboot not found, ADB error 10. I've never seen anything like this. I also get an MTP driver error.
It got bricked by a Playstore app update then when Titanium backup pro came up, that's when it crashed???
I have a Nandroid backup on my pc but it's useless.
Thanx, I hope someone can figure this out. I'm running stock ROM, 5.1.1, unlocked and rooted.
I'm using Nexus Root Toolkit but can't push fastboot or ADB, because, like I said, it doesn't show in my computer???
Click to expand...
Click to collapse
Try using a friends windows laptop/computer and windows will most likely install drivers on it for you then use nrt to fix your phone from fastboot could also be a bad USB cable or bad USB port though
Nomad5000 said:
That's the thing. I've tried all the button combos. The problem is my PC doesn't fully recognize my phone so I can't access or push fastboot or ADB. It shows up in device manager but that's it, nothing else. The phone goes only as far as the boot animation and stays like that for days. I've soft bricked my other phones before but was able to repair them.
I get fastboot not found, ADB error 10. I've never seen anything like this. I also get an MTP driver error.
It got bricked by a Playstore app update then when Titanium backup pro came up, that's when it crashed???
I have a Nandroid backup on my pc but it's useless.
Thanx, I hope someone can figure this out. I'm running stock ROM, 5.1.1, unlocked and rooted.
I'm using Nexus Root Toolkit but can't push fastboot or ADB, because, like I said, it doesn't show in my computer???
Click to expand...
Click to collapse
As far as I have seen, Nexus 4 can not be bricked You can even remove the bottom 2 screws to remove the battery, it is not so difficult (I can say that as I have replaced the battery, power button as well as back of the phone on multiple occasions)
Also try what @[email protected] has suggested.
Nitin
I used platform-tools-v16 and Universal_Naked_Driver_0.72 to flash stock room and unlock bootloader... worked fine. Maybe this helps...
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
My 6T is currently a paperweight (bricked, screen won't turn on, no fastboot, no nothing) and here's the succession of events that led to it:
I live in the US and bought the unlocked 6T.
1) A few weeks ago I rooted it with same steps described in this post --> https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/. Everything seemed to go well, I had Magisk and my phone worked just fine.
2) About a week later I got a notification that my phone had a software update ready. I idiotically obliged and installed it. After the install, I still got the bootloader unlocked screen at start up so I thought my phone might still be rooted. However, I couldn't download any mods on Magisk and my root checker said I was no longer rooted. So basically, my phone appeared rooted (apps like Google Pay wouldn't work, I got the warning about the Bootloader at start-up, etc.) but I no longer had the benefit of being able to install mods through Magisk.
3) A few weeks later (yesterday) I decided I would explore options for un-rooting, mainly so I could use Google Pay again. Remember, my phone wasn't actually rooted anymore, since the update. So I thought locking the bootloader should fix my problems. I did that with fastboot oem lock and then my phone was stuck in a fastboot loop. I tried every option in fastboot and would just end up right back there. I started looking for fixes and came across the MSMDownload Tool --> http://https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892. I downloaded the driver, it recognized my device, I downloaded the tool, then ran it. At 16 seconds, the download stopped and I got an error saying "Sahara communication failed." After looking up a fix that involved holding down the volume+ button, I decided I'd try again. This is where I f*cked up. I unplugged my phone without stopping the download, and that leads us to this very moment. My phone does not turn on at all. I have no access to fastboot or anything. My computer does recognize it when I plug it back in (I'm on Windows).
If you read this it's probably obvious that I only know enough to be dangerous and bricking my phone was inevitable. Feel free to call me an idiot, I only ask that you provide some useful information, preferably on the subject of getting my phone working again. Thank you all in advance. I hope this post isn't redundant. I didn't find anything on here that was a fix for my situation. I'm also open to contacting OnePlus if anyone thinks I should do that first. I genuinely thank anyone that takes the time to read/help! xd
Use the msm tool...doesn't use fastboot
Edit...nevermind
You need to get your phone to show up as "US8_BULK" like in the MSM thread you linked. You can do this even if your phone wont boot properly. I have done it multiple times before. When in the Qualcom flashing mode the screen will not light up at all.
Hold all the buttons until it resets. This could take up to 30 seconds of holding the buttons. The just follow the steps in the MSM thread starting with this one:
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process - (https://www.youtube.com/watch?v=PpLvmID1wdI)
Edit: It can take some practice to get the timing down, especially if your screen is not coming on at all. Just keep trying as you will be able to get into that Qualcom flashing mode unless there is physical hardware damage to your phone.
Jager said:
You need to get your phone to show up as "US8_BULK" like in the MSM thread you linked. You can do this even if your phone wont boot properly. I have done it multiple times before. When in the Qualcom flashing mode the screen will not light up at all.
Hold all the buttons until it resets. This could take up to 30 seconds of holding the buttons. The just follow the steps in the MSM thread starting with this one:
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process -
Edit: It can take some practice to get the timing down, especially if your screen is not coming on at all. Just keep trying as you will be able to get into that Qualcom flashing mode unless there is physical hardware damage to your phone.
Click to expand...
Click to collapse
Awesome, that worked! I kept seeing I needed to hold volume+ and power but holding both and power is what actually worked for me. Thanks a lot my friend
@lapitman, glad to see that you finally got it to work!
Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!
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.