Database Develop

Bricked Nexus One?

Took my Nexus One off my cradle today to see it was locked up. Thought no biggie, I'll pull battery and restart it.
Now when it boots it comes up with four bars. Red, Green, Blue, White and the 3 skateboarding Droid Bots. I have no clue what to do now.
I was running Cyanogenmod (Forget the version, but it was 2-3 months old. I have not done anything to my phone except add the ebay app to it yesterday.
I can not get my computer to recognize it as a Nexus One anymore so I can not use Fastboot. I tried recovery from HBOOT, but keep coming up the same way.
Please Help
Ray

Picture of my Nexus One from Wifes iPhone...

I can get to FASTBOOT and when connected to USB it says FASTBOOT USB, but my computer fails to recognize the device and it goes back to FASTBOOT.
I can not turn on USB Debuging because it will not boot normal. I do not know what to do.

Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)

Yes its the only thing I see.
I do not see anything Prior.
I have tried to boot to recovery many many times. I have 3 different results.
1. Nexus X with nothing else
2. Nexus X with Unlocked icon below
3. The screen you see
Either way, it does not move forward it just hangs. Is there a way to turn on USB debugging from FASTBOOT or HBOOT?
Ray
Russ T. Nail said:
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Click to expand...
Click to collapse

looks like the bootloader screen, thats what the rainbow screen was on the g1.
havent seen it on the nexus though so it could be something else.

Did you try a factory reset using hardware keys?
I believe you do this by holding vol-down, power and trackball for 5 secs.

That does not seem to do anything but take me to FASTBOOT

There has to be a way to turn on USB Debugging from FASTBOOT?

If you can get fastboot usb to work you could try the following (using latest amon_ra recovery.img):
Code:
fastboot boot c:\path\to\recovery.img
To boot into recovery, then use adb or try nand-ing etc.
if you get that far (recovery)
Code:
adb shell reboot normal
should take you into os.
However, the colored bars look like some pretty serious hardware failure I'd guess...

I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray

check this out to help you get fastboot to work http://forum.xda-developers.com/showthread.php?t=613217
i know its titled ADB but it might help you out.

TheQue said:
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
Click to expand...
Click to collapse
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing

have you tried to contact htc or even google?theyve helped me over the phone even knowing i have an unlocked bootloader.

pvillasuso said:
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
Click to expand...
Click to collapse
not the sd card if it was a bad card it would just bootloop

if you have SDK you can see what the phone is doing with ddms

I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot

That pic reminds me of the MDA Win Mobile 5 boot screen, real similar...
Don't know how to help, keep us updated if you figure this one out.

gtrplr71 said:
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
Click to expand...
Click to collapse
I 2nd that. Try using ddms or logcat.
Good luck man!

What happens when you try to flash a rom?

[Q] UPDATED: ODIN wont recognize my phone with USB debugging on, but will without it

Alright, so I was having some problems with my cognition rom and decided go back to stock so I could flash the new cognition. I put my phone into download mode, and it took a few times for ODIN to see my phone. After I got ODIN to see my phone I tried to master clear, it did not work. I had to pull the battery out and try again. I rebooted my phone again, and many program errors came up. I shut off my phone, tried to get into download mode and it wouldn't let me using the volume down + up then insert USB with ODIN open.
Now to get into download mode I must hold buttons with battery out, put USB in, and put battery in and I get download mode instantly, but I cant get ODIN to recognize my phone at all anymore. I tried many different methods(odin open before DL mode, odin closed before download mode, etc). I looked through a few threads and couldnt find anything that would work. Also my window 7 64 now says it doesn't recognize the USB device when I plug it in. Whats going on with my phone?? Im getting very annoyed! Is there any way to go back to stock besides ODIN??? Any help is appreciated!!
***UPDATE***
Seems like I may have a 3 button combo lock, and no USB support of any kind(besides charging).

UPDATE: I used rom manager to flash over my old rom. My phone works again, but it wont go into download mode at all now. Only when I use the cognition menu to send it to download mode will it work. I still cant get ODIN to see my phone. I want to go back to stock still, but without ODIN working, can I?

ziphoward said:
UPDATE: I used rom manager to flash over my old rom. My phone works again, but it wont go into download mode at all now. Only when I use the cognition menu to send it to download mode will it work. I still cant get ODIN to see my phone. I want to go back to stock still, but without ODIN working, can I?
Click to expand...
Click to collapse
under your captivate battery, there is a number like 1008, 1010, what is yours?

I've had the same trouble with download mode + odin on my Windows 7 64 bit pc too.
I have to have odin running, phone off with battery out, and usb cable in. I leave the battery out for about a 10 second count. Then put the battery in and hit all the buttons at the exact same time (power + volume up and down). The key here is that I only had to hit all three buttons momentarily to get it to go into download mode. I didn't have to hold them down for any length of time.
I easily spent 1 hour trying to get odin to work the last time I had to reflash to stock. Only because I forgot how hard it was three last time with my 64 bit machine.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

mengbo said:
under your captivate battery, there is a number like 1008, 1010, what is yours?
Click to expand...
Click to collapse
1006
So should I just keep trying to get into ODIN by just fiddling around with it? Ive tried an XP machine and it wouldnt work either. Does booting into download mode from the cognition power menu any different than entering download mode the manual way? Every time I put the battery in with the USB it takes me to the battery charger screen. At first with that issue, putting in the battery last while holding down volume up and down, would put the phone into download mode(as opposed to the normal ways of getting into download mode). Now that wont even work at all.

first you can try the 3 button fix, just search the forum for that.
you may need to build a jig or buy one online just in case, it will get you into the download mode easily.
http://cgi.ebay.com/ws/eBayISAPI.dl...47234&ssPageName=STRK:MESELX:IT#ht_511wt_1139

im having horrible trouble with adb cmd. I installed the samsung drivers, put my phone in usb debugging, did some tutorials on how to install sdk correctly, went to the correct file paths in cmd promt, and still cant access the adb shell. Any pointers on this?
Also, could I wipe all data off internal storage and use the "reinstall package" option in recovery mode to use rom manager update.zip to restore my rom from my sd card? Im not sure if thats possible. Im getting errors with my rom, and it feels slower since I just reinstalled over the top of my faulty rom.
Seems the only usb function I have right now is to charge it. Hmmm USB brick?

Any help out there???
3g stopped working on my phone when I woke up. I really need to get a fresh rom installed.

If I recall correctly, the path to where adb is had changed. Check all folders inside the sdk folder. to make my life easier, I put the sdk folder right into the root directory (c and renamed it sdk. Don't know if that well help or not...
Sent from my SGH-I897 using XDA App

I changed the folder to androidsdk from whatever it was.
bueller bueller bueller...anyone?

Well, if your phone is a rev 1006 you "should" have a problem like losing your button combo. I guess that could have happened but I doubt it, I've got a 1007 and never lost it.
So, as for ADB here's what I do. Take the android SDK folder you downloaded and look inside it. There is a folder called tools. I take the tools folder and copy it to the root of my C: drive. Make sure you have all the drivers loaded, speaking of which I would uninstall and reinstall the drivers. Sounds like they flaked out for some reason. Next open up a cmd window, Start > Run > CMD.
Then type,
cd /
cd tools
adb devices <<this shows if your phone is recognized. if it is...
adb reboot download
*or
adb reboot recovery
*or
adb shell
For what it's worth, I have been flashing my phone since I got it in July and the only time I Master Clear is when I have had a problem like a soft brick or something that I was suspicious about the data on my internal SD. Which, so far has been maybe 3 times. I don't think necessary to Master Clear every time you flash to stock.
Also, you shouldn't really have to the pop out the batter to do the download mode trick. I turn my phone off, hold both Vol up and down, then plug in USB and I'm in download mode.

bobbylx said:
Well, if your phone is a rev 1006 you "should" have a problem like losing your button combo. I guess that could have happened but I doubt it, I've got a 1007 and never lost it.
So, as for ADB here's what I do. Take the android SDK folder you downloaded and look inside it. There is a folder called tools. I take the tools folder and copy it to the root of my C: drive. Make sure you have all the drivers loaded, speaking of which I would uninstall and reinstall the drivers. Sounds like they flaked out for some reason. Next open up a cmd window, Start > Run > CMD.
Then type,
cd /
cd tools
adb devices <<this shows if your phone is recognized. if it is...
adb reboot download
*or
adb reboot recovery
*or
adb shell
For what it's worth, I have been flashing my phone since I got it in July and the only time I Master Clear is when I have had a problem like a soft brick or something that I was suspicious about the data on my internal SD. Which, so far has been maybe 3 times. I don't think necessary to Master Clear every time you flash to stock.
Also, you shouldn't really have to the pop out the batter to do the download mode trick. I turn my phone off, hold both Vol up and down, then plug in USB and I'm in download mode.
Click to expand...
Click to collapse
Im having USB driver problems, windows 7 will not recognize my phone. I think this is why adb wont recognize my phone correct? I can only get into download mode now but using the power menu thats custom from Cognition. Is my phone screwed?? Can I flash a ROM without ODIN?

ziphoward said:
Im having USB driver problems, windows 7 will not recognize my phone. I think this is why adb wont recognize my phone correct? I can only get into download mode now but using the power menu thats custom from Cognition. Is my phone screwed?? Can I flash a ROM without ODIN?
Click to expand...
Click to collapse
Like I said, have you tried uninstalling the drivers from windows and reinstalling them? I am running Win 7 x64 and have had that happen. After i flash a rom or flash to stock sometimes windows doesn't recognize my phone at all. The first time I just used my laptop to flash but the second time I uninstalled the drivers and reinstalled. It's also important that you plug into the USB ports directly on the motherboard on the back of your PC. There are known problems when trying the front usb ports or through a hub.

bobbylx said:
Like I said, have you tried uninstalling the drivers from windows and reinstalling them? I am running Win 7 x64 and have had that happen. After i flash a rom or flash to stock sometimes windows doesn't recognize my phone at all. The first time I just used my laptop to flash but the second time I uninstalled the drivers and reinstalled. It's also important that you plug into the USB ports directly on the motherboard on the back of your PC. There are known problems when trying the front usb ports or through a hub.
Click to expand...
Click to collapse
Ive tried uninstalling and reinstalling many many times. I am using a laptop and ive tried all the USB ports but still no luck. I hate having my phone like this, it will drive me insane until its fixed.. or officially considered usb bricked.

ziphoward said:
Ive tried uninstalling and reinstalling many many times. I am using a laptop and ive tried all the USB ports but still no luck. I hate having my phone like this, it will drive me insane until its fixed.. or officially considered usb bricked.
Click to expand...
Click to collapse
Just curious, is it a Dell laptop? My Dell never recognizes my phone unless I power the laptop on with the phone/USB plugged in. If the laptop is on, and I plug phone in it never works, so I leave it plugged in and reboot and it works. It drives me crazy, but whatever it's my work PC.

bobbylx said:
Just curious, is it a Dell laptop? My Dell never recognizes my phone unless I power the laptop on with the phone/USB plugged in. If the laptop is on, and I plug phone in it never works, so I leave it plugged in and reboot and it works. It drives me crazy, but whatever it's my work PC.
Click to expand...
Click to collapse
It is a dell actually, but I just tried your method and it didnt work for me. Thanks for the input though!

Alright, I downloaded kies mini today and it actually installed some drivers correctly. I was able to pull up my internal drive on the computer, but it wouldn't read it. I was able to get ODIN to see my phone(first time in weeks), but it only shows up when my phone is NOT in debugging mode. So im assuming Master Clear will work now. I was using AIO captivate tool box, and my phone rebooted at the click of the button into download mode, but once again it wont see my phone in ODIN while in download mode. Im getting closer!
Why wont ODIN recognize my phone with USB debugging on? Any more suggestions on how to make this happen?

Have I hard-bricked my device?

Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance

JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.

AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.

after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.

AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance

Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app

D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks

Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!

Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....

Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.

Help Recovering Files from Phone With NO DISPLAY. - Rooted and Fully Unlocked

If anyone has any ideas on how to do this I'd really appreciate it. I can still power the phone on and connect it to the PC which detects it, but the default mount type is "charge only", and I'm unable to change it to an MTP connection on the phone.
Phone was rooted, unlocked, etc running Pure Nexus. I stepped on the phone at the gym, and now have no display whatsoever (COMPLETELY black, but I know the phone itself still works).
I know the system itself still works. Any help is greatly appreciated.

reboot to recovery and do an adb pull of the storage directory.

If the screen is inop maybe you can figure out a way to run Vysor. I think you run it on chrome, and you install it by accessing Google Play store on your PC and telling it to push an install to your device.
I keep a version on my phone just in case something like that happens to mine.
https://www.vysor.io

Vysor is the best indeed
Sent from my Nexus 6 using Tapatalk

SynisterWolf said:
reboot to recovery and do an adb pull of the storage directory.
Click to expand...
Click to collapse
That was my first thought, but is there a way to boot to recovery with no screen?
I tried blindly holding the key combination but wasn't able to get it (or at least not get it and *know* that I was in recovery). I guess trial and error would be the only way to eventually get it.
Dusty Rhodes said:
If the screen is inop maybe you can figure out a way to run Vysor. I think you run it on chrome, and you install it by accessing Google Play store on your PC and telling it to push an install to your device.
I keep a version on my phone just in case something like that happens to mine.
https://www.vysor.io
Click to expand...
Click to collapse
Thanks Dusty and Ahmad, I'll try this out tonight and post results.
Edit: I'm not sure if Marshmellow will allow Vysor to run. I also don't have USB debugging enabled so I'm not sure if this will be an option.
Will ADB start running automatically if I reboot into recovery?

internetcommand said:
That was my first thought, but is there a way to boot to recovery with no screen?
I tried blindly holding the key combination but wasn't able to get it (or at least not get it and *know* that I was in recovery). I guess trial and error would be the only way to eventually get it.
Thanks Dusty and Ahmad, I'll try this out tonight and post results.
Edit: I'm not sure if Marshmellow will allow Vysor to run. I also don't have USB debugging enabled so I'm not sure if this will be an option.
Will ADB start running automatically if I reboot into recovery?
Click to expand...
Click to collapse
"ADB devices" let's you know if you have a working connection with your phone.
"ADB reboot recovery" reboots into recovery.

Push Helium to your device from the Play Store (from a desktop computer), then install Clockworkmod Carbon to the desktop. Connect the phone via USB.

Unfortunately vysor will not work unless usb debug is enabled
Sent from my Nexus 6 using Tapatalk

OP3T Bootloop - no way to flash new firmware?

Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus

If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?

Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.

Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...

grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)

If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/

Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,

Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.

Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:

Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Might be a dumb question, but you did remember to mount the USB when you connected the otg right?

If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.

try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out