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!
Related
Hello Everyone,
I customized the rom.zip from the official gingerbread update and removed the new hboot. I flashed this new rom to my s-off desire. After that I rooted the rom via recovery by installing su-binary and superuser apk. Everything is fine.
Now I want this nice looking tv/crt animation. I tried this tutorial http://forum.xda-developers.com/showthread.php?t=1109363 but no success...
Any ideas how I can get this working?
Thanks!
sorry for my poor english
Zittermann said:
Hello Everyone,
I customized the rom.zip from the official gingerbread update and removed the new hboot. I flashed this new rom to my s-off desire. After that I rooted the rom via recovery by installing su-binary and superuser apk. Everything is fine.
Now I want this nice looking tv/crt animation. I tried this tutorial http://forum.xda-developers.com/showthread.php?t=1109363 but no success...
Any ideas how I can get this working?
Thanks!
sorry for my poor english
Click to expand...
Click to collapse
how exactly did you manage to flash the update??? Boot partitions have changed so how did you manage to do it?
I read certain posts, that partitions not changed....
as I said:
- I modified the rom.zip with http://forum.xda-developers.com/showthread.php?t=633246 (only small changes, cut hboot off and disabled startup sounds)
- then i flashed the signed zip with clockwork recovery
Everything works fine...
Paul told me the same: Customize the framework-res.apk. I tried it again with a different method, but no success.
Now I read something, that I have to modify services.jar/odex. I deodexed the file, but I have no idea what I have to change there.
Any suggestions?
I found that other devs included this animation in there stock gingerbread roms. i tried to use the framework-res.apk from there rom but nothing happend? I'm doing something wrong?
my steps are:
booting to recovery
mount /system rw
push new framework-res.apk to /system
connect via adb shell
chmod 644 framework-res.apk
rm /system/framework/framework-res.apk
mv /system/framework-res.apk /system/framework/framework-res.apk
untmount, reboot
please any help...
did you find a way
Hi Zittermann,
Did you find a way for getting the CRT screen close on the HTC desire?
I have the GB pre-rooted and would like the CRT off.
Enip
hi evil_nipple,
I didn't found a way yet....
did you try to modify framework-res.apk? I still think this should be the right way, but I think I missed something on this process.
Not Yet but look at this
No I followed the instruction as you.
Been doing a bit more digging and found this http://forum.xda-developers.com/showthread.php?p=15976400
This has some extra steps changing the "build.prop" file, I just checked and this is not in the method you found. Not had chance to try it yet.
hi guys and gals i am taking my first steps into the world of rooting my android phone it is a samsung galaxy note II GT-N7105. well thanks to a few giudes found on these forums it was fairly straight froward(even for me mega noob lol) having rooted my phone i wanted to install a clean blank rom (think that the term for it) i found one, from this site, added it to my interntal memory of my phone, then using clock work recovery mod. phone reboots comes up with lots of difrent opion including install from zip, so follow what it said, got the installed sucessfuly, hit the restart/reboot opion phone boots up and then comes up with android is updating 1 of 84 when it gets to 84 it boots into stock rom with everything still there. having looked around and finding MSKIPS post and His F.A.Q i saw this... I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system.
so i though ah that must be the problem, at least i now know what to do about it, so i first tryed to rename the file in question, no joy still booted to stock. i then tryed to delete the whole file, it deleted and its still deleted but yet same again, reboot.. oh look android is updating. anything else that i could try? thanks inadvance
simon
Hi guys, please direct me to the correct place if this is not it. I am currently running revolt and I want to flash a new ROM. I had a status 7 error, which I have had before and I fixed that by updating CWM. But here is where I get hung up. I get an error that I thought was related to ROM manager not having the correct permissions. I went to update my supersu and give it the correct permissions, but I decided I wanted to change to Superuser and uninstalled supersu. I have now having an error where I can not download anything from he play store because my memory is full. When I check my memory it does not add up. I have 12gb of space and a I am using roughly 4 gb of that. If anyone knows of a way that I can fix the issue so that I can update my CWM and flash a new ROM it will be greatly appreciated!
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Guynan said:
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Click to expand...
Click to collapse
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
eviltweak said:
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
Click to expand...
Click to collapse
That is really confusing. When it says wrong permissions, it won't mean the root managing app has the wrong permissions, it means that the system has wrong permissions somewhere. This cannot be fixed through Supersu or Superuser. If you can still go into recovery, go into advanced, and then 'fix permissions' and that should fix issues if that is what it pertains to.
Because Android it is based off a Linux kernel, it is very picky with the permissions you give it. Too little and it doesn't work. Too much, and it doesn't work.
Let me know how you go.
I don't think I explained this very well in my first post. My issue lies when I try to flash the new version of cwm. I get this screen.
I went into recovery and advanced and I don't have an option that is fix permissions?
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Guynan said:
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Click to expand...
Click to collapse
I am running CMW 6.0.3.7. When I go to advanced all that I see is Reboot recovery, Reboot to bootloader, Power Off, Wipe Dalvik Cache, Report Error, Key Test, Show Log, *******Go back*******.
My recovery works, its just not up to date so when I go to flash a new ROM I get a status 7 error. I have had this issue before and I fixed it by updating my recovery. BUT this time when I go to flash an updated version of CWM I get the screen that I posted above.
the status seven error is usually to do with the updater-script. So make sure the ROM you want to flash is for your device, if it isn't (which may be why you have run into issues) don't flash it. But if you are sure it is, go into the ROM, META-INF>Android>Google>Updater-script (the android and google may be the other way round, it won't take you long to find it) And then open the updater script in a text editing program and remove the first few lines of stuff. It will have the words "assert" "getprop" and looks different to the rest, so just delete that section, and rezip if you have to, and try reflashing. But if that doesn't work and the issues are becoming intrusive, a full reset might be in order.
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.
Hello guys,
I moved yesterday to Android Marshmallow on my Htc one m8 with a customROM and I am just wondering, why I can't delete any system apps. I tried to Google the thing, but I get over and over advertisement and reviews about Android Marshmallow. Nothing that helps.
I tried to delete them with several tools and manually with a data explorer. Nothing worked. It seems like the system is restoring itself. Is there any way to "fix" my problem?
It seems like it's not a device-specific thing, so I've decided to ask in the general Q and A section.. I am sorry, if this wasn't correct.
Thank for any help!
What custom ROM?
This device has write protection on the system partition, even with root. But most custom ROMs have the mod applied to bypass the write protection (and allow such changes). So its surprising to see this issue on a custom ROM.
If using a file explorer, try to change the permissions on the folder to RW (rewrite) and see if that helps.
redpoint73 said:
What custom ROM?
This device has write protection on the system partition, even with root. But most custom ROMs have the mod applied to bypass the write protection (and allow such changes). So its surprising to see this issue on a custom ROM.
If using a file explorer, try to change the permissions on the folder to RW (rewrite) and see if that helps.
Click to expand...
Click to collapse
Thanks for your response!
I am on ViperOneM8 6.1.0...
I have already mount System as R/W in Venom Tweaks.
YEA64 said:
I am on ViperOneM8 6.1.0...
I have already mount System as R/W in Venom Tweaks.
Click to expand...
Click to collapse
Strange, it should work.
Did you dirty flash the ROM? If so, that may have something to do with the bug.
Did you try to mount as RW in the file explorer, as I suggested?
Or you can try to flash wp_mod, which is normally how you would remove the system write protection on the stock Sense ROM: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Highly suggest to make a TWRP backup of you current ROM and user data, before flashing the wp_mod; in case the mod causes any problems. Not sure if this mod will play well with a custom ROM that has all the modifications like Viper.
redpoint73 said:
Strange, it should work.
Did you dirty flash the ROM? If so, that may have something to do with the bug.
Did you try to mount as RW in the file explorer, as I suggested?
Or you can try to flash wp_mod, which is normally how you would remove the system write protection on the stock Sense ROM: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Highly suggest to make a TWRP backup of you current ROM and user data, before flashing the wp_mod; in case the mod causes any problems. Not sure if this mod will play well with a custom ROM that has all the modifications like Viper.
Click to expand...
Click to collapse
No, I did a full wipe before flashing the ROM on a clean, stock ROM. I mounted system as RW in the file explorer, yes, but it didn't work. I am going to look for some other ways, if them doesn't work, I will try the file you linked. Thank for your help and ideas!
Did you look at the Viper thread, to see if its a known problem, or any fixes?
redpoint73 said:
Did you look at the Viper thread, to see if its a known problem, or any fixes?
Click to expand...
Click to collapse
I've searched for "uninstall" and "uninstall system", but it seems like I am alone.
One guy, who had the similar problem, was suggested to use Titanium to uninstall. After that he didn't respond anymore.
Titanium didnt work for me, too.