Hey,
I have 4 (four) Xperia Z3 compact.
One is now rooted with fw 2.93 and right now I'm in the process of updating it to the latest 5.77 fw with pre-root. If (hopefully) successfully I want to clean up the system a bit (remove all that sony adware, etc.).
Ofc I want to have this also on the other 3 phones, but doing it four times in total seems to much work. So I was wondering:
Once I have setup one phone to my liking, can't I just get an image of that phone (with system, apps, etc) and flash it on my other z3 compact?
How would I do that?
TIA
Anyone?
faxd said:
Anyone?
Click to expand...
Click to collapse
Hi there the only way i have found to do this is to use TWRP tools to make a backup of your device and then pull the backup off using adb tools, once you have pulled the backup off the phone you are cloning, you will need to make a backup on your new device and then pull that too, you will see that the backups are help under the serial number of the phone you are transferring, simple remove the backup from the new device and copy the files from the old back up to the new back up with the new devices serial number. If you complete this successfully you will be able to load the backup onto your new device fire up TWRP and restore.. Boom you done!
Related
I just bought a new Z3 compact phone and looking on how to install gmail 5.0 because Inbox is not what i need. I read that you can't unlock bootloader or root without losing DRM (or am i wrong?) Is it possible to maybe backup everything (including drm), root the device and whenever time comes and 5.0 is introduced officially go back to the backup (so you have the drm again).
Or another way to just install gmail 5.0
wardpeet said:
I just bought a new Z3 compact phone and looking on how to install gmail 5.0 because Inbox is not what i need. I read that you can't unlock bootloader or root without losing DRM (or am i wrong?) Is it possible to maybe backup everything (including drm), root the device and whenever time comes and 5.0 is introduced officially go back to the backup (so you have the drm again).
Or another way to just install gmail 5.0
Click to expand...
Click to collapse
Why would you require root to install an App? Get it, install it. Done.
sxtester said:
Why would you require root to install an App? Get it, install it. Done.
Click to expand...
Click to collapse
Not sure because the guide for gmail 5.0 tells me to rename some files in system/app which I can't because of no write access and mounting doesn't work due permissions.
Guide
I have googled this but all the solution I find are either to factory reset or re-flash your firmware. I'd really like to avoid that.
I have a Z3 compact, rooted and then flashed with the latest firmware I think its the .77 at the end.
Xposed framework with a few mods running beautifully on it.
The last 3 changes I did before the phone got stuck in the boot loop:
- updated minmin xposed module from 1.8.1 to 1.9
- updated another module but forgot its name
- fiddled with the settings of this app: https://play.google.com/store/apps/details?id=org.namelessrom.devicecontrol
I'm pretty sure its the latter as it sets certain kernel parameters at reboot.
Can anyone give me instructions on how to disable this app from booting or how/where to find it and delete it?
Where can I find logs of this boot loop?
I really want to avoid re-flashing, re-rooting, re-flashing and restoring my backup again as that will take half a day.
I've just brought back mine from bootlooping after I've installed several extensions (just discovered that the culprit was DonkeyGuard) and I'm about to do it for the second time, by flashing a Xposed-Disabler-Recovery.zip file that's stored either in the root of your phone or at
/storage/emulated/0/Android/data/de.robv.android.xposed.installer/files/Xposed-Disabler-Recovery.zip
But that would only work in case you messed it up with Xposed.
Thanks, I'll keep that in mind if I encounter this problem again.
Still finding it hard to believe there's no other reply to a seemingly common problem / question, does everyone just pack up and factory reset when boot looping?
Well, it's as common as people repeating to make a nandroid backup, you know
Btw, before I will flash yesterday a black theme (modded system files), I made the backup, so when my Z3C got stuck in a bootloop for the third time, I had nandroid ready. Such a shame, I really liked that mod.
If the kernel is problem, how about just reflashing your kernel?
Believe it or not, I started looking into nandroid backups today already made my first tests.
Until now I relied on titanium backups but that still makes me do a factory restore before I can restore stuff from those backups.
But the issue is, I am not looking for better "protection" I'm trying to find out how I can fix something minor like this i.e. via adb and command line...
Talking about a custom kernel, is there one? I have a rooted xperia z3 compact and wouldn't mind checking out a different kernel but I held back unlocking my bootloader until there is a custom ROM available that can fully replace my rooted stock ROM.
If love to get PAC man ROM for my phone.
I had the same issue, but by using 3C toolbox (similar to the app you've mentioned).
In my case putting back the original build.prop into /system via ADB fixed the bootloop.
As for custom kernel, you can try AndroPlus kernel HERE
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
-V-O-Y-A-G-E-R- said:
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
Click to expand...
Click to collapse
Hm, I was thinking along the lines of accessing log files, like a system log file, check what went wrong, i.e. auto start of a certain app, or setting of kernel parameters at boot time, then remove the offending apps/entries?
Just not sure if that's possible, hence this question here
Checking out the suggested ap and the kernel! Thanks!
Hi everyone
I would like to know whether or not there is a rooting method that would allow me both to keep my data and my Sony goodies
New in this device thread and feeling a bit lost... thanks very much!
This is what you need: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Follow those steps and you should be good.
Thanks very much but actually, this would make me downgrade and lose all my data if I understand well. So the answer is no, ther's no such solution ?
You might be able to save some datas with Sony PC compagnon software, or Helium backup (witch doesn't requier root)
https://play.google.com/store/apps/details?id=com.koushikdutta.backup&hl=fr
I used the second one for my Z3 Tablet compact without root... Workes fine. Sur, there's things you'll not be able to save, but the most parts should be there.
Once your datas are saved you can do all the stuff requiered for rooting and restore your datas after.
Le_Poilu said:
You might be able to save some datas with Sony PC compagnon software, or Helium backup (witch doesn't requier root)
https://play.google.com/store/apps/details?id=com.koushikdutta.backup&hl=fr
I used the second one for my Z3 Tablet compact without root... Workes fine. Sur, there's things you'll not be able to save, but the most parts should be there.
Once your datas are saved you can do all the stuff requiered for rooting and restore your datas after.
Click to expand...
Click to collapse
Merci !! :good:
Hello,
Sorry for the odd thread but I didn't want to make two separate threads. I have made enough nooby posts for the day as it is! lol. My Nexus 6 is currently on 6.0 MRA58R / TWRP Recovery / Rooted / No Encryption.
1. What is the best APP to use to activate and control the notification light on the Nexus 6? I see there are a few different apps for this but I would like the one that works with / works best with the Nexus 6.
2. Best option to back up my Nexus 6. I have Titanium Backup Pro as well as TWRP Recovery. I don't get understand Titanium Backup. I get how to use it mostly. I just don't get the point of storing the backup for your phone, on your phone... Doesn't that kind of defeat the purpose? If your phone locks up how are you going to load the backup / recover it? I am assuming TWRP backs up directly to the device as well. So I am just wondering the best method to use when backing up, and what all to back up. Can TWRP recover device with a Titanium Backup - Backup?
Thank you in advance for your time.
Rektifying said:
Hello,
Sorry for the odd thread but I didn't want to make two separate threads. I have made enough nooby posts for the day as it is! lol. My Nexus 6 is currently on 6.0 MRA58R / TWRP Recovery / Rooted / No Encryption.
1. What is the best APP to use to activate and control the notification light on the Nexus 6? I see there are a few different apps for this but I would like the one that works with / works best with the Nexus 6.
2. Best option to back up my Nexus 6. I have Titanium Backup Pro as well as TWRP Recovery. I don't get understand Titanium Backup. I get how to use it mostly. I just don't get the point of storing the backup for your phone, on your phone... Doesn't that kind of defeat the purpose? If your phone locks up how are you going to load the backup / recover it? I am assuming TWRP backs up directly to the device as well. So I am just wondering the best method to use when backing up, and what all to back up. Can TWRP recover device with a Titanium Backup - Backup?
Thank you in advance for your time.
Click to expand...
Click to collapse
1. Lightflow is the best app to control the LED light.
2. Titanium backup also allows you to backup individual app data which you can then upload to the cloud or save elsewhere. TWRP doesn't allow this.
You can even set periodic backup and upload times for your apps in TB.
Hi,
I have a Nexus 6 with a shattered screen, and just bought another one to replace it (exact same model, XT1103 32GB).
I want to make a Nandroid dump of the old device by booting into TWRP temporarily, then restoring the backup to the new phone using the same method. Both phones are bootloader unlocked and totally stock (latest Android update).
Is there anything in particular that I should watch out for? Which partitions should I not touch - a friend on another forum suggested that I should not touch EFS?
Cheers,
Su
If you restore the efs from one to the other you'll loose your imei number on the second one
needleyepoke
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
I've cloned a Nexus 5 but I'm not sure if it's the same way.... P.S. of course your not supposed to do it unless you own both phones... From what I've been told
needleyepoke
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Sumanji said:
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Click to expand...
Click to collapse
Yes if they're on the same version. I cloned a 32 into a 64.
Ok I just tried this now, and it is not working...
The restore to the new device worked fine, but when I power up I get the "your device is corrupt screen" (which I think is normal if you use TWRP), but then after that it's just a blank screen...
The phone is still able to boot into bootloader and recovery (stock).
Any ideas what could have gone wrong please?
Thanks,
Suman
I think this might be something to do with encryption... when booting into TWRP the new phone still requires the encryption pin I set up from its original software....
Do I need to start again?
Ok, I flashed the new phone with the factory image and started again... this time, when I restore the backup it just hangs on the white Google logo screen...
Any help appreciated please!
Thanks,
Su
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
zelendel said:
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
Click to expand...
Click to collapse
Oh well,
I'm remembering what I did and I did not restore the Nandroid from Device A to Device B, I titanium Backup'd all the apps and moved them to TitaniumBackup folder on the new phone, restored from there.
For /sdcard/ I had to copy and paste it from one phone to the other...
I'm going to reply this to your reddit thread also.
Lawstorant said:
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Click to expand...
Click to collapse
Ah dang, so there is no way for me to do what I want then... that's annoying, I would have bought a different phone in that case!
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Strephon Alkhalikoi said:
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Click to expand...
Click to collapse
I believe that is correct. All Nexus devices going forward will have the kernel force encryption. The only way around it is to format data in TWRP (completely wipe the phone) and then when you re setup your ROM (or even the stock image) just make sure you flash a custom kernel that doesn't force encryption (which pretty much all custom kernels don't) before booting into OS for the first time. I run mine unencrypted because nandroid backups are wayyyyy quicker without encryption. I know the security isn't as good but not a deal breaker for me.
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
TriguyRN said:
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
Click to expand...
Click to collapse
It is a bad idea. Restoring any system files from one device to another is a risky game. I wouldn't even recommend restoring data from one device to another.
Start fresh, clean. No need to bring junk over, or risk issues. Takes 15 minutes to setup a phone how I like it after a clean rom flash. That's not a long time.
Last year I returned my N6 because of the peeling-back problem. I had a full TWRP backup on my laptop. I loaded it on to the replacement N6, renamed the backup folder to the new device id, and restored it. Worked perfectly, no problems.