Related
I just received a "new" Photon Q thanks to a warranty swap from Motorola. When I got my 1st Photon Q last year, I used this thread to root the thing...
http://forum.xda-developers.com/showthread.php?t=1856480
That thread is ancient, though, and some of the links don't work.
I've been searching and searching... and I'm stuck. This is my 2nd day of searching, so I'm resorting to a new thread.
The phone is unlocked thanks to Motorola's unlocking tool.
I finally found & downloaded the 6.0.1.3 recovery from here:
http://clockworkmod.com/rommanager
Following the directions that are pretty uniform across the 'net, I keep getting errors. Is this file/image no longer good? Is there another way to gain root access? I'm not particularly interested in installing ROMs (not opposed to it, it's just not my main goal at this point.) I just want Root access so I can do a few minor tweaks.
Thanks to anyone who can help... this wasn't nearly this difficult the last time I did it!
Try TWRP, it auto-root's the device after flashing recovery.
Use this version until the official is updated.
arrrghhh said:
Try TWRP, it auto-root's the device after flashing recovery.
Use this version until the official is updated.
Click to expand...
Click to collapse
Thanks for the fast reply!
So, I just download that & use it as the recovery image, right? As in, I use that instead of the 6.0.1.3 file from CWM that isn't working...
Sorry... not necessarily a noob, but it's been a long time since I've fooled with any of this.
roopull said:
Thanks for the fast reply!
So, I just download that & use it as the recovery image, right? As in, I use that instead of the 6.0.1.3 file from CWM that isn't working...
Sorry... not necessarily a noob, but it's been a long time since I've fooled with any of this.
Click to expand...
Click to collapse
No worries. TWRP has directions on how to flash on their page.
http://teamw.in/project/twrp2/137
I just use the fastboot method myself. Just use that "test" image I linked earlier - or if you want official, use 2.6.3.1. I'm working to get the official updated, but it's been difficult coordinating with the TWRP team... especially since the device is now in so much limbo. I can tell you the test image works great, I'm still using it.
arrrghhh said:
No worries. TWRP has directions on how to flash on their page.
http://teamw.in/project/twrp2/137
I just use the fastboot method myself. Just use that "test" image I linked earlier - or if you want official, use 2.6.3.1. I'm working to get the official updated, but it's been difficult coordinating with the TWRP team... especially since the device is now in so much limbo. I can tell you the test image works great, I'm still using it.
Click to expand...
Click to collapse
Just sent you a tiny thank you via PayPal... I'm rooted. Let the tinkering begin. Ha!:laugh:
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
niksy+ said:
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
Click to expand...
Click to collapse
have a look at this post.
bweN diorD said:
have a look at this post.
Click to expand...
Click to collapse
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
The official BL unlock is still available as far as I know, but its not available for all phones. You basically have to try it to know if it will work.
I think the official way is reversible, it has always been said motopocalypse is not. Those facts may be wrong though. There was discussion about it in one of the threads but I don't recall exactly what was stated. If you don't care about ever locking it back, it wouldn't be relevant then.
About cm, I still have my rmhd but haven't used it other than for testing since last year. So I can't provide any current help on that, sorry.
Sent from my LG-VS980 using XDA Premium 4 mobile app
niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
Just go to the Motorola web site and look for the unlocking program and attempt it there. Here is the link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You'll have to either sign in with your Google+ ID or register an account with Motorola. It's free and then you can attempt to unlock your phone.
The XT925's are always unlockable since they are not in the US. It's Verizon that won't allow it and the XT926s are US phones.
Okay, guys, I've ran into some problems :/
Current status: bootloader loads fine, CWM (6.0.4.4, touch version) loads fine, but the system wouldn't boot after making a backup. I've tried flashing CM11 (cm-11-20140710-NIGHTLY-moto_msm8960-epinter.zip which is supposedly with the 3.0 kernel) and it still will not boot. (I've wiped /system /data and /cache before flashing) All it does is sit at the "Warning bootloader unlocked" screen and it doesn't even become warm...
What I've done: basically, followed all the steps from the thread @bweN diorD posted. Rooted with MotoChopper, unlocked bl with MotoPocalypse and flashed CWM via adb. That was all fine. Then I noticed that CWM keeps disappearing, so I said yes when it asked me if I want it to remove that script from the stock ROM . It also asked "Fix root?" at the same time to which I said yes... Since then the system will not boot. Does anyone know what's gone wrong and what can I do to fix it? Is RSD the only way now?
@bweN diorD @iBolski and everybody else... pretty please :/
*EDIT* Got my stock firmware and flashed it via RSD-lite. Had to remove that check in the xml, but that was it, it has come back to life
Now what puzzles me... Why did the system die after saying yes to "remove the recovery remover script" and "fix root"? And why was CM11 dead on boot, too? Any ideas? :/
*EDIT #2* Nevermind, I'm on CM11 now Rooted again, the bl was still unlocked, installed latest PhilZ recovery and flashed CM11 straight up without even booting stock ROM after installing recovery. All is well! CM11 is so smooth on the R HD that I came a little bit. I loved my petite DEFY+ but this is freaking awesome!
glad you got it worked out
Drivers issue
Guys, I've now got a freaking drivers issue I cannot resolve... Need assistance
I am currently on CM11, on the jbbl. Last time I flashed an sbf was at the time of my previous post in this thread, so 5 months ago. Since then, I have changed my system drive (to an SSD, yay!) and lost the drivers set-up. Back then I was on Win7 x64, now I'm on Win8.1 x64.
At the moment, I cannot get ADB to work (it lists my device, but says it's offline) and cannot get RSD Lite (it's v6.1.6) to detect the phone when in fastboot. I'm attaching a screenshot of device manager's current status. The mot composite adb interface driver is fine, but the two in other devices remain question marks.
Motorola Device Manager (2.4.5) just looks for updates for my device and then quits after finding none. No matter if the phone is connected or not. Not sure if it's incompatible with win8.1 or just normal behaviour since my phone's not on the stock rom.
Does anyone know the right steps for setting up ADB and Fastboot drivers on win8.1 for our device? MTP works fine, no problems there.
*EDIT* Tried using [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer and ADB connects now, but RSD lite still doesn't detect the phone in fastboot. The device manager list looks the same... I hate driver issues >_< And just to be clear, RSD lite does not show anything while the phone is connect as MTP with debugging enabled, too.
*EDIT 2* All fine now. Just uninstalled everything and started from scratch. Drivers that come with Moto Manager are the only requirement.
Hi everyone! I ordered the bamboo OnePlus One from a reseller online. The ad listing said that it comes with CM11s but I highly doubt that so I'm preparing in advance to flash CM11s. I've seen the Jumping from Color OS to CM11s thread here which uses the manual adb method to install CM11s but I've also seen elsewhere that you can just use the Color OS recovery and flash CM11s like any normal ROM. My question is, what's the difference between manually installing it with adb and flashing it through Color OS recovery? Do I still get OTA updates with both? And do I need to flash a new baseband with either method? All details would be highly appreciated!
Thanks guys! Excited to get my OnePlus One!
kylethelife said:
Hi everyone! I ordered the bamboo OnePlus One from a reseller online. The ad listing said that it comes with CM11s but I highly doubt that so I'm preparing in advance to flash CM11s. I've seen the Jumping from Color OS to CM11s thread here which uses the manual adb method to install CM11s but I've also seen elsewhere that you can just use the Color OS recovery and flash CM11s like any normal ROM. My question is, what's the difference between manually installing it with adb and flashing it through Color OS recovery? Do I still get OTA updates with both? And do I need to flash a new baseband with either method? All details would be highly appreciated!
Thanks guys! Excited to get my OnePlus One!
Click to expand...
Click to collapse
Flashing the ROM through a recovery will only flash the ROM, whereas using the fastboot method will flash all the other bits and pieces too. You'll still get OTA updates either way. What you should do before anything else though is unlock your bootloader, because doing so wipes the user data, so you want to get that out of the way before you start fiddling. The device probably will ship with CM11 though, not CM11S, but the differences are tiny. That's what a lot of the grey sellers do. Check out the threads in my signature, you'll probably find them very helpful.
Transmitted via Bacon
timmaaa said:
Flashing the ROM through a recovery will only flash the ROM, whereas using the fastboot method will flash all the other bits and pieces too. You'll still get OTA updates either way. What you should do before anything else though is unlock your bootloader, because doing so wipes the user data, so you want to get that out of the way before you start fiddling. The device probably will ship with CM11 though, not CM11S, but the differences are tiny. That's what a lot of the grey sellers do. Check out the threads in my signature, you'll probably find them very helpful.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks man! I guess I'll start learning about fastboot and stuff asap. I've only had experience with flashing and custom recovery since I came from a Nexus 5 and there are a lot of tools for rooting and stuff. Yeah planning to unlock the bootloader for sure.
The FAQ thread in my signature contains a couple of links to some very good adb/fastboot tutorials, it may seem daunting but it's pretty simple stuff.
Transmitted via Bacon
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Exactly which zip files are you trying to flash? What are the filenames?
Transmitted via Bacon
use a toolbox and an option to flash to stock
gfusion said:
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Click to expand...
Click to collapse
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
playya said:
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Click to expand...
Click to collapse
gfusion said:
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
Click to expand...
Click to collapse
Here's a hint. Fastboot IS how you flash a new room for the first time had you not used the tool kit you would have seen this and done it that way lol
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!
Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon