Question Those who run ProtonAOSP - Google Pixel 6

You don't have to root your phone to run ProtonAOSP right?
Also, is there a way to back up your data on the stock ROM before flashing ProtonAOSP and restore it afterwards, or do you have to manually reinstall everything afterwards?

As far as my understanding goes, unless you manually backup your phone (plug into a PC and back up files/photos) you're SOL. Proton somehow utilizes the same type of browser-based installation that Google does for factory restoring. Root isn't needed, but you also lose a lot of Google specific features. Ymmv, but looking through what it does/doesn't offer turned me off from it.

Related

Updating to official GB and retaining data?

Kind of new to the technical part of android here.
I have an Atrix running 4.1.8.3 with the following:
Rooted
Enabled Sideloading
SD Speed Hack
I have no other major system mods (no webtop mod, prom's, etc).
Here's my problem:
I don't want to lose my data/brick my phone.
How can I make a complete backup of every last thing on my phone? (Camera images, messages, ringtones, etc).
I have Titanium Backup installed that backs up apps, but is there a way to make sort of a "recovery image" or a mirror backup of my entire phone that I can flash?
Am I better off unlocking the BL first, and then flashing the sbf? (I know that this involves a factory reset in the process).
Or should I just use the OTA? My root, sideloading, and sd hack shouldn't interfere with the update, right?
Can I use the preinstall method to root my phone for GB, even though I'm rooted already? (Used gladroot)
I don't intend to jump into the custom ROM wagon just as yet, mainly because my job leaves me with no extra time to sit down and do it, restore my data, etc.
Today, I'm off though
Sorry for my noobishness, atleast I didn't post this in the development section
Thanks!

A noob's (i.e. Me) guide to rooting the i717 and flashing a new ROM

So, after much research and trepidation, I flashed my first ROM to my i717 last week. Then I decided I didn't like that ROM and flashed another an hour later. So far it's been stable and speedy. I'm very happy. Thanks to XDA-Developers, Google, the Internet, and everyone who made this possible.
So, now, here's my simplified guide to doing what I did. This should NOT be taken as gospel. Please read as much as you can first. But, in an effort to give back, I thought a simple, step by step guide (or, more like links to the guides I found helpful) would be useful to someone. Are we sitting comfortably? Then let us begin.
1. Go here - http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/ - and root your phone. It will also install ClockworkMod Recovery. Both of these need to be done before you can flash a new ROM.
NOTE: I hear that TWRP is the preferred recovery app. I've tried it and it's very nice. It just so happens that I had ClockworkMod installed when I actually decided to flash a ROM. But use whatever you like.
2. Go to the Play Store and buy Titanium Backup Pro. Well, actually, download the free version then buy the Pro key. There are other backup methods, but I like this one.
3. Backup EVERYTHING. You might never restore a particular app, but best to have it and not need it than need it and not have it. I like to use the Google Drive option in Titanium to push by backup off my phone. But you can just hook it up to your PC and copy the backup folder from your SD card to your PC. This is just in case something REALLY bad happens. Best to have an off-phone backup.
4. Find a nice ROM to settle down with. I'm using Revolt (http://forum.xda-developers.com/showthread.php?t=2288566&highlight=revolt) but do your research and find one you like. If you decide to go with something built off Android 4.2 or 4.3 then you'll lose the Samsung Touchwiz stuff (fancy SPen features, etc.), but to me that wasn't as big a deal as I though.
NOTE: Make sure you know if the ROM need an additional Google Apps package. Sometimes they're listed with the ROM, sometimes not. Read and make sure or you could lose a lot of phone features or it may not even boot. Again, READING IS YOUR FRIEND.
5. Save the ROM (and GApps file if needed) to your phone's SD card (internal or external doesn't matter)
6. Boot into recovery (Hold Vol UP+Vol DOWN then press PWR and hold all 3 until you feel a vibration, then let go of PWR). When ClockworkMod (Or TWRP) comes up, RUN A BACKUP!
7. Read 6. Make sure you actually do it. I'll know.
8. Once you're sure you have your Titanium and ClockworkMod backups, follow the instructions for installing the ROM. Usually this involves (from ClockworkMod or TWRP):
a. Factory Reset
b. Wipe Cache (this is usually a part of Factory Reset, but doesn't hurt to do again)
c. Wipe Dalvik Cache (see cyanogen's response here for what this does - http://forum.xda-developers.com/showthread.php?t=519495)
d. Flash new ROM
e, Flash Google Apps (you can also wipe cache and Dalvik cache between d and e)
9. Now the moment of truth. Reboot. Wait. This can take some time, so don't fret if it seems to be taking too long. I'd say if it's over 15 minutes then you might need to worry, but chill before then)
10. When it does boot, you'll basically have a fresh, new phone. You'll need to enter your Google account and follow all the usual stuff you did when you first got your phone.
11. Leave your phone alone now. You can click around, but don't install anything new just yet. I've seen many a post about letting things settle. So, maybe, poke around for 15-30 minutes just to see but don't change anything. Then Reboot
12. Now reinstall Titanium. You can start reinstalling your apps. DON'T reinstall standard apps or they could break (e.g. email app or its data) as the new ROM might not support the old version of the app. My rule of thumb is don't restore any data I can get back from my online accounts (Email, FB, G+, Keep, etc.). All of your pics and that should be on your SD card and should not need to be restored.
13. That's it. If you enabled a scheduled backup in Titanium you might want to disable it for a while to make sure you like what you have. That way, you can go back if you don't like it.
Hopefully that helps someone. Please forgive any mistakes or omissions and if anyone with more experience wants to give it a once over I'd appreciate it.
Thanks and good luck.
Sorry guy, but on step one there is a very high probability of someone bricking their phone.
Why? Because it has happened about 100 times over the past two years from people using that site/method. If you flash the wrong kernel you kill your precious.
You should edit your step to say in the strongest terms triple check your operating system and get the correct kernel.
And step one is unnecessary because all roms here are already rooted.
1. Flash TWRP using pc and Odin.
2. Download new rom.
3. Boot into recovery.
4. Wipe cache, system, data.
5. Flash rom. Boot and wait 10 minutes.
6. Check settings for networks.
7. Optional modem flash.
Only wipe that's needed is a factory reset within recovery. That wipes /cache too. The dalvik cache resides on the data partition and is thusly wiped as well.
The Rom will have a format /system line within the updater script.
And within titanium backup don't backup or restore system settings (anything in the list that's red.)
And as said rooting first isn't needed unless you've been using stock for awhile and have apps you'd like to backup first... the easiest way to root is simply flash the latest twrp with Odin.. boot into recovery... then when you go to reboot the system it'll see that you're not rooted and ask if you'd like to do so.
Thanks for the feedback. Like I hope I stressed, this is the method that worked for me.
I guess I have the terms mixed up in 1. I'm saying to install ClockworkMod (or TWRP) and root your phone. I want to root it here because I want Titanium installed before I change ROMS so I can go back to exactly how everything was before modding if I want. Does that make sense?
Also, can you tell me what's specifically wrong with the site I link in Step 1? I was on ICS at the time I think. Does it brick if you do it on JB?
I'll change the step to say to go here instead - http://teamw.in/project/twrp2/96
Is that better?
Also, can you explain your cache wipe suggestions. I've seen the official instructions say to Reset, then Wipe Cache, then Wipe Dalvik. I know the last 2 are included in the first, but why are we explicitly asked to do them again? Why do you think we don't?
My thinking behind adding it here is that it does no harm and if some devs think that not doing it will cause problems then why not include it to be extra safe.
If you wanted it back to the way it was before modding anything then you could flash a custom recovery and do a nandroid backup before rooting at all.
Titanium backup needs root. If you want your app data after flashing a rom then that's when it's needed.
As far as extra wiping... putting your arms over your head spinning in a circle while chanting a manta does no harm either and is just as effective.
When you flash as often as I do... you wanna streamline the process. Extra anything is just that... Extra... and is just a waste of time
His first step is correct. No one that I know has bricked their phone using those directions because that link does not install any kernels. And it never did. It works for all versions of android. Even after all this time there is so much misinformation given.
Studacris's help is as good as gold though. He has put me in my place in the past.
Thanks Everyone.

[Q] What should I Back Up?

So now that I have root on my phone, using Titanium Backup, WHAT should I backup? I mean... my phone doesn't have inherent instability now does it?
Or does the instability (possibly) come from xposed modules I install?
Are there sets of steps I should take before installing new root apps?
Thanks!
-Matt
Root details:
Verizon S4 (sch-i545)
Stock ROM (4.4.2)
Back up anything you would miss loosing if something happed. For me thats nothing, for others thats maybe a particular apk version, or an apps data.
What do you need to do before installing root apps? Root apps are just programs that require admin rights. Nothing magic, do whatever that app might need, which is probably nothing.
It is generally good to have a full system backup from your recovery... For when you try to do _______ and **** it up.
scryan said:
Back up anything you would miss loosing if something happed. For me thats nothing, for others thats maybe a particular apk version, or an apps data.
What do you need to do before installing root apps? Root apps are just programs that require admin rights. Nothing magic, do whatever that app might need, which is probably nothing.
It is generally good to have a full system backup from your recovery... For when you try to do _______ and **** it up.
Click to expand...
Click to collapse
Okay great! I already backed up any folders (pictures, pdfs from camsacanner, roms) to my computer via usb before rooting... so...
So when people are talking about TWRP/CWmod recovery... how is it different from stock recovery?
So basically a custom recovery is an all in one answer that allows you to back up EVERYTHING but also allows you to back up EVERYTHING in one blow?
blueman189 said:
Okay great! I already backed up any folders (pictures, pdfs from camsacanner, roms) to my computer via usb before rooting... so...
So when people are talking about TWRP/CWmod recovery... how is it different from stock recovery?
So basically a custom recovery is an all in one answer that allows you to back up EVERYTHING but also allows you to back up EVERYTHING in one blow?
Click to expand...
Click to collapse
Stock recovery will let you do a factory wipe to basically clear data and reset your system to recover from something that messes up your install and makes your phone unusable.
Custom recoveries allow you to flash unofficial files, as well as take basically a snapshot of your system. With a custom recovery you can make a backup of your phone, and almost no matter what happens, you can flash that backup and it will be like nothing happened.
So when you try and run some xposed module that isn't written well, and now makes your phone crash every 2 minutes, you can boot to recovery and flash back to the backup you took right before you installed that module, and it will be like you never did it.
The recovery images are kinda large, as its all your data/apps/the OS all in one. Many custom recoveries will have a file manager that will allow you to deal with files individually, but most typically the point is taking a snapshot of your current system so you can go back to it. I make backups before trying a new rom, that way if after a little bit I am not happy I just flash back and its like I never changed anything.

Dealing with an encrypted android phone

I have a OnePlus 3 and I was thinking of encrypting it for additional security & privacy reasons. But since I flash various ROM level mods / use xposed modules on my phone, I was wondering about the negative consequences I have to face after encrypting an android phone.
I have a few doubts which need to be cleared.
1) Since my android phone would be encrypted, would I absolutely not be able to flash any new files/make nandroid backup from the recovery?
2) If 1) is true, which means, let's say I install an xposed module which causes a bootloop. Now I would have no way to disable all the active xposed modules from recovery since the files are encrypted, which means I would have to restore everything from scratch?
3) Is there absolutely no known way of decrypting android/access files unencrypted from recovery if we know the master PIN/password?
Can somebody who has dealt/dealing with an encrypted android phone please answer these questions? Thanks.
Deleted
Hi, thanks for your reply.
Just Passing By said:
1. When you access recovery on an encrypted phone, you have to decrypt your phone. After that, your recovery can do anything it normally could do. This would of course include flashing ROMs, zip files, and making nandroid backups.
.
Click to expand...
Click to collapse
2 things to say about that.
1)Decrypting just to flash files is a huge problem. TWRP/CWM should have a feature when it asks for the master PIN/password on the recovery, then after I enter it, it should decrypt the data on the fly and then mount the system and data partitions unencrypted so that I can flash files without going though all the decryption process.
2)Correct me if I'm wrong, but all android decryption processes I read online require wiping all data/doing a factory reset. That's again a huge problem. Why? In case I flash a mod/install a xposed module which causes a bootloop, I would have no way to decrypt my data, even if I have my master password. Which would mean I would lose all my files which I haven't backed up.
Problems like these could be avoided if TWRP provided permanent decryption/on the fly decryption using the master PIN. Comparing this with veracrypt on windows for e.g. , let's say my windows is encrypted with veracrypt and a hardware failure occurs at some point in the future & windows refuses to boot, but I'm able to load a live ISO. In this case, veracrypt offers a rescue ISO which I could use to decrypt the data without losing all my files after I enter the master PIN. So in this case, I can have security of encryption & also the convenience of decrypting it without losing all my files with the master password in case my main OS refuses to boot.
If I can't decrypt android from the recovery using the master PIN, that would mean in any case my android refuses to boot, I have lost all my files.
3. I'm assume you meant to say "... If we don't know the master PIN/Password?" And the answer to that is yes. If you can't decrypt your phone, you'll lose everything in it, so making periodic backups is a must. Otherwise, there'd be no point if you could just decrypt things right?
Click to expand...
Click to collapse
No, I did not say that wrong, sorry if I wasn't clear enough on my first post. I just wanted to know if there was a way to permanently decrypt android from recovery using the master PIN so that i would be able to recover my files to a USB in case my android refuses to boot.
Deleted

Can I Backup a locked phone?

Hey Every One
I have a Galaxy A 21s on wich I broke the Screen.
Now a few Yeas later I replaced the LCD but forgot my Password.
-Usb Debuging is Disabled.
-No Custom ROM installed, so i cant delete the Password File.
-oem Unlock is alsoe disabled.
-Find my Phone is deactivated and Google recovery also.
I have now tried a lot of ways to get to my Data but nothing worked so far.
My last resorts are trying to get a full Backup of the Phone and use it in an Android Emulator to Brutforce my Passcode.
or install Custom Recovery, restor my Backup and delete the Password File or get in with adb.
Hence my question woud it be possible to Make a Complet Backup, wit example Odin and use it in an Emulator or restore it on a Rooted Phone?
If any one knows further ways of getting back my Data im open to try things out.
Thanks for the Help.
Edit: I found that i could use adb Sideload to install Apps from stock Recovery. The only Problem i woud need to spoof the signature of the .zip im trying to instal, maybe any one knows a way wit that method?
If you can't access it you can't copy anything.
A data recovery specialist that works with Samsung's might be able to.
I never set a lock on mobile phones or PC bios because you are the one most likely to get locked out! Security is physical, one will pay with blood for trying to steal my phone.
I redundantly back up all critical data often and keep backups in separate locations. Never encrypt backup drives. Hdds are best, flash for quick "dirty" backups. I use my 1tb SD card as a data drive then back that up. Also use two .5th OTG flashsticks.
Phone is always cased. Don't put yourself in the predicament again. Think it through and tie up the loose ends before they trip you. I've lost entire, irreplaceable databases before, not fun.
There's no such thing as overkill when it comes to backing up critical data. Digital data is otherwise very fragile.
Hi, I am in the same situation as you. I forgot the pattern but I really need to recover some data before restoring the phone. With the stock recovery were you able to remove any protection via adb sideload? Thanks

Categories

Resources