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.

[Q] A complete backup?

My phone has root using MotoChopper but I am still using the stock ROM. I really don't want to go through the effort of custom ROM.
The nice thing about the Galaxy S3 was the Kies software that backed up everything important. Is there something like that for Motorola? I have an SD car installed with plenty of space.
Is there something in the Motorola recovery menu that would allow me to perform a backup, or an app? I have titanium backup installed by the way.

Search for recoveries
As you know TB doesn't do a full backup. But as long as you are rooted there are options open to you other than getting another rom installed to do a full Nandroid Backup. Do a search for "Recoveries". I have preferred CWM http://www.clockworkmod.com/ with my past phones but there are a few more you may want to peruse before flashing one.
The great thing about recoveries is that you can Nandroid backup your current rom before flashing a new one. And if you don't like the new one, or it has issues you don't like, just use the recovery to flash back.
I hope this helps you in some way.

gps4213 said:
As you know TB doesn't do a full backup..
Click to expand...
Click to collapse
I've used CWM with previous Android phones. Yes I liked it. A few follow ups ....
1. If all I care about was retoring apps and their settings to the Stock Moto ROM -- could I trust TB for that purpose?
2. Supposing I had the bootloader unlocked -- could I install CWM and just keep the ROM that I have or would I be forced to install a custom ROM?

strike3 said:
1. If all I care about was restoring apps and their settings to the Stock Moto ROM -- could I trust TB for that purpose?
Click to expand...
Click to collapse
Yes, but if all you want is app backups with the ability to restore (Not data just apps) I prefer appsaver. But if you want data as well then TB is superb.
strike3 said:
2. Supposing I had the bootloader unlocked -- could I install CWM and just keep the ROM that I have or would I be forced to install a custom ROM?
Click to expand...
Click to collapse
Having root and or an unlocked boot loader (As phones used to come with) does not mean you have to use any other rom. I plan on keeping the stock rom on my phone as I like it over the present roms.
Remember, you will never be forced to use any rom. With the unlocked boot loader you can use any you choose including stock.
---Edit---
CWM does not yet have a stock recovery for the XT926, give it time and they will. You did not state your exact phone version but I would guess it is the 925/926.
As I just rooted my self I am also looking for a recovery to do a Nandroid backup.
I did find this thread that has some answers IF your boot loader is unlocked...
http://forum.xda-developers.com/showthread.php?t=1973904

gps4213 said:
Yes, but if all you want is app backups with the ability to restore (Not data just apps) I prefer appsaver. But if you want data as well then TB is superb.
Having root and or an unlocked boot loader (As phones used to come with) does not mean you have to use any other rom. I plan on keeping the stock rom on my phone as I like it over the present roms.
Remember, you will never be forced to use any rom. With the unlocked boot loader you can use any you choose including stock.
---Edit---
CWM does not yet have a stock recovery for the XT926, give it time and they will. You did not state your exact phone version but I would guess it is the 925/926.
As I just rooted my self I am also looking for a recovery to do a Nandroid backup.
I did find this thread that has some answers IF your boot loader is unlocked...
http://forum.xda-developers.com/showthread.php?t=1973904
Click to expand...
Click to collapse
I have the 926. I used the recently posted MotoChopper - April 2013 edition -- from DJR bliss to root. I don't know if that unlocks the bootloader as well. Perhaps someone could clue me in.

strike3 said:
I have the 926. I used the recently posted MotoChopper - April 2013 edition -- from DJR bliss to root. I don't know if that unlocks the bootloader as well. Perhaps someone could clue me in.
Click to expand...
Click to collapse
Nope, that JUST allows root access. To unlock the boot loader you need a tad more. Search this forum for droid razr HD utility by Mattlgroff. It has every thing you need to root (And that can be undone) and unlock the boot loader (THIS CAN NOT be undone). Linky
--FYI--
I do not recommend flashing the 4.1.2, but as I said if you are unlocked you can do what ever you want. Being just rooted (Or even not rooted) you can flash 4.0.4 and 4.1.1, when you flash to 4.1.2 you can NOT go back to 4.0.4 or 4.1.1 with out an unlocked boot loader.
And the droid razr HD utility has the CWM custom recovery included!
Bonus!
Any more questions that I can answer before I go to sleep tonight?

Thanks for everything you did -- you deserve sleep. I already had 4.1.2 when i ran MotoChopper. I don't plan on going back or doing a custom recovery or custom ROM. I know I am not using the droid to its full potential however -- i'm just thankful to end the 2 months of banging my head against a wall. As I mentioned on another thread I bought the iPhone 5 on verizon 4 times and returned it all 4 times. I bought the S3 for Verizon once and returned it. 3 of the iPhones and the S3 had chronic wifi issues. I was beginning to think it was me. It was not. With no other variables in my work flow changing -- the Razr HD had none of these problems. I'm sure the M and the Maxx HD would have been fine also. However, I wanted something slightly better than the M and I would have had a hard time squeezing the Maxx HD with a case into my shirt pockets.

strike3 said:
Thanks for everything you did -- you deserve sleep. I already had 4.1.2 when i ran MotoChopper. I don't plan on going back or doing a custom recovery or custom ROM. I know I am not using the droid to its full potential however -- i'm just thankful to end the 2 months of banging my head against a wall. As I mentioned on another thread I bought the iPhone 5 on verizon 4 times and returned it all 4 times. I bought the S3 for Verizon once and returned it. 3 of the iPhones and the S3 had chronic wifi issues. I was beginning to think it was me. It was not. With no other variables in my work flow changing -- the Razr HD had none of these problems. I'm sure the M and the Maxx HD would have been fine also. However, I wanted something slightly better than the M and I would have had a hard time squeezing the Maxx HD with a case into my shirt pockets.
Click to expand...
Click to collapse
Just install twrp as your recovery and make a full backup that way. unlocked bootloader required.
Yes you can trust tibu for app backup and recovery. I flash several times per week and it's the app I use and trust.
Sent from my XT926 using Tapatalk 2

koftheworld said:
Just install twrp as your recovery and make a full backup that way. unlocked bootloader required.
Yes you can trust tibu for app backup and recovery. I flash several times per week and it's the app I use and trust.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Thank you Kofthworld, I will give that a whirl as well. CWM is still my pref until I find better though.

gps4213 said:
Thank you Kofthworld, I will give that a whirl as well. CWM is still my pref until I find better though.
Click to expand...
Click to collapse
I understand where you're coming from. I used to use cmw since the og droid. Twrp has supplanted it fully imo. all of the devs prefer it and it's easy to use. Nonetheless both exist for the xt926. Use this utility for the recovery of your choice.
http://www.droidrzr.com/index.php?/...Ver.3 {UPDATED-4/16/13} More Options Manually
Sent from my XT926 using Tapatalk 2

I think I should have screwed this one up -- and should have done the custom recovery to make a FULL backup. I backed up all my apps using TB. did a complete wipe -- not just a system reset from Settings but -- a motorola AP fastboot style wipe -- with the stock 4.1.2. I re-rooted. Then logged in to Play installed TB.
I think the problem i created occurred when I tried to reinstall system stuff -- not just user apps. I have stock recovery, root at this point. After restarting once i restored those apps and their data I am perpetually stuck on the Droid eye.

strike3 said:
I think I should have screwed this one up -- and should have done the custom recovery to make a FULL backup. I backed up all my apps using TB. did a complete wipe -- not just a system reset from Settings but -- a motorola AP fastboot style wipe -- with the stock 4.1.2. I re-rooted. Then logged in to Play installed TB.
I think the problem i created occurred when I tried to reinstall system stuff -- not just user apps. I have stock recovery, root at this point. After restarting once i restored those apps and their data I am perpetually stuck on the Droid eye.
Click to expand...
Click to collapse
Ok -- I reflashed a stock recovery under AP Fastboot, re-rooted, and then installed TB, doing a 'restore missing apps' - meaning the user installed apps. hopefully ill be ok now.

[Q] How do I stop the update from installing?

So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!

Shamrock13 said:
So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Click to expand...
Click to collapse
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.

mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.

mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
MrMeester said:
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
Click to expand...
Click to collapse
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?

Ya, cm 10.1 has better bat life. I liked liquidsmooths settings better though. Carbon doesn't seem to be as stable atleast for me. But it seems like no one else is having the problems I'm having. I recommend twrp recovery. Run it, see what you think. PM me if you need help.

Shamrock13 said:
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Click to expand...
Click to collapse
Yes you are right, it is the update one.
Sent from my DROID RAZR HD using Tapatalk 4

What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.

Shamrock13 said:
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Click to expand...
Click to collapse
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:

I took an xt 925 today, but i have some knowledgment from my Razr I, which is + - the same procedure/flash.
I want to install some custom roms, so basically all i have to do is unlock my bl, install a custom recovery and try out?
I'm asking that, because i'm on jelly bean, but its a carrier based firmware, and i dont know if this model got any limitation which break me up.

I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!

Shamrock13 said:
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Click to expand...
Click to collapse
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4

mentose457 said:
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
The thing is, I couldn't get back into recovery at all. I had to try like 50 times holding down the buttons to finally get it to even boot to the recovery select screen, and even then it wasn't a sure thing if I were going to get it to boot into recovery. I flashed another ROM, and it still didn't work. I read on the Droid forums that you need to mount system first and then flash, so I tried that and my phone booted up right away.

was kicsnia
mentose457 said:
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
Click to expand...
Click to collapse
Yeah, the brave little toaster! Old school and under rated. Ha ha!

Disable Moto Services. No root, no unlocked bootloader needed. You will never see any update nagging. Even when you turn off/on your phone.
Sent from my DROID RAZR HD using xda app-developers app

(Q) (Help) Problems flashing Roms - can't mount system

Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would try: fastboot flash cache cache.img. use cache.img from the 4.4 factory image.

golem95 said:
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one
Click to expand...
Click to collapse
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app

I've used cataclysm rom with franko kernel and have gotten 24 hours with over 7 screen on

nelomen said:
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wow, 5hrs i get barely 3h +/-

golem95 said:
wow, 5hrs i get barely 3h +/-
Click to expand...
Click to collapse
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Maybe u must change ur cwm
Sent from my GT-S5360 using xda app-developers app

nelomen said:
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
(not sure if pics attached but they are of my 5hrs screen time)
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk

OptimusVDarwin said:
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I've never tried that but am willing to give it a shot after I finish my testing of battery life on stock compared to custom roms.
For some reason I am getting about 2 hours more screen time with stock then with custom rom.
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] Buying the phone today and rooting?

If I buy the S3 from a verizon store today brand new, will I be able to root it and unlock the boot loader still or will it come with a firmware too new?
Sorry if this was answered before. Tried searching but couldn't find results. If they are out there then I blame iOS 7 and my iPhone that needs replacing

I'm not sure what, if any, updates they've had in the last few months but I just got my s3 in August. I did take an update on it and had no issues with using casual to root & unlock. Perhaps someone may have a more recent experience.
Sent from my Slim GS3

Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app

Rooting is a great idea- I'm loving 4.4 on the s3.

clembrowning said:
Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks

fbiryujin said:
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks
Click to expand...
Click to collapse
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.

MisterSprinkles said:
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.
Click to expand...
Click to collapse
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Ah crap. Thanks for the warning. I decided to order a Verizon Moto X Dev Edition. Can't wait for that to arrive.
Thanks to everyone for the info/advice.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium

Macrodroid said:
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I have no problem getting the recovery installed. The custom recoveries are just *non-functional* because they can't mount any partitions. The error logs' are pretty clear, and every custom recovery I've tried behaves exactly the same.