Database Develop

[Q] Returning to un-rooted 5.0 on XT1095?

I'm assuming that since I've rooted my Pure Edition that once the official 5.1 OTA comes it will fail to install just like 5.0-5.02 on my N7 did. I'm wondering how I can get back to unrooted without wiping the phone out (if that's possible). I can't seem to find the factory 5.0 image at the Motorola site so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?
When I ran into this on my N7 other than rooting the only system installed app I had added in was better battery stats and removing root and getting rid of (at least I think I got rid of it) BBS the OTA failed still and I had to just flash the system.img from the factory image. On my XT1095 I only have SuperSU installed. I never installed BBS or any other new apps as system apps so maybe telling SuperSU to unroot and clean up will work?

Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.

Paddington said:
Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.
Click to expand...
Click to collapse
It used to be that way before 5.0. Something changed in 5.0+ and now if certain parts of the file system are off at all from stock, OTA will fail. That's why I mentioned the example of my Nexus 7 failing the update from 5.0 to 5.02. I don't know if Motorola is keeping the same kinds of checks as Nexus OTA's though. I do still have the stock recovery. If I need TWRP for something I just temporarily boot it with fastboot instead.

Any luck with this? I too would like to unroot. Still stock recovery.

flyinion said:
I can't seem to find the factory 5.0 image at the Motorola site
Click to expand...
Click to collapse
Here you go:
http://www.graffixnyc.com/motox.php
flyinion said:
so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?:cyclops:
Click to expand...
Click to collapse
No, 4.4.4 won't boot with the 5.0 boot.img. And NEVER attempt to downgrade the bootloader (motoboot.img) or partition table (gpt.bin) of a Motorola Moto X. These are NOT Nexus devices.

Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Hmm. Not available on that site anymore but found it at http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/

Mnemoch said:
Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Click to expand...
Click to collapse
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.

Thanks for the advice, I will check out MDM and yes, waiting for the OTA to be published officially.
That other link I posted for the full image file was corrupt, but I found http://graffixnyc.com/development/motox2014/lollipop/22.21.11/ which has system.img available. But this is huge! Does it seem correct to you by any chance? Should be able to flash without losing my data?
JulesJam said:
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.
Click to expand...
Click to collapse

Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?

flyinion said:
Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?
Click to expand...
Click to collapse
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all

JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Ah ok, I thought I needed mfastboot from what I was able to read around here. So the standard fastboot that comes with the android sdk can be used on the chunks?

Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?

Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
flyinion said:
Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?
Click to expand...
Click to collapse

Mnemoch said:
Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
Click to expand...
Click to collapse
Oh, the one that doesn't work anymore. I downloaded it a few weeks ago. Not sure when it got taken offline since the link is there, but yeah I see the download doesn't work any longer. If you have just a single system.img and not a bunch of system.img_sparsechunk.n files then you have a different image.

Anyone unrooted since the OTA came out?

JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks

eKeith said:
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks
Click to expand...
Click to collapse
Unrooting using this method does work!

Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.

dcdrew713 said:
Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.
Click to expand...
Click to collapse
Not possible. You have to flash the stock rom first, then take the ota.
Sent from my XT1095 using Tapatalk

Any idea what stock rom to use? 5.0? Sorry, I'm not the best with this stuff anymore, haha.

Update Available 2.19.401.2

Here you can download OTA, fresh firmware or system image to update your device.
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
firmware.zip only [19.6 MB]
2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip [TWRP] [1.15 GB]
Downloads: mega
​Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer. Don't know, what's that. Looks like a hash or a signature.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed). If you want just firmware, take it. Should be fastboot flashable.
*Additional notes*
Next lines describe my experience before I returned the device state to nearly stock.
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.

city2026 said:
OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.19.401.2-2.18.401.3_release_448048.zip [41.2 MB]
Download: mega
Let's see what's underneath
Main difference, I believe, is a security fix (libStageFright). I assume, that's it:
/system/framework/android.policy.jar
/system/framework/conscrypt.jar
/system/framework/framework3.jar
/system/lib/modules/moc_crypto.ko.sig.3.4.10
Zip also contains lots of *.p files (odexes, apk, jars mainly). Viewable through windows explorer.
OTA includes firmware.zip containing {boot, hboot, recovery}, which can be opened through WinRAR (7Zip 15β failed).
*Additional notes*
Hello there. )
Want to share my experience. I have 2.18.401.3 and got promt to upgrade to 2.19.401.2.
Basically, as I get it, you need original recovery and that's it. (Pushed original kernel just in case. Also device is unlocked (tampered))
But under updating process the script mechanism checks some files to be original. Many system odexes, framework stuff and some libs.
My update failed on checking Books.odex (meanwhile, this app was deleted and redownloaded as user-app)
So, I might try to edit updater-script later or just copy files from update to folders they belong. The ota got a simple and obvious updater script for people who used to deal with them before. I'm considering delete parsing part or just push on screen what gives fail, but let updating happen. Need to be tested with system backup.
Click to expand...
Click to collapse
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know

TWRP system backup added
csoulr666 said:
My update stopped for "basicdreams.odex". If you are able to get the update flashed do let the community know
Click to expand...
Click to collapse
I tried to update from recent backup (the one before I changed kernel and deleted system apps), but facebook.odex didn't let me.
Finally, the very first backup did it. I took only system and boot, switched twrp recovery to htc, skipped all setup and installed OTA over fresh system.
Here you go. Now you have TWRP image of this update.
BTW, kernel version is different. CL build number is the same.

Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks

ash0r said:
Hi,
can't I just flash it somehow with TWRP?
The standard update way does not work for me, because of changed *.odex files.
Already tried to flash original recovery etc.
Thanks
Click to expand...
Click to collapse
Unfortunately you cannot flash this with TWRP.

Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks

ash0r said:
Is there a possibility to install this update (or any OTA updates) without having a "not-touched" system?
I could of course flash the TWRP recovery (what I've already done - it worked) but in that case I lose all my modifications. Is it possible to restore the TWRP recovery from that post and afterwards restore my own recovery without overwriting the system files which are needed to be up to date?
Thanks
Click to expand...
Click to collapse
You can try to restore the TWRP backup in the post. And yes, you will lose every mod since it is a backup of the stock, unrooted firmware.
The main problem of flashing the OTA zip would be that you will have to relock the bootloader before installing . So if you unlock it again, the internal storage will be wiped. The best way is to backup everything(Including the internal storage) and then proceed.

Actually, you can save your data while upgrading from non-worthy stock.
So, you may do this
Full backup, you never know what can go wrong.
Save or make a note of what you changed by yourself in system (from busybox to xposed & various modes.). You may use TB for sys-apps and simple file copying for modes. *
Restore updated system image from 1st post, so you have updated system.
See if it worked out and restore/reinstall your other system stuff.
* Remember, you still may access files of your twrp backup images through some archiver. Like I do using 7-Zip.
It's very important to save backup somewhere, cause it might be that my image can be not absolutely clean or can be not absolute right for your phone (like sell location difference). So it'll be easy to return back to working machine.
For this purposes I also setted up my TB for daily auto-backup of texts and settings and weekly backup of apps.
---
Don't sure about relock for upgrading. It seems to be launching, but it needs pure system and original boot & recovery. Some fastboot-magic helps here. That's how I did it after restoring to the very first backup.

So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful

The Watergod said:
So I have build number 2.18.161.3 rooted software on Vodafone, and received an OTA update build number 2.18.161.5-2.18.161.3. Obviously when I come to update it it goes to my custom recovery and can't go any further.
A couple of queries though I wanted to delete all the bloatware from my stock rom, after rooting I found I needed to S-Off as the bloatware keeps coming back on reboot so here are my queries.
Can I delete the APK files from the new OTA update and will this remove them if I install the OTA as a zip through custom recovery. Or can I use this update to wipe the bloatware from it all advice would be helpful
Click to expand...
Click to collapse
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.

My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.

keninzeg said:
My htc one mini 2 is all stock. Software number is 1.16.61.2 and my fon cant to update software. Please help. Sory for my english.
Click to expand...
Click to collapse
Did you buy your phone from a carrier? Carrier phones get different software updates

csoulr666 said:
Did you buy your phone from a carrier? Carrier phones get different software updates
Click to expand...
Click to collapse
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.

keninzeg said:
I bought it used, it has installed EE application from the UK. So is there a way to update. Thanks a lot...
I tried to install OTA_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.16.401.1-1.16.401.2_release from stock recovery and failed.
Click to expand...
Click to collapse
If it has EE applications then it is an EE branded phone. Your updates will arrive differently and will have a different software number. So using the Europe zip will not help.

city2026 said:
For bloatware removal just push a custom boot.img. Liberty kernel or dt2w presented here works fine, you may try them at least with making a backup of original kernel at first. (Custom made kernel might give you permission to write to /system without being s-off.)
I used liberty one, recently flashed the one with double tap to wake, works perfectly fine. Even sd is fine.
I'm not into kernels, perhaps as long as they suit your device they are fine.
OTA have its script, if it has such strings or if you write it into the script, you may delete some apps. Maybe, didn't try nothing with ota scripting. It easier to find working universal bloatware removal script as flashable zip package.
Otherwise, ota just adds some stuff or replaces current stuff.
Click to expand...
Click to collapse
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance

The Watergod said:
Excellent thanks for the reply so in short,
Grab the downloads from above (4 in total?)
Push and override existing TWRP recovery back to stock recovery (Dumbass Details would be helpful as I have not done this in ages)
copy the ADB the new rom to the phone (Again please forgive me as I have not done this in a few years need a memory jog)
Again thanks in advance
Click to expand...
Click to collapse
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.

city2026 said:
If you'll ask more specificly, I'll provide even shorter reply. )
As I get it, you ask for some short check-list / instruction
You need one of three files I uploaded, based on what do you want. )
You can flash big 1 gb system image v2.19.401.2 through twrp.
You can grab small upgrade package and update your 2.18.401.3 by yourself to have 2.19.401.2. Original firmware and fresh rom state might be needed.
You have other needs, you need just freshest kernel or etc., you grab firmware package and try hook it with bootloader or unzip and get the thing you need.
Pick the option and I'll write simple instruction.
I forget to read your previous post. ) So, you have 2.18.161.3 Vodafone. With root privileges (half-root, I assume)
So, yes, you need to restore original recovery of yours. Then it could handle the ota. If you can get it somewhere, you can update. You can get it in vodafone firmware (big package with everything) or if someone made recovery backup earlier.
My upload contains files for non-locked (operator's) devices.
As long as your phone has operator's rom, I can't give you proper advice. I assume, other recoveries/kernels/etc. might not be ok with your device due to hardware lock or difference.
But you can try always, if you sure you can handle it and revert or if you read on your situation enough. I can't advice you here on 100%.
But. If device is just a device, and roms are just roms (and some operator's special version is just a rom), you can flash other system and kernel and see what happens.
You may do a complete backup and save it somewhere and do one of the following:
Flash firmware.zip* contents, then go to TWRP and format all partitions except sdcard, then flash system image from above.
Just flash some custom 5.1.1 release. I use NostromoPop. It much smoother and it's lollipop.
*Firmware.zip contains boot, hboot, recovery. All that was for 2.19.401.2 but presumably can work separate. So you can get what you want and flash through adb. Like boot and hboot for proper device work on 2.19.401.2, or just recovery to try your vodafone ota w/o dramatic changes.
For futher safeness, you can backup hboot and boot or what you want.
I can recommend you to try custom sense-kernel for system write privileges.
Click to expand...
Click to collapse
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved

The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Simply flash custom kernel: like liberty sense or stock sense w/ dt2w.
It will unlock the opportunity to write on every partition. I mean system, cache, etc.

The Watergod said:
Sorry to be a pain and your help is invaluable but just trying not to screw this up, My phone has been unlocked to all networks, and I would like either a stock rom bloatware free or a custom sense rom.
The phone is still S-On but I have unlocked the bootloader (Obviously). I Kept the stock rom hoping to use titanium backup to remove the bloat however I quickly found out the phone needed to be S-Off to remove it completely because as soon as the phone rebooted the bloatware re-installed it's self.
This is how I have the OTA update sat on my phone, I only Rooted for SU privs and put on TWRP everything else was stock. I did as a question in another post "Could I remove the APK from the OTA Zip on my phone then install it using TWRP and would that remove the bloat" but no response to that one.
Any help would be greatly recieved
Click to expand...
Click to collapse
Hi
I will assume you have the virus I have been seeing lately that wouldn't allow you to reset the phone, where in reset option the automatic restore option remains checked and you can't uncheck it.
The only solution is through TWRP, you need to enter TWRP, erase Cache, Data, System then flash the Lollipop ROM again or stock from here: http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743

So there is no Rom available that's pretty much stock without bloatware that I can install with twrp? If not is there some idiots guide to putting my stock recovery back on thank you all again

Anyone know what's in the Verizon Update pushed on 4/12? OTA XT1096

I'm wondering if it's worth it. Version 23.201.2.en.us

I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.

I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?

dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
To take the ota you have to reflash the full 5.1 firmware for verizon.
You can't have root nor a modified sytem for OTAs to work. So you need back all those apps you removed and get rid of root.
Sent from my XT1095 using Tapatalk

jonnythan said:
I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.
Click to expand...
Click to collapse
dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Please review the first post in that thread as the ROM is partially debloated and has SuperSU and Xposed pre-installed. GApps have been removed and you need to install your own. It is possible with the files posted to have a full stock install but you'll need the instructions from that thread to accomplish that.

mikeoswego said:
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Click to expand...
Click to collapse
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.

jonnythan said:
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.
Click to expand...
Click to collapse
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.

mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
Click to expand...
Click to collapse
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?

mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?

dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?
Click to expand...
Click to collapse
jonnythan said:
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?
Click to expand...
Click to collapse
The two smaller zips are the bootloader and modem firmware, the rom and kernel are in the xt1096-5.1-23.32-25-5-2_1.zip file. You could extract the boot.img file from the zip and flash it with fastboot. If you want the full ROM and want to flash SuperSU yourself and remove whatever bloat yourself, then use xt1096-full-stock-23.32-25-5-2.img.7z file; you can flash the image file within that archive with current versions of fastboot. (Or, using 7zip, you could delete the system.img file from xt1096-5.1-23.32-25-5-2_1.zip then rename the .img file in xt1096-full-stock-23.32-25-5-2.img.7z to system.img and place it in xt1096-5.1-23.32-25-5-2_1.zip. Then you would TWRP flash that, it would update your kernel (boot.img) and install the system partition just as if you took the OTA on the stock system.) Like AGISCI said above, the only way to use the OTA directly is on an unmodified stock system.

Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?

jonnythan said:
Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?
Click to expand...
Click to collapse
You must flash the full firmware like was mentioned earlier. It is impossible to do the update with a modified system.
Sent from my XT1095 using Tapatalk

I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.

I flashed the system .img file and it just updated my system without wiping anything. Seems to be working fine, but I had to reflash SuperSU.

desertcat said:
I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.
Click to expand...
Click to collapse
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.

desertcat said:
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.
Click to expand...
Click to collapse
THANK YOU!!! After being stuck on vacation for a week with this !#@[email protected]#$ update bugging me to install it every couple of minutes this fix stopped the problem.

[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps

I am not responsible if you break your phone in any way, these are here for your aid. I will help as much as i can, but it is on YOU, the user to read the OP and understand exactly what it is you are doing at ALL times.
READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS
These can be used to return to 100% stock as long as you can get into fastboot mode on the device, and have unlocked the bootloader and critical partitions. All images contained in the zips are directly from the essential Fastboot zips and OTA's, and dumps for the rest
Prerequisites:
1. Working fastboot environment in bootloader: (test using the command fastboot devices should return your s/n) Windows drivers are at the bottom of the OP.
Essentials windows drivers contain working ADB/Fastboot and places an environment variable to link to these binaries, i would HIGHLY recommend ditching any and all adb/fastboots you may have (minimal, HTC, etc) and use what is supplied by essential, they just work (Not gonna help you either if your hellbent on using your adb/fastboot).
The zips contain all the firmware (19 Images), TWRP11.img (the latest version), and a stockboot.img (so you can conveniently place on your phone and flash in twrp) when rooting with magisk, and boot.fix.red.img (In case you kill verity).
2. Bootloader unlocked: run the command fastboot flashing unlock in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock will relock the bootloader. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
3. Critical partition unlocked: run the command fastboot flashing unlock_critical in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock_critical will relock the critical partition flashability. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
4. Common Sense: Use IT!!!!!
Downloads
Android 10 BTS Folder: https://sourceforge.net/projects/mata-bts/files/10
Q Beta BTS Folder: https://sourceforge.net/projects/mata-bts/files/Q-Beta/
Pie BTS & Novendor Folder: https://sourceforge.net/projects/mata-bts/files/Pie
P Beta BTS: https://sourceforge.net/projects/mata-bts/files/P-Beta/
Oreo BTS & NOVENDOR: https://sourceforge.net/projects/mata-bts/files/Oreo/
The Files below are OLD as dirt BTS
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
OPM1.170911.130 mega.nz (oreo 8.0 beta)
NMK32F AFH (latest nougat 7.1)
NMJ88C mega.nz (nougat 7.1)
NMJ51B AFH (nougat 7.1)
NMJ32F AFH (nougat 7.1)
NMJ20D mega.nz (nougat 7.1)
NMI81C AFH (nougat 7.1)
Drive Folder of Patched Essential Boot images Credit Goes to @dazeone
Some OLD AS DIRT Novendor zips aswell... if anyone still cares
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
Windows Drivers
drivers
Unzip this and check out the flash-all.[bat,sh] scripts for win/lin (they're identical but provided for easier flashability).
They're set up to flash to both slots. Most people will want to do this on a back to stock mission, but they can be adjusted if your goal is something else.
If coming from some other rom, you're also going to want to wipe your data, or you're not going to boot. This can be accomplished by the command in the bootloader: fastboot -w keep in mind there are multiple scripts to wipe for you in the zips.
These can also be used to make custom roms/rooted boot images/etc too, so have fun with it!
Thanks:
@invisiblek - aer0zer0 stole his thread, he put most of it together
@aer0zer0 - i stole the thread from aer0, his 2yr old son makes more use of the PH-1 than he does.
@bmg1001 - Root thread, found here root
@dazeone - Provides independent patched boot images and has an awesome YouTube Channel of Guides! DazeOne Youtube Channel
Enjoy

Heck ya

Yesssss

Ill be giving this a shot in a few days hoping to return my phone back to complete stock.

Hot diggity... been fun reading/watching you all work on this through Discord, think I'll go ahead and unlock it while I still have my S8 in case I trash things

Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.

vekenti said:
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
Click to expand...
Click to collapse
Lineage okay for you lol?
You've got one of the top devs on Lineage working on this so I think you're good.

Thank you! I'll be rooting now that we have a safety net!

I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.

invisiblek said:
So as we're still waiting for Essential to release official factory images, I thought it'd be helpful to link the dumps that we've produced. These can be used to return to 100% stock as long as you can get into fastboot mode on the device.
Click to expand...
Click to collapse
Thanks for this. My fingerprint sensor was not working for some reason after rooting and I thought i would go completely stock. This thread helped me to go completely stock and get the fingerprint back to working.
Thought I haven't locked the bootloader yet. Will try it later.
---------- Post added at 05:55 AM ---------- Previous post was at 05:48 AM ----------
sarcoptic said:
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
Click to expand...
Click to collapse
For flashing to critical partition you need to unlock them. The command is similar to unlock boot-loader.
Code:
fastboot flashing unlock_critical
And to lock it again
Code:
fastboot flashing lock_critical

The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.

sarcoptic said:
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
Click to expand...
Click to collapse
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.

invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Freaking rockstar thanks!

invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Thanks mate.

Thanks for the dump! Just yesterday I was trying to figure out how to do the adb backup command but I gave up cause I couldn't get a good reliable connection to my phone (driver issues, then to failed to connect to device, then to using the adb shell and a mouse on recovery, fun times.)

Great

please can someone guide on how to root it

chambar said:
please can someone guide on how to root it
Click to expand...
Click to collapse
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976

charlie.s said:
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
Click to expand...
Click to collapse
Much appreciated, indeed dunno how i missed it.

free XDA points for @invisiblek .......Thanks for putting it all together, hopefully you can get a teiko sports watch when you turn all the points in, LOL
Seriously, thanks for putting it all together

Backing up stock rom before flashing another

Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though

jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
Search for Huawei ERecovery you may find something useful..

jusumgeezer said:
Hi
I have been following the thread for the linage os in the View 10 forum.
Several people have reported it working on Honor 9 Lite which is treble compatible, before I try it out however I wanted to be sure I could go back to my current rom which is the official LLD-L31 for the UK honor 9 lite.
My current build number is LLD-L31 8.0.0.121(C432)
What options do I have to restore if I don't like the rom I flash?
So far I have managed to pull the System & ODM folders to my pc. all except the Vendor file due to a permissions error.
Is this enough? Can I simply push these folders back? and at which point do I attempt the push? When booted/in recovery etc?
Otherwise, Is there an official or unofficial Huawei/Honor restore tool? or maybe a full rom I can flash? HiSuite says it has this function, but my device isn't listed.
Sorry for all the questions, it's been a while since I flashed a rom & it was always via TWRP I understand treble roms are flashed via the stock recovery though
Click to expand...
Click to collapse
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.

xzyk said:
I have the same model and have also been following the thread. My understanding, and hopefully someone will correct if wrong, is that with project treble GSI you're only overwriting, via fastboot, system.img partition, therefore if you want to return to your original I suspect you can do the same thing again and fastboot original.img with a factory reset.
There is a utility called huawei firmware finder which allows you to look for firmware. I tried it but can only find the LLD-AL10 8.0.0.100(C675CUSTC675D4) which i think is for the 4/64GB veresion or may even be for the huawei P smart. Until honor make the firmware available not sure what other options exist.
BTW it would help if you report back with any success/failures if you try it. Also interested in what this version Lineage OS is missing/not working, I think the camera still has some issues last i checked the thread.
Click to expand...
Click to collapse
Thanks for the reply, I suspected that's how it worked, just flash back the original system image.
I think I'm gonna hang fire for the time being until I know I have the correct firmware to go back if needed, hopefully the camera will be sorted by then too.

I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?

evolucja said:
I flashed a firmware today and couldn't revert to stock because can't find it. Any ideas?
Click to expand...
Click to collapse
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.

xzyk said:
When you unlocked your bootloader and before you overwrote your system partition you should have taken a backup of your stock system partition so you can restore it. Honor has not made the firmware available yet as far as I know.
Click to expand...
Click to collapse
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?

jusumgeezer said:
Just in case I decide to try this, how do I get a flashable file?
I pulled the contents of system + odm via ADB but just ended up with 2.3GB of folders.
Can I convert this to a flashable .img file? Or should I have done this another way?
Click to expand...
Click to collapse
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.

xzyk said:
found description for how to do it for v10 on another site:
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
this implies root is required so I guess you would:
1. unlock bootloader
2. load TWRP.
3. load root (su).
4. reboot back into TWRP and save system.img.
However, you make it work you need to make sure system.img is saved before any changes are made.
Click to expand...
Click to collapse
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go

jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.

jusumgeezer said:
I was thinking about this today & came to the same conclusion.
The idea is to pull a clean unmodified system image, but the only way to do that is by using root privileges SU, then via TWRP - Does that not make it a modified image?
Maybe I'm thinking about it too much:silly:
What Root method & TWRP versions have Honor 9 Lite users had success with? I'm keen to give this a go
Click to expand...
Click to collapse
xzyk said:
Not TWRP as that is the recovery partition (recovery.img) not the system partition (system. Img). Not sure about root though as i believe that does add stuff in one, or more, of the system sub folders, maybe someone else can confirm, but if you're using superuser then unzipping that should tell you what's being added and where. However, if you think about it, this has always been a bit of an issue with any android. You cannot take a nandroid backup without some kind of custom recovery so how can you ever take a snapshot of the stock rom. Specialised tools can do it as they can dump the entire rom but how can any android be dumped in full straight out of the box without first changing something.?
You could try this:
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
but it never really worked properly for me.
Click to expand...
Click to collapse
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin

VigneshS007 said:
Guys TWRP Test Alpha build booted in Honor 9 Lite.
Tonight Stable build with all TWRP features is going to release in XDA i hope so.
Credits to @XePeleato - Team OpenKirin
Click to expand...
Click to collapse
Great, that's good news. Please report back with a link so we can all share. Thanks.

Thanks for the replies everyone.
Great news about TWRP too, I look forward to trying it out.