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!
Related
Dear all,
I am very new to android. I want to change better ROM for my HTC one s.
I have my S3 HTC one rooted with superboot following the below post from paulobrien
http://forum.xda-developers.com/showthread.php?t=1577831
I have installed Goomanager and TWRP recovery.
I want to flash the TrickDroid Rom as follows:
http://forum.xda-developers.com/showthread.php?t=1637102
As tell from the heading, it's compatible for S3 ?
But when I scan the Q & A section, it says "Do not use this ROM if you have an S3 processor based One S"
I m a bit confused for which ROMs are compatible for S3.
It also says " Relying on TWRP to flash the boot.img is not reliable. Please use the Boot_flash_script to flash the boot.img or do it yourself in fastboot. Having an incompatible boot.img is the common reason for being stuck at the boot logo.?
I have stupidly tried to flash it with the boot_flash_Script and it stuck at the boot logo.
is there any compatible boot.img specially for s3 processor which can run for the TrickDroid?
1. If the ROM is compatible with s3, how can I flash it ( I m just a newbie, really need those step by step guides)
2. are there any ROMs which are compatible with s3
3. is there any better method to root from phone in such a way that my phone will be compatible with most of the ROM [stupid enough]
4. anyone having the same case with me? [s3, root by superboot, Goomanager and TWRP]
5. I have flashed it with the boot.img from TrickDroid thread and it was stuck in the htc boot logo, fortunately i was able to boot it by superboot (from paulobrien). But then I cannot use switch on my wifi connection and I need to use superboot (through my computer) to boot my phone otherwise it just stuck at the htc logo.
Is there any method that I can restore my phone (restore to the situation before I flashed the TrickDroid) ?
Sorry, I should have posted this questions under the Trickdroid thread...but i m just too new to post in the development page.
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
Hi.. I'm sorry for the long post, but I've been trying to install a nice Google Play Edition ROM on my phone for 2 days now and I'm hitting dead-end after dead-end. I'm just so tired and frustrated!! :crying:
I have rooted my At&T Galaxy S4 (NC1) using Geohot's Towelroot.
I then installed the TWRP app off the Play Store and used it to "Install TWRP".
At this point, when I tried to create a backup by rebooting to recovery, the phone reboots and it gets stuck with the following message (paraphrasing a bit):
"Unable to perform normal boot. Using ODIN.. Downloading.. Do not turn off device"
I then used the "Home+Vol dwn+Power" combo to reboot back into the stock ROM.
At this point I read about Loki and having to bypass the bootloader.
So I downloaded the loki_tool file from https://github.com/djrbliss/loki and followed the instructions there to create the aboot.img. However, when I tried to created the .lok file from a TWRP 2.8.0.1 open recovery image, it said "Failed to find function to patch". (For this step I tried with both ADB and a terminal emulator on my phone).
On Danvdh's forum http://forum.xda-developers.com/showthread.php?t=2557353, he simply says
"I only support the latest TWRP recovery, AT&T users must loki after flashing
-Full wipe
-Flash ROM
-Reboot"
But I'm not even able to boot into TWRP recovery!!
I don't know what the fundamental problem is and trying to wade through the ocean of information out there looking for a solution is just too exhausting when I don't even know the problem!
PLEASE HELP!!
Thanks in advance!:fingers-crossed:
Hi,
Here is the best place to ask for help with your device,
AT&T, Canadian Bell, Rogers, Telus, Virgin Samsung Galaxy S 4>AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshooting
Good luck!
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.
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