My phone was working fine, and I decided to change ROMs, as I wanted to be able to use Split Screen, and the current custom ROM had a few issues. Anyway, I try flashing this new ROM, ExtendedUI: wiped the data, cache, and system and flash everything correctly, or at least I followed the instructions word for word. However, as I flashed magisk, there was an error, and I assumed that I would have to boot the phone first, as I have done in the past and it has always fixed the issue, come to find that when i reboot, it reboots into fastboot, and nothing else is on the system. Great. So i go back to MiFlash and flash davinci 11.0.2 and then go to reboot the phone and then nothing. Black. Phone doesn't vibrate when pressing both Vol up and power and/or Vol down and power. Left the phone to charge to see if it was just over drained battery wise and still nothing. Opened up the back and reconnected the battery to see if there had been some kind of hardware disconnect and, you guessed it, nothing. Any ideas on what I should do?
Well since you already bothered to open the phone I guess your can try the EDL/testpoint flash method.
I'd also double check or change the USB cable. For MiFlash to hard brick your device there must have been some transfer issues (or the source files were corrupted).
ShiningScias said:
Well since you already bothered to open the phone I guess your can try the EDL/testpoint flash method.
I'd also double check or change the USB cable. For MiFlash to hard brick your device there must have been some transfer issues (or the source files were corrupted).
Click to expand...
Click to collapse
After posting this message, I went to sleep, and woke up to the phone LED flashing. But nothing else had changed, even after trying all the key combos and connecting to the pc and whatnot. So I decided to try the EDL flash method, with multiple cables that have worked previously for data transfers, as well as different usb ports, and still nothing. I made sure to disconnect the battery. I'm not sure what else I can do.
Related
So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
*deleted*
vesheljinn said:
So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
Click to expand...
Click to collapse
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
This is what I thougth as well. But his link only refers to B08 in MM. So he didn't want to install B08 on Nougat. As his bootloader is still locked he cannot install this ROM in no way.
Choose an username... said:
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
Click to expand...
Click to collapse
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
vesheljinn said:
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
Click to expand...
Click to collapse
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
jjallday said:
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
Click to expand...
Click to collapse
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
hmm well idk i had this problem earlier today, even when i had mine connected to the pc the pc would make a noise as if the phone was turning on, but when i connected to the actual charger is when the 60sec thing actually worked , also i noticed that when i finally got it on the battery was down to 1% maybe some sort of battery issue. maybe let it set on the actual wall charger for awhile and try again.
vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
Do the 4th category brick repair guide. Yes,you have to tear apart the phone, but I did this and didn't break it idk
No USB jigs or weird cables will work, you need to use the test pad to get into EDL.
There is another way though: it seems that if you discharge the phone completely, then hold vol down and power, and try a bunch of times, you might be able to get into FTM mode. You'll have adb from there, so you can do 'adb reboot edl' and use MiFlash to fix the software. But I haven't tried
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
EDIT: solved with 6T MsmDownloadTool V4.0 (OOS 9.0.5).
Thanks a lot.
I have 6T only 2 days.
When received, I updated to latest ROM, and start restoring data via OnePlus Switch app. Phone crashed, not even hour I start to use it.
I unlocked Bootloader, root it with TWRP and Magisk.
Many crashes without reason, when in pocket, laying on table, without launching any app.
Now it's dead.
Evening when I went to sleep, 70% battery, morning it was dead as brick. And it do not start charging, no reaction.
Anybody has similar experience?
Any advice?
Brzi999 said:
I have 6T only 2 days.
When received, I updated to latest ROM, and start restoring data via OnePlus Switch app. Phone crashed, not even hour I start to use it.
I unlocked Bootloader, root it with TWRP and Magisk.
Many crashes without reason, when in pocket, laying on table, without launching any app.
Now it's dead.
Evening when I went to sleep, 70% battery, morning it was dead as brick. And it do not start charging, no reaction.
Anybody has similar experience?
Any advice?
Click to expand...
Click to collapse
at least on OP6,with magisk installed, there was a bug when charging. It didn't charge switched off.
try do enter EDL mode and use msmdownloadtool to get back to stock
Thanks for advice, but how to? Phone is off, not reacting to Power button, or Volume- and power.
An not charging.
I do not know how to wake it up.
EDIT:
Seems at least via TOOL ALL IN ONE it is detected when connected to PC.
And EDL mode available there. Thanks a lot for aiming me to right direction.
Brzi999 said:
Thanks for advice, but how to? Phone is off, not reacting to Power button, or Volume- and power.
An not charging.
I do not know how to wake it up.
EDIT:
Seems at least via TOOL ALL IN ONE it is detected when connected to PC.
And EDL mode available there. Thanks a lot for aiming me to right direction.
Click to expand...
Click to collapse
Try to enter EDL Mode. Open MSMDownloadtool https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448 and connect device to PC/Laptop. Then press combination for Fastboot Mode by holdong Vol UP+Power and DON'T RELEASE them until MSMdownloadTool detects the device. Then just press START on MSMdownloadTool
Strange. I saw my phone in adb mode via TOOL ALL IN ONE.
I disconnected phone to follow your advice with MSMdownloadTool. But phone is not detected at all.
And worse, now also in TOOL ALL IN ONE it is not detected. It connects, visible on USB list.
On device manager, OnePlus is listed under Universal Serial Buss Controllers, but not under Ports (COM & LPT).
I reinstalled drivers, but no help.
Still the same. When connecting phone to PC, sound as device connected, it appears under USB, but not as adb.
Brzi999 said:
Strange. I saw my phone in adb mode via TOOL ALL IN ONE.
I disconnected phone to follow your advice with MSMdownloadTool. But phone is not detected at all.
And worse, now also in TOOL ALL IN ONE it is not detected. It connects, visible on USB list.
On device manager, OnePlus is listed under Universal Serial Buss Controllers, but not under Ports (COM & LPT).
I reinstalled drivers, but no help.
Still the same. When connecting phone to PC, sound as device connected, it appears under USB, but not as adb.
Click to expand...
Click to collapse
When power off, are you sure then you keep pressing Vol Up+Power till MSMDownloadTool detects?
Even if you enter fastboot mode, you have to keep pressing button till MSMDownloadTool detects
After many tries, phone just went on...
By MSMDownloadTool I installed clean 9.0.5 and lock bootloader.
With clean phone, I installed my apps in batch offered by startup settings.
During that process, first 2 restarts. From then, 11 restarts (in 3 days) and 2x display freeze (I had to force restart).
I really like the phone, but these restarts/freezes are annoying.
Brzi999 said:
After many tries, phone just went on...
By MSMDownloadTool I installed clean 9.0.5 and lock bootloader.
With clean phone, I installed my apps in batch offered by startup settings.
During that process, first 2 restarts. From then, 11 restarts (in 3 days) and 2x display freeze (I had to force restart).
I really like the phone, but these restarts/freezes are annoying.
Click to expand...
Click to collapse
Based on your story I suspect a rough app.
I'm using the 6T now for 3 weeks and not a single issue.
kantjer said:
Based on your story I suspect a rough app.
I'm using the 6T now for 3 weeks and not a single issue.
Click to expand...
Click to collapse
That's what I hoped for.
Yesterday I made factory reset without deleting internal storage. Didn't recover apps, installed from Play.
Several crashes, and display freezes.
Today morning, complete reinstall ROM 9.0.6 from internal storage, full ROM.
Than factory reset with deleting internal storage.
I installed only BluMail, Messenger, SMS backup and recovery, AnyDo.
In 4 hrs, crash and restart. Phone in pocket.
Now I opened slot, cleaned SIMs. But these worked in 3T for 2 years.
I am frustrated as hell.
EDIT:
I want to return phone.
Will it be visible that I unlocked and re-locked bootloader?
I am afraid it can affect warranty...
My HTC U Ultra suddenly froze past nigth, then it rebooted... and never came back, it won't go past the HTC logo over and over. I am not able to enter in recovery mode either, the only thing I can do is, by pressing both volume buttons and power, entering in what seems to be fastboot menu. In that state I can send the phone fastboot commands (no adb commands though) but If i try to wipe it it says "unable to do in s-on" or similar. I was pretty happy with this phone, and spent a few bucks in a new battery not two months ago.... anything I can do?
Thanks.
PS: I failed to state that the phone is stock, not unlocked or rooted.
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
spikey001 said:
If it has just happened out of the blue and you haven't been doing anything with your phone, have you tried a simple reset? (Press and hold volume down and power button until your phone vibrates - Usually about 20 seconds for me)
If not, and you are struggling to get into recovery etc, see if you can follow the method in the thread linked below if you are currently on stock rom!?
(Not sure if this would delete all your data or not, so perhaps only use as a last resort....)
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
Click to expand...
Click to collapse
Reset doesn't work, and the other procedure didn't work either.
If I leave it plugged to the charger, it will fall into an endless reboot loop. Sometimes (few) it will end up booting, but If i try to do something with the phone it doesn't respond and reboots again.
Thanks.
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
spikey001 said:
As you can send fastboot commands, can you flash a recovery.img (i.e. TWRP), and then wipe cache and dalvik/art to see if that helps, but if not, flash corresponding rom to that which you already have?
Click to expand...
Click to collapse
I tried that, too, but didn't work. If I do a fastboot devices it detects the phone, but if I do a fastboot getvar all it doesn't give me any information, it doesn't admit adb commands, when I try to flash a rom or a recovery, it fails, I suspect it needs to have the USB debugging enabled, but I can't enable it in this state.
As I said before, if I leave it plugged to the charger, It will randomly end up booting (it can happen in the third loop or in the 50th), but it will freeze or reboot again in few seconds.
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
spikey001 said:
Ah I see, if you haven't got USB debugging enabled then I am unsure how to help sorry. Have you got your media backed up, or stored on micro sd? If so, might have to bite the bullet and do a factory reset. Sorry I couldn't be of any help. Maybe someone else would be able to help you further?
Click to expand...
Click to collapse
The data is not a problem, every important file has been backed up.
Regarding factory reset, since the device won't go to recovery, I can't see how can I do it.
-- Edit --
I noticed that when the phone is cold, those few times it boots, it lasts a little bit more (a matter of seconds) until it freezes again, so I tried to leave it in the freezer for a few minutes, and tried to boot it, and had enough time to do a factory reset. The factory reset worked, because now, when it boots, it goes straight to the intial setup, but keeps hanging after a few seconds. I suspect that the internal memory was somehow damaged, I don't think there is much left to do...
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
spikey001 said:
Is it possible to skip setup in order to get to settings and enable USB debugging so you can install a recovery?
If you can, then it might be an idea to try performing a repair of all the partitions and install a fresh ROM... Just to ensure it isn't a hardware issue!!
Click to expand...
Click to collapse
I can't see how to skip initial setup... and I don't have time enough to go through it, the phone will hang in 30 seconds or less. At this point, I really needed a working phone, so I bite the bullet and bought a new one... I will deal with the old one later, or I might sell it for parts.
Thanks everybody for the help.
No worries, enjoy your new phone
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.