• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][UNOFFICIAL][4.4.4] DeCAF Cyanogenmod 11, Release 1

EmoUzuma said:
Hey I was looking into how to get LTE fixed and I think I've stumbled upon something. At the link below I downloaded "Universal LTE builds APN FIX" and flashed it. I also made a backup before I flashed it. It appears now that LTE is working for me and can now use it. Can anyone check to see if it works for them?


http://androidforums.com/threads/mod-universal-lte-virgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/
Click to expand...

Can you make calls?
That was the main issue I had when the LTE icon was showing above my signal..
I don't believe I was getting LTE speeds either, but my signal is somewhat weak where I was trying..
 

Attachments

  • 1421594131609.jpg
    1421594131609.jpg
    70.4 KB · Views: 106
adamhos1234 said:
Can you make calls?
That was the main issue I had when the LTE icon was showing above my signal..
I don't believe I was getting LTE speeds either, but my signal is somewhat weak where I was trying..
Click to expand...
Yeah I was getting weak LTE signals and when I tried to make a call it said "Mobile Network not avaliable".
 
So I decided to try this out. I got "status 7" so I edited the updater script. It installs for a few seconds then claims its done. I use tera copy to move the file and test so i know its good. I cant restore a backup, i cant install another recovery, it just boots into CWM no matter what. I cant get it into download mode either. I read somewhere that roms that try to copy the recovery will cause the bootloop problem I have. Anyone have this issue? Did you fix it somehow?
 
3simplex said:
So I decided to try this out. I got "status 7" so I edited the updater script. It installs for a few seconds then claims its done. I use tera copy to move the file and test so i know its good. I cant restore a backup, i cant install another recovery, it just boots into CWM no matter what. I cant get it into download mode either. I read somewhere that roms that try to copy the recovery will cause the bootloop problem I have. Anyone have this issue? Did you fix it somehow?
Click to expand...
If you can fastboot into twrp you'll be able to flash this, twrp is recommended over cwm for this one. You might be able to flash twrp from cwm but I'm not sure... http://androidforums.com/threads/re...-fixed-touchscreen-radio-still-borked.882847/
 
I know it worked real good for me when i had my galaxy s3, but idk how it would work for the volt, if it'll work at all, i was under the influence that was made specifically for the s3, but im no expert yet lol
 
3simplex said:
So I decided to try this out. I got "status 7" so I edited the updater script. It installs for a few seconds then claims its done. I use tera copy to move the file and test so i know its good. I cant restore a backup, i cant install another recovery, it just boots into CWM no matter what. I cant get it into download mode either. I read somewhere that roms that try to copy the recovery will cause the bootloop problem I have. Anyone have this issue? Did you fix it somehow?
Click to expand...

Turns out I was right. This ROM is corrupting the recovery partition. I had to build a recoveryinstaller.zip to overwrite my CWM recovery. Then I used my backup to restore my system.
 
3simplex said:
Turns out I was right. This ROM is corrupting the recovery partition. I had to build a recoveryinstaller.zip to overwrite my CWM recovery. Then I used my backup to restore my system.
Click to expand...

That's why in the op i will now specifically recommend twrp. Cwm is dead, and should stay dead. Honestly, it was a half hearted attempt at a recovery from cyanogenmod its whole life.

Also, gonna need some proof of a corrupted recovery partition since I haven't heard anyone else say anything about it. Logs would be nice, dmesg if you can. I have never had a problem with using twrp for making a good backup and installing cm11 builds, and then restoring my backup afterward. Please don't make accusations about what things do and don't do without proof to back up the claim. I can't fix a problem if all you do is say "its broke" and I can't reproduce it or have some logs to look at to see why its broke.

Are you sure you aren't going into developer options and checking the box that "updates" the recovery? That would most likely cause the problems you are running into.
 
Last edited:
Step one: Use the original CWM to flash this ROM unaltered.
Step two: Reboot (You'll only get back to CWM)
Step three: Proceed to fix it with a recoveryinstaller.zip

Never touched the developer options your talking about. How would that effect installing a new ROM from an empty emmc?

I'm a helpful guy so I thought I would share what I can. Once I fixed CWM I restored my backup. I flashed TWRP (my preferred recovery) and the ROM writes beautifully.
 
What does this do? Could it be part of the problem?
cm-11-20150112-UNOFFICIAL-x5.zip\recovery\etc\install-cm-recovery.sh

#!/system/bin/sh
if [ -f /system/etc/recovery-transform.sh ]; then
exec sh /system/etc/recovery-transform.sh 12707856 eae1cb5afb874405188b34b76b549dae23d7a0c6 10457104 aa2d7a67a9845e3f8f01f94fad4d64c47f411aac
fi

if ! applypatch -c EMMC:/dev/block/platform/msm_sdcc.1/by-name/recovery:12707856:eae1cb5afb874405188b34b76b549dae23d7a0c6; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:10457104:aa2d7a67a9845e3f8f01f94fad4d64c47f411aac EMMC:/dev/block/platform/msm_sdcc.1/by-name/recovery eae1cb5afb874405188b34b76b549dae23d7a0c6 12707856 aa2d7a67a9845e3f8f01f94fad4d64c47f411aac:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
 
I had big problems installing this rom with cwm . So i took the advice and switched to twrp and had no issues at all. The op even says the preffered way is to use twrp .

Cant wait till whoshot has time to work on the LTE. Great job thusfar this rom is great!
 
3simplex,

That's something that cm puts in by default. It looks like it could be updating the recovery image, but I'm pretty sure its tied to the function in developer options that updates the recovery if checked.

I'll say this one last and final time since its in the op now, please don't use cwm to flash my cm11. Its broke, and is not going to be fixed since cwm is obsolete now. Danhalen did not post source, so nothing about his recovery can be fixed. Use twrp, or I can't and won't help anyone. Problem solved.

Also, danhalens cwm is using an naming scheme that really wasn't agreed upon for a device check at the beginning of the updater script. I set mine to the device standard x5, I believe his is x5_zv3 or something of the like which at the time was OK since that was the source used, but won't be used now since we are up to zv5. So what I did was named it only x5, that's why cwm is broken. I could fix his recovery image if I wanted to, but choose not to because what's the point in investing time into something that's obsolete. Twrp is the future unless cm comes out with something better.

Not trying to be a jerk, just tired of explaining the same thing over and over to those who either can't or won't investigate further or read through the thread and see that cwm is a waste of time.
 
All that's well and good, but the fact remains that TWRP does not work for installing the stock zv4 ROM. It had to be installed with cwm, for whatever reason. I have both images on my phone and flash the one I need for a given task.
 
bg4m3r said:
All that's well and good, but the fact remains that TWRP does not work for installing the stock zv4 ROM. It had to be installed with cwm, for whatever reason. I have both images on my phone and flash the one I need for a given task.
Click to expand...

This isn't the twrp or zv4 thread so if you have problems with those, direct them there. We really need to get back on topic, so discussion of cwm and its brokenness ends here now. Im not going to support something i didnt build and have no source for. Open a new thread to discuss it if you want. The source is out there, if anyone really wants it fixed that bad, then please be my guest and fix it.
 
well afaik no threads for any recoveries exist, everything is just kind of all over the place. We could use better organisation. Also I believe that is a big problem that is a very relevant discussion here. I would fault twrp before I would fault cwm. So for cwm to not work with just this rom or the fact that there are no clear threads or details on recovery options for our device seems rather odd. Also cwm is not a waste of time, there are very good engineering reasons behind it not being a touch based interface. I don't think younger generations really understand the true difference between a good cli and a bloated touch interface.
 
Guys, I understand the different points of view, but please stop bickering. I think everyone involved here has the common goal of trying to support the Volt and this community, so let's rally around that and keep it positive and productive. Thank you very much to each of you for your contributions! I would hate to see any of you leave.

With that said, this is whshotjr2006's thread, so I think we should respect his wishes to keep it focused on the ROM itself.

Thanks!
 
spocko said:
With that said, this is whshotjr2006's thread, so I think we should respect his wishes to keep it focused on the ROM itself.

Thanks!
Click to expand...

I couldn't agree more. I wiped out some posts that weren't helpful towards the development of the rom, and more might go, but the recent posts have been cleaned. Moving forward, lets keep this thread about this rom and only this rom. Off topic chatter may be removed and bickering may result in further action beyond that.
 
Thanks to everyone for this rom. Quick suggestion/request based on various comments and my own naivety:

Could you add a link to the best recovery for this rom in the first post? I think that might save some frustration, unless of course you have and I'm one more idiot who didn't see it.

Thanks again! :)
 
You must log in or register to reply here.
Back
Top Bottom