Related
I'll make this as short and quick as I can. I had unlocked my bootloader, rooted my device and flashed a custom ROM(PureNexus) and TWRP. I had made a full nandroid backup and all was good.
Then the Android N Developer preview came along and I just HAD TO get it. So I used a tutorial on YouTube to ease the process and it went downhill from there. I used my fastboot folder and a command prompt to run the version of the file that wouldn't wipe my data.
When the device rebooted I noticed that none of my third party (downloaded) apps were working. I was upset and decided to just go back and restore my backup. That's when I noticed that I had no custom recovery anymore. I reinstalled TWRP, but when it loaded it told me my internal storage was encrypted. I tried the method of getting rid of all lock screen security and fingerprints but to no success. I also noticed that every time I reboot TWRP never seems to stick, I have to reinstall it through the fastboot folder and a command prompt every single time. I just wnna be able to get back to where i was and use my backup.
I'm lost on the situation, any suggestions guys? Any help is much appreciated
Big-K said:
I'll make this as short and quick as I can. I had unlocked my bootloader, rooted my device and flashed a custom ROM(PureNexus) and TWRP. I had made a full nandroid backup and all was good.
Then the Android N Developer preview came along and I just HAD TO get it. So I used a tutorial on YouTube to ease the process and it went downhill from there. I used my fastboot folder and a command prompt to run the version of the file that wouldn't wipe my data.
When the device rebooted I noticed that none of my third party (downloaded) apps were working. I was upset and decided to just go back and restore my backup. That's when I noticed that I had no custom recovery anymore. I reinstalled TWRP, but when it loaded it told me my internal storage was encrypted. I tried the method of getting rid of all lock screen security and fingerprints but to no success. I also noticed that every time I reboot TWRP never seems to stick, I have to reinstall it through the fastboot folder and a command prompt every single time. I just wnna be able to get back to where i was and use my backup.
I'm lost on the situation, any suggestions guys? Any help is much appreciated
Click to expand...
Click to collapse
Flash the MHC19I factory images to get back to a stock configuration, then start fresh; flash TWRP again (the latest) and then flash whatever ROM you want to use.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Thank you for the reply and info. I actually just got an RMA request approved because my Nexus also had some hardware issues. So my question now is, will my phone being rooted, with an unlocked bootloader, and in this condition have its warranty voided? Or am I good to exchange it just the way it is?
Big-K said:
Thank you for the reply and info. I actually just got an RMA request approved because my Nexus also had some hardware issues. So my question now is, will my phone being rooted, with an unlocked bootloader, and in this condition have its warranty voided? Or am I good to exchange it just the way it is?
Click to expand...
Click to collapse
The warranty isn't voided by unlocking or rooting, but you should return it to a stock configuration before sending it back anyway. Check out section 10 of my guide.
Heisenberg said:
The warranty isn't voided by unlocking or rooting, but you should return it to a stock configuration before sending it back anyway. Check out section 10 of my guide.
Click to expand...
Click to collapse
Thanks for all your help!
Big-K said:
Thanks for all your help!
Click to expand...
Click to collapse
No problems.
I wanted to share two things with you guys here in Tablet z forum:
1- First of all, @zxz0O0 has developed a code based on the CVE-2015-1805 vulnerability that gives temporary root access to a select range of devices (including Tablet Z4). Let me try to explain in my words what that means. A full blown root gives permanent read/write access to /system and /data partitions. On an unrooted Tablet Z4 you only have read access to /system and no access to /data. With this root, you will be able to have a temporary terminal or adb session that gives you read access to /system and read/write access to /data. Why not write access to /system? Because Sony runs a service called RIC on Xperia devices that makes it impossible to mount /system as writable. In the past this would be patched by modifying the system partition. But in the recent Kernels sony has implemented a mechanism (dm-verity) which checks /system and if it is modified the device does not boot. So even if this (or any other) root method gave you the ability to write in /system you could not use it because your device would not restart the next time you turn it off. The solution would be to patch the kernel which requires an unlocked bootloader. IF you unlock your bootloader you lose your TA partition permanently which includes some of the Xperia features and licenses that have to do with image processing and some DRM. So a lot of us do not want to unlock the bootloader.
Then what good is this new root method? Since it gives you read access to the system partitions you can use this method to back up your TA partition. The idea is that if you ever unlock your bootloader you may be able to use this TA back up to return the system to its original state if you ever decide to relock it. Another benefit is that tools like Titanium back up which require access to the /data partition can now function (in a limited sense) although someone has to work out the details of that.
To download the pack that allows backup and restore of the TA partition go to http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
After you create the backup, you can unlock the bootloader, and use your TA backup and the procedure outlined here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 to create a csutom kernel that uses all the good stuff in the TA backup and emulates an environment where your tablet behaves like one with an unlocked bootloader. The camera denoising algorithm and all other Sony proprietary software which would be disabled after unlocking the bootloader should work.
If you want to return the tablet to its unlocked condition you will need this TA backup. Some explanation about retrieving the TA partition from this backup, if you unlock the bootloader and decide to relock it, is given here http://forum.xda-developers.com/showpost.php?p=66142823&postcount=16 and methods to do so are outlined at: http://forum.xda-developers.com/showpost.php?p=66158970&postcount=68
Note that to use this root you need to downgrade to lollipop (preferably version 28.0.A.8.260)
I have explained procedures to use the above tools here http://forum.xda-developers.com/z4-tablet/general/guide-safe-bootloader-unlock-restore-t3362391 at length.
2- Now, here is the use I have found for this temporary root: I was always bothered by the fact that not only I could not (easily) get the 17 hour advertised on-screen use out of my tablet, the standby power consumption was always too much. Whereas I could optimize my other (rooted) devices to only drain 1-2% a day in standby, tablet Z4 seems to settle for nothing less that 5-10% a day in standby. This is what you can do to get excellent standby power from your tablet:
A) Say goodbye to your google apps (with the exception of Chrome and Maps) and other marginally advantageous apps. They wake your device up all the time when it is supposed be sleeping and endlessly chat with google servers even if you turn all the communications off in the google settings. So disable all of the apps listed in the attached pictures , plus lifelog,via settings. Don't complain about not being able to use the gmail or youtube apps. Other great replacements exist. Leave "Google App" active if you use the voice search or voice typing feature. Also uninstall the pre-loaded apps that you aren't using like facebook (which is cancer for any phone), Lifelog, Privilege, spotify, etc.
B) In settings under wifi open the advance menu turn off both "network notification" and "scanning always available", and change "keep wifi on" to "only when plugged in"
C) Under "power management" in settings, activate stamina mode and extended standby (no need to activate extended usage).
D) Finally (and here is where the temp root becomes useful) extract the file "iovyroot" from the file in the above link and put it in your adb directory. Open a command terminal and type:
Code:
adb push root\iovyroot /data/local/tmp/iovyroot
adb shell chmod 777 /data/local/tmp/iovyroot
adb shell
This gives you an android terminal shell. Continue with the following:
Code:
/data/local/tmp/iovyroot
pm disable com.sonyericsson.idd.agent
pm disable com.sonymobile.entrance
pm disable com.sonyericsson.updatecenter
pm disable com.sonymobile.anondata
pm disable com.dsi.ant.server
pm disable com.sonymobile.gmailreaderservice
pm disable com.sonymobile.googleanalyticsproxy
pm disable com.sonymobile.mx.android
pm disable com.sonymobile.enterprise.service
pm disable com.sonymobile.synchub
pm disable com.sonymobile.phoneusage
That is it. You just disabled the update service and a bunch of other things and extended your standby battery life. These settings will survive a reboot.
Let me know how it works out for you. If you find other creative uses for this temp root share here.
This is the BEST and probably the most right to the real point post ive ever readed in this particular forum since I joined....
Forgive me if I say I have had lost the faith on sony's z4t development here... It's a real pleasure to know there's still ppl working on what I think should be the right development direction on gettin' control of our loved devices, instead of breaking them and throw a lot of expensive features to the flush.
Thanks again mate to share it.
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Stevethegreat said:
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Click to expand...
Click to collapse
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Hmm, but if you can also temp root then you can backup everything using TitaniumBackup anyway before unlocking.
So if I understand this right, if you can back up TA we can infact unlock the bootloader now with no loss of DRM ?
So can now actually get full root based on that ?
najoor said:
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Click to expand...
Click to collapse
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Stevethegreat said:
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Click to expand...
Click to collapse
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
najoor said:
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
Click to expand...
Click to collapse
Mostly to save time as I have too much data. I though to do it like this
Downgrade to Lollipop -> Use the Exploit -> TA Backup -> Upgrade back to Marshmallow.
In principle everything should have had worked as by the end of it I would be back to Marshmallow (I would not linger into Lollipop). But now that you're telling me that lollipop may corrupt my data permanently I have second thoughts.
I thought, that my data would not work well on Lollipop, but that wouldn't matter to me; but now you're telling me that they won't work when I'll back in Marshmallow too, which is a totally different beast. Am I understanding you correctly?
Does everyone need to downgrade tho?
Once we have the TA partition available to restore, once its made available online surely everyone else can just restore the same one?
Or is the key unique?
Kinda assuming here that all the stuff that needs the TA partition will work with an unlocked bootloader, or does it have to be locked to be usable again?
Edit: Can we restore TA partition after unlocking bootloader?
Yes but this will also relock the bootloader.
Bugger
Ultimately never rooted my device for fear of losing something (that I will never use anyway!)
DRM Keys are unique, in fact that's the whole point of TA backups.
Also there's a talk (on the other thread) of a tool that would merge your particular keys with a particular custom kernel.
That way you'd keep all Sony Exclusive features, but also be able to make use of root apps. It would be great if such a tool becomes usable with AndroPlus Kernel...
Nice, had all but given up hope of being able to unlock my Z4 so that sounds promising!
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
D0MINO said:
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
Click to expand...
Click to collapse
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
I unlocked the bootloader and rooted the device SGP771.
Bevor that, i backed up the TA.
Then i flashed the androplus kernel.
Everything works great.
But you cannot modify androplus kernel with that tool. That means DRM restore is only possible on stock rom.
When you restore TA to stock rom, your bootloader will be in a lockes status again and there is no more root. Too bad
odicamillo said:
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
Click to expand...
Click to collapse
Can ta be restored on any fw like marshmallow or can it only be restored on the fw that you backed it up from?
This looks very promising, thanks OP.
Has anyone else managed to get it to work as described?
Thanks in advance
najoor said:
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Click to expand...
Click to collapse
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
retikulatus said:
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
Click to expand...
Click to collapse
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
najoor said:
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
Click to expand...
Click to collapse
Thanks for the fast reply even if you ruined my hopes
no, i don't think i have myXperia , i checked on my apps and find nothing.
Since i had display issues with my tab s (sm-t800), i tried the z4 tablet for its LCD screen instead of the super amoled of samsung...
My bootloader was already locked when i purchased it, i updated it thinking it will change that but unfortunatly that did nothing.
It wasn't a new one though, perhaps the previews owner messed up with it and got its bootloader locked :/
Because it is some kind of lotery to have a bootloader unlockable with sony, i will wait patiently until samsumg release its 16:9/10 tab s4: imho, the tab s3 actual 4:3 format is a nonsense....
Thank you again
Kind regards from France
Hi I would like to unlock the bootloader and root once the new update rolls out but have quite a few private apps with preferences set. If I had TWRP I would just backup the data partition but I cannot do that.
I wanted to ask what you feel the most effective way to backup my apps and app data on a non-rooted virgin Shield? Does Google allow app data syncing on Android TV platform?
Thanks.
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Bump
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Bump
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Anyone???
Please use the QUOTE feature when replying to me to get my attention. Thanks!
E--Man said:
Anyone???
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Click to expand...
Click to collapse
Is it a 16GB og Pro version?
If it's a 16GB, there isn't really anything that just works, unfortunately.
If it's a Pro version, then you can pull the HDD and alter a partition to make it unlocked, then flash TWRP, backup and update (in theory).
E--Man said:
Anyone???
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Click to expand...
Click to collapse
Umm you can't... That's kind of One, of the many other possible reasons why you root to begin with. e.g. being able to access restricted /data, and /system Partitions, for instance. As it is I would guess the only way you could possibly get at them would be though ADB. But, lol you have to also have root for that.*
NOTE: This is where those Rooted Recovery Images from nVIDIA come from. They are only rooted for ADB, and not for SuperSU. Or so I understand it.
So again I fairly sure your just going to have to bite it this time. Also (from someone with some experience in the matter), you may want to remove your SSHD, and make a few backups of it (See the SSHD to SSD Migration To), in case thing ever go ugh wrong. If your hell bent on rooting.
hallydamaster said:
Is it a 16GB og Pro version?
If it's a 16GB, there isn't really anything that just works, unfortunately.
If it's a Pro version, then you can pull the HDD and alter a partition to make it unlocked, then flash TWRP, backup and update (in theory).
Click to expand...
Click to collapse
Ichijoe said:
Umm you can't... That's kind of One, of the many other possible reasons why you root to begin with. e.g. being able to access restricted /data, and /system Partitions, for instance. As it is I would guess the only way you could possibly get at them would be though ADB. But, lol you have to also have root for that.*
NOTE: This is where those Rooted Recovery Images from nVIDIA come from. They are only rooted for ADB, and not for SuperSU. Or so I understand it.
So again I fairly sure your just going to have to bite it this time. Also (from someone with some experience in the matter), you may want to remove your SSHD, and make a few backups of it (See the SSHD to SSD Migration To), in case thing ever go ugh wrong. If your hell bent on rooting.
Click to expand...
Click to collapse
Taking the above into consideration, I am actually registered in the nVidia Developer Program and have access to the Developer images. Having said that, if I flash the Developer image, then I not just use the rooted ADB to make a backup of all the app data and then unlock boot loader and restore it?
Well irregardless of your having a Pro (Or, not)... You're still not going to get very far with what you are hoping to do. As you would have had, to have unlocked the Bootloader first. Before you could flash anything at all.
Unlocking the Bootloader will of course totally erase ALL OF YOUR PERSONAL DATA! And, that seems to be the catch-22 here, as you presumably do not want this. Of course OtOH if you ~are~ already unlocked then it shouldn't be a problem, then again booting TWRP from Fastboot, and eventually rooting shouldn't be a problem either.
But, since your Device has NOT yet been Bootloader unlocked, you CAN NOT actually do any of this yet.
I don't know what exactly it is you want to "backup", but you could use something like ES File Explorer to backup your Installed Apps, and your 'hidden' /system Apps (e.g. iPlayer), if thats your thing.
If you wanted to backup your Kodi stuff then ESFE could do that as well (But, you would have to enable Hidden Files to do this). Considering the recent loss of TVAddons. This in-and-of-itself, may well be good advice going forward for a while yet.
Ichijoe said:
Well irregardless of your having a Pro (Or, not)... You're still not going to get very far with what you are hoping to do. As you would have had, to have unlocked the Bootloader first. Before you could flash anything at all.
Unlocking the Bootloader will of course totally erase ALL OF YOUR PERSONAL DATA! And, that seems to be the catch-22 here, as you presumably do not want this. Of course OtOH if you ~are~ already unlocked then it shouldn't be a problem, then again booting TWRP from Fastboot, and eventually rooting shouldn't be a problem either.
But, since your Device has NOT yet been Bootloader unlocked, you CAN NOT actually do any of this yet.
I don't know what exactly it is you want to "backup", but you could use something like ES File Explorer to backup your Installed Apps, and your 'hidden' /system Apps (e.g. iPlayer), if thats your thing.
If you wanted to backup your Kodi stuff then ESFE could do that as well (But, you would have to enable Hidden Files to do this). Considering the recent loss of TVAddons. This in-and-of-itself, may well be good advice going forward for a while yet.
Click to expand...
Click to collapse
Thanks for the reply. There is only one discrepancy/question I have with your post - I was under the impression that I can flash the nVidia signed Developer ROM image *without* unlocking the bootloader, is that correct? If not, then I see your point and there is no way to access the app data files in the "data" partition. However, if I do not need to unlock the bootloader to flash the nVidia signed Developer image, and the nVidia signed Developer image is ADB rooted then I should be able to access the "data" partition.
Unless of course the flashing the nVidia signed Developer image will also wipe the "data" partition in the process
E--Man said:
Thanks for the reply. There is only one discrepancy/question I have with your post - I was under the impression that I can flash the nVidia signed Developer ROM image *without* unlocking the bootloader, is that correct? If not, then I see your point and there is no way to access the app data files in the "data" partition. However, if I do not need to unlock the bootloader to flash the nVidia signed Developer image, and the nVidia signed Developer image is ADB rooted then I should be able to access the "data" partition.
Unless of course the flashing the nVidia signed Developer image will also wipe the "data" partition in the process
Click to expand...
Click to collapse
This is taken from the Nvidia developer page:
NOTE: On the SHIELD Android TV Pro 500GB edition, some steps of the flash process may take a
Click to expand...
Click to collapse
hallydamaster said:
This is taken from the Nvidia developer page:
NOTE: On the SHIELD Android TV Pro 500GB edition, some steps of the flash process may take a
Click to expand...
Click to collapse
Darn, you are correct - it is required to unlock the bootloader to flash the nVidia Developer image. Too bad. Wish there was a way to extract app data! Some apps on mobile Devices use the Google Sync for app data, but I am not sure if this is employable on Android TV.
Click to expand...
Click to collapse
E--Man said:
Thanks for the reply. There is only one discrepancy/question I have with your post - I was under the impression that I can flash the nVidia signed Developer ROM image *without* unlocking the bootloader, is that correct? If not, then I see your point and there is no way to access the app data files in the "data" partition. However, if I do not need to unlock the bootloader to flash the nVidia signed Developer image, and the nVidia signed Developer image is ADB rooted then I should be able to access the "data" partition.
Unless of course the flashing the nVidia signed Developer image will also wipe the "data" partition in the process
Click to expand...
Click to collapse
To be fair, you would have to read the enclosed README File with the Dev ROM in question. I Have yet had no much reason to use it. So to be quite honest here I wouldn't know. OtOH though you do have to bootloader unlock the Device first of you wanted to flash a stock recovery Image. So everything that I think I know comes from that.
But, please extrapolate this idea of App Data further. I mean are we speaking about Apps, of pure Data (Al-la Kodi Data)?
'Cause these things can be backed up to degrees. If it's something well deeper than this. Well your just outta luck I'm afraid.
Ichijoe said:
To be fair, you would have to read the enclosed README File with the Dev ROM in question. I Have yet had no much reason to use it. So to be quite honest here I wouldn't know. OtOH though you do have to bootloader unlock the Device first of you wanted to flash a stock recovery Image. So everything that I think I know comes from that.
But, please extrapolate this idea of App Data further. I mean are we speaking about Apps, of pure Data (Al-la Kodi Data)?
'Cause these things can be backed up to degrees. If it's something well deeper than this. Well your just outta luck I'm afraid.
Click to expand...
Click to collapse
Hi lchijoe, I am just referring to the app preferences and their personal data that usually exists inside the "/data/data" folder. Some manufacturers allow exporting of this data even on non-rooted devices. For example, Huawei has a backup app which exports apps along with their personal data such that if you restore them it is as if you didn't even uninstall them to begin with. If I basically want to have everything restored as if I didn't do a factory reset.
.
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Just bumping this in case anyone has any other input
Hi everyone.
I have been looking to join for a long time now, I hope my first post is not considered a poor quality post as I'm really stuck at the moment and can't wait to fullfil this learning curve.
I've been reading as much as I can for a long time, considering to root my Z2 mobile for a long time also, I finally decided I would like to for various reasons.
I am running D6503 / 6.0.1 / 23.5.A.1.291
So far I have enabled my Windows 10 machine to allow adb, this took a few attempts but when reading the comments it became clear I needed to type ./adb devices and not just "adb devices", once I noticed this small issue the process worked.
I then tried to run Backup-TA.bat as this is needed before rooting, to save losing any DRM Keys
Waiting for USB Debugging...OK
Pushing Backup TA Tools...OK
Checking for SU binary...FAILED
Requesting root permissions...FAILED
I'm sorry if this is a typical newbie question, I have an idea that I'm missing the SU Binary and need to provide root permission due to the message but I've not read a clear comment about where to get those.
EDIT:
Not to sound even further like a newbie or like I've not read anything, but I've read you need to root first, before backing up TA/DRM?
I thought the point was to backup TA/DRM before rooting since rooting will lose the DRM forever?
EDIT2:
I'm not looking for anything too advanced right now and would be happy with just rooting, no custom roms, just happy to remove bloatware, add some apps, mod the camera etc
Can somebody confirm, you need to root and then backup ta/drm, then unlock bootloader (which will lose your ta/drm forever unless you backup first)?
I'm sure it's all simple after the first success, I just don't want to make any mistakes that can't be undone.
unknown5 said:
Hi everyone.
I have been looking to join for a long time now, I hope my first post is not considered a poor quality post as I'm really stuck at the moment and can't wait to fullfil this learning curve.
I've been reading as much as I can for a long time, considering to root my Z2 mobile for a long time also, I finally decided I would like to for various reasons.
I am running D6503 / 6.0.1 / 23.5.A.1.291
So far I have enabled my Windows 10 machine to allow adb, this took a few attempts but when reading the comments it became clear I needed to type ./adb devices and not just "adb devices", once I noticed this small issue the process worked.
I then tried to run Backup-TA.bat as this is needed before rooting, to save losing any DRM Keys
Waiting for USB Debugging...OK
Pushing Backup TA Tools...OK
Checking for SU binary...FAILED
Requesting root permissions...FAILED
I'm sorry if this is a typical newbie question, I have an idea that I'm missing the SU Binary and need to provide root permission due to the message but I've not read a clear comment about where to get those.
EDIT:
Not to sound even further like a newbie or like I've not read anything, but I've read you need to root first, before backing up TA/DRM?
I thought the point was to backup TA/DRM before rooting since rooting will lose the DRM forever?
EDIT2:
I'm not looking for anything too advanced right now and would be happy with just rooting, no custom roms, just happy to remove bloatware, add some apps, mod the camera etc
Can somebody confirm, you need to root and then backup ta/drm, then unlock bootloader (which will lose your ta/drm forever unless you backup first)?
I'm sure it's all simple after the first success, I just don't want to make any mistakes that can't be undone.
Click to expand...
Click to collapse
Yes you can root on LB and backup TA partition.just follow the awesome guide by @rocker00.
Link: https://forum.xda-developers.com/xperia-z2/general/tool-rooting-23-5-1-291-supersu-t3437280
vikash1994b said:
Yes you can root on LB and backup TA partition.just follow the awesome guide by @rocker00.
Link: https://forum.xda-developers.com/xperia-z2/general/tool-rooting-23-5-1-291-supersu-t3437280
Click to expand...
Click to collapse
Thank you but I have read this thread again and again, I am still looking to get everything in order fully.
Waiting for USB Debugging...OK
Pushing Backup TA Tools...OK
Checking for SU binary...FAILED
Requesting root permissions...FAILED
You failed. Why failed?
You need accept permission SuperSu for device.
Before you plug in device, you need turn USB Debugging and plug in device you need to accept permission SuperSu, allow all (important)
Ok. Do it, again and enjoy your phone.
When you are a Sony Xperia Z2 owner on Android 6.0.1 you need to be a wizard to get started with rooting your device.
I managed to get a wizard. The huge problem is: When you wanna root your z2 6.0.1 you need to get into the recovery but you cant get into the recovery without root ....... the magical trick is to downgrade to android 5.x and use kingroots or whatever the app is called and than you can flash a recovery and install a custom rom. Or use the android 6.0.1 magic which is just another workaround: https://forum.xda-developers.com/xpe...persu-t3437280
When you have trouble to deal with that instructions let us know why you fail.
A super awesome super user here helped me with every step if moderators wish to close this thread now.
EDIT 2: ISSUE SOLVED. Go to the bottom of this comment for how to get it done right. Credits to @rizkyxculture and @orma1
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
EDIT 2: Sorry for necroing this thread, but just to clear things up a bit, from my own experience, and include and clarify what @orma1 said below in this thread so you don't have to scroll down. Before all this, make sure you have SYSTEM WIDE ADB AND FASTBOOT INSTALLED for simplicity's sake.
All credits go to @orma1 and @rizkyxculture for your amazing efforts into this <3. None of it is mine, so thank them in their respective comments/threads if you wish to.
1. REMOVE ALL PASSWORDS AND FINGERPRINTS BEFORE PROCEEDING WHILE IN PIE, and do CLEAN DATA WIPE (do not choose the relock bootloader in Mi Flash Tool).
2. Do everything in that guide sent, and at the end, where rizky mentions flashing November update after the TWRP restore, don't do it. Instead, re-flash the March update. Thanks @orma1 for your comment. If your phone just straight up boots like mine did, without bootlooping, just power it off and go to fastboot again. Link to guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624.
3. Once your phone boots normally, go to developer options, and uncheck the automatic system updates to prevent it from going to pie automatically later on. in the future. Install GCam at this stage if you wish (follow manual installation guide on XDA). Link: https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
4. After you've installed GCam (which is why you're probably doing all this in the first place, or not, regardless), chances are you still want to keep your warranty (and for security reasons) and therefore you should relock your bootloader, else the servicemen are just going to see that BIG warning at your phone's boot, and are likely revoke any warranty straight up. To do this, simply go back to fastboot and type the command below in Command Prompt and WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON (or copy paste the line below WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON):
fastboot oem lock
Once it says okay, type the following command:
fastboot reboot
Done. Now reboot, go to system update, and download and install the November update. Enjoy your still in warranty Mi A1 with Oreo and/or GCam (just make sure you uninstall the apk when giving it to the service center should you ever need to service it). Also, the power down button press prevents the auto data wipe function from activating. Have fun.
Also I have verified this works even on the April 2019 update. Just don't update any further, else I can't be sure.
Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Guess I'll just stick to pie and bite the sand and live with it till someone gets a solid, working method...
As a second thought, if I make a backup of everything (system, boot, etc. etc.) in TWRP and then carry out the flashing process, will reflashing those backups restore my device in case of a brick?
Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
Just flashing oreo from pie should cause IMEI loss.
I used the method from here: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
although I had to do his method a little differently.
also make sure if you can to backup your data as you can lose it in the process.
first of all, after oreo march update flash, my phone did boot but with no IMEI.
second of all, flashing November update after restoring IMEI caused bootloop, instead you need to flash march update again. afterwards your phone should boot with the correct IMEI (you can double check with the one on your phone's box) . worked for me with two Mi A1s.
after all of this I was able to update to 8.1 November update via system update in the settings.
and lastly I made sure to disable automatic system update from developer settings.
Good luck!
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Meme :D said:
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Click to expand...
Click to collapse
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Thanks, will see about all this.
orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Nafis-ul-Islam said:
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Click to expand...
Click to collapse
I used the backup from this thread
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
It's a backup of someone else's efs and boot patiotions. At first I thought too that restoring someone else's backup should result in me getting his IMEI.
But after trying to restore through this backup My IMEI changed from 0 to the one on my phone's original box meaning I got my own IMEI. the method there worked perfectly for me and now I am rocking 8.1 Oreo November update with Magisk and TWRP. the only thing is that following step 10 in the tutorial there resulted in a bootloop for me. Instead I followed the suggestion of one of the comments saying that instead of flashing November update after restoring IMEI you need to flash the same March update you flashed before. this time my phone booted with IMEI and I updated to 8.1 November through OTA.
Did you downgraded succesfully?
Meme :D said:
Did you downgraded succesfully?
Click to expand...
Click to collapse
I was able to downgrade successfully following this guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
In step 10 you need to flash oreo march update again and not November update as mentioned as flashing November update caused me bootloop.
afterwards you can update to November update via System update in the settings.
besides this I followed the tutorial exactly and was able to downgrade two Mi A1s.
I have successfully downgraded my Mi A1 with this thread
"Tutorial Downgrade 9.0 to 8.1 No EDL, No IMEI Problem & No Signal Problem"
Also im a 14 Yr old nearly 15 on April 20.
I was afraid too, now I'm on Nougat )
Just follow this tutorial : https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Before doing anything, boot TWRP and create a full backup of your system, after that transfer it to your PC. Probably you don't need it but better safe than sorry.
After you will flash March firmware, your phone will boot but you will not have signal, it's okay. Thing is, you don't lose the IMEI, it's still there, but somehow you lose the signal. Boot TWRP again, create a backup of your boot and EFS, you will see TWRP folder in your phone, go there and you will see a backup. Remove your backup files and replace them with the one from the guide, then you can restore them without issues (you will see a modem error, ignore it). Restart and let it boot a bit, then go to bootloader again, flash March firmware again (don't flash the November one! ignore that from the guide) and the signal will be back. If you do this, I doubt you will lose your IMEI somehow. I never lost mine, it's the same from the box.
Good luck! Make sure you go in developer settings after and disable automatic updates or you will be back to Pie. I rooted my phone so it can't update.
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Nafis-ul-Islam said:
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Click to expand...
Click to collapse
I'm happy to help
but all the credit goes to rizkyxculture for finding this method and ibooth2004 for correcting us to flash March update again instead of the November one.
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Marcos OC said:
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Click to expand...
Click to collapse
I agree the system's performance on pie is horrible and also the mic volume is low which is very annoying.