Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
I made a stupid mistake when unlocking my DNA and flashing a custom ROM (ViperDNA 4.1). I ran the rumrunner S-OFF which seemed to go without flaw. The mistake I made was checking to see if root installed which I'm assuming now it didn't. I installed Clockwork Recovery on it and booted into recovery and installed ViperDNA which gave errors. When I rebooted I was stuck at the boot splash. I tried an unbricking method posted on YouTube that required going into Fastboot USB and running an OEM Lock command and then using HTC's ROM update utility to reflash stock back to it which failed. I've rooted and flashed recovery to a lot of devices so I wouldn't consider myself to be a total noob but I'm at a loss here. Any help would be greatly appreciated! :fingers-crossed:
Black htc screen with triangles on each corner
Man I really need help. ...I tried to flash and something went wrong to where I erased the entire os and I continued to fix this issue because all I had access to was twrp(custom rom) and bootloader. then what was crazy is that it appeared that based on the fact that I was on 4.4.2 kit kat that I was unable to fix it. after researching I found a ruu that didn't have the boot image so I flashed the factory ruu with no boot image and my htc scrren with the status bar filled all the way up but it never moved off of that screen I assume because that ruu didn't have the boot image so I thought that common sense would be to at one of the boot images that I had to the zip file of the ruu without the boot image....that's when I made things worst and now im stuck on this htc screen with the four triangles...my pc wont detect my device and im in need of some serious help....can you help? can anybody help?
I believe i can help!!!
jazoon said:
i made a stupid mistake when unlocking my dna and flashing a custom rom (viperdna 4.1). I ran the rumrunner s-off which seemed to go without flaw. The mistake i made was checking to see if root installed which i'm assuming now it didn't. I installed clockwork recovery on it and booted into recovery and installed viperdna which gave errors. When i rebooted i was stuck at the boot splash. I tried an unbricking method posted on youtube that required going into fastboot usb and running an oem lock command and then using htc's rom update utility to reflash stock back to it which failed. I've rooted and flashed recovery to a lot of devices so i wouldn't consider myself to be a total noob but i'm at a loss here. Any help would be greatly appreciated! :fingers-crossed:
Click to expand...
Click to collapse
look at my situation (right below yours) i just got myself out of that situation everything is back to stock and at least i have a fresh start...whats your current status?
CHRIST STARZ said:
look at my situation (right below yours) i just got myself out of that situation everything is back to stock and at least i have a fresh start...whats your current status?
Click to expand...
Click to collapse
I had the same problem last night. I couldn't get fastboot to work properly and thought I was screwed. Here is what I did:
I downloaded a stock rooted rom and put it on a flash drive. I used my USB OTG cable and booted into recovery. I then mounted the external drive and flashed the stock 4.1 rom back on it and that cleared it up. I haven't re-tried to flash the ROM I tried, but I think my issue was an old recovery version.
Once you get back to stock, update or change your recovery to a new one and then try again would be my suggestion.
If you don't have an OTG cable, I'd suggest at a minimum order one for when it happens again
Hi everyone, so this is my first post here on Xda, heard a lot of good things though
Anyways, I just re-rooted my HTC One M8 at&t model for the second time, I have rooted before, but had some issues so I decided to unroot and relock it, that is until today, when android 5 came out for the developer edition I decided I would try to convert mine so I could install the official ota.
So I unlocked my bootloader and flashed
./fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.IMG
Said it wrote it successfully, so I tried to boot into recovery to flash super su.
When I tried however, it just sat and hung at the "entering recovery" screen.
I held down the power and volume up to get back to my home screen and retried after booting back into the bootloader.
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Is it possible that somehow the old version of TWRP from my previous rooting experience is creating conflict with the one I just flashed? I'm really new to all this, so thanks for putting up with my uneducated self
Any ideas?
Thanks in advance!-Z
PR4X15 said:
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Click to expand...
Click to collapse
Right, as long as its not meant for CDMA or the dual SIM version, you are good to go.
Failure to boot into recovery from bootloader can usually be solved by fastboot erase cache, and install TWRP again. Probably just a problem with TWRP not being properly installed the first time around.
Or even try an older version. TWRP 2.8.4.0 is really new, so maybe there are issues.
Q&A for ★ ☆ [ROM/RADIO][4.4.2] Stock 4.09.605.5 | Rooted | Sense 5.5
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for ★ ☆ [ROM/RADIO][4.4.2] Stock 4.09.605.5 | Rooted | Sense 5.5. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
bootloop when flashing 4.09.605.5 Rooted to DNA using CWMR
Hi there, long time follower of these forums, first time posting. I can usually find what I need but I couldn't in this case. My primary question is, do I HAVE to flash the ROM zip with oem RUU?
I am unlocked with s-off. I installed CMWR and CWM SU. For some reason I originally thought I had to install the ROM update before the updated FW. I tried to Flash odex debloated update with CWM (selecting option in Rom Manager to delete data and cache before flashing), but it boot loops on white htc splash screen. I recovered/restored previous image via CWMrecovery. I installed CM11 (4.4.4 base), then flashed RUU via fastboot, in order to install new FW via fastboot (had to flash twice, just like instructions state), rebooted into CM11/4.4.4, FW seems to have installed fine. Flash CWM recovery again, make ROM backup. Tried to flash odex/debloated 4.09.605.5 with CWM (again selecting delete data / cache before flashing), but now freezes on the black/red android eye every time I try to boot. Tried to flash full odex with CWM (after full wipe again), again it freezes on the black/red android eye screen. Each time it freezes or bootloops I am at least able to reboot into recovery and revert to CM11. I recovered to my original backup (rooted stock 4.2.2), verify it shows I have the updated radios, and from there try to flash the full odex update (without wiping data/cache this time) through CWM since I have the updated FW. Bootloops on HTC splash screen, as it did before. Then I wiped everything and restored to CM11/4.4.4 ROM.
I am afraid that if I fastboot flash the update with RUU and I get bootloops or frozen boot that I won't be able to recover from it, unless the answer is that I have to do it that way.
ra2dc said:
Hi there, long time follower of these forums, first time posting. I can usually find what I need but I couldn't in this case. My primary question is, do I HAVE to flash the ROM zip with oem RUU?
I am unlocked with s-off. I installed CMWR and CWM SU. For some reason I originally thought I had to install the ROM update before the updated FW. I tried to Flash odex debloated update with CWM (selecting option in Rom Manager to delete data and cache before flashing), but it boot loops on white htc splash screen. I recovered/restored previous image via CWMrecovery. I installed CM11 (4.4.4 base), then flashed RUU via fastboot, in order to install new FW via fastboot (had to flash twice, just like instructions state), rebooted into CM11/4.4.4, FW seems to have installed fine. Flash CWM recovery again, make ROM backup. Tried to flash odex/debloated 4.09.605.5 with CWM (again selecting delete data / cache before flashing), but now freezes on the black/red android eye every time I try to boot. Tried to flash full odex with CWM (after full wipe again), again it freezes on the black/red android eye screen. Each time it freezes or bootloops I am at least able to reboot into recovery and revert to CM11. I recovered to my original backup (rooted stock 4.2.2), verify it shows I have the updated radios, and from there try to flash the full odex update (without wiping data/cache this time) through CWM since I have the updated FW. Bootloops on HTC splash screen, as it did before. Then I wiped everything and restored to CM11/4.4.4 ROM.
I am afraid that if I fastboot flash the update with RUU and I get bootloops or frozen boot that I won't be able to recover from it, unless the answer is that I have to do it that way.
Click to expand...
Click to collapse
Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
santod040 said:
Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
Click to expand...
Click to collapse
tarp? was that an auto-correct fail? the only thing I could dig up as what you might have meant is TWRP, have never used it before, but should I flash TWRP if I'm on CM11, and then flash the odex debloated rooted 4.09 ROM directly from CM11, or should I recover to stock (rooted) 4.2.2 first and then flash the update with TWRP? Should I do a full wipe? I assume if I'm doing a full wipe it doesnt matter where I'm coming from (which means I can try right from CM11), and I also assume I can flash TWRP while on CM11, but haven't tried yet.
thanks for the answers
santod040 said:
Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
Click to expand...
Click to collapse
Thanks I tried with TWRP and at first I thought it froze again on the android eye, so I restarted and it froze again, but I put my phone down and left, came back in 10 minutes and it was on the home screen. It must take a while to boot the first time, doh! Maybe CWM actually worked and I was just impatient.
Now I have new issues though, adroid wifi tether app doesn't work (I've read many blogs, I tried all of the suggested settings), it starts with errors but the log doesnt record anything, and I get terrible reception. Maybe I'll try the debloated but that probably won't fix the reception thing. Verizon says I might have to factory reset, but I don't know how that will impact my root-ability
ra2dc said:
Thanks I tried with TWRP and at first I thought it froze again on the android eye, so I restarted and it froze again, but I put my phone down and left, came back in 10 minutes and it was on the home screen. It must take a while to boot the first time, doh! Maybe CWM actually worked and I was just impatient.
Click to expand...
Click to collapse
I've seen the same thing after flashing certain things - adb shell "top -m 10" revealed that it was dex2oat which I believe is handling one-time code compilation on first boot. Eventually the GUI loads and I see "android is upgrading (apps)..." for part of the first boot process.
ra2dc said:
Now I have new issues though, adroid wifi tether app doesn't work (I've read many blogs, I tried all of the suggested settings), it starts with errors but the log doesnt record anything, and I get terrible reception. Maybe I'll try the debloated but that probably won't fix the reception thing. Verizon says I might have to factory reset, but I don't know how that will impact my root-ability
Click to expand...
Click to collapse
Factory reset should not impact your root-ability but mostly the same system software will be running afterward so I find it rarely resolves core issues with ROM compatibility or my installation of it. Might be worth a shot tho, I suppose clearing out device settings and such could help fix tethering.
firmware update question
First...A big thank you for all the tremendous development work!
Wanted to report a curious thing. When I updated firmware using 4.09.605.5 NoBootImg_firmware.zip; it finished in one step without stopping. Never asked to "flush again" as mentioned in the OP. So I was just wondering if I did something wrong. After reboot, the phone now shows the updated baseband 1.02.01.0818. So far, seems like all is in order. Any comments would be greatly appreciated.
DNA (HTC6435LVW) RELOCKED S-OFF problems flashing to rooted stock
First time poster on XDA. Please forgive any impropriety!
I went through the process of flashing the 4.09.605.5 Rooted Full Odex Stock Kitkat (RUU RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2.exe) and latest firmware for the DNA from this thread. Everything went fine but when I tried to boot into stock the Verizon splash screen came up for a second and then the image became scrambled and then nothing. I waited for several minutes to see if the phone would boot to the Stock rom but didn't.
My phone is a relocked s-off DNA currently running latest version of CM and TWRP. More phone details:
hboot 1.57
radio 1.02.01.0818
CM 11-20141112-SNAPSHOT-M12-dlx
kernel 3.4.10-CM
Here's the steps I followed:
Downloaded latest stock RUU rom ( RUU RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2.exe) from this thread - http://forum.xda-developers.com/showthread.php?t=2560010
Downloaded latest firmware from same thread - 4.09.605.5_NoBootImg_Firmware.zip.
Verified MD5 on both downloads
Boot into fastboot
Successfully flashed latest firmware via fastboot RUU
Boot into TWRP
Wiped phone from TWRP
Successfully flashed latest stock rom via TWRP
Reboot phone
Stuck on scrambled Verizon splash screen
I was able to restore my CM rom from backup using TWRP, but I'd really like to go to rooted stock because some functionality is missing in CM (headphone jack doesn't work for one thing, intermittent radio/3g issues).
Thanks in advance for any help you can provide!
DNA (HTC6435LVW) RELOCKED S-OFF problems flashing to rooted stock
I'm familiar with flashing custom roms/recoveries and have been doing so for a few years now with no problems. I have a DNA that is Relocked with S-Off. Recovery is ClockWorkMod recovery. Backups and restore of CM 11 ROM works fine. I've been having intermittent problems with signal strength and 3G as well as headphone jack doesn't work with CM, so I decided to try going back to a rooted 'stock' ROM which I found at http://forum.xda-developers.com/showthread.php?t=2560010. I flashed the latest firmware update from the same thread. Then I downloaded the file marked "4.09.605.5 Rooted Odex Debloated Stock Kitkat" and installed it from CWM with no problems. I did a wipe data/factory reset before I flashed the ROM as suggested. When I attempted to boot up to the new ROM it got stuck on the Verizon splash screen. The splash screen came up and almost immediately the image became scrambled (no, not like eggs . I waited about 5 mins for it to come up and then forced a hard-reboot into CWM by holding down the power button and reflashed my backup of CM 11.
Anyway, anyone have any ideas on what I can try to get the stock rooted ROM image up and running?
Current system is...
HBOOT 1.57
RADIO 1.02.01.0818
S-OFF
CID VZW__001
ANDROID 4.4.4
CM 11 ROM
KERNEL 3.4.10
CLOCKWORKMOD RECOVERY
Nice ROM Cook
I love it, stable is so good
Santod, Will Xposed framework work with 4.09.605.5 Rooted Deodex Debloated Stock Kitkat. I do not see it installed and was wondering which one would work with this ROM. Thank you
Update, found it installed it, working great, cheers
I just can feel gratitude
I JUST CAN FEEL GRATITUDE
TY TY TY TY TY ...
Friend you are the best develoader for Android and for HTC DROID DNA,
your work is impeccable, faultless, dapper, and Excelent.
I hope someday give you more that the thanks.
a hug, you're the best.
greetings from Latin America.
Any eta on de bloated versions bring available? Grandfathered in on Verizon unlimited plan and need my high speed laptop internet fix with hotspot and would like to update firmware and ROM at same time. Thank you at for the best ROM I've found so far
Can I use this ROM in HTC J Butterfly HTL21 Japan Version?
Hi, I have HTC J Butterfly HTL21 japan version (au KDDI operator).
Right now, it is installed with the ported ROM from here [ROM][GSM/CDMA] HTC One *STOCK* ROM Port | 4.19.401.8 | 4.4.2 | HTC Sense 5.5. But, that ROM gives me unstable internet connection. I wonder if I can install this ROM on my J Butterfly, and is the 4G will also working?
Any help would be a great things for me.
Thanks in advance.
Hello there,
so as of late i've been wanting to upgrade to a newer version of firmware, which sadly couldn't be done because of my old phone. So i eventually ended up here, and read about how to get unofficial versions
of newer firmware. Thing is, i'm stuck at the first part; succesfully installing a recovery mod on your phone. I tried flashing twrp tar files with odin (which i did succesfully, according to the guides i found here atleast), yet when i open into recovery mode it gives me an error and redirects me to the stock recovery mode. Same deal with philz touch, and i'm not quite sure why.
Any thoughts? Any help would be appreciated!
EDIT: Managed to solve it, although i do not know what constituted the difference. Followed the first part of the guide on the wiki of Cyanogenmod, and it was smooth sailing from there on.