Related
Hello everyone.
I unlocked the bootloader of my phone, and I rooted it today. I want to ask you guys, is it normal to lose all your applications,widgets and contacts? Cause I didn't see any warnings. Anyway I don't really care about the apps and the widgets but I could use my contacts if you guys have a clue. Else I would need to ask a lot of people to remake the list .
Thanks
I think unlocking of bootloader using official method wipes all data for safety...
dont know about other method
and about contect, you can sync it with your google account..
Unlocking by testpin method and rooting not affect any data!
Is the possible that you after instaling zip from cwm recovery accidentaly do full wipe?
I in fact unlocked the bootloader with the official method. And I notice this now:
Certain content on your phone may also be inaccessible due to the removal of DRM security keys and the secure user data partition while unlocking the boot loader.
We advise you to create backups, since user data, settings and accounts will be removed.
Click to expand...
Click to collapse
So yeeea . Well serves me right I guess! Anyway thanks a lot for the replies guys
Cr0ne said:
I in fact unlocked the bootloader with the official method. And I notice this now:
So yeeea . Well serves me right I guess! Anyway thanks a lot for the replies guys
Click to expand...
Click to collapse
I also used the official method and didn't lose any contacts, so I don't think the warning applies to that. I think it's a "just in case" warning...
Requirements:
[ROOT REQUIRED]
[OEM Unlocking must be allowed under the developer options before flashing this file AND stay activated
as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]
* I am not responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this method before using it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!
I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.
Tested and confirmed working on:
OxygenOS 2.2.0 - thanks to @pryggi
OxygenOS 2.1.1
Hydrogen OS 1.2.0 - thanks to @fareed_xtreme
I looked at this thread, thanks to Naman Bhalla for this great work.
and found out that the file attached to this post is the answer to my problem, described in another thread.
After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.
On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.
By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:
Code:
dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img
The output should look like the following:
Code:
0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)
You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:
Credits:
Naman Bhalla
Also to segv11 who already managed this in the OnePlus One and Nexus devices
wow nice job m8
sent from rooted phone
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
fareed_xtreme said:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Click to expand...
Click to collapse
thedropdead said:
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
Click to expand...
Click to collapse
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
fareed_xtreme said:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
Click to expand...
Click to collapse
Thats another good thing to do with it
It was a pleasure to help you out mate
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
pryggi said:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Hello pryggi,
It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:
Code:
dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img
And looking at the file in the hex editor for differences or by posting it here and i can check it for you.
I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.
You can also execute dd in the Android Terminal Emulator App.
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
pryggi said:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
Click to expand...
Click to collapse
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.
I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).
So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
pryggi said:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
Click to expand...
Click to collapse
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.
It is hard to explain
Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.
I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).
So the problem here lies in flashing twrp.
I solved this problem by keeping the stock recovery and locking the device via the image file.
Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.
I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp
Hope that this post helps somehow
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
fareed_xtreme said:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
Click to expand...
Click to collapse
That is right, i just included the notice in the first post so nobody can tell me i have not told them
It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway.
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
casual_kikoo said:
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
Click to expand...
Click to collapse
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
thedropdead said:
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
Click to expand...
Click to collapse
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
casual_kikoo said:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
Click to expand...
Click to collapse
Okay thanks for the clarification.
In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.
Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.
so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.
But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
Hi,
I have a Xiaomi Redmi Note 3 Pro International Version 3GB 32GB.
I never modified this device (no root, unlock etc.).
However, I have enabled the encryption option.
Today, there was another system update which I installed (since I own this device, there was never a problem with these updates).
After installing the update, the device got stuck in a boot loop :crying:
Question: How can I backup my personal data now (e.g. photos)? -- I really would like to have this data (unfortunately, my last backup is a little old).
I assume that, since the device is encrypted and in a boot loop, I cannot wipe the device without losing all my data, correct?
Can I install a boot loader from where I can backup my photos?
Thank you in advance!
Happened to me as well. I had to format it. One thing you could do is unlock it using mi unlocked app. Install twrp via ADB. Twrp will ask for password. Once unencrypted in twrp, you could copy your files onto a SD card quickly. I personally didn't want to go through this hassle and simply wiped data. Lost a ton of data for not backing up sooner.
Thanks for your reply! Sorry that you lost your data...
Can I unlock the phone using the method you described when the phone is already in the boot loop? -- I understood that I have to log in to the Mi account on the phone (which I cannot do at the moment due to the boot loop.
Is there any other way to unlock the device?
Thanks!
It worked -- I could create a backup of all my data.
I described the details in a blog article -- however, this forum unfortunately does not allow me to post the link. You will find it when googling "Irgendwas Verschwurbeltes"
RedmiNote3User said:
It worked -- I could create a backup of all my data.
I described the details in a blog article -- however, this forum unfortunately does not allow me to post the link. You will find it when googling "Irgendwas Verschwurbeltes"
Click to expand...
Click to collapse
Thank you for sharing the method, here is the link.
I am surprised that fastboot_edl worked on a locked device, but perhaps it depends on a model and MIUI/bootloader version. Anyway, the EDL mode always works with the "test point" or "deep flash cable" methods. I suppose that instead of editing rawprogram0.xml you could just delete userdata.img and the flash would continue with only a minor error and user data intact.
:good:
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
The Marionette said:
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
Click to expand...
Click to collapse
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
hypafly said:
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
Click to expand...
Click to collapse
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
The Marionette said:
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
Click to expand...
Click to collapse
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
hypafly said:
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
Click to expand...
Click to collapse
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
So sorry to hear this.
My Moto Z has the WiFi bug too. But Bluetooth works though. It's very annoying because I've tried various fixes and different custom roms which didn't fix the problem. Maybe it's hardware? I wouldn't know. But I'm managing it for now until I get another phone.
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
How to Fix EFS over ADB
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
How to Fix EFS from Bootloader Mode using Fastboot commands
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
How to Fix EFS from TWRP recovery
Boot into TWRP recovery.
From TWRP’s main screen, selectAdvanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.
Edit: Those using twrp may experience efs restoration issues.
While creating the backup of EFS, you will end up with:
efs1.emmc.win (modemst1 partition raw data)
efs2.emmc.win (modemst2 partition raw data)
When restoring this EFS backup, what happened was the file name was not updated for restore, and you ended up with:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs1.emmc.win to modemst2
It should have been:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs2.emmc.win to modemst2
Twrp issue, the steps above will restore your devices.
Click to expand...
Click to collapse
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
eLaDiio said:
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
Click to expand...
Click to collapse
I appreciate the help but it sadly didn't fix anything. :/
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
eLaDiio said:
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
Click to expand...
Click to collapse
I have access to everything, everything besides the wifi, bluetooth and sim functions works.
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
eLaDiio said:
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
Click to expand...
Click to collapse
I't not a hard brick, the phone boots. Wifi, Bluetooth and SIM functions are the only things that are dead. xD
Sorry, I expressed myself badly, what I wanted to say is that your case is a strange situation, by the way, I have a full backup of my phone and if you want, I can share it so you can try flashing it and see if you can recover the wifi, although I think it could end up in a hard brick so it is risky to try it. Tell me if you're interested in flashing my backup
My OP3 retired and have upgrade to 7T pro (Global version purchased in India). Will receive the phone tomorrow.
Can someone guide based on their experience on what should be the first steps ?
- Do I take backup ?
---- If yes of what - Boot image, EFS etc ( )
---- Should I run all OTA updates first ?
---- Any guide/reference to do the same
- Should I root ? ( Primary need ad blocker, tasker automation etc, freeze bloatware .. heard they are rolling out facebook ) ( No custom roms )
It has been long time that I tried such things. I may need to read guides . Appreciate any inputs.
hyperorb said:
My OP3 retired and have upgrade to 7T pro (Global version purchased in India). Will receive the phone tomorrow.
Can someone guide based on their experience on what should be the first steps ?
- Do I take backup ?
---- If yes of what - Boot image, EFS etc ( )
---- Should I run all OTA updates first ?
---- Any guide/reference to do the same
- Should I root ? ( Primary need ad blocker, tasker automation etc, freeze bloatware .. heard they are rolling out facebook ) ( No custom roms )
It has been long time that I tried such things. I may need to read guides . Appreciate any inputs.
Click to expand...
Click to collapse
With OOS you currently can't make a Nandroid backup meaning TitaniumBackup etc. is your only option.
I would backup your boot image, EFS and persist partition. Here is the guide for EFS: https://forum.xda-developers.com/7t-pro/how-to/guide-backup-efs-partition-decryptable-t4086625
For boot and persist it is the same procedure with these commands in adb shell:
- dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
- dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
Do you mean OTA updating before rooting or before backuping? I'm not sure what you mean by that question?
Depends on if you need it. If you can live without Widevine L1 and Netflix HD I would unlock the bootloader and try root. If you don't need it, unroot and done. Otherwise you'd need to wipe your device to unlock the bootloader which can be quite some hassle.
Macusercom said:
With OOS you currently can't make a Nandroid backup meaning TitaniumBackup etc. is your only option.
I would backup your boot image, EFS and persist partition. Here is the guide for EFS: https://forum.xda-developers.com/7t-pro/how-to/guide-backup-efs-partition-decryptable-t4086625
For boot and persist it is the same procedure with these commands in adb shell:
- dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
- dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
Do you mean OTA updating before rooting or before backuping? I'm not sure what you mean by that question?
Depends on if you need it. If you can live without Widevine L1 and Netflix HD I would unlock the bootloader and try root. If you don't need it, unroot and done. Otherwise you'd need to wipe your device to unlock the bootloader which can be quite some hassle.
Click to expand...
Click to collapse
Many Thanks.
I meant should I perform all OTA updates before backuping or should I backup vanilla and then perform the updates.
About root. Didn't know about persist partition, widevine L1 etc. Searched and came across this thread. Will backup the partitions for sure.
hyperorb said:
Many Thanks.
I meant should I perform all OTA updates before backuping or should I backup vanilla and then perform the updates.
About root. Didn't know about persist partition, widevine L1 etc. Searched and came across this thread. Will backup the partitions for sure.
Click to expand...
Click to collapse
I would backup before as some people had issues with /persist after updating. An no backup means you probably have to send your device in to get the sensors (including the fp sensor) restored.
Widevine L1 unfortunately is unfixable as long as the bootloader is unlocked.
I saw your EFS guide. It seems its a choice between EFS and Widevine.
In order to backup EFS one need to unlock the bootloader. But once unlocked it will affect widevine. And it seems there is no other way.
hyperorb said:
I saw your EFS guide. It seems its a choice between EFS and Widevine.
In order to backup EFS one need to unlock the bootloader. But once unlocked it will affect widevine. And it seems there is no other way.
Click to expand...
Click to collapse
Yeah. Ideally, EFS and persist are irrelevant for locked bootloaders. There might be some rare issues where you need a backup but IMHO if you don't unlock the bootloader, the EFS backups aren't really necessary.
You can, however, unlock it, backup and then restore with MSM tool to get a locked device again. Though restoring it would require unlocking it again but you wouldn't need to send it in. If this is useful is another question. It won't hurt but it is unlikely you need it.
Enable USB debugging
Code:
adb devices
adb shell
dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
Results in permission denied error.
EDIT : I guess these require unlocked bootloader > Then use your EFS guide to backup.
However, if I do not plan to root, should I still back these up. Netflix SD is not a show stopper for me
hyperorb said:
Enable USB debugging
Results in permission denied error.
EDIT : I guess these require unlocked bootloader > Then use your EFS guide to backup.
However, if I do not plan to root, should I still back these up. Netflix SD is not a show stopper for me
Click to expand...
Click to collapse
If you plan to unlock the bootloader, back them up.
If not, you can back it up and then lock the bootloader. However, it is highly unlikely you'd need it in this situation
Macusercom said:
If you plan to unlock the bootloader, back them up.
If not, you can back it up and then lock the bootloader. However, it is highly unlikely you'd need it in this situation
Click to expand...
Click to collapse
OK. Thanks for helping with my queries.
1) Unlock bootloader
> Dev option > OEM unlock > Reboot to Bootloader > Fast OEM unlock (wiped data)
> Is this ok ?
2) But what is the safe way lock it back ??
3) If i understand correctly .. by leaving the bootloader unlocked, the only 2 key issues is Widevine L3 + no OTA updates
4) If i continue and decide to root ( leaving the bootloader unlocked )
> What is the current best method to perform root
>> Download firmware > Dump payload to get boot.img > patch in magisk > FLASH and BOOT patched image > FLASH Magisk ... ( is this ok .. or any other way )
hyperorb said:
OK. Thanks for helping with my queries.
1) Unlock bootloader
> Dev option > OEM unlock > Reboot to Bootloader > Fast OEM unlock (wiped data)
> Is this ok ?
2) But what is the safe way lock it back ??
3) If i understand correctly .. by leaving the bootloader unlocked, the only 2 key issues is Widevine L3 + no OTA updates
4) If i continue and decide to root ( leaving the bootloader unlocked )
> What is the current best method to perform root
>> Download firmware > Dump payload to get boot.img > patch in magisk > FLASH and BOOT patched image > FLASH Magisk ... ( is this ok .. or any other way )
Click to expand...
Click to collapse
1) Yes.
2) Either remove everything and lock it manually or simply use the MSM tool which will do everything for you.
3) Widevine L3 yes, OTA is only broken for T-Mobile McLaren editions. Otherwise you'd need to flash the full OTA (which can be done automatically via the System Updater). Only the partial ones won't work.
4) This would be fine. I simply use "dd" to copy the boot.img from my device and patch it then. Either way, it should work. It is a good idea to patch it yourself. A lot of people get Wi-Fi issues etc. as they flash the wrong patched kernel they find. Like an older OOS version or even EU instead of Global etc.