Database Users

M8 Eye Recovery and Root

Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks

This update supersu no longer works. I installed that twrp and did the process for that version of supersu and it said successful. Upon checking supersu, it says the binary files are missing. Then I installed the newer supersu verison through twrp, without deleting the old supersu and now the phone is stuck on htc boot screen. This may work for some, but DO NOT install another supersu over an old one without deleting it first. You WILL get stuck on boot.

Weisheit7 said:
Then I installed the newer supersu verison through twrp
Click to expand...
Click to collapse
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.

redpoint73 said:
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
Click to expand...
Click to collapse
You're right, and as of right now I have a different issue. I found a link for the Chinese ROM of the htc m8 eye and I successfully installed it. Now the device is on 4.4.4 rooted. I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
How can I fix the OTA problem through stock recovery? I checked the /system/bin/reboot file and there's nothing there specifically that I can see is corrupted or changed. Is there any possibility that supersu has system permissions and is causing this error? If so, how do I fix the /reboot has unexpected contents problem? How can I delete supersu (su) from having system permissions over everything?
I cannot find a stock Chinese ROM for this device, only the rooted one. I'm at a loss here..

Weisheit7 said:
I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
Click to expand...
Click to collapse
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.

redpoint73 said:
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
Click to expand...
Click to collapse
I've read online that if you unroot it the OTA update should go through. It depends on how the root was done, correct? If root has (owner) permissions over system files, how can I put it back to stock? Are you aware of any HTC One M8 eye mels_tuhl stock rom China region? I've scoured the internet forever and cannot find one. If you need my getvar info I'll post it here and I appreciate any help you can potentially give me.

Weisheit7 said:
I've read online that if you unroot it the OTA update should go through.
Click to expand...
Click to collapse
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Weisheit7 said:
It depends on how the root was done, correct?
Click to expand...
Click to collapse
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Weisheit7 said:
Are you aware of any HTC One M8 eye mels_tuhl stock rom China region?
Click to expand...
Click to collapse
Unfortunately, no.

redpoint73 said:
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Unfortunately, no.
Click to expand...
Click to collapse
Thanks for taking the time to reply. Since then I have corrected the problem. I downloaded a TWRP backup of Marshmallow from another user on here in a different thread, placed it into my TWRP backup folder, wiped system, internal storage, cache etc and then flashed the backup. Everything went well...marshmallow is on the phone and root is gone.

necaticetinkaya said:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
Click to expand...
Click to collapse
Can you provide another share of the file? The previous link has expired

Factory images with January security patch now available

This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?

Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?

simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.

Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out

Everything's fine for me.

FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.

Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk

anyone having trouble downloading the new system image from the site?

simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.

maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.

Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk

tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance

i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.

daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ

Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

How to restore IMEI number on a official rom?

okay now I am starting to get lost and the guide for ''fixing your IMEI number'' caused my phone to soft-brick once again so it didn't really help
and yes I used the most recent SuperSU (stable) version V2.78 (I hope that is a correct version)
http://forum.xda-developers.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
my baseband gives a I think correct version but my IMEI number still is ''0''
Please!, can anyone tell me how to restore my IMEI number?

Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed

dempixels said:
Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed
Click to expand...
Click to collapse
Did you try to make a complete reset of the phone?

Dio-Genes said:
Did you try to make a complete reset of the phone?
Click to expand...
Click to collapse
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it

dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.

dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486

Dio-Genes said:
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''

bablu048 said:
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.
Click to expand...
Click to collapse
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.

dempixels said:
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.
Click to expand...
Click to collapse
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
Have you downgraded earlier??

dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.

Dio-Genes said:
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.
Click to expand...
Click to collapse
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
also some further info:
I think in the past when I tried to install the official stock rom. I accidentally removed/erased the EFS file. or some file that holds my IMEI information.
and now I practically have to re-write it (since.. well you can't just create a IMEI ID or Can I?). but it seems impossible if I look at it.
but I do have the original box with the original IMEI number.

bablu048 said:
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Have you downgraded earlier??
Click to expand...
Click to collapse
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?

dempixels said:
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
.
Click to expand...
Click to collapse
Sorry, that's beyond my knowledge.

dempixels said:
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?
Click to expand...
Click to collapse
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.

bablu048 said:
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.
Click to expand...
Click to collapse
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that

dempixels said:
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that
Click to expand...
Click to collapse
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
alright 2 final questions before I am gonna start the whole flashing again
1. does this superSU version work with 6.0.1? (just to be sure)
2.what does it backup to be precise? only the system or everything (probably everything)

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
YES!! it's rooted thanks for the guide but now... ermm.. how do I change my IMEI number?

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?

dempixels said:
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?
Click to expand...
Click to collapse
you dont have su app even after flashing su2.62-3??

[OTA] Marshmallow Build MCG24.251-5-5

Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.

TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.

ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.

TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?

3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.

TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?

koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.

Yee!

I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk

mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795

I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia

I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.

Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.

So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store

TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk

mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.

trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.

Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason