FORUMS

Analysis & Opinion

Top Forum Discussions

[Q&A] ★ ☆ [ROM/RADIO][4.4.2] Stock 4.09.605.5 | Rooted | Sense 5.5

n/a posts
Thanks Meter: 0
 
By QA Bot, Guest on 13th February 2015, 04:08 PM
Post Reply Subscribe to Thread Email Thread
Announcement from santod040: Updated to latest 4.4.2 Stock OTA: 4.09.605.1 CL322791 Release Keys
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!
 
 
13th February 2015, 04:08 PM |#2  
Junior Member
Flag Syracuse
Thanks Meter: 0
 
More
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.
13th February 2015, 06:40 PM |#3  
santod040's Avatar
Recognized Developer / Recognized Contributor
Flag NorCal
Thanks Meter: 17,839
 
Donate to Me
More
Quote:
Originally Posted by ra2dc

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.

Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...
13th February 2015, 06:49 PM |#4  
Junior Member
Flag Syracuse
Thanks Meter: 0
 
More
Quote:
Originally Posted by santod040

Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...

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
16th February 2015, 09:08 PM |#5  
Junior Member
Flag Syracuse
Thanks Meter: 0
 
More
Quote:
Originally Posted by santod040

Get rid of that age old CWM and use tarp as suggested, you'll have much better luck...

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
17th February 2015, 10:18 PM |#6  
Junior Member
Flag Portland
Thanks Meter: 15
 
More
Quote:
Originally Posted by ra2dc

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.

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.

Quote:
Originally Posted by ra2dc

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

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.
23rd February 2015, 03:50 PM |#7  
Junior Member
Thanks Meter: 0
 
More
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.
6th April 2015, 04:12 PM |#8  
Junior Member
Thanks Meter: 0
 
More
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!
21st April 2015, 09:47 PM |#9  
Junior Member
Thanks Meter: 0
 
More
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
30th April 2015, 10:06 AM |#10  
Junior Member
Thanks Meter: 0
 
More
Nice ROM Cook
I love it, stable is so good
27th June 2015, 02:59 AM |#11  
Member
Thanks Meter: 13
 
More
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
Last edited by BladeNY; 28th June 2015 at 03:02 AM.

Read More
Post Reply Subscribe to Thread

Tags
auto-qa

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes