[Completed] TWRP Write protection preventing flashing / Backup's - XDA Assist

I rooted / S-off and installed a custom ROM from day 1 with this phone (Verizon HTC One M8).
I have been using the phone for awhile and haven't flashed anything. Today, i started looking into upgrading to a new ROM and realized that I needed to update my firmware before hand. I used this to get back to stock with the new firmware - (http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914). I used the SD card and Hboot loaded the RUU from the 0P6BIMG.zip.
I am currently running this official software with s-off and root. I installed TWRP with flashify. I booted in to TWRP recovery and attempted a backup and it failed. I attempted to flash a new ROM (i verified the MD5) and it also failed. After some reading it seem as if the stock HTC kernel has write protection turned off preventing TWRP from accessing these files.
I think i will be fine if i get another ROM installed....The new ROM will have a kernel with write access. I would even be happy with replacing the kernel on the official ROM (therefore enabling write access).
I don't know, I'm stuck. Please help!!!
-Kesnik

kesnik said:
I rooted / S-off and installed a custom ROM from day 1 with this phone (Verizon HTC One M8).
I have been using the phone for awhile and haven't flashed anything. Today, i started looking into upgrading to a new ROM and realized that I needed to update my firmware before hand. I used this to get back to stock with the new firmware - (http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914). I used the SD card and Hboot loaded the RUU from the 0P6BIMG.zip.
I am currently running this official software with s-off and root. I installed TWRP with flashify. I booted in to TWRP recovery and attempted a backup and it failed. I attempted to flash a new ROM (i verified the MD5) and it also failed. After some reading it seem as if the stock HTC kernel has write protection turned off preventing TWRP from accessing these files.
I think i will be fine if i get another ROM installed....The new ROM will have a kernel with write access. I would even be happy with replacing the kernel on the official ROM (therefore enabling write access).
I don't know, I'm stuck. Please help!!!
-Kesnik
Click to expand...
Click to collapse
Yes, seems that you might be right.
Maybe flashing a cusom kernel will be enough to gain read/write access in TWRP recovery.
But first:
Are you on the latest TWRP version? (Check in the Verizon One (M8) Original Android Development > [RECOVERY][m8wlv] TWRP 2.8.3.0 touch recovery [2014-12-22] thread.) There was an update yesterday to v2.8.3.0.
The new version has updated support for latest SuperSu app. Check that you are on the latest SuperSU app (viw Play store) too.
If both versions (TWRP and SuperSU) are up-to-date and you still have the access issue, then you should try to flash a custom kernel.
Check this for available kernels: Verizon HTC One (M8) > Kernel.
And here is a discussion thread about ROMs and kernels for your device: Verizon One (M8) Q&A, Help & Troubleshooting > ROM's and kernel suggestions.
In case that you still have questions or need detailed help, please ask in the Verizon One (M8) Q&A, Help & Troubleshooting forum.

Thread closed and thank you.

Related

[Q] Rooting help

All,
I have just bought a 'new to me' Rogers HTC One X. It already had JB 4.1.1 installed.
I managed to unlock the bootloader via htcdev without issue and managed to flash TWRP 2.3.3 installed via Hasoon2000's tool however it is unusable because the touchscreen doesn't work within it. Is there a work around for this?
I also cannot root the device through the various one-click approaches listed here.
Any help you can offer on rooting it and getting a recovery manager working would be appreciated.
If you need any details from me (various version numbers, etc.) please let me know. I've been out of the Android world for a while so you may need to tell me where to look.
Cheers!
SOLVED
In case others run into this I was able to flash TWRP 2.4.0.0 to the device - touch screen within recovery now works. Once that was done everything was gold: Flashed SU, Viper, and the Viper boot loop fix.
As you have found, root using one-clicks or Hasoon2000's toolkit is not needed on any version except the AT&T variant.
For all other variants (besides AT&T) just unlock bootloader, install TWRP, and flash SU or a rooted ROM.
The problem was the version of TWRP it pushed. I could never flash anything until I updated it so touch worked again.
Sent from my HTC One XL using xda premium

[Completed] [Q] SGS3, CM11 M9, CM Installer, ART/Dalvik Bootloop

Hi,
I have a Rooted Samsung Galaxy S3 (GT-i9300) 16GB Intl. Variant, running "KitKat 4.4.4 installed via CM installer"
I was using 'ART' runtime instead of 'Dalvik' and all seemed to work fine until today.
A week ago I installed "Xposed Framework" to try out some different MODS which still was not a problem. Later I did notice that the runtime reverted back to 'Dalvik' which I wasn't aware of. After doing a Google search I came to know that "Xposed Framework" only works with 'Dalvik' hence I was not able to change back 'ART' through 'developer options', although I have uninstalled 'Xposed Framework'. (Phone only restarts after selecting ART, nothing changes)
Furthermore, I learned that I would require a root explorer to navigate to a system file and rename it back to the original, which was complete bogus as after doing so, my phone is stuck on 'bootloop'.
I am now only able to enter 'Download Mode' and a 'CyanogenMod Simple Recovery <3' which doesn't give me the option to flash a New Custom ROM (Like Nightly, or PA, Omni, etc)
I have already tried, the following methods
1. 'CyanogenMod Simple Recovery <3' (wipe data/factory reset, wipe cache partition, wipe media) still stuck in 'bootloop'
2. Kies 3 (Firmware Upgrade & Initialization) phone cannot be detected.
3. ODIN (phone cannot be detected & also Too Risky)
The biggest fear of mine here is, a year back when I was on 4.1.2 Jellybean, I installed an unofficial release of 4.2.2 from SamMobile and was unhappy with the performance and decided to downgrade back to the official software i.e. 4.1.2 (both were ODIN methods). After successfully doing the downgrade, my phone lost network (causing a generic IMEI) compelling me to visit the service center and have it repaired at a rip-off INR7000 (cost of changing the motherboard).
Therefore, reverting back to a previous version of android is not an option.
Please don't provide me with any downgrades, if anything then it should be Equal or an upgrade!
Thanks in advance for any kind of guidance to a thread or any method to work this out.
Apologies for the long thread. But hope it covers all that is required for a solution.
First and foremost, you need to try and flash a custom recovery such as CWM [i930x][CWM Advanced Edition] PhilZ Touch
Or TWRP [RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]
Once done, you should be able reflash CM 11 as you had before.
If you still have questions, please post in [HELP THREAD] Galaxy S3 Ask any question.
Perseus71 said:
First and foremost, you need to try and flash a custom recovery such as CWM [i930x][CWM Advanced Edition] PhilZ Touch
Or TWRP [RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]
Once done, you should be able reflash CM 11 as you had before.
If you still have questions, please post in [HELP THREAD] Galaxy S3 Ask any question.
Click to expand...
Click to collapse
UPDATE
I just tried using ODIN to flash TWRP/CWM but unsuccessful, the furthest I have progressed is to a point where I get an Error (Line 1949). Searched Google, it turns out to be something that has got to do with Region Specific ROMs. So now we rollback to the point where I would require to re-install the latest update Device Specific & REGION Specific i.e. 4.3 Jellybean/TouchWiz, which would mean downgrading...
Please review [APP][2013.11.04] RegionLock Away v1.3 [ROOT]
Perseus71 said:
Please review [APP][2013.11.04] RegionLock Away v1.3 [ROOT]
Click to expand...
Click to collapse
that review did not help.
Is there any way that I can flash a Custom Recovery on to my phone beside Odin. 'Cause if I'm able to boot into recovery then only I will be able to flash another ROM. Thanks for all the help so far!

[Completed] [Q] Cannot Log into Recovery Mode on HTC One X+

Hi Masters,
I'm kind of new to Rooting Devices stuff.
I own a HTC One x+ International Version 64Gb.
After HTC declared no further upgrade to my device, I decided to go for rooting & custom ROM.
I somehow managed to unlock the bootloader & root the device, however, I am unable to get into the Recovery Mode to flash CM11 on my device.
Tried many options, no success :crying: Every time I try to access Recovery Mode, the device stops at the boot screen.
Bootloader Unlocked using HTCDev Tool
Currently Running 4.2.2
Tried to flash CWM 6.0.4.8
Tried Quick Boot from Play Store - Recovery Doesn't work
Titanium has backed up my ROM.
Please help me to Root this Device to CM11
Hi,
I'm not sure the exact recovery thread you are trying to use, but asking for help in the thread you downloaded it from is your best option.
Or try a different recovery.... Browse through here for others... Read the instructions carefully and follow them exactly. Any issues, ask in the thread you are using.
> HTC One X > One X Original Android Development
Good luck!

how to install android 5.0 for htc one s like?

how to install android 5.0 for htc one s like.
my current machine is using the original room now want to install 5.0 how. machines without root, unlock and install CWM.
who have integrated software for all we ask, to thank everyone help
help me!!!!
You're not being very clear in your question, is your device already rooted or not?
If rooted, go here: http://forum.xda-developers.com/htc-one-s/development/rom-cyanogenmod-12-lollipop-htc-one-s-t2946468
this is a thread about the CM12 rom which works on Android 5.0. You will have to flash the TWRP 2.8.1.1 recovery as said in the Installation Guide (instead of the CWM recovery)
you can download the latest versions of the rom here: https://drive.google.com/folderview?id=0B_THDHRTYTJTNXZBdnZNbFM0VGs&usp=sharing make sure you download the correct version depending on what hboot you have (2.15 or 2.16)
However this rom is not yet a stable finished build, so bugs can occur.
If your device is not yet rooted, and you're not really familiar with it, the best you can do is use the "all in one rootkit for htc one s" which can be found here: http://forum.xda-developers.com/showthread.php?t=1604677
Good luck! :good:
-feel free to hit the thanks button-

[Completed] [Q] HTC one M8 softbrick state. Please help

Hi,
I am first timer in the installing custom rom world and I purchased a factory unlocked HTC M8 and unlocked the bootloader and installed the twrp recovery. few days later I tried installing a custom rom without realizing that my device is S-ON. the ROM i tried installing was not stable, when i tried to install the stock rom back that dosent work either. hence now i am currently in a soft brick state. and would like to know if i could use tools like Sunshine to get to S-OFF state?? I basically would like to able to install a working ROM if not a custom one then atleast get back to the stock version.
Please help.!
Hi there,
All you need is in this threads:
Audio RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
[GUIDE] ADB Workshop and Guide for everyone
For more questions please register an account on XDA and ask directly in this thread:
[HELP THREAD] HTC One M8 - Ask any questions here!
Good luck

Categories

Resources