Develop Bugs

[Q] Lollipop OTA Update help! Converted GPE

Running converted GPE 4.4.4, stock rooted (recently followed steps to un-root), S-off (sunshine), Unlocked stock bootloader with CID: GOOGL001.
I received the OTA for 5.0.1 last week and received an error. Is there a way for me to install the OTA without wiping my phone?
I've spent the last week looking over the forums and haven't found an answer. Any help will be appreciated as I really want to avoid wiping to get the update if possible. Thanks!

Are you on stock recovery? I realize if you did the full conversion, it would have installed stock recovery. But just wanted to make sure you didn't flash a custom recovery after that.
Also, on the topic of wiping the phone, I would recommend backing up any important data in any case, if you don't already. There is never a guarantee against data loss even with an OTA; or just losing data from day to day usage for that matter.

Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?

Jamister989 said:
Yea, I'm on stock recovery still. I was hoping to be done with too much modding and wanted to stay completely stock after the conversion, with the exception of root.
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
a recovery.log would be useful here to see where the ota fails.
pure guessing : I think if you've messed with the system partition (SDfix) it is likely what is causing your problem (infamous "unexpected content" error in recovery while installing ota).

I'll post one this evening. Where is a quick explaniation of how to the report?

Jamister989 said:
I'll post one this evening. Where is a quick explaniation of how to the report?
Click to expand...
Click to collapse
what do you mean by 'how to the report?' ?

Jamister989 said:
I did use SDfix: Kitkat Writeable MicroSD which changes some system files so apps can write to the microSD, could this be my problem?
Click to expand...
Click to collapse
If any system files have been altered by root, the OTA will fail. You either need to return the files to the exact "stock" condition, or re-install the stock ROM.

Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.

The SD fix app should have made a back up copy of the original look in /etc/permissions and it's platform.xml the original will have original pre sdfix in the file name..

I had a failed attempt of OTA and it stated that my "platform.xml " was the reason.
Like @graffixnyc said only you you will have to rename the platform.xml to platform.bak and the platform.presdfix to platform.xml as it's the unmodified xml you need.

Jamister989 said:
Sorry, what I meant was, how do I view the Recovery.log? I did a search in root browser and turned up nothing. Cache folder is empty.
Click to expand...
Click to collapse
you can :
- reboot in recovery, try to apply ota, view the recovery.log in recovery menu, adb pull it and eventually post it....
- or assuming your issue is because of the modification of platform.xml as @graffixnyc and @jball stated, switch it with its backup (same dir) and then retry the ota.

System modifications don't stick?

Hi guys, I've looked all over XDA and I can't seem to find anything related to this, so here goes.
I have a rooted HTC One m8 a custom Marshmellow 6.0.1 Rom with TWRP installed.
however, when I try to install mods that modify the system, like busybox or audio mods, they never install and the changes don't stick when I reboot my phone. (e.g; busbox will say it's not installed after I reboot when it clearly has been, but everything done is reverted after I reboot the phone.) Does this mean my phone is NAND locked or something? or does it have something to do with /vendor restoring things? I've looked in /vendor and /system/vendor but none of them have any of the named files busybox or any lib or /etc files that should be replaced upon reboot, so idk where to go from there. Do I just delete the entire /vendor folder?
I really want to get this to work, but none of my mods will install because they keep asking me to install busybox, which I must have done 1,000 times by now, but the changes always revert on reboot.
Can anyone help me please? Thank you

The system is write protected now. You need to flash a permissive kernel. ElementalX works good.

Above suggestion works, or you can also flash the write protection mod (wp_mod) posted in the following ROM thread:
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894

I was looking for that link, but didn't find it. Thanks for jumping in buddy!

[ROOT] SuperSU 2.74-2 With ForceEncrypt Set to Default

Update (May 20): Update to latest version 2.74-2
All versions after SuperSU 2.72 has force encrypt support built in. However it will still disable force encryption by default, you have to set flags manually.
I only modified the default value of the force encrypt flag in the flashing script, so no need to worry that this might break things
If your OCD forces you to use the official version, please look here for instructions to set the flag manually by yourself.
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
I slightly modified the SuperSU flashing script, so now it won't change the encryption flag.
This zip will remain useful until we find a way to decrypt our data partition with working signal.

Hi,
this works without problems, big tanks. Device is rooted now.
regards
starbase64

Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?

MNoisy said:
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
Click to expand...
Click to collapse
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3

datafoo said:
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
Click to expand...
Click to collapse
Yes yes yes please! THANK YOU!
Where can I find them?

Nice buddy, will update the method used in my build, makes life a lot easier.
I had considered making similar modifications but you appear to have beaten me too it

topjohnwu said:
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
Here I come up with a more elegant solution. I slightly modified the SuperSU flashing script, so now it won't change the encryption flag, and also won't remove dm-verify.
NOTE: If your boot image is already modified, it will not reset the flag back to forceencrypt. You have to restore to the stock boot image, then flash this zip. The way I accomplished this is reverting a few modification from the previous ramdisk, so the ramdisk itself has to be stock.
Devs can include this zip into their rom, so users can wipe their whole data with your rom installed.
This zip will be useful until we find a way to decrypt our data partition with working signal.
Click to expand...
Click to collapse
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity

SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.

Chainfire said:
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Click to expand...
Click to collapse
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.

jcase said:
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
Click to expand...
Click to collapse
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.

topjohnwu said:
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
Click to expand...
Click to collapse
I'd have to look at the zip and test to see why. It could be that your particular firmware isn't actually enforcing dm-verity (I believe google mandates this on 6.0+), that HTC disables enforcing when s-off or the zip isn't properly enforcing verity.
Best advice is not to enforce verity on system if you are rooted.
What should (and did for my phone) happen if you have dm-verity enabled on system and a modified system is the phone shouldn't successfully boot.

Captain_Throwback said:
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
Click to expand...
Click to collapse
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.

Chainfire said:
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Click to expand...
Click to collapse
Will that cause complications for users who wipe cache often?

Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?

topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
Will have a bash tonight mate

topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
still no go on boot

LeeDroid said:
still no go on boot
Click to expand...
Click to collapse
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.

Is it OK to use SYSTEMLESS with your current build?
Thanks

ah, perhaps encountered a blarf
you wanna stick with blarp ... he's much nicer

topjohnwu said:
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Click to expand...
Click to collapse
Ahh, I knew why.
I cannot separate the forceencrypt flag patch and verify flag by modifying the script.
Had to wait for Chainfire to release new version, or we have to manually modify the boot image.

Pass safetynet to play PokemonGo on custom ROM.

As title say, it is possible?
I prefer Cyanogenmod or DstrikerZ1.

HoshiYamazaki said:
As title say, it is possible?
I prefer Cyanogenmod or DstrikerZ1.
Click to expand...
Click to collapse
Rootswitch: works fine on stock based Roms.
ISU: works on CyanogenMod based roms
Use those without any issue. U just need to click the button Everytime to TEMP unroot and back again.

I tried Rootswitch on DstrikerZ1, it doesn't work. When I click the switch, it returns to enabled position :/

HoshiYamazaki said:
I tried Rootswitch on DstrikerZ1, it doesn't work. When I click the switch, it returns to enabled position :/
Click to expand...
Click to collapse
See if the log says something about it.
I was on dstrikerz1 004 ROM and used that method (version 3.2.*) till yesterday without any issues.
The script that are used to get it working can be found inside the app. If u execute them directly from a command prompt u can see what the errors are and correct them if necessary. Just make sure u have a system backup with root.

Ok, I will check it.
Do you use any custom kernel? I installed dstriker via aroma without flashing it as tutotial says. I have unblocked bl if you ask.

HoshiYamazaki said:
Ok, I will check it.
Do you use any custom kernel? I installed dstriker via aroma without flashing it as tutotial says. I have unblocked bl if you ask.
Click to expand...
Click to collapse
It doesn't have anything to do with the kernel or the bootloader.
The script should change the name of the "su" binarys, and back again. If stops if it can't do something. But now is the question, what stops the script from running.

Ok, the /system directory (or partition, whatever) is read-only and I can't force it to be rw with app from google play, indeed I don't got access to any recovery.
Maybe is there an option in ROM to modify it?

HoshiYamazaki said:
Ok, the /system directory (or partition, whatever) is read-only and I can't force it to be rw with app from google play, indeed I don't got access to any recovery.
Maybe is there an option in ROM to modify it?
Click to expand...
Click to collapse
Sound more like, u don't have a correct working superuser installed.

It was preinstalled with DstrikerZ1, when my phone charge I will try to analyze the issue.

Ok, I had working PokemonGO to today, now due to Safetynet changes it doesn't work. Probably kernel needs some changes, do you know an fix?

Disable write protection (help)

I have a htc m8 eye . Recently installed twrp and rooted. I tried to delete some apps but after boot they come again. So googled for it and found that we should disable write protection.
Can anyone help me????
Device : htc m8 eye

True, the M8 (and presumably M8 eye) has system write protection, even with unlocked bootloader and root. For the M8, there is a kernel mod that disables system write protection. But the M8 and M8 eye use different kernels, and therefore not compatible. Not sure if the M8 eye has it's own similar kernel mod.
I think some folks may have had luck using a root browser app to enable write permissions to the system folder, then simply delete the bloat apps from the system folder. It's worth a try, anyway.

redpoint73 said:
True, the M8 (and presumably M8 eye) has system write protection, even with unlocked bootloader and root. For the M8, there is a kernel mod that disables system write protection. But the M8 and M8 eye use different kernels, and therefore not compatible. Not sure if the M8 eye has it's own similar kernel mod.
I think some folks may have had luck using a root browser app to enable write permissions to the system folder, then simply delete the bloat apps from the system folder. It's worth a try, anyway.
Click to expand...
Click to collapse
Thanks for reply.
I tried using many root browsers to delete those bloat apps but they come back again after reboot.

Revantark said:
Thanks for reply.
I tried using many root browsers to delete those bloat apps but they come back again after reboot.
Click to expand...
Click to collapse
Are you changing the permissions in the folder from "read" to "read/write" using the root browser apps? This is usually a separate action in the root browser apps.

redpoint73 said:
Are you changing the permissions in the folder from "read" to "read/write" using the root browser apps? This is usually a separate action in the root browser apps.
Click to expand...
Click to collapse
Yes I changed but same problem apps come again after reboot

Revantark said:
I have a htc m8 eye . Recently installed twrp and rooted. I tried to delete some apps but after boot they come again. So googled for it and found that we should disable write protection.
Can anyone help me????
Device : htc m8 eye
Click to expand...
Click to collapse
To delete system apps, boot to recovery (twrp), mount system in mount menu. Then go advance menu, file manager. Browse to system/app or system/priv-app delete any app that you want to delete (I advise you to rename the .apk to .bak, so you can have it back when needed)
Whatever you're going to do, make a complete nandroid back in backup menu first before you start modding.

ckpv5 said:
To delete system apps, boot to recovery (twrp), mount system in mount menu. Then go advance menu, file manager. Browse to system/app or system/priv-app delete any app that you want to delete (I advise you to rename the .apk to .bak, so you can have it back when needed)
Whatever you're going to do, make a complete nandroid back in backup menu first before you start modding.
Click to expand...
Click to collapse
Thanks a lot it worked.
Off topic : Can we install custom Rom (stock modified) on s-on devices??

Revantark said:
Off topic : Can we install custom Rom (stock modified) on s-on devices??
Click to expand...
Click to collapse
Yes. Unfortunately I don't see any custom ROM for M8 Eye on XDA so your own rooted ROM is stock modified the best that you can have.