Database Info

Help: Wipe+Root

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

Help With Nandroid To New Device

So I cracked my N5 and got a new one today. Did a Nadroid via CWM on the old phone and was looking to transfer to the new and then restore. I see that it's located in /mnt/etc/etc/ but I can't tell if I'm transferring it correctly or not.
I'm doing adb push (file) to /mnt/etc/ but since it's almost a 2gb file, I can't tell if it's working or if it's crashed out.
Is what I'm doing correct? I'm hoping once the transfer is done, I can just restore in RomManager.
Thanks guys!

Minker17 said:
So I cracked my N5 and got a new one today. Did a Nadroid via CWM on the old phone and was looking to transfer to the new and then restore. I see that it's located in /mnt/etc/etc/ but I can't tell if I'm transferring it correctly or not.
I'm doing adb push (file) to /mnt/etc/ but since it's almost a 2gb file, I can't tell if it's working or if it's crashed out.
Is what I'm doing correct? I'm hoping once the transfer is done, I can just restore in RomManager.
Thanks guys!
Click to expand...
Click to collapse
First of all do not use Rom Manager as it is a buggy, unstable and crappy app. Uninstall it immediately and never use it again Flash CWM or Philz Touch CWM to make or restore a backup. Just place the nandroid you made via usb in the /clockworkmod/backup/ file and see if you can restore it in recovery.
- Edit- as @rootSU said don`t restore EFS or it will mess up you`re phone. Can you restore apps with Tit. Backup or Helium or adb?

Do NOT restore efs
Sent from my Nexus 5 using Tapatalk

rootSU said:
Do NOT restore efs
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
S**t you`re right, made a booboo here

do i need to backup/restore cache?

Minker17 said:
do i need to backup/restore cache?
Click to expand...
Click to collapse
I wouldn`t restore the backup cause the EFS files of your former and current phone are different. You will mess up your phone severely. Its best to restore your apps by other means.

So what's the best way to "clone" my broken device to the new one?

If you're using philz, you wont be backing up efs by default so restoring nandroid is fine. Can't talk for TWRP though
Sent from my Nexus 5 using Tapatalk

Minker17 said:
So what's the best way to "clone" my broken device to the new one?
Click to expand...
Click to collapse
Unless you we`re able to isolate and delete your old EFS files from the backup and replace them with your current one i wouldn`t do it. Don`t know if thats possible and i wouldn`t know how to do that myself anyway. I`d just restore the apps and its data and set it up as you want to. Maybe someone else can give you better advice but thats what i can tell you.

Backed up and restored and everything appears to be going great! Thanks guys!
Is there a main thread for Philz so I can familiarize myself?

Minker17 said:
Backed up and restored and everything appears to be going great! Thanks guys!
Is there a main thread for Philz so I can familiarize myself?
Click to expand...
Click to collapse
http://forum.xda-developers.com/goo...ouch-custom-gui-gesture-t2565174/post51634791, next time use the search function please Top right corner.

gee2012 said:
http://forum.xda-developers.com/goo...ouch-custom-gui-gesture-t2565174/post51634791, next time use the search function please Top right corner.
Click to expand...
Click to collapse
Thanks for that.
I didn't know about Philz Touch.
I am glad I can finally get the right date and time on my backups plus it adds the ROM name and version +1. :good:

dechronic said:
Thanks for that.
I didn't know about Philz Touch.
I am glad I can finally get the right date and time on my backups plus it adds the ROM name and version +1. :good:
Click to expand...
Click to collapse
Oooh that reminds me I needed to update recommended time settings. Done
Sent from my Nexus 5 using Tapatalk

rootSU said:
Oooh that reminds me I needed to update recommended time settings. Done
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
In the Time settings, I set the Time Zone for my region and Time Zone offset to +0 min and used the Qualcom Time Daemon to get the current date and time.
That is what worked for me.
There is another recommended way?

dechronic said:
In the Time settings, I set the Time Zone for my region and Time Zone offset to +0 min and used the Qualcom Time Daemon to get the current date and time.
That is what worked for me.
There is another recommended way?
Click to expand...
Click to collapse
No, that is recommended way but my thread had an older,outdated way
Sent from my Nexus 5 using Tapatalk

[Q] Can I Flash another OnePlus' TWRP backup?

Hey guys. I just got my second OnePlus after mine fell and got a new one.
I was wondering if I can flash my other oneplus' TWRP backup on this so i dont have to configure all over again.
Thank you!

badjoras said:
Hey guys. I just got my second OnePlus after mine fell and got a new one.
I was wondering if I can flash my other oneplus' TWRP backup on this so i dont have to configure all over again.
Thank you!
Click to expand...
Click to collapse
I would say no. I just remember some people doing this would and it replaced IMEI information from previous phone and could potentially screw up your new phone. What is so important that you need to restore for TWRP anyways. A fresh flash on a new phone is the best route to take my friend
We make too much of simply taken the time to restore and reset things on a new flash.

playya said:
I would say no. I just remember some people doing this would and it replaced IMEI information from previous phone and could potentially screw up your new phone. What is so important that you need to restore for TWRP anyways. A fresh flash on a new phone is the best route to take my friend
We make too much of simply taken the time to restore and reset things on a new flash.
Click to expand...
Click to collapse
HMMMMMMMM... The OPO only backs up: boot, data, system and cache. It does not backup EFS nor would i check it on the restore menu,
I guess i will give it a go, and see how it goes. already got it backed up

badjoras said:
HMMMMMMMM... The OPO only backs up: boot, data, system and cache. It does not backup EFS nor would i check it on the restore menu,
I guess i will give it a go, and see how it goes. already got it backed up
Click to expand...
Click to collapse
Its your OPO I just don't see why you would risk it but go ahead if it don't work can only be mad at yourself. Lol
Still don't see the big deal in flashing ROM and using TB to restore apps from nandroid
Sent from my A0001 using Tapatalk

playya said:
Its your OPO I just don't see why you would risk it but go ahead if it don't work can only be mad at yourself. Lol
Still don't see the big deal in flashing ROM and using TB to restore apps from nandroid
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Done it, it's all good, as expected.
Like I mentioned to you, that whole EFS problem does not exist if it does not back it up from another phone and restore it onto a new one.
Props and thanks

badjoras said:
Done it, it's all good, as expected.
Like I mentioned to you, that whole EFS problem does not exist if it does not back it up from another phone and restore it onto a new one.
Props and thanks
Click to expand...
Click to collapse
cool and yeah I know that but I just dont see the reason to take the risk at all. I see so many take shortcuts and then we have a million how do I fix this that and the third threads. Glad it worked for you

I was going to say yes even if I never tried it as nand only backs up system, boot and data which should be no problem to copy and paste to a same model phone...you tried it first by yourself so good move
Sent from my Oneplus One

Shouldn't be a problem part of restoring to stock on some other phones is flashing a twrp backup and stock recovery. It shouldn't be a problem atall

As long as your not restoring EFS your fine. I have done this many times on many different phones.

com.android.systemui has stopped

I get the following error:
Unfortunately the process com.android.systemui has stopped
The error just keeps repeating if I press OK.
What I did to get this error was:
Backup current ROM using TWRP
Flash a Lollipop ROM (that didn't work)
Restore my backup
and now I'm screwed
I've read somewhere about Italians having this issue and that it had to do with low battery level. I have now recharged my phone to 95% but still no dice And my phone is running US English (though I'm in Denmark).
I'm running CM11 M11.
Can anyone help?

Clean flash.
Transmitted via Bacon

timmaaa said:
Clean flash
Click to expand...
Click to collapse
And how would I do that if I cannot transfer zip files to my phone?
And would I be able to restore my backup afterwards?

You didn't say anything about not being able to transfer zips to your phone, but I'm assuming you mean while booted into Android because of the persistent error. TWRP 2.8.x has MTP enabled so if you connect your phone to your PC while booted into that recovery you can copy a zip across to flash. And no, you can't restore your backup afterwards, the whole point of a clean flash is that it's a clean flash, completely fresh. Plus, restoring a backup after flashing a ROM would overwrite the ROM you just flashed, making it a pointless exercise. Plus, the backup that you have is obviously corrupt and that's what's causing your problem.
In short: download a ROM zip (and gapps), flash the latest TWRP to your phone (if you don't already have it), copy the zips to your phone, perform a full wipe (system, data, cache, dalvik cache), flash the ROM + gapps, reboot and start fresh.
Transmitted via Bacon

The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.

I'm kind of thinking that it's my TWRP that has some issue. I've tried restoring 3 or 4 different backups and they all come up with the same error.
I'll update my TWRP when I get home and hopefully get a bit further...

Gamm86 said:
The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.
Click to expand...
Click to collapse
He's talking about a nandroid backup, not a TiBu backup.
Transmitted via Bacon

timmaaa said:
He's talking about a nandroid backup, not a TiBu backup
Click to expand...
Click to collapse
I know, just talking about restoring backups in general after flashing a ROM.
Hence why I said "The only backup you should be restoring..."
EDIT* misread the OP. My posts were indeed a bit out of context...

Did a clean install - no dice
Then did an install without gapps and then I get to the initial setup where I have to choose language. And then it reboots - over and over. It completely bypasses any indication that there is a SIM card in the phone.
When trying to restore my previous backups I also go straight to my home screen bypassing SIM unlock and phone unlock.
Any other suggestions?

Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471

Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Either that or this automated tool:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon

Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life

kroogar said:
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life
Click to expand...
Click to collapse
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Transmitted via Bacon

Hmm, sounds like a hardware issue to me if you can't even get passed the welcome setup without your phone rebooting... Especially after a FULL factory reset.
Does the reboot start as soon as you touch the screen? This might indicate some kind of malfunction between hardware and drivers.
Raise a ticket on the OnePlus website and request for an RMA. You might also want to file a Paypal claim to speed things up.

timmaaa said:
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Click to expand...
Click to collapse
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Okay - breakthrough: I downloaded the package from this post: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ran all 3 ONEPLUS ONE - x.bat and now it has prompted me to unlock my sim card. Got through to wifi so I have higher hopes this time around Will see how it goes...

kroogar said:
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Click to expand...
Click to collapse
Whether you know your IMEI or not isn't the point, it's whether it's still present on your device that matters. There have been cases where the IMEI simply disappears (along with your baseband) and having no signal is a consequence of that. I hope you made a backup of your EFS at some point because it's looking like this is what's happened.
Have you tried the automated tool I linked to a few posts back?
Transmitted via Bacon

timmaaa said:
Have you tried the automated tool I linked to a few posts back?
Click to expand...
Click to collapse
Se my updated previous post

kroogar said:
Se my updated previous post
Click to expand...
Click to collapse
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Transmitted via Bacon

timmaaa said:
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Click to expand...
Click to collapse
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.

kroogar said:
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.
Click to expand...
Click to collapse
Be careful, I firmly believe it's a backup that caused this problem, and you might not be so lucky next time. I'd seriously suggest just clean flashing now or you could be inviting the devil to your doorstep.
Transmitted via Bacon

Anyway to downgrade from Android 9.0

Hi all. Was curious what is the best way to downgrade from pie. I upgraded and don't like it. I have a twrp backup of 8.1 but when I restored it I just bootloop. I know Google makes it difficult to downgrade so was wondering if it can be done, preferably without losing data.

dichandcheck said:
Hi all. Was curious what is the best way to downgrade from pie. I upgraded and don't like it. I have a twrp backup of 8.1 but when I restored it I just bootloop. I know Google makes it difficult to downgrade so was wondering if it can be done, preferably without losing data.
Click to expand...
Click to collapse
I was able to downgrade by using the last Oreo factory image

Meowdib said:
I was able to downgrade by using the last Oreo factory image
Click to expand...
Click to collapse
Did you have to wipe data? Thought you couldn't use Google's images to downgrade.

dichandcheck said:
Did you have to wipe data? Thought you couldn't use Google's images to downgrade.
Click to expand...
Click to collapse
I did a full wipe, so yeah. Not sure if you can ota downgrade, plus I don't want to risk it or have any headaches. Just titanium backup and restore for me.

Meowdib said:
I did a full wipe, so yeah. Not sure if you can ota downgrade, plus I don't want to risk it or have any headaches. Just titanium backup and restore for me.
Click to expand...
Click to collapse
Thanks I'll give it a shot

Yeah. Full wipe and run the flash-all.bat from the July 8.1 factory image (or whichever image matches your TWRP backup). Then you should be able to restore from your last TWRP backup without any issue. If that doesn't work, at least you can restore from TiBu if you have it, you'll just have to set the device back up and manually set all your system settings.

Meowdib said:
I was able to downgrade by using the last Oreo factory image
Click to expand...
Click to collapse
Then you should be able to restore your 8.1 backup once you flash latest 8.1 factory image

What has happened to XDA? This thread would've never been left here for more than an hour a couple of years ago.
Sent from my Pixel 2 using Tapatalk

superchilpil said:
What has happened to XDA? This thread would've never been left here for more than an hour a couple of years ago.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I don't think it's as much an XDA problem as it is that this subforum doesn't get a whole lot of action. All around activity for the Pixel2 is pretty quiet. Its hard to say exactly why, but I'd wager it's probably due to the overall satisfaction with the device and the stock OS as is. That said, XDA activity as a whole definitely isn't quite what it used to be.