Related
Hi all.
How can I wipe my Nexus 5 so it is a plain Kit Kat 4.4.2 (like the day I received it) and just root it? it's currently in 4.4.2 and rooted, but with a lot of stuf in it too. My main concern is how to wipe once it's rooted, and how to reroot.
For those who like to read, a little more info:
I have a Nexus 5 which received 2 days ago. I come from an iPhone 5S, so... pretty newbie...
I unlocked the bootloader and rooted the device after unboxing, and have been using it since. Problems are:
1. I just found out about CWM and its capabilities, and I intend to use the backups a lot.
2. I kind of ****ed up with a couple of apps I regret installing.
3. After a backup I just did today, it asked to whether or not fix the recovery (or something like that). Selected YES, nothing happened. It then asked to fix the root... said YES and screwed it completely. I had to put SuperSu in the phone as a ZIP and manually install it again to recover my root access. It kind of looks "dirty" now, lol.
Anyways, I'd like to make a whole device backup from CWM with Kit Kat out of the box, no extra apps installed. Just rooted. Then install all my stuff, sync contacts and so on, and make another backup.
That's why I want to erase the device and have it all clean (just rooted).
Thanks!
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
rwed said:
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
Click to expand...
Click to collapse
It can, but I'd recommend you do it per the link.
jd1639 said:
It can, but I'd recommend you do it per the link.
Click to expand...
Click to collapse
Mmm. OK. And why? (Just curious at this point)
rwed said:
Mmm. OK. And why? (Just curious at this point)
Click to expand...
Click to collapse
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Click to expand...
Click to collapse
lol OK. Thanks guys.
I come from iOS after several years. Please bear that in mind.
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
rootSU said:
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh please, I know. I was just hiding my ignorance under the iOS carpet.
Will give a read to both links tomorrow. Will definitely do link1 on friday if I find the time, and will then consider either doing link2 or going the CF-Auto-Root way.
I'll let you know how this all ends.
Again, thanks!
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
rootSU said:
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
rwed said:
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
Click to expand...
Click to collapse
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
rootSU said:
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
jd1639 said:
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Click to expand...
Click to collapse
rwed said:
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
Click to expand...
Click to collapse
No to both your questions.
jd1639 said:
No to both your questions.
Click to expand...
Click to collapse
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
Not for the nexus 5. I think you're looking at cwm.
jd1639 said:
Not for the nexus 5. I think you're looking at cwm.
Click to expand...
Click to collapse
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
rwed said:
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
jd1639 said:
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
Click to expand...
Click to collapse
I'll just install your file, specially if you can't even tell what that thing I linked is. Thank you jd. :good:
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
That's the twrp manager. Different things. One is an app and one is a recovery
Sent from my Nexus 5
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
adambombz said:
This phone has had my attention for a while now, and after reading and watching videos on the phone, my biggest question is about root. If Cyanogenmod 11s isn't pre-rooted right out of the box, is there a root method/someone working on a root method and if not, how long will it be until that becomes a reality? If the phone doesn't have root, I'm afraid that I may not be able to go for this phone as I am heavily invested a number of root operations and apps that I have set up on my phone. Let me know if anyone knows anything.
Click to expand...
Click to collapse
It's not rooted out-of-the-box. Google doesn't allow this. But apparently, root will be very easy; just plug it into your computer and enter in a few command lines and you're set (so I've heard). Undoubtedly someone will make a one-click script that makes it even easier.
EDIT: Sorry for that one, was posting too fast without thinking first... Actually rooting includes unlocking bootloader and flashing the required binaries via recovery like said below my post.
Sent from my Desire X using XDA Premium 4 mobile app
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Click to expand...
Click to collapse
Really? Sweet!
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Naturally if you want to root the phone, it's only a quick USB cable plug into your computer and a few command line entries away.
Click to expand...
Click to collapse
Good read, BTW.
OnePlus One Review | Android Central
CafeKampuchia said:
Andrew Martonik at Android Central spent almost a month with the phone and had this to say about rooting in the review he released just a couple days ago.
Good read, BTW.
OnePlus One Review | Android Central
Click to expand...
Click to collapse
That's where I heard it. In any case, it'll be simple; that much was promised from the beginning.
What about SuperSU though? I'm honestly not sure how that gets installed to the right place; the only times I've rooted were with programs that did it for me.
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
dansou901 said:
It will be even easier then that. You'll just have to enable root in developer settings, that's all.
Sent from my Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh really? Absolutely ridiculous.
tiny4579 said:
I don't think the retail cm11 will have root. In order to pass android cts, they had to remove root from the release builds. Don't worry, the phone is likely either unlocked or unlockable and it can be rooted with supersu or superuser like a Nexus device. Speculation but I don't see the cm folk going with a locked down phone. Maybe someone who has cm11s should confirm if it has root.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Correct - no retail device shipping with Google CTS/GMS can have root enabled, much less the ability to right OUT OF THE BOX. It has to be done manually by the user, at their discretion.
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Chromium said:
From what I've read so far, it seems that the phone is fastboot unlocked by default (Normally you'd have to run "fastboot oem unlock"). Since that's already been taken care of, all that would need to be done to gain root is flash a recovery using "fastboot flash recovery recovery.img" (official TWRP build is available), and finally install the SuperSU zip via your newly flashed custom recovery.
Essentially the same method as a Nexus device, other than the fact that the bootloader is already unlocked so that step can be skipped.
Click to expand...
Click to collapse
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
dmo580 said:
So no way to use CM's SuperUser app huh because that's built into the OS. We'll have to use a 3rd party app like SuperSU?
Click to expand...
Click to collapse
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
cyanogenmod has been planning to separate root for years. i think they are coming up with a simple method of root. maybe just an app install?
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Cm I think opted to make root removal so they could get cts approval and install Google Apps.
Sent from my HTC One using Tapatalk
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
The Jack of Clubs said:
it doesnt come with cwm. thats a different project, by a different group. and you dont necessarily need an alternative recovery, depending on the rooting method.
Click to expand...
Click to collapse
I wonder if they're using this recovery.
https://github.com/CyanogenMod/android_bootable_recovery-cm
Simple recovery is the working title.
You are correct that custom recoveries aren't always needed for root; however, in Android 4.3 and later, the two primary root applications need to install a superuser daemon which makes rooting outside of recovery more difficult.
tiny4579 said:
You will be able to root with any existing root method with a custom recovery. I'm not sure if cm11s comes with cwm. Anyway rooting is trivial.
Click to expand...
Click to collapse
You all guys keep saying that rooting is trivial, but nobody told how to root. I believe you that it's trivial but - anyway -please tell me how to do this step by step.
I'm actually having trouble getting my 64GB production unit to boot into TWRP or have it flash and stick. fastboot says everything is fine, then rebooting into recovery produces the stock simple recovery.
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
I'm sort of at a loss - I've done this to many Nexus devices before, and the idea is the same. My bootloader is unlocked, that went without any issues.
Booting a debug boot.img from https://cyngn.com/products/oneplusone via fastboot just ends up shutting down and showing the battery charging icon.
Volume Up + Power while booting ends up with a black screen - in fact, the only way I can get into recovery is from a booted OS.
Edit: After many tries, trying different cables and unchecking the Settings -> Development -> update recovery with system updates, the TWRP flash succeeded, and the subsequent SuperSU sideload went just fine. Now I'm rooted.
Another tip regarding using Power+VolDn or Power+VolUp - things happen so slowly that if you keep holding Power, it'll actually trip a reboot before it has a chance to load. Just hold the Power button for a few seconds when booting, then let go and keep the VolUp or VolDn pressed.
Chromium said:
Well, I'm just speculating since I don't actually have the device yet. The CM rom that comes on the phone is not prerooted, nor does it have the Superuser app in it (I'm basing that off an update.zip that's posted in the dev section which doesnt seem to contain the apk). So you'd most likely have to do as I explained above. You dont necessarily have to use SuperSU though. You could probably obtain root by flashing the Superuser zip instead.
Click to expand...
Click to collapse
I just did this and it seems to have worked. TiBu just completed..
Used "Fastboot boot TWRP-2.7.1.0.zip" at ADB/Fastboot interface. It booted to TWRP. As I closed, it stated that it looks like "Your device isn't rooted, Do you want to install SuperSU?" To which I said Yes. It rebooted and I was able to open SuperSU, already on the phone, and get root. Then, opened TiBU and performed a full backup.
Archon810 said:
fastboot boot twrprecovery.img ends up hanging on the fastboot screen, basically nothing happens, but fastboot does stop responding to commands.
Click to expand...
Click to collapse
The first time I did this it hung for a while. it eventually boots into the recovery. I think it took about 2 minutes for it to finally boot into it.
Maybe that helps?
Root One+ fastboot devices hnags "waiting for device"
I amd trying to unlock bootlaoder, and install TWRP on my ONE+. I have tried both android SDK, and TOOLKIT FOR ONEPLUS FROM XDA, and I cannot get fastboot devices to recognize my One+.
What I have do so far:
My PC: windows 7 - 64bit
Installed SDK kit form developer.android.com, and installed the latest composite usb driver from Google.
Installed OnePLus toolkit and tried using that, no dice.
when I execute "fastboot devices" from my fastboot folder, my prompt hangs "waiting for device" FOREVER!!!
"ADB DEVICES" WORKS PERFECTLY, AND ECHOES MY SERIAL NUMBER BACK TO ME."
Hey guys,
I am pretty new to the rooting stuff on the Nexus.
I read the sticky threat from rootSU (http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527) and followed his description. So I installed ADB and fastboot through the "15 sec. installer" (http://forum.xda-developers.com/showthread.php?t=2588979).
So fast so good, everything went fine. But as I tried to "check" if ADB and fastboot are recognizing my device with the command "adb devices" and "fastboot devices" in cmd, I got some strange output (look at the picture).
How can it be that ADB "sees" my device and fastboot not? What I did wrong there?
(I didn't installed the drivers with the 15 sec tool; when I plugged in my device to the computer, it downloaded the drivers itself)
Any help would be very appreciated!
Follow the next step on my thread and install the naked drivers
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Blackbox421 said:
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Click to expand...
Click to collapse
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
EddyOS said:
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
Click to expand...
Click to collapse
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Blackbox421 said:
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Click to expand...
Click to collapse
@rootSU has posted some new guides on rooting Lollipop, so best read his threads in the General section
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Blackbox421 said:
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Click to expand...
Click to collapse
That's correct!
EddyOS said:
That's correct!
Click to expand...
Click to collapse
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Blackbox421 said:
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Click to expand...
Click to collapse
It's all very easy with a Nexus device
EddyOS said:
It's all very easy with a Nexus device
Click to expand...
Click to collapse
Yeah I think I got it now. I unlocked my bootloader and flashed the official 4.4.4. factory image from the google developers website. Afterwards I booted into the stock recovery and wiped data/factory reset and reboot. Everything is fine now!
Thank you for your help! Learned a lot of basic understandings.
Jnewell05 said:
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Click to expand...
Click to collapse
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
rootSU said:
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
Click to expand...
Click to collapse
Huh, I thought the methods from your thread would be only for KitKat
Blackbox421 said:
Huh, I thought the methods from your thread would be only for KitKat
Click to expand...
Click to collapse
I usualy root my Nexus by booting into a custom recovery (TWRP), flash the latest superSU.zip and any mod i want and reboot/done That way i keep my stock recovery.
I have a oneplus one that I just returned to stock using the method in this thread: http://forum.xda-developers.com/onep...stock-t2826541
Problem is that at some point, while it was rooted, I used this method to make my phone microphone work (changing the build.prop file): https://forums.oneplus.net/threads/f...-issue.284449/
If I had remembered that I'd done that, I might have just left the phone alone. So, now that I'm back to stock and unrooted, my microphone doesn't work and I can't use the above method to make it so. Is there a solution out there I can use without going back to root?
My exact problem with the mic is that when I talk into the phone, the person on the other end can't hear me but I can hear myself (echo) in my earpiece. I can hear the person on the other end fine. If I switch to speaker phone I still have the same issue. Any help would be appreciated.
You'll need to go root again. Lucky this isn't too hard especially if you maintained a custom recovery. If not, then you will have to use adb. Or bacon root toolkit (the easy way).
Sent from my A0001 using Tapatalk
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
You can use KingRoot to root without custom recovery. After changing the values you can then unroot it to get future OTA updates
anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk
Elius2676 said:
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I got Cyanogen Recovery. Options are "reboot system now", "Apply update", "factory reset", and "advanced".
So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.
anonymous93 said:
So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.
Click to expand...
Click to collapse
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk
Elius2676 said:
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?
anonymous93 said:
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?
Click to expand...
Click to collapse
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk
Elius2676 said:
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yes and no. Turns out I was actually able to boot my phone into fastboot mode. So I did that, used the baconroot toolkit option of "flash stock + unroot" and I was back to the start. My device now has an unlocked bootloader, but I think I have issues with the tamper bit. When I get my device info the "Device tampered" is set to "false" and the "device unlocked" is set to "true". I know they should both be true, but I can't for the life of me figure out how to use the zip file to change the tamper bit. I did it before, but I'm just not figuring it out this time. I hate doing this stuff.
I think once the tamper bit is correct I should be able to go back to baconroot to root and reinstall the custom recovery.
Update: I finally figured this out, now rooting with bacon root, hoping it works.
I'm all set, now to make the adjustments so my microphone works. Thanks to everyone that helped!
So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.
anonymous93 said:
So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.
Click to expand...
Click to collapse
So sounds like you just wiped everything and your phone is back to stock now, but I'm getting the impression you still have a custom recovery or modified system partition and the OTA updates don't like that. So yes, you'll need to flash updates in your recovery. It's not as bad as it sounds.
And about Android versions available to you, the stock COS (which might actually say "CM..." when you check your Android version in "about phone" in settings - confusing, I know) can normally receive the OTA updates (except in the cases mentioned above) or you can get the official updates online in zip form and flash them yourself (even with the stock recovery -which I'm pretty sure you have still, unless one of your methods to fix the phone installed a custom one like TWRP or CWM). The other ROM/OS options you have are about as plentiful as the stars in the heavens (since android is open source). I personally like to stick with CM especially since they do what they do very well and they have a particular interest in there OnePlus One. They just released CM 14 nightlies (which basically means it's the latest version of the OS, bugs and all, built every day). Though, to be honest, this CM 14 nightly is ridiculously stable for a freshly released nightly. At this point, though, cyanogen hasn't implemented a fair number of their customizations that are in their previous versions. So if you want the best complete CM experience right now, go with CM 13.
And to answer your question, updates like the ones that are OTA, don't wipe your data or storage. However, if you switch from COS to CM, you'll have to clean install and that will lose your data at the least (your internal storage can usually be kept between ROMs if you've got a custom recovery).
Sorry, in throwing a lot at you right now. Probably just created more questions than answers...
Sent from my A0001 using Tapatalk
Thanks for your help and the explanations. When you talk about COS vs. CM is that Cyanogen OS vs. Cyanogen Mod?
I was able to root and I have TWRP installed. In about phone it says "Cyanogen OS version" is "12.1-yog4pas1n0". That's the Cyanogen OS correct?
Where do I go to download the update for 13 (whatever matches what I already have) and is there a guide for doing that? I'm reading about updating to 13 and everything I see (so far) states that the update has to happen with stock recovery. Is there an option to run the update with TWRP?
Wait a minute... If I unroot but keep the bootloader unlocked then it won't wipe my phone and I'll be able to take the ota updates right? What about the change I made to the build.prop file for my phones microphone? Will that get wiped if I unroot? That's the big question.
Nevermind about unrooting. After some searches it seems that a full unroot would require a rest which would delete the mod I made for the microphone. I found that supersu can "unroot", but it's not actually a fill unroot which means that I still probably wouldn't be able to do the ota updates.
Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk
Elius2676 said:
Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?
anonymous93 said:
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?
Click to expand...
Click to collapse
A backup in TWRP (or nandroid backup) is like a perfect picture of what you phone was running just before you booted it into recovery. So when you restore one of them, it is like the phone steps back in time to when you made the backup, restoring the system (read: OS), data (read: apps), and cache.
In other words, you do a backup so that you always have something you can restore if you break your phone/have boot loops or what have you when flashing new ROMs.
If you go from COS to CM, it will require a clean install which means you will need to setup your phone the way you like it again. That being said, there is an app called Titanium backup that doesn't work the same as a nandroid, but can backup your apps and data and is capable of restoring them from one ROM to the next. It's not always perfect, but it can do a lot.
I personally have just chosen to embrace the chance of needing to start fresh every once in a while. I use Nova launcher and I have a Kustom LWP, both of which I made backups of in their respective app settings. I save those backups and whatever else I want to internal storage and I just don't wipe that partition in TWRP. To be safe, I also keep backups in the cloud. Everything else I just download again from the play store and setup the way I like.
Sent from my A0001 using Tapatalk
Well, its looking more and more like I might go to cm. Once I do that will I still have to wipe my phone to flash updates? Or will I still have to do that for updates every once in a while?
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
Diesel_Jeremiah said:
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
TWRP actually just came out of beta with 12/12 Walleye(12/14 Taimen) build, hopefully there will be some custom roms soon... You can use the Skipsoft Android toolkit to root, unlock, flash twrp etc. Or do it manually following guides here on XDA under development section https://forum.xda-developers.com/pixel-2/development, ADB has been updated so make sure to have the latest platform tools.
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
bland.life said:
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
Click to expand...
Click to collapse
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
Click to expand...
Click to collapse
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh..so the android system error always happens? Ok..it does not seem to affect anything.
I used the Skipsoft package, which does all the things. Couple snags, it only wanted to accept the beta of magisk.
I'm thinking I got it all right now. I will report back if I find a problem
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So rooting your Pixel 2 will invariably trigger this error message on boot, for any user?
Are there other undesirable side effects to rooting your Pixel 2 at the moment?
Thanks