Database Info

[Q] NEXUS 5 BRICKED TRYING TO ROOT WITH CF AutoRoot. HELP!?

Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.

Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?

abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot

Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.

abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?

Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?

abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?

Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.

abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.

abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.

Would opening the command prompt window with administrative rights make a difference? Worth a shot.

Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.

Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.

It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.

[Q] [Correct Forum?]Some Questions About This Phone

I will be getting a Sony Xperia E from Immix (with a SIM Card), and I am wondering if I am in the correct section of the forums. I have a few questions, since I had an HTC One V before, about the current status of this phone:
Has this phone been S-Off'd yet?
If not, is TWRP at least released for this phone?
I think that's it. I'll update with more questions as I get them
Thanks in advance,
NarWhat

123386761 said:
I will be getting a Sony Xperia E from Immix (with a SIM Card), and I am wondering if I am in the correct section of the forums. I have a few questions, since I had an HTC One V before, about the current status of this phone:
Has this phone been S-Off'd yet?
If not, is TWRP at least released for this phone?
I think that's it. I'll update with more questions as I get them
Thanks in advance,
NarWhat
Click to expand...
Click to collapse
S-OFF (unlock bootloader) in Sony terms is can be done by visit http://unlockbootloader.sonymobile.com and follow the instructions. make sure you test by enter *#*#7378423#*#* on dialer and then, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
dunno if someone already build TWRP for Xperia E, but there is CWM for Xperia E

AshRoller said:
S-OFF (unlock bootloader) in Sony terms is can be done by visit http://unlockbootloader.sonymobile.com and follow the instructions. make sure you test by enter *#*#7378423#*#* on dialer and then, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
dunno if someone already build TWRP for Xperia E, but there is CWM for Xperia E
Click to expand...
Click to collapse
Sorry, in [HTC One V] terms, S-Off not only requires the bootloader to already be unlocked, but then you can also edit the boot, radio and other partitions that are still locked while the bootloader is unlocked.
And that phone number is very helpful, thanks! I'll have to test it Wednesday, when my phone is supposed to arrive
And about building TWRP, I'll do it. I've built several pieces of software for my previous phone, aaaaand I hope it's the same process LOL

123386761 said:
Sorry, in [HTC One V] terms, S-Off not only requires the bootloader to already be unlocked, but then you can also edit the boot, radio and other partitions that are still locked while the bootloader is unlocked.
And that phone number is very helpful, thanks! I'll have to test it Wednesday, when my phone is supposed to arrive
And about building TWRP, I'll do it. I've built several pieces of software for my previous phone, aaaaand I hope it's the same process LOL
Click to expand...
Click to collapse
ah sorry forgot that s-off/on terms, i'm also have htc device, S-ON, but unlocked bootloader.
Sent from my iPad using Tapatalk

123386761 said:
Sorry, in [HTC One V] terms, S-Off not only requires the bootloader to already be unlocked, but then you can also edit the boot, radio and other partitions that are still locked while the bootloader is unlocked.
And that phone number is very helpful, thanks! I'll have to test it Wednesday, when my phone is supposed to arrive
And about building TWRP, I'll do it. I've built several pieces of software for my previous phone, aaaaand I hope it's the same process LOL
Click to expand...
Click to collapse
You've had a One V? Cool, there's one in the family, still stock, of course.
I think the radio and stuff can be changed even when the bootloader is locked , using Flashtool to flash the firmwares in flash mode. [citation needed] At least the baseband can be changed easily, probably other stuff too.
TWRP has been built for CM10 (actually it's a dual recovery; both CWM and TWRP) by hsr0. Others have been built too, but since our phones have no recovery image, the recovery has to be built into the kernel, and this is the most stable CM10 kernel, I recommend this one. Not sure if there's a stock TWRP, though.

NSDCars5 said:
You've had a One V? Cool, there's one in the family, still stock, of course.
I think the radio and stuff can be changed even when the bootloader is locked , using Flashtool to flash the firmwares in flash mode. [citation needed] At least the baseband can be changed easily, probably other stuff too.
TWRP has been built for CM10 (actually it's a dual recovery; both CWM and TWRP) by hsr0. Others have been built too, but since our phones have no recovery image, the recovery has to be built into the kernel, and this is the most stable CM10 kernel, I recommend this one. Not sure if there's a stock TWRP, though.
Click to expand...
Click to collapse
So from this info I'm guessing you're a major developer for this phone?
Just a note- I plan on unlocking the bootloader as soon as I get the phone, so I don't lose any personal data stored on it

123386761 said:
So from this info I'm guessing you're a major developer for this phone?
Just a note- I plan on unlocking the bootloader as soon as I get the phone, so I don't lose any personal data stored on it
Click to expand...
Click to collapse
LOL, no. I've just started my first project, and hardly anybody here knows what it is.
Before unlocking your phone's bootloader, be sure to root it (many guides to root it with a locked bootloader here) and backup the TA partition: this partition has some DRM keys that are removed once you unlock the bootloader. I'm not sure what they do, but you can check whether the DRM keys are there or not, so if you take it to Sony, you can reflash TA, unroot, and they'll honour the warranty.

NSDCars5 said:
LOL, no. I've just started my first project, and hardly anybody here knows what it is.
Before unlocking your phone's bootloader, be sure to root it (many guides to root it with a locked bootloader here) and backup the TA partition: this partition has some DRM keys that are removed once you unlock the bootloader. I'm not sure what they do, but you can check whether the DRM keys are there or not, so if you take it to Sony, you can reflash TA, unroot, and they'll honour the warranty.
Click to expand...
Click to collapse
Oh okay this is good info! Thanks!
**EDIT** should I root, THEN backup the TA partition?
Thanks!

123386761 said:
Oh okay this is good info! Thanks!
**EDIT** should I root, THEN backup the TA partition?
Thanks!
Click to expand...
Click to collapse
Yes.
And also make sure,you've got a few ftf files.

In case you want to know in HTC terms: FTFs are like RUUs, but safer to flash - so much that we've been using Xperia E dual's FTF files on the Xperia E single.

NSDCars5 said:
In case you want to know in HTC terms: FTFs are like RUUs, but safer to flash - so much that we've been using Xperia E dual's FTF files on the Xperia E single.
Click to expand...
Click to collapse
Cool this is exactly what I'm looking for. Now I feel safe to unlock the bootloader and root

Okay, got the phone in yesterday, and after a LONG night of downloading all the necessary files, I am about to use flashtool to root my phone
**EDIT** ... sitting in homeroom at school hoping to get this done before class, and realize I don't have an android USB cable on me :l

123386761 said:
Iam about to use flashtool to root my phone
Click to expand...
Click to collapse
To flash the kernels, I assume? Just asking to be sure.
123386761 said:
and realize I don't have an android USB cable on me :l
Click to expand...
Click to collapse
:banghead: Didn't you get one with the phone?
Well, have a nice day!
Sent from a bad phone

Yeah I got one for the phone, but I was rushing out of the house lol
Sent from my C1504 using xda app-developers app

Well this sucks. Apparently Windows 8.1 has issues with connecting Sony devices. Probably just install W7 for a dual boot... but thanks a lot Microsoft! Making me go out of my way to root my phone :l

123386761 said:
Well this sucks. Apparently Windows 8.1 has issues with connecting Sony devices. Probably just install W7 for a dual boot... but thanks a lot Microsoft! Making me go out of my way to root my phone :l
Click to expand...
Click to collapse
Don't worry; I feel the same way - my Nexus's fastboot drivers work awesome, but Sony's drivers seem to have problems in 8.1. I need to use another PC for this (no other Windows 7 license around)...

NSDCars5 said:
Don't worry; I feel the same way - my Nexus's fastboot drivers work awesome, but Sony's drivers seem to have problems in 8.1. I need to use another PC for this (no other Windows 7 license around)...
Click to expand...
Click to collapse
Ugh. I hate it when things don't support each other. Might just do this at school, they run Windows XP XD

123386761 said:
Ugh. I hate it when things don't support each other. Might just do this at school, they run Windows XP XD
Click to expand...
Click to collapse
You know, I've been liking you (and a couple of other forum members) more and more, as I read your (and their) posts.
Another tip: don't, ever let the battery level on your phone go down below 15%. Because when the battery goes down to 0%, it's pretty difficult to wake it up - I just had to wake up mine.

NSDCars5 said:
You know, I've been liking you (and a couple of other forum members) more and more, as I read your (and their) posts.
Another tip: don't, ever let the battery level on your phone go down below 15%. Because when the battery goes down to 0%, it's pretty difficult to wake it up - I just had to wake up mine.
Click to expand...
Click to collapse
Thanks! And I've already been at 8% once >_>... I just let it charge overnight, like I do every night. Now it's back to normal

Downloading Windows 7 now, 90% done. Will post results after installation of OS + Android SDK + phone drivers :l

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

[Q] How to restore to bone stock with backed-up TA partition

So I cracked my screen and the top half of the digitizer doesn't work now. I sent it in to be repaired (damage claim, not warranty claim) but it turns out if it has modified software they just straight up won't touch it.
So after sobbing to myself here's what I did:
Flashed the stock FTF to it
Locked bootloader
Rooted ROM
Tried to restore DRM keys (I used TA backup before unlocking the Bootloader)
And it all seems well and good, the PC companion doesn't throw an unrecognized software error anymore but the DRM keys for MERLIN and the other two show up with "Unknown Error"
Is there something I'm missing? And also I'm just assuming the center will check for these things and boot my phone back to me again so I'd like to get them as close to perfect as possible before trying again. I'm not looking for them to fix my phone for free. I just want the right people repairing it.
EDIT: Just FYI I have a D6603

Did you reboot your phone after restoring the drn keys?

freddy1991 said:
Did you reboot your phone after restoring the drn keys?
Click to expand...
Click to collapse
Yeah :\
One thing I'm worried about is I backed up the partition the very day that an exploit was found. So I think the TA backup utility was able to do it but is there any chance there was a compatibility update that needed to happen?

I did the same too.
Root My z3 just after the exploit had been discovered and backup the keys using TA backup tool.
Actually I did unlock mine quite a few times already and successfully restored the keys every time with TA backup.

What method are you using to lock the bootloader? I just hit the checkbox on the FTF flasher app so maybe that's the problem? I guess I'll try it with fastboot instead?
freddy1991 said:
I did the same too.
Root My z3 just after the exploit had been discovered and backup the keys using TA backup tool.
Actually I did unlock mine quite a few times already and successfully restored the keys every time with TA backup.
Click to expand...
Click to collapse

topherhead said:
What method are you using to lock the bootloader? I just hit the checkbox on the FTF flasher app so maybe that's the problem? I guess I'll try it with fastboot instead?
Click to expand...
Click to collapse
Actually, you don't need to relock the bootloader.
Restoring TA backup automatically relocks the bootloader.

freddy1991 said:
Actually, you don't need to relock the bootloader.
Restoring TA backup automatically relocks the bootloader.
Click to expand...
Click to collapse
Well I feel kinda dumb for not checking this first. But I went into the service tests and checked the bootloader and it's still showing up as unlocked so that explains that. Now why I'm having difficulty locking it is another concern.
So I booted into fastboot and entered fastboot oem lock and now it's just sitting... I'm not sure it's doing anything (first time I've tried to lock rather than unlock) It just made a ... then the cursor is blinking on a new line... So I'm a little concerned there but there's gotta be a way to relock it right?

topherhead said:
Well I feel kinda dumb for not checking this first. But I went into the service tests and checked the bootloader and it's still showing up as unlocked so that explains that. Now why I'm having difficulty locking it is another concern.
So I booted into fastboot and entered fastboot oem lock and now it's just sitting... I'm not sure it's doing anything (first time I've tried to lock rather than unlock) It just made a ... then the cursor is blinking on a new line... So I'm a little concerned there but there's gotta be a way to relock it right?
Click to expand...
Click to collapse
Just restore your TA partition via TA-backup tool and you are good to go.

profprof said:
Just restore your TA partition via TA-backup tool and you are good to go.
Click to expand...
Click to collapse
I'm at work now so I can't test but my concern is that I've already tried that a few times. I didn't check bootloader status after each one, just the keys. So far using fastboot, the TA backup tool, and the flashtool doesn't seem to work. The TA tool and the flashtool seem to think everything went fine while fastboot just hangs...
I do like that now at least I know what's wrong, so I just need all the ways to lock a bootloader...

topherhead said:
I'm at work now so I can't test but my concern is that I've already tried that a few times. I didn't check bootloader status after each one, just the keys. So far using fastboot, the TA backup tool, and the flashtool doesn't seem to work. The TA tool and the flashtool seem to think everything went fine while fastboot just hangs...
I do like that now at least I know what's wrong, so I just need all the ways to lock a bootloader...
Click to expand...
Click to collapse
When you restored ta partition it will be relocked automatically, you won't need any other steps to relock bootloader

profprof said:
When you restored ta partition it will be relocked automatically, you won't need any other steps to relock bootloader
Click to expand...
Click to collapse
That's what I'm trying to tell you! I restored the keys using TA-Backup and it says everything was successful but in the service tests the bootloader still shows as unlocked and the keys show an unknown error though they are "Active" I'm not sure what that means really.

Alright got it.
At some point I did that thing in TA-Backup where you convert the backup into a new type that the later versions of TA can use (oor at least that's how I interpreted it) and I forgot I did that. So I tried using one of the older versions and it worked perfectly!

Bootloader Unlocked - Camera not working - DRM patch anyone?

Hi everbody,
I've my device since 2 days and i'm looking for a solution to my problem : when i take a photo with the stock app, it shows me a green screen after the shutter :/
Of course i tasted all i can before this post : restore my device, Emme (not possible when bootloader unlock), ... Maybe if someone send me the original apk, i can install it and resolve my pb.
Hope someone can do it
Thx

Pretty sure this is the one you need.
http://www.apkmirror.com/apk/sony-mobile-communications/sony-camera/camera-sony-mobile-communications-2-0-0-release/sony-camera-2-0-0-4-android-apk-download/
It's the same version as I have.

jms.flynn said:
Pretty sure this is the one you need.
http://www.apkmirror.com/apk/sony-mobile-communications/sony-camera/camera-sony-mobile-communications-2-0-0-release/sony-camera-2-0-0-4-android-apk-download/
It's the same version as I have.
Click to expand...
Click to collapse
Thanks for your reply ! Unfortunately, it's "corrupted" (i'm french, sorry for my english)
I made a test with other apps and it works... But not Sony camera

Today, Emma detects my device and software is downloading new version (1309 vs 1306). Crosse my fingers to resolve my pb with this !

Nikom69 said:
Today, Emma detects my device and software is downloading new version (1309 vs 1306). Crosse my fingers to resolve my pb with this !
Click to expand...
Click to collapse
Probably won't but fingers crossed - This looks like something that happens when you unlock bootloader. Some functions might get disabled (it's usually only the advanced camera functions such as noise cancelling, but on my X camera was only showing green). Try the Emma dev version - should work (should give you at least some functionality), or wait for a kernel to be developed.
As a cautionary tale, it's way too early for BL unlock where there is No dev support. This release is just too recent. Personally, I'll wait for tested root methods and hopefully a TA backup solution.

Do you know where I can find Emma dev version ?
Coz you're right : it didn't work...

Nikom69 said:
Do you know where I can find Emma dev version ?
Coz you're right : it didn't work...
Click to expand...
Click to collapse
Download the EMMA from sony website. As soon as it detects your unlocked bootloader it will automagically download the latest dev fw version - customization is outside of what xperiafirm offers and it should work. Should. I'm still waiting for my phone to be delivered so I can't help you further than that. I just know it works for terrible failures.
In any case, a kernel that addresses the DRM content functionality is probably weeks away weeks away. Maybe relocking the bootloader will help? Could restore partial camera functionality, instead of a green screen.
Again, I'm coming with ideas under a huge maybe but you should give it a try.

Sebi673 said:
Download the EMMA from sony website. As soon as it detects your unlocked bootloader it will automagically download the latest dev fw version - customization is outside of what xperiafirm offers and it should work. Should. I'm still waiting for my phone to be delivered so I can't help you further than that. I just know it works for terrible failures.
In any case, a kernel that addresses the DRM content functionality is probably weeks away weeks away. Maybe relocking the bootloader will help? Could restore partial camera functionality, instead of a green screen.
Again, I'm coming with ideas under a huge maybe but you should give it a try.
Click to expand...
Click to collapse
i think for the moment relocking bootloader is the best... but how ? Could you (or someone) help me step by step ?
In flashtool / Emma the "volume down + plug usb" isn't working, so i have only fastboot command...

Nikom69 said:
i think for the moment relocking bootloader is the best... but how ? Could you (or someone) help me step by step ?
In flashtool / Emma the "volume down + plug usb" isn't working, so i have only fastboot command...
Click to expand...
Click to collapse
It should be working although you need to install the drivers without Enforcing Driver signature.
To do that you need to restart your PC while holding the Shift key. Shift, click restart and a 'new' screen will appear asking you how do you want to restart. go through the menus till you see the F1-12 options. As far as I remember F7 is the one that disables driver signature enforcement. After that PC should restart normally but without that thingy. Once restarted go to flashtool folder - drivers - and install the drivers - click allow everywhere and voila, drivers are set. From there on, you should see the phone as connected. Emma should also work.
hrs a vid of how to custom restart https://youtu.be/71YAIw7_-kg?t=1m1s

Sebi673 said:
It should be working although you need to install the drivers without Enforcing Driver signature.
To do that you need to restart your PC while holding the Shift key. Shift, click restart and a 'new' screen will appear asking you how do you want to restart. go through the menus till you see the F1-12 options. As far as I remember F7 is the one that disables driver signature enforcement. After that PC should restart normally but without that thingy. Once restarted go to flashtool folder - drivers - and install the drivers - click allow everywhere and voila, drivers are set. From there on, you should see the phone as connected. Emma should also work.
hrs a vid of how to custom restart https://youtu.be/71YAIw7_-kg?t=1m1s
Click to expand...
Click to collapse
After doing all things... same issue ! In FlashTool driver setup, i didn't find exactly xzp drivers... so i install all to make a test and this is what i had :

Nikom69 said:
After doing all things... same issue ! In FlashTool driver setup, i didn't find exactly xzp drivers... so i install all to make a test and this is what i had :
Click to expand...
Click to collapse
You just need the generic adb drivers. but if they're not working try those. https://developer.sonymobile.com/downloads/drivers/xperia-xz-premium-driver/ Although flashtool might not be compatible. I can't confirm this since I'm still waiting for my phone to be delivered. Soon this should be populated, is where you can find a custom kernel that restores DRM functionality https://kernel.andro.plus/yoshino.html

In Windows, my device with green led (volume - and plugged) => SOMC Flash Device. If i click on "upgrade drivers" and go in Sony Driver folder, windows tells me my driver is up to date.
I certainly forget or loose something, but it's the first time i have pb with any device since 10 years !! :/

DRM patch?
@FartyParty @kemod @AndroPlus
Hey guys, can you please help @Nikom69 with his DRM issue?
He unlocked BL and has no camera functionality - green screen. He flashed the FW with EMMA and still no camera. And flashtool isn't working. I did my best to help him but I'm still waiting for my phone to arrive.
So do you have a working DRM patch or something to get him at least basic camera functions back? I told him to wait for AndroPlus Kernel but maybe there's a quick fix or a different idea.

Sebi673 said:
...He unlocked BL and has no camera functionality - green screen. ...
Click to expand...
Click to collapse
Unfortunately no, I experienced the same and also posted this issue on another thread hoping that someone won't repeat my mistake
https://forum.xda-developers.com/showpost.php?p=72645858&postcount=19
It seems like all proprietary post processing is no longer functional after bootloader unlock, but video still work to some extent and you can still use the camera only in manual mode with ISO 100 and all features off (which is useless). My Sony XZP just turn into an expensive and beautiful "worse than AOSP phone" right now. I really hope someone could have a solution to this, heck I even willing to pay for it.

Yes, unlocking the bootloader destroys the drm-keys and disables stuff.
The keys are gone, warranty gone, no amount of flashing this or that will restore anything.
Relocking the bootloader will NOT restore drm-keys because they are gone FOREVER.
Just wait for a custom kernel with drm-fix included and the camera will work again.
How were you even able to unlock the bootloader if you can't get flashtool to work?

FartyParty said:
Yes, unlocking the bootloader destroys the drm-keys and disables stuff.
The keys are gone, warranty gone, no amount of flashing this or that will restore anything.
Relocking the bootloader will NOT restore drm-keys because they are gone FOREVER.
Just wait for a custom kernel with drm-fix included and the camera will work again.
How were you even able to unlock the bootloader if you can't get flashtool to work?
Click to expand...
Click to collapse
That's simple - Fastboot commands. I'm receiving my XZp today but now I'll think twice and wait for the Androplus.
I was thinking for bootloader relock - cause on my Xperia X after relocking camera was working to some extent, but its not the case here..... Anyway if you think of something write it here. He'll be happy for any solution you find. I know how it feels to go from flagship to brick in under 3 seconds so he's got my full support :laugh:

Sebi673 said:
That's simple - Fastboot commands. I'm receiving my XZp today but now I'll think twice and wait for the Androplus.
I was thinking for bootloader relock - cause on my Xperia X after relocking camera was working to some extent, but its not the case here..... Anyway if you think of something write it here. He'll be happy for any solution you find. I know how it feels to go from flagship to brick in under 3 seconds so he's got my full support :laugh:
Click to expand...
Click to collapse
So he managed to unlock bootloader with adb fastboot but adb flashboot doesn't work?
If he were able to flash twrp he could just flash drm-fix etc.
But eh, just gotta wait a little.

FartyParty said:
So he managed to unlock bootloader with adb fastboot but adb flashboot doesn't work?
If he were able to flash twrp he could just flash drm-fix etc.
But eh, just gotta wait a little.
Click to expand...
Click to collapse
Exactly, he needs the DRMfix, do you have it? Or should he wait for the kernel to come out. This Thread should be a cautionary tale for first timers so information is the key. :cyclops:

Sebi673 said:
Exactly, he needs the DRMfix, do you have it? Or should he wait for the kernel to come out. This Thread should be a cautionary tale for first timers so information is the key. :cyclops:
Click to expand...
Click to collapse
This is what I used on the Sony XZ, XZs
LINK

Nikom69 said:
Hi everbody,
I've my device since 2 days and i'm looking for a solution to my problem : when i take a photo with the stock app, it shows me a green screen after the shutter :/
Of course i tasted all i can before this post : restore my device, Emme (not possible when bootloader unlock), ... Maybe if someone send me the original apk, i can install it and resolve my pb.
Hope someone can do it
Thx
Click to expand...
Click to collapse
You have to flash the modified kernel with the drm patch.. The same thing happened in my XZs, got solved only after I flashed the modified kernel..