I have a problem with rooting my Oneplus One. It all goes well until twrp needs to start.
My screen is all black and its not reacting to anything. I have to wait till the battery is empty to turn off.
Also when its in this stage my laptop gives me an error: 'USB Device is Not Recognized'.
I hope you can help me.
Did you check the md5 of the recovery image before flashing it? Please copy/paste the text from the command prompt on a flash attempt.
Transmitted via Bacon
Can you access fastboot mode?
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
hazefetish said:
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
Click to expand...
Click to collapse
That doesn't make sense, what do you mean by bootmode? And you didn't answer either of my questions, I asked those for a reason, if you're not going to provide the information that's needed it's pretty much impossible to help you.
Transmitted via Bacon
You can always turn off your phone by holding the power button for 10 seconds.
Try fastbooting the latest TWRP. => http://techerrata.com/browse/twrp2/bacon
It's possible that you have flashed a corrupted file or even a TWRP for a different device.
Alright
Ive tried it again.
At the moment it should boot into twrp the screen turns black.
It shows up as normal adb device, its still connected but my screen wont show me a picture.
I did it with Oneplus One Toolkit 2.0.
Did everything the steps told me.
You still haven't answered my questions...
Transmitted via Bacon
I didnt check the md5 hash but due to the tool its the right iso.
And i cant copy something out of the command promt because it closes automatically.
When i did it the command promt way i didnt even get a message that something failed.
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
hazefetish said:
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
Click to expand...
Click to collapse
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root. And at no point did you mention doing it yourself, you've only mentioned using a tool.
Transmitted via Bacon
timmaaa said:
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root.
Transmitted via Bacon
Click to expand...
Click to collapse
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
When i did it the command promt way i didnt even get a message that something failed.
Click to expand...
Click to collapse
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
hazefetish said:
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
Click to expand...
Click to collapse
My problem is you came here asking for help, and then it took me asking three times over the course of 19 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
timmaaa said:
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
My problem is you came here asking for help, and then it took me asking three times over the course of 31 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
Click to expand...
Click to collapse
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
hazefetish said:
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
Click to expand...
Click to collapse
We can though, we can find out what went wrong by investigating. I'm trying to help you, but I need this information:
Check the md5, let me know if it matches or not.
Make another manual attempt and copy the text here.
And answer whether you've tried any recovery other than TWRP.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
Listen to Timmaaa.... His guides & other experts from XDA-OPO forums has helped me understand a lot of things about rooting, flashing & other areas.........
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
skyguy126 said:
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
Click to expand...
Click to collapse
It's a nice idea, very generous, but I don't think it's the right way to go, nobody learns anything when using an automated process.
Transmitted via Bacon
Related
Hi XDA.
This was a thread I started last night ( http://forum.xda-developers.com/oneplus-one/help/one-chinese-import-flash-to-bacon-issue-t2923211) and where it ends is where I realised my device wasn't unlocked. "yeah I know"
So I downloaded and followed these steps shown on this great tutorial https://www.youtube.com/watch?v=5O2e_R_TbVg
But now my phone appears to have no OS. It wont show up as a USB device to allow me to put a zip across to install.
I have learnt alot this evening and am enjoying the process and this is the last step....
If I haven't bricked my phone!
Any help much appreciated.
That's the video that gets you to use a toolkit, right? My first piece of advice: ditch the toolkit and never use one again. They're more trouble than they're worth and clearly cause problems. Plus doing things manually allows you to actually learn a great deal of crucial stuff that you really need to know. Anyway, please provide some more information on your device, is the bootloader unlocked now? Do you have TWRP recovery installed?
Transmitted via Bacon
Hi and thanks for replying. I followed the guide and unlocked and installed TWRP and can access it easily but when tring to re boot the device it just stays on the +1 logo.
I have subsequently tried unlocking again if that was the problem.
Boot the phone into TWRP, go into the wipe menu and perform a factory reset, then reboot the phone.
Transmitted via Bacon
Ok just tried a factory reset and it failed stating among many things.
E:Unable to mount '/data
E:Unable to mount storage
Also the first line was E:could not mount / data and unable to find cry pto folder.
It might be time to start fresh, you're gonna have to try flashing the fastboot images I think.
Transmitted via Bacon
Ok thanks again for your support.
With this in mind can you please give me a nod in the right direction on how to do this please. I appreciate im a little out of my depth here. Swimmimg in deep android.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Follow step 8.
Yep, that's the one. Keep in mind though that I haven't yet updated that to suit the latest version (38R), so you can download the latest version from here:
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip
And then modify the last command to suit.
Transmitted via Bacon
Ok I'm going in! Will follow those 8 steps however the phone doesn't show as a USB device any more so will this work?
Really sorry guys but step two is a no-go as the device wont boot to enable me to get into dev options.
jnapier10 said:
Really sorry guys but step two is a no-go as the device wont boot to enable me to get into dev options.
Click to expand...
Click to collapse
All you need to worry about is section 8. They're not steps that need to be followed in sequence, they're separate sections.
Transmitted via Bacon
Ok that's a relief. I have completed step one and it says its unlocked.
Ok so im downloading the OS you suggested but cannot get the phone to come up as a USB device to put the new OS onto the internal memory.
jnapier10 said:
Ok that's a relief. I have completed step one and it says its unlocked.
Ok so im downloading the OS you suggested but cannot get the phone to come up as a USB device to put the new OS onto the internal memory.
Click to expand...
Click to collapse
You don't put it on the phone, you need to put it in your adb/fastboot directory on your PC as per the directions in section 8.
Transmitted via Bacon
Yip my bad. Sorry morning eyes and nerves dont mix.
Right installed fast-boot to my desktop and unzipped all files into fast-boot folder.
Ok lets see what happens
Hmmm
jnapier10 said:
Hmmm
Click to expand...
Click to collapse
If you follow the correct instructions you'll see that it doesn't even mention this command...
ONLY follow the instructions in section 8.
Ok everything was going great but on the final step I received this. Thanks again so much for your help, I really appreciate it. I think its close to being sorted.
Gamm86 said:
If you follow the correct instructions you'll see that it doesn't even mention this command...
ONLY follow the instructions in section 8.
Click to expand...
Click to collapse
Yip im again being a chief idiot. I realised just after I had posted.
jnapier10 said:
Ok everything was going great but on the final step I received this. Thanks again so much for your help, I really appreciate it. I think its close to being sorted.
Click to expand...
Click to collapse
Make sure the zip file is in the fastboot folder aswell and make sure the name of the file you use in the command is identical to the name of the zip file.
After the final step your phone should boot again.
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon
Cheers mate.
What build of CM11S are/were you on?
Transmitted via Bacon
timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon
Will have a crack when i get home, thanks for your help.
No good mate as you said.
Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon
Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
METAL66 said:
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow Sections 1-4 and then Section 8.
Transmitted via Bacon
Dear Timmaa
after Code:
fastboot oem device-info
It should have a couple of lines there, both with the flag set to true.
Please note: this will erase all user data from your device, it is best to do this before turning your phone on for the first time, otherwise make sure you backup anything important.
the fastboot is still on the screen, how do i move to step 2 ? just remove the cable? force restart or how ?
Are you saying that fastboot isn't working?
Transmitted via Bacon
timmaaa said:
Are you saying that fastboot isn't working?
Transmitted via Bacon
Click to expand...
Click to collapse
i see fastboot in english and chinese on the phone, i do the commands on cmd prompt, but nothing happens to the phone when i finish the steps.
You didn't answer my question though, is fastboot working? Are you getting a response in your command prompt when you enter commands? Try this:
Code:
fastboot devices
What's the result?
Transmitted via Bacon
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
METAL66 said:
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
Click to expand...
Click to collapse
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
ok i will try to make a very detailed answer, sorry. await the answer in few hours.
detailed video of how i did it
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=4N0evbwCNgI&feature=youtu.be
hope this works better ?
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
did you see my video ?
METAL66 said:
did you see my video ?
Click to expand...
Click to collapse
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
timmaaa said:
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
METAL66 said:
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
Click to expand...
Click to collapse
Cool, glad you got it sorted out. If you have any questions in future please don't hesitate to ask here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Thanks, now there are some problems with the network, is this normal? can it be solved?
METAL66 said:
Thanks, now there are some problems with the network, is this normal? can it be solved?
Click to expand...
Click to collapse
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
timmaaa said:
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
Click to expand...
Click to collapse
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
METAL66 said:
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
Click to expand...
Click to collapse
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
timmaaa said:
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, it worked perfectly, i dont know why the APN settings were empty, but now it works.
perfect, thanks a lot timmaaa
No problems [emoji3]
Transmitted via Bacon
I went to wipe my phone to sell it and in doing so I wiped pretty much everything. I can get it go into fastboot mode and load TWRP but thats about it. Please let me know what I need to do to get this thing back up and running. Thank you in advance.
Flash the 44S fastboot images, I have instructions in my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Do I do each of those steps or do I skip some things to do what I need too. I am very new at this and don't understand how to get the rom on the phone to update. Sorry for my lack of knowledge.
I bought the phone already rooted so I didn't do it. I downloaded liquidsmooth rom on the phone and installed in twrp which was easy. I made a nono when I clicked internal memory Im assuming.
They're sections in my guide, not steps. Section 8 is the section you need to do, you don't need to worry about the other sections.
Transmitted via Bacon
Oh Im getting such a headache from this. How do I get adb.exe and fastboot.exe on my computer? Way out of my league here. I may just need to find someone local to do this.
ezekielguy86 said:
Oh Im getting such a headache from this. How do I get adb.exe and fastboot.exe on my computer? Way out of my league here. I may just need to find someone local to do this.
Click to expand...
Click to collapse
Try the 15 second adb installer. Assuming you have Windows.
http://forum.xda-developers.com/showthread.php?t=2588979
Thank you very much. This worked and made me feel like a super computer geek lol. Looks like I lost root but really don't care at this point. Thank you once again.
ezekielguy86 said:
Thank you very much. This worked and made me feel like a super computer geek lol. Looks like I lost root but really don't care at this point. Thank you once again.
Click to expand...
Click to collapse
You can get root again, just by installing TWRP recovery and flashing SuperSU. Again, details are in my guide thread.
Transmitted via Bacon
Hello my friends,
now it happened to me. My OPO bricked after I installed the ColorOS port. I wanted to restart it after a succesful installation of the 2.06 port in TWRP. Now it doesn't start, neither gets recognized by windows as QHSUSB or something like that. Any ideas what I can do? It doesn't vibrate even if I hold the power button for 2 minutes.
Please help!
Thanks in advance,
Felix
Try these:
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Thanks, but the problem is that the device doesn't get listed at all in the device manager. There isn't even a "usb connect/disconnect"-sound in windows, like the device is totally dead.
Nothing you can do. Sell it at a junkyard or try to get it warranty swapped.
oneplus said:
Nothing you can do. Sell it at a junkyard or try to get it warranty swapped.
Click to expand...
Click to collapse
What are you talking about? Plenty of devices in this situation have been revived. Unless you're actually knowledgeable about something, maybe don't comment.
Transmitted via Bacon
---------- Post added at 10:51 AM ---------- Previous post was at 10:51 AM ----------
felix297 said:
Thanks, but the problem is that the device doesn't get listed at all in the device manager. There isn't even a "usb connect/disconnect"-sound in windows, like the device is totally dead.
Click to expand...
Click to collapse
So you attempted both?
Transmitted via Bacon
timmaaa said:
So you attempted both?
Transmitted via Bacon
Click to expand...
Click to collapse
No, because they're based on the same method. I can't install any drivers because there is no device listed in the device manager.
I've tried 3 different USB cables, still no luck.
But I stumbled on this:
3) If drivers dont work or your device is not detected for whatever reason install the QPST tool.
Click to expand...
Click to collapse
I installed it but don't know what to do. Its not just a single tool, its a toolkit.
felix297 said:
No, because they're based on the same method. I can't install any drivers because there is no device listed in the device manager.
I've tried 3 different USB cables, still no luck.
But I stumbled on this:
I installed it but don't know what to do. Its not just a single tool, its a toolkit.
Click to expand...
Click to collapse
Ok, but many other people in your exact situation have recovered by using those methods, you can't say it doesn't work until you actually attempt it.
Transmitted via Bacon
timmaaa said:
What are you talking about? Plenty of devices in this situation have been revived. Unless you're actually knowledgeable about something, maybe don't comment.
Transmitted via Bacon
---------- Post added at 10:51 AM ---------- Previous post was at 10:51 AM ----------
So you attempted both?
Transmitted via Bacon
Click to expand...
Click to collapse
What knowledge do you have except copy pasting some random link? The guy got hard brick. What you talk about is soft brick. Read what he says in the post then copy paste links.
The problem is that I cant attempt it because im not able to do the first step.
I think there is a misunderstanding here.
To follow these instructions the device has to be recognized by the pc, which in my special case isn't.
So I think thats it with my OPO.. Very sad
You have to turn off windows driver signing before installing the drivers otherwise it might install the drivers correctly. Did you try install the drivers with driver signing off?
No, because they're based on the same method. I can't install any drivers because there is no device listed in the device manager.
I've tried 3 different USB cables, still no luck.
But I stumbled on this:
Quote:
3) If drivers dont work or your device is not detected for whatever reason install the QPST tool.
Click to expand...
Click to collapse
oneplus said:
What knowledge do you have except copy pasting some random link? The guy got hard brick. What you talk about is soft brick. Read what he says in the post then copy paste links.
Click to expand...
Click to collapse
Exactly what I thought. You might want to brush up a bit, he is not experiencing a proper hard brick. Do some reading before you claim to know something, as I said, many people in the exact same situation have brought their phones back to life.
Transmitted via Bacon
Hey timmaaa, i don't want to speak against you, but its not the exact same situation. I think I have a proper hard brick, because the device isn't showing any sign of life
These tutorials have no use in my case until now.
felix297 said:
Hey timmaaa, i don't want to speak against you, but its not the exact same situation. I think I have a proper hard brick, because the device isn't showing any sign of life
These tutorials have no use in my case until now.
Click to expand...
Click to collapse
I understand what you're saying, but I'm telling you that several devices that were just like yours is now have been revived.
Transmitted via Bacon
timmaaa said:
Exactly what I thought. You might want to brush up a bit, he is not experiencing a proper hard brick. Do some reading before you claim to know something, as I said, many people in the exact same situation have brought their phones back to life.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok lmk how it goes.