im running the latest version of the cm 11 nightlies but every time i try to use the in rom updater under settings it downloads and takes me to recovery but when its installing it. i get an error and then it reboots me right back into the rom. i dont mind flashing the new nightly manually but it would make things easier for me to be able to use the updater. so if anyone can help that would be greatly appreciated
I'd like to see a answer on this as well!! I can get it to flash but always bootlooops on me! I've not tried in the last 5 or 6 but it would be much easier and faster!!
Sent from my SCH-R970 using Tapatalk
Sometimes it'll still flash the update even with the error check the build info after you flash
sent from Isaac's GS4
Related
Hi guys,
I'd like you to help enlighten me on this subject. I remember reading somewhere that if you're already running CM10.1 on a device, you can simply flash the updates right on top of it, disregarding a data wipe or cache wipe. I'm running the M1 build (CM10.1) for grouper (Nexus 7 WIFI), and would like to update to the latest nightly (Jelly Bean 4.2.2) because my OTA update failed when I was on the stock ROM.
Is this true, and does it work for other ROMs as well? In other words, if I take another Jelly Bean ROM (say version 1.0.1), and update to the next latest version (1.0.2), does this same process apply, where I can just flash the updates over the top and be done?
Thank you!
??? Cm10.1 comes with a self updater. It looks after cache and app compatibility for you. None of the other ROMs have it. Its one of the many reasons why I like cm so much. I update it once a week. Its like a dirty flash without the extra work. Look in About Tablet for it.
Sent from my Nexus 7 using XDA Premium HD app
I don't mean wirelessly. I mean actually downloading the files, and flashing through recovery. I don't have a stable WIFI connection from my Nexus 7, so I have to use direct download. I have a pretty fast network, though, plus a download accelerator, so I get the .zips in like 15 seconds.
Again, I want to know if I can flash any update of CM10.1 on my Nexus 7 and be fine. I'm running the M1 experimental release for grouper. I heard about people saying you can just flash the updates without clearing cache or anything like that. Just flash and you're done.
Hello,
I've been trying to look for help the past couple of hours and just can't seem to find any.. It is getting a bit frustrating.
I recently put CyanogenMod 10.2 on my Nexus 4 using the CyanogenMod Installer that was released a few days ago, as I was using my phone for the past couple of days I noticed that I would get a solid 4 hours of battery life using this ROM which is really frustrating...
I'm looking for a nice and simple (DETAILED) way of flashing back to stock android
or
Flashing a new custom ROM from one of the threads...
I hope someone out there will guide me to help me solve my issue since my phone is very important for me during work.
Well you probably have a recovery.
Power off the phone, then power on holding power+voldwn. You'll be in the bootloader, and use the volume keys to make the option on the box say recovery. Then hit power to confirm. Since you used the app you'll probably have ClockworkMod. If you do, good . Reboot and go on XDA via PC/ best method. Look for a nice Android ROM for the Nexus 4. I personally like Slim. Download it and the correct Google Apps for the Android Version. Slim has there own on there website. Or a quick Google for PA Gapps will find the medifire link. It's easy ass hell. You already did the hard part . Once recovery is one the phone and the bootloader is unlocked your good . Just download a to for the Nexus 4 via XDA and flash in recovery. Just always wipe if your changing ROMs. Youtube can also help .
Sent from my Nexus 4 using XDA Premium HD app
Georific said:
Hello,
I've been trying to look for help the past couple of hours and just can't seem to find any.. It is getting a bit frustrating.
I recently put CyanogenMod 10.2 on my Nexus 4 using the CyanogenMod Installer that was released a few days ago, as I was using my phone for the past couple of days I noticed that I would get a solid 4 hours of battery life using this ROM which is really frustrating...
I'm looking for a nice and simple (DETAILED) way of flashing back to stock android
or
Flashing a new custom ROM from one of the threads...
I hope someone out there will guide me to help me solve my issue since my phone is very important for me during work.
Click to expand...
Click to collapse
Here's the official deodexed 4.4 kitkat rom .Backup, full wipe and install. Gapps included.
http://forum.xda-developers.com/showthread.php?t=2010887
Or download this for 4.3 jellbean. JWRXXV
http://www.androidrootz.com/2013/07/stock-43-rom-for-nexus-4-rooted.html
Hello,
I have been using Snapshot M8 for longest time and have quite enjoyed it.
For last day or so, i have been trying to update to M10 but i have been unsuccesful.
Im very technical savvy but when it comes to understanding some of lingo on this board, i am terrible.
So, ive tried updating to the KitKat firmware but after so much trouble ive decided to abandon it in favor of the JellyBean firmware. After bricking my phone over and over again, i finally got back to stock 4.4.2 with working modem's and the like. Also, ive reverted back stock recovery.
Ive read through quite a few threads but to no avail, can not understand how to upgrade or downgrade to M10.
Can anyone help me find what version of the firmware i have and advise me how to upgrade to M10? (jellybean, since i heard they're are problems)
I hate asking for help, i just cant understand what to do.
ALSO, THANK YOU DEVELOPERS for such a great port!
I believe you need the KK bootloader for M10.
So you'll need to flash this first (or just an official stock KitKat firmware), then a compatible recovery (e.g. CWM 6.0.4.9) and then CM M10.
lem22,
Thank you for your reply!
So its not a good idea to flash M10 using the jellybean firmware?
I can successfully flash CMW 6.0.4.9 using RSDLite. (ive become quite fluent after bricking my phone, haha.)
but when i tried to install M10 through CWM i get a status 7 error, i believe im flashing with 6.0.4.9 KitKat.
You must flash KitKat update first (http://sbf.droid-developers.org/phone.php?device=8), then compatible recovery and then CM11 M10.
I suggesting to use CM Nightly builds (mine is 9/27, which is more stable than snapshot builds.
UuN said:
I suggesting to use CM Nightly builds (mine is 9/27, which is more stable than snapshot builds.
Click to expand...
Click to collapse
Is wifi and bluetooth fixed in the latest nightly? KK BL?
Wifi & BT works fine, but gps kinda less acuration..
Yes, im using KK BL.
UuN said:
Wifi & BT works fine, but gps kinda less acuration..
Yes, im using KK BL.
Click to expand...
Click to collapse
Any major bugs with the new nightly that would be bad if your going to daily the phone?
Sent from my XT907 using Tapatalk
Any major bugs with the new nightly that would be bad if your going to daily the phone?
Click to expand...
Click to collapse
So far there is no major bug/issues i found in my daily use like phone calls, wifi, themes, games & apps running fine, and i do dirty flashing with last nightly build if there are a lot changes/fixed.
Q&A for [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
NEO2598 said:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
Click to expand...
Click to collapse
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
MeestaAytch said:
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
It has been stated in the ROM thread multiple times that you must use a 4.2 STOCK JB MODEM for best compatibility. Any other modems you guys use is solely at YOUR OWN DISCRETION. @MeestaAytch they should know what to use at this point but thanks for clarifying again for those who don't want to search before posting :highfive:
@jakew02 no problem. I know it's tiring repeating the same information but from what I've seen in my time using XDA.... It'll never change.
I'm glad you devs still continue doing what you're doing for us though knowing this nonsense goes on.
Sent from my LG-LS980 using Tapatalk
A few bugs
Hi,
The thread is too big for me to go thru it post by post so I'll just make a few questions and hopefully I'll get some answers. I flashed this ROM and it was working flawlessly. I only found very few bugs like not being able to set up multiple recurrent alarms because the app would freeze and there was another bug but I can't remember. The problem I find frustrating is with the text messages or SMSs. At first I was not receiving SMSs. Then I was receiving them but I couldn't send any. I returned back to stock VS98024a and I'm still having the same problem but at least I'm getting a pop-up when "General problems: cause code 96". I have googled this several times in several ways and can't seem to find a solution, not even on the Verizon site or help app on the phone. I need help with this please.
How to keep the back home task manager buttor on the screen?
battery life? i want to install on lg d800 and its beta only..
dori kernel
Hi,
From where you get Dorimanx kernel for AOSP ROMs ?
My phone says it can't connect to the camera, and the torch. Does anyone know how to solve this?
Sent from my LG-LS980 using XDA Free mobile app
LG G2 D802 SIM not recognized
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
a13xch1 said:
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
Click to expand...
Click to collapse
Please state exact filename and order of wipe/flash.
Just tried the test build for D802. Booted at LG logo for a while then screen turned black with 2 red lines and one green vertical line. I was so sure I was gonna get the permanent black lines but then again I read that the damaged screens are caused by already faulty hardware under high heat.
Anyways, I panicked and then I restarted the phone by pressing power + down. Then I got the weird boot sequence like everyone above describes and it boots into the OS. Thank God I got no black lines! However it wasn't stable for me as the phone rebooted itself twice within the span of 20 minutes. I'm going back to 13/10 build for now.
Any d802 users flashing latest twitter released rom can you please report here if jdi or lgd and whether or not weird logo appeared?
I'm on jdi and had weird logo appeared after clean flash. I did not let the rom boot and reflashed previous version without further problems
FYI, houston's latest works great so far on the VS980. Clean flash, using RenderKernel R24.
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
jclemens23 said:
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
Click to expand...
Click to collapse
Migrating from one ROM to another is for me like this:
1. Nandroid backup
2. Wipe all except sdcard (yes, wipe system)
3. Flash new ROM
Be sure to always have a Nandroid backup!
And always check what baseband (aka radios or modem) your new ROM is requiring.
-___-
If you are UPDATING your current ROM, I.e. flashing a new build of let's say paranoid android, you can flash the updated file right on top of your old system. That is called DIRTY FLASHING and it's actually risky, so please, always do Nandroid backups!
-____-
Peace
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
jclemens23 said:
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
Click to expand...
Click to collapse
Ok
I would;
Update my custom recovery to the latest
Download recommended baseband, to be on the safe side
Redownload the ROM
Check the md5-checksum
Retry to install it
Flash the recommended baseband, better safe than sorry
Never give up
Peace
Hi guys i just flashed the newest build and out of all the roms i have flashed i have never seen this problem. After i flashed i have no sim service at all. Done a clean install still no good.
Hey everyone, I've been away for a very long time from this device (and forum obviously), I need some help catching up. My device is currently running rastapop rom (5.0.1) with CWM 6.0.4.7. I want to renew my device with a clean, latest and stablest rom, I dont care about features or Android version. Can anyone recommend me a good, solid rom, and provide some details regarding the installation? (e.g should I update bootloader or CWM?)
Many thanks in advance.
I found that the latest stock 5.1.1 on a nexus 4 is very stable without any issues.
Latest build of purenexus rom is awesome.
I had been away from this phone for a while as well and I have to agree the latest Pure Nexus is butter(first I updated to the latest official 5.1.1 to get the latest partition updates.). Better than average battery life, super stable. I've yet to have a single reboot or any other unpleasantness.
Sent from my Nexus 4 using XDA-Developers mobile app
un.droid said:
Hey everyone, I've been away for a very long time from this device (and forum obviously), I need some help catching up. My device is currently running rastapop rom (5.0.1) with CWM 6.0.4.7. I want to renew my device with a clean, latest and stablest rom, I dont care about features or Android version. Can anyone recommend me a good, solid rom, and provide some details regarding the installation? (e.g should I update bootloader or CWM?)
Many thanks in advance.
Click to expand...
Click to collapse
The first thing you should do is to flash the latest twrp recovery, CWM is not maintained anymore for the nexus 4.
Sent from my Nexus 4 using XDA Labs