Database Info

Issues with Video on Cory's Unofficial Cyanogen

Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!

greategress said:
Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
Click to expand...
Click to collapse
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.

greategress said:
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
Click to expand...
Click to collapse
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?

imutau said:
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
Click to expand...
Click to collapse
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:

greategress said:
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
Click to expand...
Click to collapse
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.

exad said:
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
Click to expand...
Click to collapse
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.

greategress said:
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
Click to expand...
Click to collapse
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.

exad said:
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
Click to expand...
Click to collapse
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.

greategress said:
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
Click to expand...
Click to collapse
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.

exad said:
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
Click to expand...
Click to collapse
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.

greategress said:
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
Click to expand...
Click to collapse
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.

Same issue
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.

exad said:
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Click to expand...
Click to collapse
*sigh* You're right. I'm sorry for getting snappy. Just not used to being the guy who doesn't know what he's doing, y'know?
Anyway, I sincerely appreciate the help, exad. And I doubly appreciate the reminder that I need to turn to Google before I come begging to you guys.

nlyang said:
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
Click to expand...
Click to collapse
Hmm. Heard anything about how to fix it?

greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?

exad said:
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
Click to expand...
Click to collapse
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!

greategress said:
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
Click to expand...
Click to collapse
Anytime friend!

the only thing that worked for me...
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
i tried erasing the cache via fastboot before the wipe+flash, but unfortunately I still had the issue. the only temp fix that works for me so far is disabling HW overlays in the developer options.

You could also try another kernel.
Sent from my One X using xda app-developers app

exad said:
You could also try another kernel.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Any kernel you'd recommend over the others? You mentioned the jacob.b2 and oc-vm-linaro before. Like one more than the other?

[Q] accidentally formatted Internal Storage - No OS installed!

Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A

You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot

DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.

Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.

Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A

For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.

DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.

hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.

zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.

DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?

J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0

same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins

minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp

still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?

minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point

still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)

minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image

truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.

minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone

jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,

[Q] Nexus 5 No OS installed!

Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!

Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5

if you can enter fastboot just flash a ROM through it ...you'll be fine

sirajgoku said:
if you can enter fastboot just push a ROM through adb ...you'll be fine
Click to expand...
Click to collapse
Massive contradiction in terms - you can't use adb commands in fastboot, you use fastboot commands in fastboot
Sent from my Nexus 5 using XDA Premium 4 mobile app

If this were me I would adb push a custom rom via recovery. Although I love stock, if I were in your shoes I would go with cataclysm or slim.

mmavani said:
Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!
Click to expand...
Click to collapse
Have you tried flashing the factory image? This should be a requirement before coming on here and asking for help.

instruction
El Daddy said:
Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5
Click to expand...
Click to collapse
can you send me guide? instructions? video?

mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
The sticky threads in general and Q&A would be a good place to look.
Sent from my Nexus 5

mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
Ay yay yay, I hear kittens dying.

This is a perfect example of why toolkits aren't beneficial to new users. If the OP had rooted manually, he'd be familiar with both fastboot and adb, and would be able to solve this issue easily.
Toolkits should only be used by experienced users, in order to save time... NOT as a pacifier for the uninitiated. :-\
Sent from my Nexus 5 using Tapatalk

@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk

Fixed
jjhiza said:
@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's already fixed.
Thanks for your help

[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.

Hi, anyone here who can build a custom recovery (maybeTWRP)

Hi all, did anyone build a recovery? I would do it but I haven't got a computer that runs Linux and I am not firm with it at all.
Edit: I couldn`t use any method that I found to create a custom recovery, is there anyone with more success?
Also I could not use SP-Flash tool to make a backup, did anyone succeed and how?
Thanks
Sent from my HTC One A9 using XDA-Developers mobile app

new device ordered hopefully we see some development in this section soon =)

i also hope but i think this was not the interessted phone for developper...

Is there nobody to do this recovery?

Brainwasher34 said:
Is there nobody to do this recovery?
Click to expand...
Click to collapse
We gotta wait

If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).

Captain_Throwback said:
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Click to expand...
Click to collapse
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.

patrixs94 said:
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
Click to expand...
Click to collapse
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.

Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Captain_Throwback said:
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Click to expand...
Click to collapse
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Click to expand...
Click to collapse

patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
Click to expand...
Click to collapse
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.

Tested
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Captain_Throwback said:
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Click to expand...
Click to collapse

vejda said:
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Click to expand...
Click to collapse
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img

Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Captain_Throwback said:
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse

vejda said:
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Click to expand...
Click to collapse
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).

Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Captain_Throwback said:
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Click to expand...
Click to collapse

vejda said:
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Click to expand...
Click to collapse
The recovery log has to exist while in TWRP.

ADB doesn´t run while TWRP, screen attached.
Captain_Throwback said:
The recovery log has to exist while in TWRP.
Click to expand...
Click to collapse

vejda said:
ADB doesn´t run while TWRP, screen attached.
Click to expand...
Click to collapse
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.

Ok, thx. I am not expirienced user of it, but try to solve it Where are all the others? Hey!!
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse

Here it is!
Here is the log, I was using old ADB.
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse