My ROG phone 3 doesnt get detected by adb or fastboot command once it goes into the fastboot mode. My bootloader is unlocked what do i do.
What did u flash? Did u flash something that bad that it bricked your phone?
Didn't flash anything I simply ADB rebooted to bootloader then it stopped working
kartikhm said:
What did u flash? Did u flash something that bad that it bricked your phone?
Click to expand...
Click to collapse
Didn't flash anything. It was already like that the instant I restarted my bootloader
My phone is WW_17.0823.2012.122 is it possible to unbrick my softbricked device? Without flashboot mode
Are you using the side usb port? Only that works for fastboot.
tuxing said:
Are you using the side usb port? Only that works for fastboot.
Click to expand...
Click to collapse
Dont have the side port
Sooo my phone is unrootable because there isnt a side port???.....
There will be a side port if it's Rog 3. It's difficult to make out at first, as it is covered snugly with a rubber cover. Here's a pic with the side port cover removed.
Yrmx said:
Dont have the side port
Click to expand...
Click to collapse
How can this possible?
Every rog 3 variant has side port...
Check ADB drivers or if ur PC is running on AMD search how to fix fastboot
sendme2pop said:
How can this possible?
Every rog 3 variant has side port...
Click to expand...
Click to collapse
Not true. The Tencent version, the side port is covered and doesn't work. I too am having this problem and have tried literally everything I know of and I can't get it to work. I'm gonna try to use Magisk and root it, then use a flashing app to see if I can flash TWRP and then try to change from CN firmware to Global.......
KilaWatts said:
Not true. The Tencent version, the side port is covered and doesn't work. I too am having this problem and have tried literally everything I know of and I can't get it to work. I'm gonna try to use Magisk and root it, then use a flashing app to see if I can flash TWRP and then try to change from CN firmware to Global.......
Click to expand...
Click to collapse
I have a Tencent version.
The side port is covered with a removable soft cover just like every other ROG 3 phone. There is no design difference in this regard between the ROG 3 variants.
elmor0 said:
I have a Tencent version.
The side port is covered with a removable soft cover just like every other ROG 3 phone. There is no design difference in this regard between the ROG 3 variants.
Click to expand...
Click to collapse
Yep, I stand corrected.....I actually got back on here to say I was wrong but you beat me to it. The place I bought it from told me that, and that it was the reason the aero fan didn't come with it! Then when I checked online, I had to see the only damn site with a chart that said the same thing (a Malaysian site)......after checking some others (because this cost me a LOT of time, and I wasn't happy lol) no other site I checked said there was any difference there. I found out because after exhausting every possible thing, I tried connecting the USB to the side one. Using a standard cable, it still didn't work. Then I tried it with the included cable eventually, and lo and behold.....fastboot recognized it and I was able to flash the latest WW version, flash TWRP, Magisk and root it, change the fingerprint, no problems. I had a hell of a time with drivers as for some reason most didn't work and I had to update it eventually, while it was still connected with the one from Google. Only way it would work and had to do it every time I connected. Glad that's over with lol. Cheers! Kila
Related
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Did you try mass storage or pc mode?
I had that issue with my USB cable. I used the one with my device and it didn't come up. I went grab another USB cable in the house and it worked.
yeah, tried them. Didn't mention that cause if I understand correctly, it should be in charge only.
thanks for the help!
I hope you figure something out good luck
Edit: have you tried running command prompt as administrator?
yeah. same result.
I read in another thread that you were required to us the cable that came with the phone for it to be detected. But also, I used a BlackBerry branded cable to do it on mine, and it worked.
come to think of it, i think i used a blackberry cable to root my first d3. will give it a shot and report back.
why the heck would it matter what cable you use? Though it doesn't make sense to me, it appears that the cable is indeed important.
SrulDog said:
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Click to expand...
Click to collapse
Download the USB and Charging Drivers off of Motorolas website, make sure your phone connects to USB mass storage after you do this, then switch to charging mode.
It took a blackberry cable *and* reinstall of the moto drivers, but im up and running and rooted. now, to figure out how to get my other d3 to stop bootlooping...
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
I had to use the cord that came with my phone. For some reason Motorola is bad about not using standards. For example there was an old 355 flip phone that is a Motorola I used to have and it wouldn't charge with anything but a Moto charger. It may be the same port but not the same compatibility. Thankfully it will accept a charge from any microUSB source.
Sent from my DROID3 using XDA App
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
LaZiODROID said:
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
Click to expand...
Click to collapse
yeah, to fiddle w/ any rooting, you need to have debug on
digitalsynner85 said:
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
Click to expand...
Click to collapse
Yeah, I was able to flash the SBF. It was really exhausted and couldn't figure it out when I originally posted, but after a nights sleep, I was able to do it just fine.
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
SrulDog said:
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
Click to expand...
Click to collapse
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
digitalsynner85 said:
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
Click to expand...
Click to collapse
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
SrulDog said:
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
Click to expand...
Click to collapse
oh ok, you said you couldn't get past the phone activation screen, i thought you were saying that your radio got botched in the process somehow lol, my bad
SrulDog said:
Now I want to know if the phone is still rooted or not. .
Click to expand...
Click to collapse
if you used rsd to sbf you are no longer rooted.
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
no one?
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
This updates been a nightmare
synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.
This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys
randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.
I'm still stuck. Any progress ?
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked
I had to RMA
randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.
Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA
im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.
Hello everyone. I updated my rooted OP3T (with TWRP installed for recovery) to OOS 4.0.1(I think? I know for sure it was 4.0.x) a week or so ago using a VPN as I live in the US and today I got the new update for whatever version that was about 30 mb, and after I rebooted I got stuck booting into TWRP so I followed the guide linked underneath here and got up to step 12 (flashing beta 9) and after swiping to restart my phone will not turn on in any way, shape, or form. Whenever I plug it in/unplug it from my computer I'll still get the Win10 device connected/disconnected sound and if I hold the power button for long enough while it's plugged in I'll get another device connected sound or disconnected, usually followed by the opposite sound. There doesn't seem to be a pattern to the sounds, but if anyone knows what's happening I really need help with this as it's the only phone I was able to afford and if it's bricked I don't know if I have the money for another one. Thanks
https://forum.xda-developers.com/showpost.php?p=70102813&postcount=5
Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Edit: Sorry if this was of use to some people when it was deleted.
Just Passing By said:
Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Click to expand...
Click to collapse
I tried to use that thread, but my phone wouldn't show up underneath Unknown Devices, in fact unknown devices would never come up at all. my pc is still in test mode from this :/
Don't worry if it doesn't appear under unknown devices. Just use the tool. A lot of what the instructions say is unnecessary. Just make sure that when you plug in your phone that one of the ports becomes "active" (I haven't had to use this tool in months, so I'm not sure exactly what it's supposed to say exactly) and press the start button.
Edit: Sorry if this was of use to some people when it was deleted.
ok. I 'll download the tool and get back to you after trying it.
edit:that worked! you are my new favorite person.
thank you so much )))))))))
Deleted
WAIT
Just Passing By said:
Deleted
Click to expand...
Click to collapse
WHY IS THIS DELETED? IM having the same problem what did you do please save me as well
Sounds like you flashed the wrong version of Oneplus 3 firmware to your phone. Do you have a 3 or a 3t? If you flash the incorrect one you will get exactly the unbootable state you describe. In that case you will have to use Qualcomm MSM Downloader tool to flash back the correct ROM and firmware partitions to get it running again. Just download the correct MSM recovery package for your phone and follow the instructions in the thread.
Hi guys .. my note 5 used to work perfectly until suddenly it stopped fast chrarging and my pc fails to recognise it
I need to get twrp for many reasons but i cant get it cuz i cant reach to odin .. and there aint a working no-pc root to my note5
Can u pls teach me a way to get twrp ..thx in advance
I had a little bit same issue. I installed official firmware and it worked. My second way is changing pc. It worked too.
CanerTR said:
I had a little bit same issue. I installed official firmware and it worked. My second way is changing pc. It worked too.
Click to expand...
Click to collapse
I cant connect it to my odin so how did u get an ofw?
Tarig Elmuntasir said:
I cant connect it to my odin so how did u get an ofw?
Click to expand...
Click to collapse
Try another computer
I had this issue as well. It turns out that somehow the micro USB cable plug was slightly damaged although i couldn't see any difference with the naked eye. But anyway, this was resolved with a new cable.
Hi, i have a problem with my note 8. Phone is bricked, I bought this phone for cheap, it has cracked screen, but wisible. Problem is, that is not turning on. Recovery, system or battery charging doesn't show off, only working mode is download. I tried install software with odin (4 files), but after install odin says PASS, but phone is turning off again. Do you have any ideas? Is it possible that this is battery problem?
(KNOX is 0x0)
I would return it and get your money back. As there is a chance that the SSD is damaged.
iceepyon said:
I would return it and get your money back. As there is a chance that the SSD is damaged.
Click to expand...
Click to collapse
Hi am wondering if you could help with my Galaxy Note 8
I am able to install the firmware using ODIN without any errors on download mode but after ODIN is finished the phone turns off and does not boot.
I have taken the phone to a repair shop as well and they have confirmed that there is no hardware issues,
Phone model number is SM-950F
Yashfauuu said:
Hi am wondering if you could help with my Galaxy Note 8
I am able to install the firmware using ODIN without any errors on download mode but after ODIN is finished the phone turns off and does not boot.
I have taken the phone to a repair shop as well and they have confirmed that there is no hardware issues,
Phone model number is SM-950F
Click to expand...
Click to collapse
I need more information bro Did you install a custom OS or the official Stock Samsung OS? Are you sure you installed the correct device's OS onto your device? Can you charge the phone via the USB charger? Etc, etc
iceepyon said:
I need more information bro Did you install a custom OS or the official Stock Samsung OS? Are you sure you installed the correct device's OS onto your device? Can you charge the phone via the USB charger? Etc, etc
Click to expand...
Click to collapse
Installed stock Vietnamese firmware which works for my Country, the phone only can be charged on download mode.
Yashfauuu said:
Installed stock Vietnamese firmware which works for my Country, the phone only can be charged on download mode.
Click to expand...
Click to collapse
In that case I believe that there is an issue with the installation of the software onto your device. I would try reinstalling it again.
iceepyon said:
In that case I believe that there is an issue with the installation of the software onto your device. I would try reinstalling it again.
Click to expand...
Click to collapse
I have tried more than once, still, the issue is not fixed
Yashfauuu said:
I have tried more than once, still, the issue is not fixed
Click to expand...
Click to collapse
Unfortunately there is something wrong with the motherboard of your device...
iceepyon said:
Unfortunately there is something wrong with the motherboard of your device...
Click to expand...
Click to collapse
thanks for the help, will try to order one and see it works
Yashfauuu said:
thanks for the help, will try to order one and see it works
Click to expand...
Click to collapse
Be sure to purchase the correct motherboard for you device. As you do not want to purchase an Snapdragon SOC motherboard for a Exynos device. As Snapdragon Modems will not work with Exynos motherboards.