Hello, I have an HTC Desire C, Fido. I have unlocked the bootloader and installed CWM recovery. The problem I have is no rom I have flashed has successfully booted. It seems I have to turn S off. I have seen methods to do so but not on my Hboot version.
Is it possible to turn S off on Hboot 1.28?
There is no S-OFF on our phone.
boot.img have to be flashed via fastboot
S off doesn't affect ROMs at all, you must be doing something wrong
I have been flashing the boot.img that comes with the rom I got, Nameless 7.4 build1. Here are the steps I take. First wipe all data though recovery, then flash boot.img, then flash .zip. Upon first boot, there is either a boot loop or boot's to a point of "optimizing applications" then restarts.
What is the best rom for use in Canada? I just installed Nameless 7.4 but it freezes and the first HTC splash screen. I dont want stock.
Monkeywoman said:
What is the best rom for use in Canada? I just installed Nameless 7.4 but it freezes and the first HTC splash screen. I dont want stock.
Click to expand...
Click to collapse
Hi,
I do have a Desire C from Virgin Canada.
I have tried other custom roms - nameless and revolutionmod. Revolutuionmod is better, but I found it unstable. Dont know if the instability came from the rom itself or the kernel.
After a lot a search I found the best option, for now, to return to the stock rom.
I have removed all the junk (with titanium backup) and the phone runs fast and smooth, with quite good battery life.
Suggestions/warnings:
- apply the ota update, if any quickly and BACKUP your working rom; if you modify the rom, or the recovery, you will not be able to install the ota update
- if ever you'd like to go back to stock rom after mdifying rom/recovery, this would be not possible for now because there is not any canadian stock rom for desire c
- if you install any custom rom, the odds are that the wi-fi will not work; you have the flash a custom kernel, such as prometheus kernel from nikhil, to make wi-fi functionnal.
Sense based ROMs will have WiFi with stock kernel, cm based ones won't even boot with a stock or sense kernel.
Monkeywoman said:
What is the best rom for use in Canada? I just installed Nameless 7.4 but it freezes and the first HTC splash screen. I dont want stock.
Click to expand...
Click to collapse
I personally hate sense so I went with revolution senseless rom 3.5 because wifi was borked in most others but the amazing devs found a fix for it so you might want to wait for all the patches to get applied to the roms to get wifi working before you make your choice. I also experienced some difficulty when I first rooted a desire c and you're having the same difficulties it seems. My problem was in the kernel. Eventually I just flashed completely stock everything with no mods tweaks or anything special and and booted right up. Try not to do anything fancy till you get the hang things
Let me know I you're having further troubles and I would be glad to help you!
Phenziox said:
Sense based ROMs will have WiFi with stock kernel, cm based ones won't even boot with a stock or sense kernel.
Click to expand...
Click to collapse
For me wi-fi didnt work. Once I flashed nameless rom, then no stock kernel returned the wi-fi back, even if I restored the stock rome backupd earlier. Flashing prometheus kernel brings wi-fi, regardless of the rom (nameless, revolutionmod, stock).
If I flash a stock rom, with its stock kernel, then wi-fi works.
well fwiw i am in canada and had no issue at all with desense rom,and just flashed the cm10 rom yesterday and lovin it!!
If currently on latest 4.1.2 with sprint , will I be able to flash 4.2.2 based roms on the 4.1.2 firmware when update comes or will I have to flash RUU's then take OTA , just curious , I think I already know the answer but it was worth a shot, also does the old wine/mac/linux method from the HTC One X work on HTC one or are there anyways to go back to stock via mac , thanks for listening!
OK, that was kind of hard to read. No offense, just saying: my comprehension may be off.
You are the latest 4.1.2, stock. The 4.2 should be coming in a couple months seeing that Int'l version already got it.
You can take OTAs when on a Sense or Stock ROM. Rooted or otherwise. Not on Stock-based ROM's like ViperROM. In fact, the OTA setting is disabled in many Stock based ROMs, so you don't mess up your setup. You will have to wait for the developer to build the ROM again from the new source. Then, you should be able to just flash over.
Beware. Your files will get moved around and/or hidden when going from 4.1 > 4.2. This includes TWRP/CWM backups, Ti backups, pictures and songs. This is because of the new multi-user function. You can use an onboard File explorer like ES to move things back. Don't worry, as long as you don't do anything dumb, they won't get deleted.
And what are these "Macs" you speak of? /s
Hello everyone, I have a VS980, I was running crdroid 4.4.2 rom and in order to flash CM12, I flashed the 12b modem, everything went well with CM12, After that one I flashed a Lollipop Resurection rom, then I flashed another Lollipop based rom, Bliss to be exact.
on that last rom I flashed Render Kernel which I didn't know was Bumped (I don't know how to go about Bump! so I was trying to stay away from it). the thing is that now I'm trying to flash back to a cloudy G3 rom (Kitkat based ) and i always end up in a bootloop (the phone reboots straight to TWRP recovery on its own). I have already tried flashing the 24a bootstack from xdabbeb's thread. and also tried flashing the Kitkat modem and I still can't flash back to cloudy. Luckily I still can flash back to Bliss Lollipop Rom, which is the one I'm running right now.
Sorry for the long explanation. Could anyone please Help me?
PS: Any insight as to how does BUMP! work (or at least a FAQ about using it vs loki based zips would be great).
Hello, anyone?
Since you are on a Verizon VS980, I would recommend using the G3 rom specifically for our phones. Cloudy G3 rom doesn't work with the Stock Messaging app, along with Visual VM and several others. The radio keeps flipping to GSM WorldWide mode and roams.
I recommend this one:
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
It also uses the BUMPed recovery... so you should be able to just wipe and flash with ease. Just flash the Bootstack update first, wipe, rom, celebrate.
I actually came from Cloudy G3 directly. It feels like the CloudyG3 rom except it is custom tailored for our Verizon phones specifically so everything works better.
Hi all,
I have recently unlocked my bootloader and upgraded to 4.4.4 (Build 14.4.A.0.157).
Going thru the General section it seem that during the 4.2.2 to 4.3 era that there is a high chance of bricking the device when there is mismatch of baseband/firmware/kernel.
Is the issue still happening on 4.4.4 and is there anything I need to take note about when flashing custom kernel ?
I'm aware that stock ROMs (or variants) should go with stock kernel variants.
Thank you.
sayatsugu said:
Hi all,
I have recently unlocked my bootloader and upgraded to 4.4.4 (Build 14.4.A.0.157).
Going thru the General section it seem that during the 4.2.2 to 4.3 era that there is a high chance of bricking the device when there is mismatch of baseband/firmware/kernel.
Is the issue still happening on 4.4.4 and is there anything I need to take note about when flashing custom kernel ?
I'm aware that stock ROMs (or variants) should go with stock kernel variants.
Thank you.
Click to expand...
Click to collapse
-Dude if you already installed recovery then first of all take a full stock ROM backup. So if in future there goes something wrong you can flash it later.
-If you don't have recovery, then install it.
-Make sure you always flash ROM that are made for your device.
-DON'T ever flash different kernels to your device. Your pre-installed ROM may misbehave.
-If you want to use the ROM as a daily driver, make sure the ROM is pretty stable.
-Always try to clean flash the ROMs.
By wiping
Cache + Dalvic cache + Data + android secure + System
Dirty flash often lead to bootloops, soft brick etc.
-Hope this would be somewhat helpful for you.
A few weeks/months after installing a ROM it starts to get slower over time. The only way I've found to fix it is going back to stock ROM and then back to a custom ROM. It happened with different ROMs.
Any idea of why this could happen or how I can fix it?
I'm thinking it may be related to some partition, because even a clean flash doesn't work. And I have to go back to stock ROM before flashing a new ROM.
My previous ROM was Pixel2ROM. Current Pixel Experience. I had to go back to stock before flashing this.
Could you help me? Any idea why is this happening?