[Q] Cant get twrp to work... - AT&T, Rogers HTC One X, Telstra One XL

Ok i have been trying to get kit kat installed for two days now. I bought this phone used and it had Cyanogenmod 4.4.4 installed on it. I had to flash an ruu on it in order to unlock it (locked to Telus). That worked perfectly except now i can't get cyanogenmod installed again. I have s-off, supercid, and im on hboot 2.14. I know that in order to flash kk, I need the modified twrp. I can get all the recoveries below 2.7 to work including the regular 2.6.3.0 one. Whenever i flash the modified one using fastboot it just ends up going into a bootloop.(Right now i have no os installed.) This is sooo frustrating.

Try the latest official TWRP for Evita, 2.7.1.0 I believe it is.

mrage said:
Try the latest official TWRP for Evita, 2.7.1.0 I believe it is.
Click to expand...
Click to collapse
No luck, still getting the boot loop.

OMFG I DID IT! What i did was reinstall the telus ruu but then this time i installed all of the ota updates after that. Now all the recoveries install fine. Back to kit kat finally

Related

Finally Got 1.85 Rooted - Can I Update to a Newer ROM?

After much-to-do following the current 1.85 rooting method (http://forum.xda-developers.com/showthread.php?t=1709296) I finally have root. I would like to update to 4.0.4, but am not sure how to do so without losing root/losing 1.85.
A quick nudge in the correct direction would be great, thanks!
Unlock bootloader, install TWRP. Then pick the ROM of your choice from Development. There are stock, but pre-rooted versions of 2.20 and later ones too (2.23, 2.29, etc.) Or flash a custom ROM based on one of the newer firmware versions.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1671237
Don't accept any OTA or run the 2.20 RUU. Either will replace your hboot and render your phone (for now) unrootable.
redpoint73 said:
Unlock bootloader, install TWRP. Then pick the ROM of your choice from Development. There are stock, but pre-rooted versions of 2.20 and later ones too (2.23, 2.29, etc.) Or flash a custom ROM based on one of the newer firmware versions.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1671237
Don't accept any OTA or run the 2.20 RUU. Either will replace your hboot and render your phone (for now) unrootable.
Click to expand...
Click to collapse
Fantastic, thanks. Yeah my previous One X was bootloader unlocked but got a warranty replacement this past week. It has been so long that I can't remember the process I used to unlock it, and didn't know if it still applied.
Where can I get a list of all the boot.img available? I need to flash the 2.29 one, apparently, before the latest CleanROM because I am getting a boot loop when using the boot.img the installer uses.
ifiweresolucky said:
Where can I get a list of all the boot.img available? I need to flash the 2.29 one, apparently, before the latest CleanROM because I am getting a boot loop when using the boot.img the installer uses.
Click to expand...
Click to collapse
An updated list of kernels doesn't exists, that I know of. Scrosler stared this, but hasn't updated it past 1.88.
Try flashing the 2.29 stock rooted ROM. That will get you on the 2.29 boot.img. I'm surprised that installing CleanROM is giving you trouble, although I personally haven't played with CleanROM 4.5 yet. You did a full wipe before flashing (data, cache, Dalvik, system)?
http://forum.xda-developers.com/showthread.php?t=1838135

[ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project

I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
kpaliyath said:
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
Click to expand...
Click to collapse
You must factory reset
Ryuinferno said:
You must factory reset
Click to expand...
Click to collapse
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
kpaliyath said:
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
Click to expand...
Click to collapse
I am not sure as this is device specific... sorry...as long as recovery is compatible it should work
kpaliyath said:
Nope didnt work. Should I have downgraded to JB and done this? I am not sure about that though as the ROM is KK
Click to expand...
Click to collapse
The ROM is KK but it was not designed for the latest boot loader version, I think. The only custom rom that will work with the most recent OTA boot loader are dhacker's test builds
You have to either downgrade the boot loader, use one of the test builds or revert to stock system.
RCOO said:
The ROM is KK but it was not designed for the latest boot loader version, I think. The only custom rom that will work with the most recent OTA boot loader are dhacker's test builds
You have to either downgrade the boot loader, use one of the test builds or revert to stock system.
Click to expand...
Click to collapse
Thanks a lot @RCOO...... I have flashed back Samuri's Stock KK.... I was worried it had hard bricked....
Will try downgrading and then flash back n see what happens....:fingers-crossed:
whao there
kpaliyath said:
I was on the 9.30 OTA and installed the KK ota via @SamuriHL method.... I rooted and unlocked the bootloader.
Next I installed CWM for KK and tried installing Mokee @Ryuinferno. Now I am in a bootloop. What could have gone wrong?
Click to expand...
Click to collapse
i did something very similiar. from what i understand (which isnt muchLOL). but Dhacker29 told me that once you upgrade you have to use the new kitkat bootloader. and the new bootloader only works with roms that have upgraded kernels 3.5 or higher(i think) so right at this momoent there are next to no roms but you can either use stock and modify it yourself or you can give Dhackers test build which isnt bad it has a few bugs but all the hardware works so far and my RAZR HD is playing games it couldnt touch before at all. here give this a try( oh turn off touch sounds to get rid of that anoying popping/cracking sound) i started this thread after having the same issues LMAO in it u will find links to the test rom . hope this helps
http://forum.xda-developers.com/showthread.php?t=2789490
@JohnnyMcG... I did the downgrade and it worked.... Flashed mokee and it works like a charm.
Sent from my DROID RAZR HD using Tapatalk

[Q] How to update HTC One M8 Vzw hboot 3.16 to current?

I am attempting to update my hboot from 3.16 to the current (which I think is 3.19) and I am just not having any luck finding what I need to do. I'm not new to Android at all, just HTC. Is there a firmware.zip that can be used for this in fastboot?
I am trying to update to the newest TWRP so I can flash CM12. I did get TWRP 2.8.x.x flashed but was stuck at the rebooting into recovery screen. Rolled back to 2.7.0.2 for now.
http://forum.xda-developers.com/att-htc-one-m8/help/cm12-htc-one-m8-hboot-3-16-t2986339 I found this thread for the AT&T version, but I know the VZW is a little different. Is there a developer edition for VZW?
MacFett said:
I am attempting to update my hboot from 3.16 to the current (which I think is 3.19) and I am just not having any luck finding what I need to do. I'm not new to Android at all, just HTC. Is there a firmware.zip that can be used for this in fastboot?
I am trying to update to the newest TWRP so I can flash CM12. I did get TWRP 2.8.x.x flashed but was stuck at the rebooting into recovery screen. Rolled back to 2.7.0.2 for now.
http://forum.xda-developers.com/att-htc-one-m8/help/cm12-htc-one-m8-hboot-3-16-t2986339 I found this thread for the AT&T version, but I know the VZW is a little different. Is there a developer edition for VZW?
Click to expand...
Click to collapse
Start here.
http://forum.xda-developers.com/showthread.php?t=2946473
VZW M8 Master RUU/Firmware Collection
Got it updated via your .exe thanks.
Could I update the hboot without having to install a new ROM? Im on OSX so i cant use the exe file.
cBreezy22 said:
Could I update the hboot without having to install a new ROM? Im on OSX so i cant use the exe file.
Click to expand...
Click to collapse
Yes you can. You can use fastboot to flash the 4.4.4 firmware I have posted which would update everything you need to be all up to date with no need to update ROM if you choose not too.
Thank You! Updating htboot solved all the issues I was having. (5mins boot + stuck in recovery boot with latest twrp)
It would appear in my fixing of the hboot I have broken my GPS again. Finally got it working on the ruu, but nothing in cm11.
A factory reset in the stock ROM with stock recovery wipes additional partitions that are vital to GPS. I would try that if wiping is a possibility.
I reinstalled the ruu then wiped and installed cm11 and it is working. Running cm12 now.

[Q] Can't boot custom rom after flashing in TWRP

I've never had issues barging into a development community and going out to the horizon of customization until this cellphone. It's been 12 hours of flashing and downloading and flushing and flashing...
I have S-off and unlocked through SunShine
I use the 0P6BIMG.zip to flash RUU back to the stock verizon rom android 4.4.2
I use 3.28.605.4-firmware.zip from the same RUU thread to update the firmware (???)
I want to install CM12 or liquidsmooth ROM, but I'm getting a hunch at this point I need to start with the stock verizon 5.0.1 installed before that because TWRP wants to patch the system file... But then why am I wiping my system before installing?
I also tried flashing FluentRom_v7.5.zip but I got stuck on the HTC initial screen, I don't even make it over to a boot animation.
What do?
Gevork Gevorkyan said:
I've never had issues barging into a development community and going out to the horizon of customization until this cellphone. It's been 12 hours of flashing and downloading and flushing and flashing...
I have S-off and unlocked through SunShine
I use the 0P6BIMG.zip to flash RUU back to the stock verizon rom android 4.4.2
I use 3.28.605.4-firmware.zip from the same RUU thread to update the firmware (???)
I want to install CM12 or liquidsmooth ROM, but I'm getting a hunch at this point I need to start with the stock verizon 5.0.1 installed before that because TWRP wants to patch the system file... But then why am I wiping my system before installing?
I also tried flashing FluentRom_v7.5.zip but I got stuck on the HTC initial screen, I don't even make it over to a boot animation.
What do?
Click to expand...
Click to collapse
I'm prettly sure you're on an older firmware. You need to be on 5.01 to flash the ROMs you have tried to flash. Use the pre-rooted RUU from this thread here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Also make sure you have the latest version of TWRP.
Edit: The firmware you flashed was 4.4.4
BladeRunner said:
I'm prettly sure you're on an older firmware. You need to be on 5.01 to flash the ROMs you have tried to flash. Use the pre-rooted RUU from this thread here: http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Also make sure you have the latest version of TWRP.
Edit: The firmware you flashed was 4.4.4
Click to expand...
Click to collapse
Thanks for the link that thread and your advice was exactly what I needed.
For whatever reason after using the app/exe to flash 5.0.1 stock-rooted, Liquid Rom failed to install in TWRP. I reflashed the stock-rooted rom and CM-12.1 worked flawlessly. So I'm on CM right now :good: but I'll take another look into Liquid rom. Thanks so much!
Since you like AOSP, I recommend visiting the main m8 thread some other Roms. They are unified builds.

Error executing updater binary in zip

I get this message when I try to flash the new CM12 snapshot on my HTC One M8, SlimROM 4.4.4, with TWRP v.2.8.1.0. When I tried it, I actually had to use an RUU on my phone to get it working again. How do I fix this (not the broken phone, I fixed that).
I've looked into similar threads, and one says I need to update my TWRP, but I can't, because anything above TWRP 2.8.1 doesn't work on KitKat 4.4.4, and I have no idea how I would update my phone past that, since that's what I'm trying to do...
darthnix said:
... anything above TWRP 2.8.1 doesn't work on KitKat 4.4.4, and I have no idea how I would update my phone past that, since that's what I'm trying to do...
Click to expand...
Click to collapse
I'm not so sure this is true. IF there's a point at which twrp is too new to flash a kit Kat Rom then you probably don't have to go back much further than 2.6 or so. If you're looking to get to a newer Rom then I would greatly recommend flashing the 5.0.1 ruu from dottat (to make sure you're on the latest official firmware) and then flashing the latest twrp followed by any one of the great lollipop roms out there.

Categories

Resources