Database Info

wifi error on every ROM

long story short, my phone was shipped with prerelease software. After rooting and flashing a customer recovery, my original nandroid was corrupted.
The only option for me now is custom ROMs, but unfortunately my wifi gives me an error on every single ROM available.
Anyone know of a quick fix?
The only thing i can think of that would solve the issue is to possible flash the stock US ROM once it's available, then hopefully that would fix my wifi issues and i'd be able to flash to any other ROM with no problem.
Alternatively - could someone please post a flashable ZIP of the stock ROM, or at least post a stock nandroid that i would be able to restore onto my phone to see if the wifi issue gets resolved.

Did flashing the stock img work
Sent from my PC36100 using Tapatalk 2

I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA

Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.

Reviewers said:
I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Thanks, hoping this will solve the problem!

suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
It's because all roms now are based on European firmware not T-Mobile firmware.
Tomorrow I'm uploading the first ever T-Mobile Rom and it'll fix everybodys problem.
Sent from my HTC VLE_U using XDA

suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.

suhailtheboss said:
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.
Click to expand...
Click to collapse
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.

nickmv said:
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately this didn't work either. I'm totally out of ideas at this point. Might just end up exchanging the phone and paying the out of warranty fee if they find out the boot loader was unlocked. Not really sure what's left for me to try.

Flash my T-Mobile Nandroid in recovery.

Reviewers said:
Flash my T-Mobile Nandroid in recovery.
Click to expand...
Click to collapse
I did within ten minutes of you posting it. Unfortunately it did not solve the problem. I thought that would be the fix...

One thing I didn't notice was a clear description of the problem. Please describe what your issue is. You say the wifi gives you an error. What does that mean?
Please describe everything in detail from start to finish, before trying to return it.

WiFi will turn on, display available networks, once a network is selected it will not connect and then says "error"
then after about ten seconds the phone will reboot, then reboot after it turns on. never-ending.
only way to have the phone work is to do a master reset, but the problem starts again when you attempt to.connect to WiFi.
also the phone will not stay off when stuck in the WiFi reboot loop. if i choose "power down" it will turn off, then turn back on within 10 seconds.

That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.

nickmv said:
That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.
Click to expand...
Click to collapse
Yeah i'm clueless. I've literally done absolutely EVERYTHING that i could imagine to fix the issue.
I actually work for T-Mo, we dont have any abilities to flash anything in store. Also exchanging the phone is a little bit more difficult for me, because the phone was not purchased through tmobile, it was given to me by HTC a week before launch.
Either way, I'm going to reload all the shipping stuff when i get home tonight then go ahead and try to process an exchange. Worst case scenario they will charge me ~100 bucks as an out of warranty fee. (due to having the *TAMPERED* logo on the bootloader scren. Although I'm fairly certain they don't check that, they shoudl only check for physical/liquid damage. I have processed many exchanges for rooted customers, who had manufacturer defects.

also another thing i just noticed, my baseband is: 0.15.31501S , but my friends retail version is 0.16.
any way for me to update this?

Early Adopters
I just got the One S myself and I'm a bit forlorn from the lack of available ROMS. Then again when I was in the Apple Ecosystem, there was no ROMS, just tweaks so different environment different timelines I guess.

Not sure if it can help in this case, but this solved my wifi error problem.
I had a "wifi error", my One S coudn't connect any AP.
The problem was a bad permision on the file /data/misc/wifi/wpa_supplicant.conf.
Logcat gave me that :
"Cannot set RW to /data/misc/wifi/wpa_supplicant.conf"
So, using Es Explorer (as root), i changed the chmod of this file to rw-rw-rw and wifi started to work again. (no reboot needed in my case).
Hope this help.

tf700 Major, strange problem after update!

Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013

bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.

Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......

What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...

I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol

Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.

Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4

bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.

bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.

I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/

vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.

I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.

vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.

I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.

Nexus 5 major software issues

Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..

NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.

simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.

NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?

simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?

NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.

simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?

NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.

Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.

wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.

You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!

[Q] XT926 Stuck on 11/07 CM 11

I have an XT926 running KKBL CM11 nightlies and have been updating through Cyandelta since Towelroot gave me an unlocked bootloader (thanks Geo). I have been updating without issue until the 11/07 nightly. Ever since then, Cyandelta shows no updates but if I go through the CM Updater, it shows all of the updates released for the moto_msm8960. If I try to apply any of these updates outside of Cyandelta (either through CM Updater or flashing full zip through recovery), I can boot my phone but will start getting a persistent error saying "There's a problem with com.android.phone process and it has to close" or something to that effect. I have tried wiping both caches and even doing factory resets but the process crashing starts back within a few minutes of getting everything set up. I did notice that even though I did a factory reset, all of the apps I have installed still had data from before the wipe so I feel like the wipe is missing something that is causing the crash(?). I've been using custom ROMs for a while on a few different devices but this is the first time I've ran across this. Any advice?

Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.

CWGSM3VO said:
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
Click to expand...
Click to collapse
I've never had to go further than a factory reset before. Which partitions should I format?

I'd format system, data, cache and dalvik. Definitely time to flash clean.
When I had my XT926, I also found that after so many updates via Cyandelta, that I would get the same issue. I would then go back, clean flash the latest update and things would be good. I eventually stopped using Cyandelta altogether. It's a nice idea, but I just don't know if I completely trust its abilities in determining what to bring down and what not to. I'd rather go with the CM updater instead. Yeah, it means longer downloads, but which is longer: downloading the full update from CM and having it work, or downloading via Cyandelta and then having to wipe clean, install and then restore all your backups?

iBolski said:
When I had my XT926,
Click to expand...
Click to collapse
You did abandon ship!

lloydsw said:
You did abandon ship!
Click to expand...
Click to collapse
Yup, but I stated in my post (where I said my goodbyes), that I would still hang around and help out. I know there are a lot of people still on this phone, especially with CM12 now running on it.
But, loving my G3. Still on stock, though (4.4.2), but I have no reason to go to anything else right now. Runs smooth, but it is rooted so I can run TiBu and also enable SD writing. But, I have no other reason to go to CM12 at this time.
I can get at LEAST one day if not more. Usually, after 24 hours, I'm right around 50% on battery. I probably could go even longer, but definitely I get more battery life out this phone than I did on the XT926 (non-MAXX), but I was able to do the same on my non-MAXX, but only if I didn't use it much. With the G3, I can do quite a lot and make it through the day without having to recharge during the day. I love that!
In any case, I'm still lurking about these forums to see if anyone needs help.

Can't get latest firmware update

Hello,
I'm a Canadian user (6045i) that installed the US firmware (7SR4-UE40) a while ago. I'm rooted (flashed SuperSU in Recovery mode).
Today, I finally decided that I wanted to get the latest firmware update (5.0.2-7SRA-UEA2). I did a full unroot with SuperSU, rebooted, checked that the phone was indeed without root access and tried to get the OTA update. Every time I try, it says my system is up to date. Why is that? What can I do to get the update?
Thanks.

So, I'm the only one with that problem?

Download UEA2 and install it like you did with UE40? That's what I've done to get the latest US firmware. We're not going to see the US OTA updates through a Canadian carrier. We have to install these ourselves, manually, just as you did with UE40.

Muskoka said:
Download UEA2 and install it like you did with UE40? That's what I've done to get the latest US firmware. We're not going to see the US OTA updates through a Canadian carrier. We have to install these ourselves, manually, just as you did with UE40.
Click to expand...
Click to collapse
I thought of doing that, but if I recall well, someone mentioned that doing this, you were missing some of the stuff that was installing while doing it with the OTA. Can someone confirm this?
Did you notice some improvement with your phone since you installed the latest update? As for me, the double tap never really works well (well maybe i out of 4 times), this is something I'd like to see improved...

metaleloi666 said:
I thought of doing that, but if I recall well, someone mentioned that doing this, you were missing some of the stuff that was installing while doing it with the OTA. Can someone confirm this?
Did you notice some improvement with your phone since you installed the latest update? As for me, the double tap never really works well (well maybe i out of 4 times), this is something I'd like to see improved...
Click to expand...
Click to collapse
As far as I know the firmware's posted here by users are the "exact" image you would get if you did a OTA update yourself. Improvement, a bit I guess. The double tap can still be an issue once and a while. I find a reboot solves the issue, but only for a while. The Chinese rom was the best performing firmware all around, but changed too much internally (files system) for my liking, so I went back to stock UEA2, with root.

Muskoka said:
As far as I know the firmware's posted here by users are the "exact" image you would get if you did a OTA update yourself. Improvement, a bit I guess. The double tap can still be an issue once and a while. I find a reboot solves the issue, but only for a while. The Chinese rom was the best performing firmware all around, but changed too much internally (files system) for my liking, so I went back to stock UEA2, with root.
Click to expand...
Click to collapse
So, no need to unroot to flash this firmware?
Do you have a link to download it? I can't find it at the moment... Thanks.

metaleloi666 said:
So, no need to unroot to flash this firmware?
Do you have a link to download it? I can't find it at the moment... Thanks.
Click to expand...
Click to collapse
Here's the post I followed (for others that might read this)....instructions are in the first post. I'm pretty sure you need to un-root, I did anyways.
http://forum.xda-developers.com/idol-3/general/convert-canadian-6045i-to-6045i-updates-t3177979
See the 3rd post of this thread for all the user submitted firmwares, UEA2 is at the top of the US firmwares, submitted by Brian117. As famewolf has stated in that thread, these are "out of the box".
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Hope that helps.....

Thanks! If I were doing this as an OTA, I won't have to wipe my device and start all over with the apps. Is there a need to wipe everything with this update? I did wipe everything when I installed the US firmware (from the Canadian) the 1st time, but I'm not too crazy to start all over again...

Try without wiping apps/data, should work fine. If not, you'll have to wipe everything. As your rooted you should have Titanium Backup installed, and doing routine backups of your apps/data. I have my apps/data backed up every night on a automatic schedule at 2 in the morning. It's always there on my external sd card should I have a issue. Makes swapping roms / firmwares a non issue.
Sent from my 6045I using XDA Premium HD app

Muskoka said:
Try without wiping apps/data, should work fine. If not, you'll have to wipe everything. As your rooted you should have Titanium Backup installed, and doing routine backups of your apps/data. I have my apps/data backed up every night on a automatic schedule at 2 in the morning. It's always there on my external sd card should I have a issue. Makes swapping roms / firmwares a non issue.
Sent from my 6045I using XDA Premium HD app
Click to expand...
Click to collapse
I do have Titanium. So, yes, I'll be able to come back to where I was quickly if I have to wipe everything. I was not rooted when I installed the US firmware at first, so I had to reinstall everything. Didn't think of Titanium before asking this time....
Thanks again!