Hey all, hopefully not too lame of a question...
But, I want to test some of the Treble Roms, but also would like to return to current configuration of my Mate SE, if desired.
Have the unlock code, adb etc etc.
So I guess the question is, if I wanted to get back to my configuration (same apps removed, installed, etc), which partitions should I back up? I'd like to use 'adb backup' instead of twrp, and then flash the image(s) with fastboot to return.
I've already flashed the open kirin Lineage, and used the oem system.img to go back, but then had to reconfigure everything of course. Do I need to backup more than 'User' (and Data) partition to get back without all the reconfiguration hassle?
Thanks!
Related
Hey lads!
I am trying to root my HTC One M8, so I can get a finer options for sounds (and other advantages, aswell). I found this post https://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748 about rooting an M8 with android 6.0. I'm writing this post, because I don't want to screw it up, so it seemed better to ask for help, before I do something stupid and brick my phone. I tried searching the forum, but after opening like 10 tabs, I lost my way. (I am using Windows 10, legit)
So, this is what I did:
1) Downloaded the Android Studio.
2) Via the studio, I downloaded the 6.0 platform.
3) And here is my first block: tried to install ADB, via Universal Naked Driver: I downloaded the ZIP, unpacked it, and while my phone was connected, tried to update its driver via the Device Manager. I got a message that it's up to date, and even tho I picked the 'I have disk' option, it wouldn't do anything. Now, I downloaded MiniADB v_1031, and when I ran the cmd from here, I could see my device with adb devicelist. I also installed HTC Sync, and used the driver installer from adbdriver.com, and it showed that I have the needed driver.
4) From the folder where I have unpacked miniadb, was able to run adb devicelist, and adb bootloader reboot aswell. But from that point, even tho I enabled developer options in my phone, and USB debugging aswell, my PC can't see the phone, only if I reboot to normal mode. When I am in fastboot USB, adb devices just says 'list of devices' and a blank line under it.
5) Tried to unlock the bootloader, and I got my identifier token. I am good to go then, I have every driver what I need for continuing from here?
5)b) Edit: Seems like I managed to unlock the bootloader.
---------
So if I understand it well:
From now on:
---------
6) Download the EU version of TWRP 3.0 from here (I am from the EU)
7) Use the cmd 'fastboot flash recovery twrp.img'
8) The site mention a key-combo to prevent the phone to go back to basic recovery, do I need this?
9) Do a backup via TWRP (is it going to be a simple option in the recovery? How big SD card do I need? Atm, I have 12 Gb one, gonna buy a 128 one in like 1-2 month)
10) Copy the SU.zip to my SD card and use a flash option in the recovery?
Sorry for any dumb question, I'm kinda scared bricking my phone, but at the same time, I would like to get the advantages of rooting.
So anyway, did I miss out on any step, screwed up anywhere, or smth like this?
Any help is much appreciated!
My comments to your steps/questions:
4 and 5) adb and fastboot are two different, but related interfaces. Don't feel bad, it's a common mistake to mix up the two (adb and fastboot). You'll really only need fastboot for rooting the phone. The step to "adb reboot bootloader" in the TWRP install instructions can alternately be done without that command, using the button combo to get to bootloader. But I think you must have figured that out by now, if you managed to unlock the bootloader.
In summary,
adb: needs USB debugging on in phone settings, only works when phone is booted in OS or alternately when booted into TWRP (last part obviously doesn't help, if you haven't installed TWRP yet).
fastboot: only works in bootloader-fastboot mode (will not work in OS or TWRP), does not need USB debugging on in phone settings.
6) The options are for download mirror locations (US vs. Europe - literally just where the download's server location is located), and do not specifically refer to different TWRP versions. The same TWRP version works for both US and Euro M8 models. What you downloaded is fine, so my comment is just FYI.
8) No, you shouldn't need this. I believe this comment refers to newer devices, and not specifically to the M8. I literally think the TWRP team has copy/pasted this statement to instructions for every device on their website, whether it applies or not.
9) Yes, this is a clear option once booted into TWRP recovery. Literally, on the TWRP main screen, you will see a big button labeled BACKUP. Tap it, and select system (ROM or OS) and boot.img, and also backup data if you like. The backup of system and boot.img will take around 2 GB. The backup of your user data might be much more, depending on your apps, etc. Although, if you just unlocked the bootloader, the phone should have been wiped, so you may not have much (if any) user data to backup.
10) While SuperSU 2.76 (mentioned in the thread you linked) should work fine, I would suggest using the latest stable version 2.79 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Just put it on the phone, boot into TWRP, select INSTALL, select SuperSU 2.79.
---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------
Rivyan said:
Sorry for any dumb question, I'm kinda scared bricking my phone, but at the same time, I would like to get the advantages of rooting.
Click to expand...
Click to collapse
Don't worry, you won't brick the phone (permanent damage) by unlocking the bootloader, custom recovery, root, etc.
Anything you do is recoverable/reversible, even if something goes wrong (especially if you make a TWRP backup of your current stock ROM before rooting).
Hi I want to format my drive and start with a completely clean system. The problem is I am not too good at using adb and fastboot.
So I used my wife's old sgs5 as a test device. I even had an SD card in there as backup. Somehow I dormated the dam SD card too.
I thought that if you sideload it would install it for you just like a twrp flash bit I can't seem to her it to work. Drivers are installed and it is detecting my device. I'm not sure what I'm doing wrong.
If someone could give me a step by step for setting this up I would forever be grateful.
I don't care about the s5 it's just a test device . But I want to root my.pixel
Thanks
First thing, the s5 is WAAAAYYY different than our pixel. That goes for partitions, flashing, adb/fastboot commands, etx. You could test and play with it all you want but as soon as you hop to the pixel it's a whole different game.
So your end goal is root on the stock rom?
If so you'll have to unlock the bootloader.
When you unlock the bootloader the device will factory reset (that takes care of your "clean" part).
After unlocking the bootloader, reboot to bootloader, fastboot boot twrp, install latest magisk, reboot.
My goal is to create a system backup (including Android OS) of my Galaxy S9 (SM-G960F), just like I can do on my PC using Acronis True Image or other similar programs, because now I have Pie but Android 10 is available, and I want to be able to roll back in case of bugs.
I've found out one of the best ways of doing this is using TWRP. Flashing a custom recovery means making changes (editing recovery partition), but some say TWRP can be run even without being installed, and that was my intent. I tried on my old Galaxy S5 mini and I could successfully run TWRP without rewriting recovery partition.
However, it turned out that bootloader unlocking is needed. No problem, I thought: I'll unlock it, backup system, and lock it again. But when I tried to switch the 'OEM unlock' item, a dialog appeared saying that my device would have been formatted and Samsung Knox services would stop working.
I was wondering:
- if I do enable OEM unlock and erase data, setting OEM unlock to off would reactivate Knox services?
- is there a way to actually unlock bootloader without erasing data?
- is there any hidden method to boot TWRP without unlocking bootloader?
- is there any better way to backup whole system and data?
I may have already partially answered the last question: using adb backup I backup as much data as possible, and by downloading OS image from Sammobile.com I have an OS backup. Can it work? If I decide to "restore" that kind of backup there would be any kind of data that would be lost during this particular roll back procedure?
Thanks in advance.
If my English is odd or incorrect, that's because it isn't my primary language. I'm from Italy - land of Pizza and Coronavirus.
I am on OOS12 rooted with twrp. I elected to do the OTA update method where you disable magisk modules, go into magisk and uninstall images, install the update, and then restore images and reboot. I have no idea why, but now my phone is in Qualcomm Crashdump mode. I have a lot of valuable things on my internal storage that I need to save or backup somehow.
Now, I can fastboot boot twrp.img and have that work, but in order to decrypt my userdata, it's asking for a pin, and I don't believe my pin is working. I'm wondering if this issue also affects what the pin code would be.
Is there any way at all to retrieve my data? Never would I expect an OTA to cause this and hence, there was no need to backup anything beforehand. Also, isn't the other a/b partition supposed to be available as a failsafe? My other partition should be just fine, although I have a feeling that assumption is because I don't understand the full gravity of this Qualcomm Crashdump mode.
bulletbling said:
As stated, there will be a reward for someone who has a solution that works.
I am on OOS12 rooted with twrp. I elected to do the OTA update method where you disable magisk modules, go into magisk and uninstall images, install the update, and then restore images and reboot. I have no idea why, but now my phone is in Qualcomm Crashdump mode. I have a lot of valuable things on my internal storage that I need to save or backup somehow.
Now, I can fastboot boot twrp.img and have that work, but in order to decrypt my userdata, it's asking for a pin, and I don't believe my pin is working. I'm wondering if this issue also affects what the pin code would be.
Is there any way at all to retrieve my data? Never would I expect an OTA to cause this and hence, there was no need to backup anything beforehand. Also, isn't the other a/b partition supposed to be available as a failsafe? My other partition should be just fine, although I have a feeling that assumption is because I don't understand the full gravity of this Qualcomm Crashdump mode.
Click to expand...
Click to collapse
As a follow-up, I am wondering if the latest twrp-3.7.0_11-0 I am temporarily booting is not allowing my pin to work correctly because it doesn't support decryption / breaks my pin for OOS 12.1 C.69, which is what the OTA wanted to update to.
---UPDATE---
I downloaded the latest Stock Firmware and extracted the payload.bin and manually flashed everything from this thread below.
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And now...instead of it going to the Qualcomm crashdump, it goes right to fastboot. I don't know if this is progress, but at least with boot slot b it's currently on, there is no more crashdump occurring. The problem now is that it still wont boot with a fresh manual install of all stock images in the payload.bin. I'm wondering if this is related to my internal storage, but that wouldn't make any sense. TWRP is still telling me my pin is incorrect, even though it's correct.
---UPDATE 2---
I had tried everything I could think of and ended up resorting to the MSM tool. I don't have any recent backups but have some things saved. It appears that no one responded meaning this is likely impossible, short of a forensics lab that can crack encryption like this.
Sadly my phone is corrupt and cant start anymore ... I want to use Newsflasher to rescue my Phone.
Before I want to use TWRP to make a backup. But I cannot enter TWRP.
As far as I understood TWRP cannot be installed on XZ2 compact, but it can be temporarily flashed (as I of course did to get my LineageOS Android 11).
But now when I flash it TWRP asks for a Password.
I just have my regular Screen Unlock Password - but if I type it in it tells me PASSWORD FAILED.
How can that be? Which other Password could it be? I dont know any ...
Obviously I would just remove the screen lock in Android. But it's corrupt x(
I want to do this before I have to do the wipe with Newflasher
If I ignore data encryption then it tells me when booting system that I have no OS installed ...
So then I will never be able to get my data back because encryption with password is still active and I cannot boot to turn it off?
And TWRP is bugged so it does not accept my real password? (How can that be omg ...)
Nothing can done now u have to flash flash a fastboot rom on your device without backup
That is
the_arxyn said:
Nothing can done now u have to flash flash a fastboot rom on your device without backup
Click to expand...
Click to collapse
That is what I was already thinking but yes let it be :/
I will use the old file that I used 2 years ago and also worked when I had to do the same.
For a strange reason it does not work when executing in the original created folder (by Xperifirm), but only if I push it on a external Hard Drive?
Otherwise it will tell FINISHED but it just took 3 seconds, which it will also do if it is played in any other folder ...
Anyways it asked me for a weird reason if I want to keep my userdata. I was thinking that there is no way to install a new OS but still keep the old data. I did it but then at the end of the Flashing it told the Sync did not work. I still booted up and it tells that it cant load the Android. So I dont know if this happened because I either left the user data intact or because that sync at the end did not work.
I'm just now scared to erase it when trying again, just in case that indeed I could safe my data.
So what is the story behind that *Erase User data Y / N*. Can I indeed keep my files this way?