I want to know (if anyone knows?), precise steps to avoid DM Verity, and root your phone?
Hey, i came here after a long time now, When i had OP3T, i use to root it, it use to have DM Verity issue, at time will prevent me from booting, at times it will boot but message will always appear before booting, it was a mess with encryption.
Then i went Apple Way and life was easy, now again i am with OP5.
I just want to root it,
1) to change fonts, to Roboto Medium, to make them bolder
2) to Freeze batch of Apps with Titanium Backup App
that's it,
What i know? from old experience with 3/3T
1- Unlock Bootloader
2- Flash TWRP
3- Flash Megisk
thats it?
Now my issue is, i don't have much brain/time now a days to tackle DM Verity, BS, which otherwise fine OnePlus has created.
I want to know (if anyone knows?), precise steps to avoid DM Verity, and root your phone?
usmanxhmed said:
What i know? from old experience with 3/3T
1- Unlock Bootloader
2- Flash TWRP
3- Flash Megisk
thats it?
Click to expand...
Click to collapse
That's it.
Pwnycorn said:
That's it.
Click to expand...
Click to collapse
Thanks?
can i also know which step or thing actually cause that (Pain in the Ass)? So we can avoid it from happening?
or by doing above, it will not happen with OP5?
usmanxhmed said:
Thanks?
can i also know which step or thing actually cause that (Pain in the Ass)? So we can avoid it from happening?
or by doing above, it will not happen with OP5?
Click to expand...
Click to collapse
As I said, that's it.
If you stay on stock ROM, there's nothing else to do.
Pwnycorn said:
As I said, that's it.
If you stay on stock ROM, there's nothing else to do.
Click to expand...
Click to collapse
Thanks, very helpful. mate!
If you plan on being decrypted make sure to also flash no verity zip
the_rooter said:
If you plan on being decrypted make sure to also flash no verity zip
Click to expand...
Click to collapse
Why would anyone plan to decrypt? Whats the need?
what is decrypt here? why needed? in lay mans term.
There were roms that will only work on decrypted devices. Once ur decrypted and use that zip u get the benefits of both sides. Stock can't run on an decrypted devices unless u use th no verity zip
Related
For those who didn't know already: yes, there's a way to root Z5 compact with MM. Bootloader needs to be unlocked.
(1) Install Marshmallow. I did it with flashtool. (I used E5823_32.1.A.1.163_1299-0270_R7C)
--> Clean install, if not, you'll get Google Play Store and Google Play Service to be forced to close.
(2) Install another kernel over here. It's AndroPlus kernel, and I choose the latest version (v20).
--> extract boot.img
-->> (in fastboot mode: power down + press vol up + insert USB) fastboot flash boot boot.img
Edit 20/03/2016: Don't use this version of TWRP. It won't work.
(3) Install TWRP over here, like found in this threat. It's TWRP 3.0.0
--> rename recovery.img
-->> fastboot flash recovery recovery.img
(4) Flash SuperSU like you can find here. I flashed v2.65
You can reboot, your Z5 compact will be on Android 6.0 with Root Access.
By the way, read this before you try to install Xposed.
It's possible to install Xposed. I used v80-sdk23-arm64.zip (framework to flash) and XposedInstaller_3.0_alpha4.apk as installer.
thanks for the summary. It might be worth mentioning that there's a way to keep the DRM functionalities with unlocked bootloader, even when the keys are erased. http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Didn't try it for myself, but according to the replys, it looks very promising.
Won't hurt you to mention its for Unlocked Bootloader (UB)...
Thanks for the guide, I'll try this once I get home.
E: Clean install means I should wipe my userdata?
bubimir13 said:
Won't hurt you to mention its for Unlocked Bootloader (UB)...
Click to expand...
Click to collapse
You're 100% right. I didn't think about that, because my bootloader was already unlocked.
Kallu609 said:
Thanks for the guide, I'll try this once I get home.
E: Clean install means I should wipe my userdata?
Click to expand...
Click to collapse
Clean install = you need to wipe userdata (not SD card)
Dirty install = you flash new ROM without changing existing userdata.
So indeed, you need to start on a blank canvas and reinstall your apps.
--> If you're using a password manager, like LastPass or something else, it's way easier to start off from a clean system. If you're not using a password manager yet, maybe it's time to reconsider using one.
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
Weird...
For me, having root access didn't change anything to SD card performance. Which means (for me):
- no problem to install/flash SuperSU using my external SD card.
- no difference after root was installed. I still can flash anything from SD Card.
does it have to be E5823_32.1.A.1.163_1299-0270_R7C?
I'm currently on 32.1.A.1.163_1298_7782_R9C.
should i flash the R7C one?
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
Helleren said:
does it have to be E5823_32.1.A.1.163_1299-0270_R7C?
I'm currently on 32.1.A.1.163_1298_7782_R9C.
should i flash the R7C one?
Click to expand...
Click to collapse
I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)
I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.
toxic_garden said:
thanks for the summary. It might be worth mentioning that there's a way to keep the DRM functionalities with unlocked bootloader, even when the keys are erased. http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Didn't try it for myself, but according to the replys, it looks very promising.
Click to expand...
Click to collapse
The solution to restore drm functions is already included in the Andropluskernel
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
For me sdcard is working normally under Marshmallow, but can't be mounted in TWRP
--jenana-- said:
I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)
I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.
Click to expand...
Click to collapse
Allright,I'll give it a go with the Nordic combined firmware.
Has anybody tried to encrypt after rooting?
Anybody knows if this could work on a E5803 model?
Sent from my E5803 using Tapatalk
I don't really understand the Kernel stuff. But would this just be a workaround to get root for now?
Is it stable?
Would you recommend waiting for a future release?
Thanks!
vibo2013 said:
The solution to restore drm functions is already included in the Andropluskernel
Hang on.... so do i have to follow the guide to update the drm functions or you saying the kernel already has this built in? as in all i need to do is flash the kernel and rom
And can i backup my TA like on the z1c.
Thanks
kam
Click to expand...
Click to collapse
do_salah said:
vibo2013 said:
The solution to restore drm functions is already included in the Andropluskernel
Hang on.... so do i have to follow the guide to update the drm functions or you saying the kernel already has this built in? as in all i need to do is flash the kernel and rom
And can i backup my TA like on the z1c.
Thanks
kam
Click to expand...
Click to collapse
"...Added DRM functions restore patch (thanks tobias.waldvogel)
--This is just a fallback and you have to delete contents of /data/credmgr to enable restore patch...."
Thats what the Changelog on the Androplus Kernel Website says
Click to expand...
Click to collapse
For me scared is working to! I also did not wipe my user data. I just flashed the german vodafone firmware over my existing LP 5.0.2 using flashtool, which kept all my apps. The rest was done as described in the first post. The only app which caused trouble was spotify, I just reinstalled it and everything was fine ...
kevinwu128 said:
I don't really understand the Kernel stuff. But would this just be a workaround to get root for now?
Is it stable?
Would you recommend waiting for a future release?
Thanks!
Click to expand...
Click to collapse
No, nothing about this is stable.
-- Dirty flash of MM could mean that certain apps or parts of the system become unstable.
-- TWRP 3.0 is only released a few days ago. Could contain bugs, who knows...
-- AndroPlus kernel is work in progress. Literally "status: testing". And for more info about that kernel, you can always read/ask in that threat (I don't know the ins and outs of kernels at all)
-- Xposed + it's modules: all work in progress. Some could be stable, some could be buggy.
For now, this is a way to get root. Maybe other developers come with different methods to root, maybe not. But getting root access means: f*ck*ng around with your system on the deepest possible level and breaking some "stability" sony intended to give us. If you would like to take advantage of what root access can give you: give it a try. If you're afraid to break anything: stay away from it or be prepared that you'll have to start over from scratch.
Yes forgot that to clear. Sdcard is working in running system, but not in twrp. Thats no big deal, only nice to know...
And I've tried it german customied did work.. Schud not make any difference as long as it the same version number...
Drm restoration I couldnt check until now.
Nice that I now can restore my app data with titanium backup
---------- Post added at 12:25 AM ---------- Previous post was at 12:20 AM ----------
--jenana-- said:
Weird...
For me, having root access didn't change anything to SD card performance. Which means (for me):
- no problem to install/flash SuperSU using my external SD card.
- no difference after root was installed. I still can flash anything from SD Card.
Click to expand...
Click to collapse
I'll think I have to try again. Perhaps the first boot something was going wrong.. But I couldn't access sdcard and flash supersu from the card with twrp. SoI booted, copied supersu to internal "sdcard" and from there it worked.. I also tried to mount sdcard.. No reaction (but also only at first boot)
--jenana-- said:
No, nothing about this is stable.
-- Dirty flash of MM could mean that certain apps or parts of the system become unstable.
-- TWRP 3.0 is only released a few days ago. Could contain bugs, who knows...
-- AndroPlus kernel is work in progress. Literally "status: testing". And for more info about that kernel, you can always read/ask in that threat (I don't know the ins and outs of kernels at all)
-- Xposed + it's modules: all work in progress. Some could be stable, some could be buggy.
For now, this is a way to get root. Maybe other developers come with different methods to root, maybe not. But getting root access means: f*ck*ng around with your system on the deepest possible level and breaking some "stability" sony intended to give us. If you would like to take advantage of what root access can give you: give it a try. If you're afraid to break anything: stay away from it or be prepared that you'll have to start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, i can't stand lollipop anymore so i'll give it a try ! I'll update once done!
Hey everyone!
In the 6 years or so that I have been rooting/unlocking the BL, this thought has never crossed my mind, until now. Unfortunately, there are some apps I need to use that wont work with rooted phones. I think this is incredibly [email protected]*king dumb, but there is nothing I can do about that.
SO the question I have is there a way to disable the root/unroot the phone/make apps think the phone is unrooted for just a few mintues so I can use the app, then quickly put the root back? Any thoughts, insights, advice, etc. would be helpful.
Thanks!
Try "magisk"
android404 said:
Try "magisk"
Click to expand...
Click to collapse
I have magisk (it was part of the rom I use) but I have to be honest, I am not familiar with using it. I googled it a few times after installing the ROM, but couldn't see what it would do for me. Can you explain to me how to use it for this?
shiboby said:
I have magisk (it was part of the rom I use) but I have to be honest, I am not familiar with using it. I googled it a few times after installing the ROM, but couldn't see what it would do for me. Can you explain to me how to use it for this?
Click to expand...
Click to collapse
Actually I can't, I just think that it's your only option to be rooted without being detected. The op of this thread seems pretty straightforward: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Good luck.
android404 said:
Actually I can't, I just think that it's your only option to be rooted without being detected. The op of this thread seems pretty straightforward: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Good luck.
Click to expand...
Click to collapse
hmm...I read through it, but don't see how...I'll play around with it a bit. Maybe in the meantime, someone else can tell me exactly what I need to do.
shiboby said:
hmm...I read through it, but don't see how...I'll play around with it a bit. Maybe in the meantime, someone else can tell me exactly what I need to do.
Click to expand...
Click to collapse
A. Hide root with magisk
1. open magisk manager, magisk hide
2. Select what apps you want to hide from root detection
3. Reboot
B. Unroot. Uninstall magisk
You can install magisk later for root
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...
HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.
Hey guys , Since I upgraded to Nougat, my phone is pre-encrypted and why can't I decrypt it? Why is it like this? I want to decrypt it so that my phone will be a little faster. So how can I decrypt it?
Unlock, install twrp and format data.
lafester said:
Unlock, install twrp and format data.
Click to expand...
Click to collapse
Can't I just do it without unlocking? I can encrypt and unencrypt the phone easily(factory rest) on all my other devices?And any clues why is it pre-encrypted?
I suppose you could try a factory reset in stock recovery.
lafester said:
I suppose you could try a factory reset in stock recovery.
Click to expand...
Click to collapse
I've reset factory a couple times but that option is not choosable and it is written encrypted.
I mean I haven't even encrypted my phone ever , so why is it encrypted?Is it done automatically? What about yours?Is it pre-encrypted too?
It was...
lafester said:
It was...
Click to expand...
Click to collapse
I guess you've got the G or U model?right?(mine is A2017)
Boot into TWRP and change the data partition type from f2s to EXT4.
Double tap screen awake
My phone double tap screen awake doesn't work since these updates what can I do.It's a axon 7 2016 model..
Paulkdixon96 said:
My phone double tap screen awake doesn't work since these updates what can I do.It's a axon 7 2016 model..
Click to expand...
Click to collapse
I think you are in the wrong thread.
Aj-jss said:
I mean I haven't even encrypted my phone ever , so why is it encrypted?Is it done automatically? What about yours?Is it pre-encrypted too?
Click to expand...
Click to collapse
Zte stock rom comes pre-encrypted on every new install. The only way to bypass it is to edl flash a stock rom with twrp. Boot right into twrp after the flash. Find a modded stock boot.img that has a modded fstab, flash it, then boot and your phone will be unencrypted with the stock rom.
Thank you all. I'll do as you said and unencrypt it.
DEAR ZTE CUSTOMER,
Pls describe clearly about the situation of your encrypted phone, because our developer confused about such encrypted issues. BTW, please provide your phone'IMEI.
Thank you!
William Guo said:
DEAR ZTE CUSTOMER,
Pls describe clearly about the situation of your encrypted phone, because our developer confused about such encrypted issues. BTW, please provide your phone'IMEI.
Thank you!
Click to expand...
Click to collapse
No issues. It is encrypted by default in stock ROM.
This guy seems to be spamming and looking for imei info.
Mine is encrypted. Brand new out of box, updated to B10 MM then to B04 Nougat 7.1.1
What are the implications of it being encrypted? Mine is remaining stock, not even TWRP recovery or root. I'm happy if it's secure as I have personal and work SIM in it and will be using a couple of apps that look for root. Kind of tired of modding phones, just want life to be simple and reliable, able to take updates when I like. The work Nexus 5X was a ****ty phone but I got used to it being updated. It's a rare one that doesn't bootloop and is on Oreo but I hate carrying two phones thus the reason for buying the Axon 7 for dual SIM.
RobboW said:
Mine is encrypted. Brand new out of box, updated to B10 MM then to Nougat.
What are the implications of it being encrypted? Mine is remaining stock, not even TWRP recovery or root. I'm happy if it's secure as I have personal and work SIM in it and will be using a couple of apps that look for root.
Click to expand...
Click to collapse
I don't believe you'll get more performance out of an unencrypted phone, or not enough to justify it for that matter. also, on some phones you need it not to be encrypted if you want to see the internal storage in TWRP, but on this phone it doesn't happen.
You can fix it in your settings--hand design(sort of, I guess),or you can update the latest version from ZTE office website. Good luck!
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Could anyone verify?
Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.
yes it is for aljeter and is working fine
Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?
Anyone get this working with the xt1922-7?
Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.
picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.