Database Info

In QHSUSB_DLOAD Mode, nothing working

Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.

usaff22 said:
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
Click to expand...
Click to collapse
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/

dc211 said:
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
Click to expand...
Click to collapse
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip

usaff22 said:
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
Click to expand...
Click to collapse
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.

dc211 said:
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
Click to expand...
Click to collapse
Thanks, I knew it wouldn't work after I saw someone on the One XL forums who tried it on his with a USB Y Cable, and didn't look for the zip on the internal storage. I used to think it would work after doing it on my brother's Sensation, but it was a no go for me.
At this stage I think I will have to visit my carrier. Hopefully they can give me a replacement or get it fixed somehow.

This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade

Fofff said:
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Click to expand...
Click to collapse
I tried that, my partitions won't show so it is of no help to me unfortunately.

[Q] HOX will not boot up or turn on or have LED response

Hey everyone. So everything was good for the last couple of days as I was on JellyBAM 6.6.0 evita. This morning after charging my phone I go to open it, view some websites etc. Phone reboots by itself, goes to lockscreen. I try unlocking my lockscreen everything good for about 10 seconds. Try to open facebook up, and boom phone goes black and will not turn on. I know for a fact that is 100% charged as when I woke up I checked the battery as I usually do to see if it charged or not.
I am pretty sure I am on Hboot 1.09 or less as I bought the phone close to the release date. Any thoughts because its weird how I cant turn even turn it on or have a LED light show up when it charges.
Thanks in advance
EDIT: Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?

have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium

NerdFurgison said:
have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah I forgot to mention I have tried getting into bootloader using the volume down + power process along with holding the power button. Nothing is working.

This phone has well-known power management issues. Sometimes the battery stats get corrupted and the phone thinks the battery is dead when it isn't. Unfortunately, this sometimes results in a brick.
Plug into your PC and see what pops up in Device Manager. If you get QHUSB_DLOAD, you've been bricked. However, this may be fixable since you're on 1.09.

Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything

Zobabe said:
Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything
Click to expand...
Click to collapse
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.

iElvis said:
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.
Click to expand...
Click to collapse
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.

Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?

Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.

iElvis said:
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?
Click to expand...
Click to collapse
I am having trouble downloading ADB drivers atm. Trying to find an article that explains it. Kind of a noob at this type of stuff. As for formatting, I dont see an option in TWRP.

razorc03 said:
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.
Click to expand...
Click to collapse
If you could please link it to me, it would be greatly appreciated. Thanks

I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks

Zobabe said:
If you could please link it to me, it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL

razorc03 said:
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Click to expand...
Click to collapse
in order to this though, my computer has to be able to recognize my htc one x. I cant even get it to recognize. any tips?

Zobabe said:
I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks
Click to expand...
Click to collapse
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.

DvineLord said:
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.
Click to expand...
Click to collapse
haha yeah I realized that once I did it and read it in the sticky in the android development section. Do you have any idea of how I could get windows 8 to recognize my htc one x?

windows 8 is the last thing in the world i would let touch my computer. windows xp for life.
i heard alot of people having issues with win8 and usb 3.0 ports.

Partially Bricked Nexus 5

I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this

I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal

snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.

Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data

I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop

do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.

Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above

rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links

snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..

rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..

snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.

rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.

snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers

rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.

rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.

theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight

[Q] Connectivity to PC issue post BOOT-Loop

Hello Lovely people of XDA,
It has been a while since I have requested help here due to the huge library of information available but I am unable to solve this one and I think it should be pretty simple.
For completeness, here is the order of events:
ROOTed One and running stock CM11s with no problems since August 2014.
Wanted a smoother system so flashed vanilla Franco Kernel (very nice) yesterday.
Wanted a bit more so after some searching, found the SlimSaber ROM with TyrV74-Linaro Kernel as a suitable choice.
Now, I followed order of install but stupidly, didnt clear the cache or dalvik cache following install.
I got stuck in boot loop so booted to fastboot to open recovery through ADB.
PROBLEM STARTS
My PC didnt recognise my device and this was confirmed through the blank list returned when using "ADB Devices" in the command window.
I updated the drivers through the ADB interface, restarted computer and tried again. Same thing. I then downloaded the drivers from the Google link in one of the forums (http://developer.android.com/sdk/win-usb.html#top), restarted and connected again. I then tried two solutions (although they both do the same thing) and update the drivers through Device Manager and searching for them using the "have disk" option.
This still didnt work.
From what I can tell this is a driver issue but I have installed several times now the most up to date drivers and from what I can tell, the only difference between my screenshots and the help pages/forum posts is that my Device Manager list doesn't recognise the phone as the A0001, just an "Android Device" (pic attached).
I have searched the forums and all roads lead to either re-installing the drivers or changing the driver settings through device manager, both of which I have tried several times but no joy when I use ADB to check for devices.
Any ideas? I will try anything as I now have a beautifully BOOT-Looped OnePlus!
Also, if anyone knows how to boot to recovery from phone off state then that will also help!

Also tried the Samsung drivers...

OK, having managed to get the Comp to regognise in Fastboot, is there a way I can flash a nandroid through fastboot? I have checked and it says I need to flash three images but the only saved backups I have are .win files and there is only one (judging by the size of the file)

ssjghost said:
OK, having managed to get the Comp to regognise in Fastboot, is there a way I can flash a nandroid through fastboot? I have checked and it says I need to flash three images but the only saved backups I have are .win files and there is only one (judging by the size of the file)
Click to expand...
Click to collapse
You can't flash a nandroid with fastboot, only with the specific recovery you used to create the nandroid.
Transmitted via Bacon

timmaaa said:
You can't flash a nandroid with fastboot, only with the specific recovery you used to create the nandroid.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?

ssjghost said:
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?
Click to expand...
Click to collapse
strangely enough....when I fastboot reboot, it loads to system and as long as I keep the phone connected to PC it loads...when I remove it and boot, it crashes. I know this is the case as I wiped cache and delvik and nothing happened when removed but when I booted to system while connected it started updated gapps.... if that helps anyone....

ssjghost said:
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?
Click to expand...
Click to collapse
You don't need to boot into the ROM to get to recovery. Turn the phone off, then hold volume down + power, once you see the initial splash screen let go of power but keep holding volume down until you get to recovery.
Why can't you move the backup? Please provide specifics, it will decrease the amount of back-and-forth we have to do to solve your issue.
Transmitted via Bacon

timmaaa said:
You don't need to boot into the ROM to get to recovery. Turn the phone off, then hold volume down + power, once you see the initial splash screen let go of power but keep holding volume down until you get to recovery.
Why can't you move the backup? Please provide specifics, it will decrease the amount of back-and-forth we have to do to solve your issue.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks,
I cant move file as, I presume, its down to drivers. Which I am unclear as to why? I can access the device through fastboot but when I go through "MyComputer", I get the icon for the phone but when I enter, no files (See Screenshots). If you want specific screenshots then let me know. When I transfer the backup....

Which drivers do you currently have installed?
Transmitted via Bacon

timmaaa said:
Which drivers do you currently have installed?
Transmitted via Bacon
Click to expand...
Click to collapse
"SAMSUNG Android ADB Interface"
They seem to be the only ones that work since flashing new ROM and Kernel...

ssjghost said:
"SAMSUNG Android ADB Interface"
They seem to be the only ones that work since flashing new ROM and Kernel...
Click to expand...
Click to collapse
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?

ssjghost said:
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?
Click to expand...
Click to collapse
Sorry, to clarify, when I say "work" I mean allow fastboot recognition....doesnt recognise files through MyComputer.....

ssjghost said:
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?
Click to expand...
Click to collapse
Yeah that's probably a reasonable option, but it most likely won't solve the issue of not being able to copy files across. When you're booted into Android does the device show up as an MTP device in Windows and allow you to copy files, or is it broken there also?
Transmitted via Bacon

timmaaa said:
Yeah that's probably a reasonable option, but it most likely won't solve the issue of not being able to copy files across. When you're booted into Android does the device show up as an MTP device in Windows and allow you to copy files, or is it broken there also?
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?

ssjghost said:
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?
Click to expand...
Click to collapse
....or phone (re-read question...)

ssjghost said:
....or phone (re-read question...)
Click to expand...
Click to collapse
(Sorry to treat board as IM but I keep thinking of potentially useful info...)
Somewhat unhelpfully, I have only flashed slim gapps so if you refer to an app, please specify which one as I likely dont have it!

ssjghost said:
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?
Click to expand...
Click to collapse
ssjghost said:
....or phone (re-read question...)
Click to expand...
Click to collapse
ssjghost said:
(Sorry to treat board as IM but I keep thinking of potentially useful info...)
Somewhat unhelpfully, I have only flashed slim gapps so if you refer to an app, please specify which one as I likely dont have it!
Click to expand...
Click to collapse
MTP is the format that's used to mount the internal storage on your phone to your PC so you see it as a removable drive. There's no app required, so if you're not seeing your phone storage on your PC then MTP isn't working.
First thing to try: go to Settings/Storage and hit the little menu button in the top corner, there should be an MTP option in there. If it isn't enabled, enable it and try connecting to your PC again. If it is already enabled then it's time to look at your drivers.
I'd completely uninstall the Samsung drivers, reboot your PC, then install the Universal adb drivers, reboot PC again, connect your phone to your PC, you should get an automatic popup saying that device drivers are installing (or something like that), let that complete, then try looking at your phone storage again.
Transmitted via Bacon

timmaaa said:
MTP is the format that's used to mount the internal storage on your phone to your PC so you see it as a removable drive. There's no app required, so if you're not seeing your phone storage on your PC then MTP isn't working.
First thing to try: go to Settings/Storage and hit the little menu button in the top corner, there should be an MTP option in there. If it isn't enabled, enable it and try connecting to your PC again. If it is already enabled then it's time to look at your drivers.
I'd completely uninstall the Samsung drivers, reboot your PC, then install the Universal adb drivers, reboot PC again, connect your phone to your PC, you should get an automatic popup saying that device drivers are installing (or something like that), let that complete, then try looking at your phone storage again.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks,
MTB is checked and phone still not seen in menu so DLing drivers and will let you know after restart.
BTW, should I update drivers through device manager before/after or not at all after restart?

ssjghost said:
Thanks,
MTB is checked and phone still not seen in menu so DLing drivers and will let you know after restart.
BTW, should I update drivers through device manager before/after or not at all after restart?
Click to expand...
Click to collapse
There should be no need to update the drivers, because they're a fresh download they should be the latest.
Transmitted via Bacon

timmaaa said:
There should be no need to update the drivers, because they're a fresh download they should be the latest.
Transmitted via Bacon
Click to expand...
Click to collapse
.....nice...it was already installed. Ill remove, restart, install, restart and let you know....:/

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.