Database Users

Bricked Oneplus 2 Not Connecting To PC

- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop

I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable

Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?

foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable

evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week

fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.

evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken

Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc

q about current root method on shield tv

the current method to root the shield tv requires that you need to use a micro sd card in twrp to install root, the only problem with that is the new 16gb models do not have a micro sd card slot will it make these new models unrootable?
it seems only the new pro 500gb models will only have root at this point unless the devs can think of a work around to avoid this issue with the micro sd cards.
using a memory card reader and putting the micro sd card in there won't work either because i tried this when i attempted to root the mad catz mojo and it didn't work.
should i hold out and wait and see what the root situation is going to be for the new models first before i order the 16gb model? just incase i need to get the 500gb model instead, it would be a pain to return and refund to do that.

Shouldn't be an issue, you should be able to use a thumbdrive. I guess we'll find out when someone tries it. Later today I'll put supersu on a thumbdrive and see if twrp will mount it. Now that I think about it, you can prob just copy it locally & flash it. I'm just curious if the old root will work on the 5.0 update.

The slim doesn't have a micro usb port anymore either. Can adb be run through the regular usb with a male to male cable?

You don´t need a micro sd-card. Only need twrp to flash su.zip. In twrp you can use usb-drive, adb push file to internal flash oder adb sideload.

Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv

unsatgoua said:
Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv
Click to expand...
Click to collapse
Thanks for that. I am picking mine up in a few minutes and going to try and root it with a USB M/M.

unsatgoua said:
Shouldn't be an issue, you should be able to use a thumbdrive. I guess we'll find out when someone tries it. Later today I'll put supersu on a thumbdrive and see if twrp will mount it. Now that I think about it, you can prob just copy it locally & flash it. I'm just curious if the old root will work on the 5.0 update.
Click to expand...
Click to collapse
i'm assuming the nougat android update will have a new bootloader so all the root methods out there right now do not work with the new 2017 model.
please try and report back the results, i'm holding off buying this till we get more info on the root status.
unsatgoua said:
Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv
Click to expand...
Click to collapse
i've googled for 2 days straight to see if any new root methods have popped up but nothing so far.
will the usb a be good enough for root i wonder?

Usually nvidia has developer images available that are already rooted so maybe just flash that on the new shield when it becomes available.

Forgot what I read a while back but the rooted images don't actually give you root but only allow you to run adb in an elevated mode. Nothing I needed. So I just fastbooted twrp and flashed supersu. Also remember reading something about those images not able to update ota which means fresh install every update. Don't quote me though but there was enough I read to say [email protected] no to the "rooted images" and just root the standard ones. As far as root I would definitely agree that waiting for a verified root will prevent a possible brick and major headache.

So I have yet to get my Shield to show up on my pc under device manager when I connect with the cable. I am hoping I just have a bad cable so I have ordered one that will come in about 2 days.

You installed the drivers? Don't forget, they said one port, so try both.

unsatgoua said:
You installed the drivers? Don't forget, they said one port, so try both.
Click to expand...
Click to collapse
When you put it into ADB mode it tells you what port to use. And when I plug it into my pc it never comes up under device manager so I can't install the drivers.
Edit: That is why i'm trying a new cable since I know the port work with my mouse.

I'm surprised they didn't provide a cable to flash images.
Sent from my SM-G935T using XDA-Developers Legacy app

unsatgoua said:
Forgot what I read a while back but the rooted images don't actually give you root but only allow you to run adb in an elevated mode. Nothing I needed. So I just fastbooted twrp and flashed supersu. Also remember reading something about those images not able to update ota which means fresh install every update. Don't quote me though but there was enough I read to say [email protected] no to the "rooted images" and just root the standard ones. As far as root I would definitely agree that waiting for a verified root will prevent a possible brick and major headache.
Click to expand...
Click to collapse
excatly, this is why I'm holding out for now.
yojoe600 said:
So I have yet to get my Shield to show up on my pc under device manager when I connect with the cable. I am hoping I just have a bad cable so I have ordered one that will come in about 2 days.
Click to expand...
Click to collapse
not a good start but let us know how it goes anyway.

I have the old 16gb version and I wont be upgrading until there is a root method.

Slayerkodi said:
I have the old 16gb version and I wont be upgrading until there is a root method.
Click to expand...
Click to collapse
I wish I would have found the old version for the price I paid for this one ($175 + tax). I am sure there will be a way to root it I hope since there is an option to connect through ADB. I am just hoping it's my cable.

yojoe600 said:
I wish I would have found the old version for the price I paid for this one ($175 + tax). I am sure there will be a way to root it I hope since there is an option to connect through ADB. I am just hoping it's my cable.
Click to expand...
Click to collapse
It can only be our cable, because i was able to install the official fastboot drivers from NVIDIA and connect via ADB
Win10 Prof. x64
SHIELD TV Gen. 2017
SHIELD TV bootloader version:
Code:
24....
enabled developer options
enabled adb debugging
rsa fingerprint acceptance
installed fastboot driver :good:
adb connection via SHIELD USB port 1 USB A <=> A :good:
Code:
adb devices
listed the shield :good:
reboot into fastboot
Code:
adb reboot bootloader
:good:
unlocked bootloader
Code:
fastboot oem unlock
after unlocking i sometimes got a flickering on my screen
could not
Code:
fastboot boot TWRP
boot TWRP, The SHIELD would reboot, show the "unlocked bootloader message" and would reboot to system
could flash recovery (success message)
Code:
fastboot flash recovery twrp-3.0.2-0-foster.img
but after reboot to system i saw the "unlocked bootloader message" and then i guess the SHIELD reflashed to stock recovery.

aVlkaFenryka said:
It can only be our cable, because i was able to install the official fastboot drivers from NVIDIA and connect via ADB
Win10 Prof. x64
SHIELD TV Gen. 2017
SHIELD TV bootloader version:
Code:
24....
enabled developer options
enabled adb debugging
rsa fingerprint acceptance
installed fastboot driver :good:
adb connection via SHIELD USB port 1 USB A <=> A :good:
Code:
adb devices
listed the shield :good:
reboot into fastboot
Code:
adb reboot bootloader
:good:
unlocked bootloader
Code:
fastboot oem unlock
after unlocking i sometimes got a flickering on my screen
could not
Code:
fastboot boot TWRP
boot TWRP, The SHIELD would reboot, show the "unlocked bootloader message" and would reboot to system
could flash recovery (success message)
Code:
fastboot flash recovery twrp-3.0.2-0-foster.img
but after reboot to system i saw the "unlocked bootloader message" and then i guess the SHIELD reflashed to stock recovery.
Click to expand...
Click to collapse
Hey did you try this bit?
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
https://twrp.me/devices/nvidiahshieldandroidtv.html

If you have a usb or 2.4ghz keyboard, theres the non root/adb method of, ALT+PRINT SCREEN+i to boot into recovery folks could test, confirmed working on first gen shield.
More details here
https://forum.xda-developers.com/shield-tv/help/accessing-satv-stock-recovery-t3300211
I believe its an android feature, rather then a shield specific one, as i believe the method was first found on the ouya console, and found to also work on other android consoles, like the ouya, nexus player, shield....... i wouldnt be surprised to find out that it works on phone/tablet
Edit
I just retested this again, pressing the combination once, and letting the shield bootup, instead of pressing again, on boot logo image, to go to recovery, and it looks like it removed root for some reason, so bare that in mind, just incase thats normal behaviour. Ive just used the method again to boot to recovery this time to flash supersu zip in twrp, everything seems back to normal

banderos101 said:
If you have a usb or 2.4ghz keyboard, theres the non root/adb method of, ALT+PRINT SCREEN+i to boot into recovery folks could test, confirmed working on first gen shield.
More details here
https://forum.xda-developers.com/shield-tv/help/accessing-satv-stock-recovery-t3300211
I believe its an android feature, rather then a shield specific one, as i believe the method was first found on the ouya console, and found to also work on other android consoles, like the ouya, nexus player, shield....... i wouldnt be surprised to find out that it works on phone/tablet
Click to expand...
Click to collapse
theirs no power button on the 2017 shield.

Big Big problem - No fastboot with Controller method and pc!!

I try update my nvidia shield tv 2017 but now the System bootloop on Android circles animation (dont start box).
- I try fastboot with Controller but dont work (many, many times)
- I try conect to pc but dont connect device with fastboot
bricked bootloader??
I dont have solutions.... please help.
Sorry my english

Try un plugging the power then plug a USB keyboard in and hold the A and B key and then plug the power back in.

same problem for 3 days, can not enter fastboot mode. my shield is in bootloop

Shot in the dark, but have you tried different USB ports on the computer? I know in my case, some otherwise working ports will not work with the shield. Seems to be very fussy when it comes to which ports I choose. None of my front ports work on this desktop, I have to plug into rear ports in order for my computer and shield to see each other.
Also be sure to use the original cable that came with the shield.

Also make sure USB debugging is on.

Any fix ? Same problem

Have you tried "adb reboot bootloader" in command prompt when the android logo is looping?

I have no Android logo i have no os just twrp and twrp with no access adb and fastboot command dont work on NVIDIA logo

If you put lineage os on a usb stick can twrp read the usb stick? If so, you can install the zip file of lineage with gapps...once that's installed and booted up, you can enable usb debugging in the developers options and fastboot and adb should work again.

Pc cant detect fastboot device

Tried miui 12 and after flashing rom the twrp is gone I tried to reflash it the same way I did first but sadly when I'm on fastboot PC can't detect it. also tried it with other softwares but same result. Device is fine and responds when open but not in fastboot mode. Currently running miui 11 .0.6 China stable. Stucked. Also all drivers are updated

Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6

Same issue indeed
That's exactly what's happening right now. I hope someone can help us

Quote me if u find any luck.

Same issues

That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .

With my PC I have to open device manager, look for the device, usually has a yellow sign next to it. Right click on the device name, click update driver, click browse my computer for driver software, click let me pick from a list of available drivers on my computer and pick mtp USB device. Then I read it. I hope this helps.

daniml3 said:
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
Click to expand...
Click to collapse
What hub?
Tried with multiple pcs with no success

epicblue8 said:
What hub?
Tried with multiple pcs with no success
Click to expand...
Click to collapse
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.

daniml3 said:
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
Click to expand...
Click to collapse
Read my 1st reply to this op
Even file transfer option doesn't show up if i connect my phone via usb to laptop.
In order to make pc show file transfer option i have to reboot phone while connecting the phone to pc so.
That way i can use adb but as soon as i boot to fastboot via cmd pc doesn't detect the fastboot mode.
Tried with 3 laptops

Issue Fixed
epicblue8 said:
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Click to expand...
Click to collapse
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".

Chipotle crackers said:
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Click to expand...
Click to collapse
Not with original but tried 3 type c cables and 3 pcs

epicblue8 said:
Quote me if u find any luck.
Click to expand...
Click to collapse
hey have find any solutions? we have the same problem

Hisense U8G Bootloader Unlock (and probably others)

Hello. I have managed to unlock the Hisense U8G bootloader in the stupidest of ways. This will likely also work on the U6G, U7G, and U9G (Android TV models ONLY) since they run the same firmware. This will probably also work on every other Hisense Android TV.
So... tl;dr just run "fastboot flashing unlock" and that's it. No need to enable OEM Unlocking in Developer settings or anything since there is no FRP.
You will need:
A computer with adb and fastboot installed
Mediatek drivers if running Windows
udev rules if running Linux (available here: https://github.com/bkerler/mtkclient/tree/main/Setup/Linux)
Step-by-step on a stock TV OS (YOUR DATA WILL BE ERASED):
Enable Developer Settings by clicking on build number 7 times, standard stuff
Enable USB Debugging (this will also enable network debugging, but you will not need it)
That's all you need to do on the TV itself, settings-wise.
On the PC:
adb devices
On the TV:
Allow USB Debugging
On the PC:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
That's it. Your bootloader is now unlocked.
I am currently trying to figure out a way to dump boot.img and vbmeta.img and/or get into BROM mode so I can use mtkclient to dump boot.img and vbmeta.img. Help would be appreciated.

Hey. Do you know how to unlock bootloader of Hisense 50A71F, it goes all black when I run "adb reboot bootloader".

jerrydevis said:
Hey. Do you know how to unlock bootloader of Hisense 50A71F, it goes all black when I run "adb reboot bootloader".
Click to expand...
Click to collapse
Thats normal, need a usb type a male to male plugged into 1 of the ports of your tv only 1 port gets detected and other not so ask me for the adb bootloader interface driver for the tv and ill provide, I have a Hisense 43A6H its a MEDIATEK MT9612 SoC which I unlocked the bootloader and cannot root it as I have all the drivers and boot.img and I patched it and typed command and on my tv and likely yours is the same command in slot B but it didn't root the tv...... Anyone know of an alternative method to patch and flash the boot.img? Mtkclient gui might work with python but idk haven't tried yet... Make sure to get the latest firmware from hisense so u can recover if u do something wrong or want to relock the bootloader.
To recover take your .pkg file which for me is update_no_tvcertificate_user.pkg and rename to update_no_tvcertificate.pkg and have only that file on your fat32 flash drive and unplug the tv plug in the flash drive and hold power button on remote pointing at tv and plug in the tv and it'll start recovering and u can let go of the power button.
Code:
fastboot flash boot_b boot.img

Don't freak out if you brick your tv make sure before u do anything to call up Hisense to get your firmware and they will email it to you. I bricked my tv like 3 times but recovered it and im talking to u now on my Hisense 43A6H Google TV Android 11 with a mini wireless keyboard mouse usb 2.4ghz dongle plugged into a usb hub by Sabrent with a 4tb hdd ntfs plugged in and a 400gb sd card fat32 it detects everything. I was gonna make a guide on how to do stuff on our tvs as well its tricky but fun when u succeed.

I've been having a hard time rooting the tv. Nothing takes, may someone help?

chris1892006 said:
Don't freak out if you brick your tv make sure before u do anything to call up Hisense to get your firmware and they will email it to you. I bricked my tv like 3 times but recovered it and im talking to u now on my Hisense 43A6H Google TV Android 11 with a mini wireless keyboard mouse usb 2.4ghz dongle plugged into a usb hub by Sabrent with a 4tb hdd ntfs plugged in and a 400gb sd card fat32 it detects everything. I was gonna make a guide on how to do stuff on our tvs as well its tricky but fun when u succeed.
Click to expand...
Click to collapse
I would be thrilled if I could just get my Hisense to default to HDMI1 input upon startup, like you can with other SmartTVs.

Have a 65H6510G with a failed eMMC. Service port UART shows CPU trying to setup eMMC to retrieve data, fails and repeats. I can replace eMMC but need to flash in signed boot code. Any ideas?