I'm trying to install the DK Zen RLS2 ROM here:
http://forum.xda-developers.com/showthread.php?t=2309928
I figured they wouldn't want me mucking the thread up with my personal problems.
What happens when I install the ROM is that it will start up and get as far as the lock screen. Instead of going into the whole new-phone-setup business, it just stays on the lock screen and doesn't respond to any touch input. I can turn the screen on and off with the power button and I can change the volume, but I can't unlock, pull down the status bar, or open the volume settings. Holding the power button won't bring up the power menu (no real surprise) but it will reboot the phone after 10 seconds.
I'm fairly certain I've used this ROM before, but I recently formatted my phone and relocked it and everything in an attempt to fix other issues. I'm able to use other ROMs just fine without getting this issue. So far I've tried Stock with Goodies (http://forum.xda-developers.com/showthread.php?t=2301672) and SuperBLUE (http://forum.xda-developers.com/showthread.php?t=2520499). It seems, from reading the threads, that each of these ROMs is based on 4.3, but considering the way DK Zen rearranges my SD card, I have a feeling it's different (it adds the "0" folders; does that mean that it's a downgrade from or an upgrade to 4.3?).
Any thoughts? The one thing I can see from this ROM is that it gives me a full 4G signal, whereas the other ROMs only get me a few bars. Maybe the ROM isn't being honest, but if it is I'd really like to get it working for this alone (also volume rocker to skip tracks).
Reading through this thread (http://forum.xda-developers.com/showthread.php?t=2470569) it sounds like going with a 1.31 firmware (which DK Zen is based on) will have touchscreen issues if my phone's firmware doesn't match. Checking the Bootloader screen, I have 3.04.651.2 on the OS line. Is that the cause of my problems? Is it possible to downgrade my firmware, and would that be advisable anyway?
I feel like not many people run into this issue, or if they do they already know why, but I might as well post what I did here.
The touch panel firmware in 3.04 isn't compatible with earlier ROMs (or at least 1.31 ROMs). So, I had to go back to an older firmware. To do that, I just used Rum Runner to get s-off which I hadn't done at any point before. That was a very simple process, though I couldn't do it on my work computer, probably because of all the server and network security software that's installed here.
Once I got s-off, I was able to flash a 1.29 firmware using fastboot. From there, I flashed the DK Zen ROM that I was looking at and the touchscreen worked just fine.
Yay for learning!
Related
Hi everyone I have an HTC VIVID with S-ON i put miui 2.9.14 and my sound volume is extremely low especially the in call volume also my gps doesn't work like the Google maps navigation or maps cant connect the gps either does anyone have a solution to the sound or gps issue?
Try to reflash the Rom and try different kernels sometimes helps also.
I've tried everything every time I install a new kernel it either knocks out my wifi or gets stuck on the white htc screen anyone with any ideas?
Nenita25 said:
I've tried everything every time I install a new kernel it either knocks out my wifi or gets stuck on the white htc screen anyone with any ideas?
Click to expand...
Click to collapse
Which kernels have you tried? And have you performed a full wipe/re-install of the rom for each different kernel you have tried?
Where did you find this version of MIUI? I'd like to try it out...
ive tried every kernal there is for htc vivid an nun work they just not out my wifi or my phone doesnt turn on all the way at all
i got my miui from here http://miuiandroid.com/community/th....androidfilehost.com/?a=show&w=files&flid=611
Nenita25 said:
Hi everyone I have an HTC VIVID with S-ON i put miui 2.9.14 and my sound volume is extremely low especially the in call volume also my gps doesn't work like the Google maps navigation or maps cant connect the gps either does anyone have a solution to the sound or gps issue?
Click to expand...
Click to collapse
When having unfixable problems sometimes the only thing that will work is returning to stock. Relock and start all over from the very beginning.
Sent from my HTC Holiday using Tapatalk 2
Nenita25 said:
Hi everyone I have an HTC VIVID with S-ON i put miui 2.9.14 and my sound volume is extremely low especially the in call volume also my gps doesn't work like the Google maps navigation or maps cant connect the gps either does anyone have a solution to the sound or gps issue?
Click to expand...
Click to collapse
I just installed MIUI 2.9.29 on my Bell Raider (which has a current base of the Rogers ICS RUU). I am S-OFF so I'm sure the kernel flashed fine as part of the rom install, but I went into Settings/About Phone to confirm. It says it is running the faux kernel it comes with (3.0.33-MSM8660-Faux123-v007+)
- Call volume is just fine for me and when it is in Speaker mode it goes pretty loud! However - It doesn't seem to do LTE (dealbreaker for me). I checked the APN. It had everything correct. I only get HSDPA. I even went into the special phone menu and the choices were only GSM or WCDMA (no LTE items listed).
- GPS also seemed to work fine for me. I installed Google Maps from the market, launched it, the GPS icon started flashing in the notification bar, and it detected my exact location pretty quickly.
- The gallery and music player showed duplicates of each photo/song for me. Strange!
I still wonder if it's a kernel issue you're having. When you do a fresh flash of MIUI, and boot into it, go into Settings/About Phone, scroll down, and check what it says for Kernel Version. Also, if you go to flash a different kernel manually via fastboot (immediately after a fresh install of the rom), go into that same menu and see if the kernel you flahed is listed.
If the kernels don't seem to be flashing, I wonder if your phone has to experience an 'insecure' kernel flash first (this can be done by flashing Kozmik's 'stockish' kernel via fastboot). I'm not sure if this even applies to S-ON phones though...
I do agree with drwario though - starting fresh from scratch (re-locking bootloader and running your specific stock ICS RUU) is a good idea.
you are s-on? sounds like what happens when you dont flash kernel correctly. try to flash the kernel using fastboot and see if it fixes it
Relock your bootloader then reflash it to stock with no interruptions then just go back unlock the bootloader and reflash your Rom make sure that if u are s-on to flash the kernel.via fastboot
Sent from my GT-I9300 using xda premium
Hello,
I have a stock Bell HTC Raider, locked, unrooted, basically never touched, all original software and state. It is updated to latest OTA software.
I'm trying to wipe it and reinstall the stock rom because it is starting to act funny and I want to start from scratch.
I am trying to flash the version 3.5 bell RUU, and it will see that I have version 3.38 on phone, and RUU is same version 3.38, and when I click "next" it will go to screen which says "sending" and it will just hang there. The "sending" progress bar just keep incrementing continuously but nothing else happens. the phone is on the white HTC logo.
I gave up after 2 hours of this. Tried several times. Phone info is not wiped, same old ROM is still on it with my apps and everything.
I also tried to put the PH39.zip file for rogers on the card (can't find one for bell) and it gives me a "wrong CID, flash fail" error.
I'm running windows 7, I am admin on the PC, I also ran the RUU as administrator.
I installed latest HTC Synch, and I can open the phone as a USB drive and copy data to it, but I don't see it in HTC synch.
HTC synch does automatically launch when I plug phone in, so it sees something, but when I go to the "home" tab it says that no device is connected. I did select "htc synch" as the connection method on phone. USB debug mode is on.
Any ideas of what could be wrong?
Is there any working link for the PH39 zip file for bell?
each umaxces
Update:
in the mean time I bit the bullet and unlocked the bootloader (still S-ON), put WCX recovery on and flashed the cyanogenmod 11 *kitkat) rom.
That had the low call volume problem, so I flashed Holic's 1.3 ROM (back to ICS) which so far works perfectly.
So I am in fact able to flash other roms in recovery but I can't get back to stock using the Bell RUU.
If I ever want to return to stock, what do I do?
tudorvictor said:
Update:
in the mean time I bit the bullet and unlocked the bootloader (still S-ON), put WCX recovery on and flashed the cyanogenmod 11 *kitkat) rom.
That had the low call volume problem, so I flashed Holic's 1.3 ROM (back to ICS) which so far works perfectly.
So I am in fact able to flash other roms in recovery but I can't get back to stock using the Bell RUU.
If I ever want to return to stock, what do I do?
Click to expand...
Click to collapse
Might want to check out http://forum.xda-developers.com/showthread.php?t=2013122 which explains:
How to run the RUU
1: Make sure your bootloader is re-locked and by using the fastboot oem lock code
2: Plug in your device and make sure you have the drivers installed ( or HTC Sync )
3: Run the RUU specific to your carrier and wait for it to load ( could take up to 20 min depending on your PC )
4: A box should popup on your screen and a progress bar will be shown ( wait )
5: Once it's done loading follow the steps to return to stock.
6: You are now unrooted
Been years since I did that. KitKat low volume? Are you running the latest nightly? http://www.chronic-buildbox.com/nightly/holiday/ Best rom I've tried and I've tried em all. (Can't wait to see what pacman can add to what Albinoman is doing an awesome job with)
I managed to return to stock using the RUU without problems.
I didn't do anything different this time, it's just that I wasn't trying to flash the stock ROM while already on the stock ROM.
Maybe that doesn't work?
you can close this thread now. thanks.
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
Hi Guys. I have searched the forum but havent found anything that applies to my problem. I have the HTC One M7 sprint version. I have been trying to sim unlock it but the phone came on an android version higher than 4.3. This is one of a batch of 4 so at this point I cant even remember the original os. My problem is that I need to be on an android os lower than 4.3 to unlock. I have been following the tutorial here: http://forum.xda-developers.com/showthread.php?t=2586704 .Only roms at kitkat or higher are stable enough to use and not even all the kitkat ones are stable.
The issue:
The phone boots and the rom loads but I am unable to do anything with it. The lockscreen shows as normal but anytime I unlock the screen I get a white screen with HTC in green letters. On some roms I am able to access the settings menu but that is it. It just stays like that forever. On some roms it will stay on but most reboot in roughly 2-3 minutes. Most of the roms that are stable go into a handsfree activation loop where I cant get past that screen. I read a tutorial about deleting the htc setup apk but that works only some of the time and then the roms are mostly unstable.
My phone is S-Off and I have attempted to downgrade to stock 4.1.2 using the official ruu.. The process was successful but the stock os is unstable. Reboots every 2-3 minutes. I have flashed the firmware separately and then run the ruu. I have run the ruu on its own. I have done factory reset with both stock and custom recoveries after running the ruu.
I have tried pretty much every sprint rom I have come across and still no love. I've been at this for nearly a month and my HTC Rom folder is about 25gb if a list is needed I am willing to provide it but I really just want to be on stock 4.1.2 or a sense rom lower than 4.3 for the purpose of unlocking the gsm sim. I have been told that the issue could be hardware but then I have roms that run without issues except that the phone isnt unlockable in that state.
I was trying to post my post, but it was flagged and blocked by the system, probably because I kept previewing it, so until I can post it, I'm going to be really brief about the latest news on my problem.
I have a T-Mo US HTC One that's now S-Offed, running CWM recovery, and running 4.19.531.10 firmware+radio. It's running Android Revolution HD 91.1, and the first error from before I did any of this was "Failed to powerup external modem!" The phone would randomly reboot and such. Now, it's running normally except for the fact that I can't get the phone part of it to work. I also don't think I can warranty it because I already opened it up because I managed to break the back and also changed the frame color, screen, and camera. In the settings, Baseband read as "Unknown." I'm hoping you guys here can help me fix my problem as I hope it's software related, but think it might be hardware related.
Is there any hope for this? At one point, running the ElementalX kernel and the Android Revolution HD ROM with it still S-On and running latest Radio from 7.18.531.2, if I wiped dalvik cache and kept power saver off, the radio would start and it would work fine until I turned power saver on (even if the turn mobile network off part was off).
aruaour said:
I was trying to post my post, but it was flagged and blocked by the system, probably because I kept previewing it, so until I can post it, I'm going to be really brief about the latest news on my problem.
I have a T-Mo US HTC One that's now S-Offed, running CWM recovery, and running 4.19.531.10 firmware+radio. It's running Android Revolution HD 91.1, and the first error from before I did any of this was "Failed to powerup external modem!" The phone would randomly reboot and such. Now, it's running normally except for the fact that I can't get the phone part of it to work. I also don't think I can warranty it because I already opened it up because I managed to break the back and also changed the frame color, screen, and camera. In the settings, Baseband read as "Unknown." I'm hoping you guys here can help me fix my problem as I hope it's software related, but think it might be hardware related.
Is there any hope for this? At one point, running the ElementalX kernel and the Android Revolution HD ROM with it still S-On and running latest Radio from 7.18.531.2, if I wiped dalvik cache and kept power saver off, the radio would start and it would work fine until I turned power saver off (even if the turn mobile network off part was off).
Click to expand...
Click to collapse
seems like you went to a lot of trouble for a $100 phone
you can find a decent replacement on eBay cheap
Meanwhile you can update your firmware to the latest it will match the rom that way
I'm a little reluctant to change anything now. I just finished flashing the ElementalX kernel and did a dalvik-cache wipe and the phone service is working again. Assuming it's just like before, power saver should cause it to fail again.
I'm busy now, so I'll do a nandroid backup when I can later and try the RUU for the firmware again. The RUU kept failing on me before and htc_fastboot.exe would crash. I don't know how to decrypt the rom zip to manually flash it.
Edit: Any idea why using the ElementalX Kernel and wiping Dalvik-Cache makes the radio work again? It seems relatively stable right now (Powersaver off, it's not very stable with it on).