Develop Bugs

Problem with touch of blue 2.2

Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled

Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled

devnulled said:
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Click to expand...
Click to collapse
The 2am reboots are not a phone issue, it is a known issue with the latest ota. I cant believe they would rather give you a new phone than to admit they sent out a messed up ota.
Try fixing permissions and wiping data as you said.
If 2.2 is installed you should not get a nag to update, as its based on the latest ota.

devnulled said:
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
Click to expand...
Click to collapse
Vzw backup was removed from the rom as most people dont use it. If you want it back, flash this http://dinc.does-it.net/APKs/VZW_Backup.zip, thru recovery.

Thank you cmlusco,
clearing cache and fixing permissions has fixed it, sorry for saying there was a problem. Verizon almost got back 3 phones (an eris that i was given, my old palm pre plus, and my incredible) at the same time with a certified letter having me cancel my contract 6 months early when the phone started rebooting back around the 4th of july. They replaced it last summer/fall when they rolled out gingerbread and my phone got half of it installed when it locked up and would not finish the update but was enough there to lock it from being fixed by ruu even.
I agree that it was not the phone, I told tech support I had it rooted for different skins and roms and to fix buggy software and they suddenly wanted to send out a new phone under warranty. I think they just wanted to get out a phone that was a little harder to root and get s-off rather than fix what was obviously a software bug issue. the new phone was supposed to be fully updated, but it wasnt installed, was still on the prior OTA and had a helluva time getting it to accept a custom recovery to begin with. Would goto the white HTC screen, then flash once or twice and go black with white bars down each side. took 3x to get it to accept it and ended up having to flash an older version first .92 i think (was 3 weeks ago now).
I will flash the backup software this time as my contacts were all edited on the website. Thank you again for the best rom Ive played with in a long time.
(forgot to add when I asked about the mods, I meant in a stock rooted rom that was similar to the old stock+ in use/appearance, but didnt get a nag screen, not that touch of blue did not have it. sorry for the confusion)
devnulled

Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?

dibmem said:
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
Click to expand...
Click to collapse
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.

cmlusco said:
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
Click to expand...
Click to collapse
Thanks for the reply... I wonder what's doing the damage - The dedicated Gmail isn't on my phone. My wife is running TOB as well with the same symptoms. She runs a lot more apps than I do and we were looking for the ext4 fix when I found TOB.
Maybe it's another app? Let me know if you want a list...
Planning to load your rooted stock this weekend and see how things go.
If, in the meantime, you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.

dibmem said:
Thanks for the reply! I saw your rooted stock build - Most likely will go with that.
I wonder what's doing the damage - I could pull Gmail off for the evening and see if mine is stable. My wife is running TOB as well with the same symptoms. We were looking for the ext4 fix when I found TOB.
If pulling Gmail doesn't work - I'll load your rooted stock and see how things go.
If you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
Click to expand...
Click to collapse
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.

cmlusco said:
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
Click to expand...
Click to collapse
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?

dibmem said:
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
Click to expand...
Click to collapse
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.

cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)

dibmem said:
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
Click to expand...
Click to collapse
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.

cmlusco said:
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
Click to expand...
Click to collapse
Results post: Ended up flashing TOB 1.3, radio 2.15.10.12.20, and CMW 5.0.2.0. Updating the radio via hboot ended up being very easy (as long as I verified md5 beforehand.) Our phones are stable overnight - no reboots. Signal sucks here at home, but seems to be slightly better - hopefully will be better around town. If not, there's plenty of other radio versions to try out.

[Q] No data after flashing rom and also a few other questions to follow.

Hello everyone,
I have a question.
I've rooted my girlfriend's S3 it's the AT&T version and I am wondering why after I flash the "JellyBam" rom I am not able to get any DATA connection.
Things I've done so far are as follows:
1.Flashed rom-successful flash-not data.
2. Flashed rom- successful flash-no data again-looked for available modems.
I've looked for what modems or what ever I would need or might have to use and I tried installing them but still no data, I even tried installing the "modem list" program *the one you can flash modems within recovery*, but still nothing. I've even tried just installing the modems in the main "modem lists" thread.
Another thing I want to ask is:
Why is there a "0" in the phones storage? I am thinking is TWRP's is file segregation*I am a noob with the S3*, it seems to me that TWRP has alocated the storage into a different "partition" which I think is dumb.
Sorry if these are noob questions and all, but I have a Dinc and have successfully rooted and flashed numerous roms and it's been a blast and I want to extend my experience with flashing ROMS to my girlfriend. I can't explain/teach her the great things about rooting if I am baffled by the S3's way of doing things.
Anyways, that's pretty much it I know there will be more questions after this... This phone is fun to mess with but if I can't get any kind of data to work then it bums me out that I won't be able to try all the wonderful ROMs this phone has for it.
Thanks for your time.
*Edit:
I like TWRP don't get me wrong, but why doesn't CWM and TWRP play well together, I've tried to flash NAN after Goo'n TWRP, and it wouldn't read the NAN I've made with CWM*I've fixed this though. Should I just ditch CWM for TWRP and be done with it or should I just deal with juggling with both.

v1ral said:
Hello everyone,
I have a question.
I've rooted my girlfriend's S3 it's the AT&T version and I am wondering why after I flash the "JellyBam" rom I am not able to get any DATA connection.
Things I've done so far are as follows:
1.Flashed rom-successful flash-not data.
2. Flashed rom- successful flash-no data again-looked for available modems.
I've looked for what modems or what ever I would need or might have to use and I tried installing them but still no data, I even tried installing the "modem list" program *the one you can flash modems within recovery*, but still nothing. I've even tried just installing the modems in the main "modem lists" thread.
Another thing I want to ask is:
Why is there a "0" in the phones storage? I am thinking is TWRP's is file segregation*I am a noob with the S3*, it seems to me that TWRP has alocated the storage into a different "partition" which I think is dumb.
Sorry if these are noob questions and all, but I have a Dinc and have successfully rooted and flashed numerous roms and it's been a blast and I want to extend my experience with flashing ROMS to my girlfriend. I can't explain/teach her the great things about rooting if I am baffled by the S3's way of doing things.
Anyways, that's pretty much it I know there will be more questions after this... This phone is fun to mess with but if I can't get any kind of data to work then it bums me out that I won't be able to try all the wonderful ROMs this phone has for it.
Thanks for your time.
*Edit:
I like TWRP don't get me wrong, but why doesn't CWM and TWRP play well together, I've tried to flash NAN after Goo'n TWRP, and it wouldn't read the NAN I've made with CWM*I've fixed this though. Should I just ditch CWM for TWRP and be done with it or should I just deal with juggling with both.
Click to expand...
Click to collapse
See TWRP as a CWM on steroids. I'd stick with it.
As for your network problem, did you flash modems specific to her carrier? That would most likely help. Also, is her IMEI still fine?
In settings, Mobile network, Network Mode, try to change it to GSM/WCDMA preferred.

Look here for some suggestions on how to get your data back.
As for recoveries, pick one and stick with it. I'd go with TWRP over CWM, personally.
---------- Post added at 08:45 AM ---------- Previous post was at 08:43 AM ----------
v1ral said:
Why is there a "0" in the phones storage? I am thinking is TWRP's is file segregation*I am a noob with the S3*, it seems to me that TWRP has alocated the storage into a different "partition" which I think is dumb.
Click to expand...
Click to collapse
This isn't a recovery thing; it's an Android 4.2 thing - it has to do with Android 4.2's multi-user support. Data from the first user of the device goes into 0/; from the second user, 1/, from the third user, 2/, etc.

BWolf56 said:
See TWRP as a CWM on steroids. I'd stick with it.
As for your network problem, did you flash modems specific to her carrier? That would most likely help. Also, is her IMEI still fine?
In settings, Mobile network, Network Mode, try to change it to GSM/WCDMA preferred.
Click to expand...
Click to collapse
smelenchuk said:
Look here for some suggestions on how to get your data back.
As for recoveries, pick one and stick with it. I'd go with TWRP over CWM, personally.
---------- Post added at 08:45 AM ---------- Previous post was at 08:43 AM ----------
This isn't a recovery thing; it's an Android 4.2 thing - it has to do with Android 4.2's multi-user support. Data from the first user of the device goes into 0/; from the second user, 1/, from the third user, 2/, etc.
Click to expand...
Click to collapse
Thanks for the replies.
I checked what the default modem was AMD searched for it, found it and installed it but nothing*I am a complete noon with flashing modems*
I haven't checked the imei thing thoroughly just yet, but I will check that out...I am just afraid I may bring the phone.
I'm liking twrp is there a way to rearrange the files , like remove the "0" and make it show like before*default way*. I don't like going through hoops so to speak transfering files on the pc.
Again thanks for the quick replies and I will get back to it wen I have the phone.
One more thing, there are many jellybean roms what are good non-vanilla roms? Or is that the "thing" with this phone?

v1ral said:
Thanks for the replies.
I checked what the default modem was AMD searched for it, found it and installed it but nothing*I am a complete noon with flashing modems*
I haven't checked the imei thing thoroughly just yet, but I will check that out...I am just afraid I may bring the phone.
I'm liking twrp is there a way to rearrange the files , like remove the "0" and make it show like before*default way*. I don't like going through hoops so to speak transfering files on the pc.
Again thanks for the quick replies and I will get back to it wen I have the phone.
One more thing, there are many jellybean roms what are good non-vanilla roms? Or is that the "thing" with this phone?
Click to expand...
Click to collapse
You can't do much about the 0. But it shouldn't affect much anyway. Honestly, it's just better organised but I guess it can't be to everyone's liking.
As for IMEI, just make sure it matches the one in the back of your phone. If not, you'll need to get back to stock with Odin.
And can't really suggest a ROM as they're all different and will act different on everyone's phone. The best I can do is to tell you to check them out and read the comments from users.

[Q] Dirty Unicorns 4.2.2 Data Question

I recently unlocked and rooted my LGOG to the Dirty Unicorns 4.2.2 aokp ROM. Since installing the ROM I've been having on and off data problems, as in sometimes my data works but for days at times it doesn't (in the same areas as when it previously worked). My WiFi is working fine but this data problem is irritating especially since I'm out of contact when I leave WiFi range.
I searched the Dirty Unicorns 4.2.2 thread for possible solutions but no one else has reported this problem. I also have searched this Q&a thread and saw people suggesting to update the PRL but I am unable to find how to do that with this new ROM (I knew how to do it on the Stock UI).
So any help would be greatly appreciated. I love everything else about this ROM except for the data problem so I would prefer to keep it for daily use.

Viewman said:
I recently unlocked and rooted my LGOG to the Dirty Unicorns 4.2.2 aokp ROM. Since installing the ROM I've been having on and off data problems, as in sometimes my data works but for days at times it doesn't (in the same areas as when it previously worked). My WiFi is working fine but this data problem is irritating especially since I'm out of contact when I leave WiFi range.
I searched the Dirty Unicorns 4.2.2 thread for possible solutions but no one else has reported this problem. I also have searched this Q&a thread and saw people suggesting to update the PRL but I am unable to find how to do that with this new ROM (I knew how to do it on the Stock UI).
So any help would be greatly appreciated. I love everything else about this ROM except for the data problem so I would prefer to keep it for daily use.
Click to expand...
Click to collapse
have you tried to swap out your apns.xml
http://d-h.st/Xin
try this one ... download extract use a rootfile browser replace the apns.xlm in system/etc giving it the same permissions as the other on rename the old to apns.xml.bak just in case the outcome is worse... reboot into recovery wipe cache and fix permissions... let me know how that goes for you...also can try restoring efs .... and can try going back to a stock based rom update prl and profile the reflash and check again

Thanks for the advice Spleef but unfortunately the apns.xml file did not work, so I guess the next step would be restoring efs. How would I go about doing that?

Viewman said:
Thanks for the advice Spleef but unfortunately the apns.xml file did not work, so I guess the next step would be restoring efs. How would I go about doing that?
Click to expand...
Click to collapse
use free gee I believe, and can try recovery of you have a back up of it

I have another question...where could I find the Stock Based ROM to try to update the PRL?

Viewman said:
I have another question...where could I find the Stock Based ROM to try to update the PRL?
Click to expand...
Click to collapse
In Development. Lifeless, Vectus, Odex, Deodex, Imperium.
Sent from my LG-LS970 using xda premium

I can't get any stock zip to update my prl n that ...
Sent from my LG-LS970 using Tapatalk 4 Beta

Tried Lifeless which turned out to be a horrible choice because the phone now randomly reboots. Upon flashing the ROM, it wiped my SD card and in the process deleted TWRP from my device. One solution I have found is to flash another ROM (I'm going to go with Vectus) but without FreeGee I cannot access recovery to flash the new ROM. I cannot keep my device from rebooting long enough to access the Play Store and combined with the fact that I need to sign in the Play Store to enable my Google account on my device (therefore eliminating the option of installing any programs online), I am unable to access FreeGee.
I originally started this process to just fix my data (by installing a Stock ROM to update my PRL) but using everything I have done has exacerbated or created more problems. If there are any solutions or suggestions from any of the more experienced users I would greatly appreciate your help. Thank you.

Viewman said:
Tried Lifeless which turned out to be a horrible choice because the phone now randomly reboots. Upon flashing the ROM, it wiped my SD card and in the process deleted TWRP from my device. One solution I have found is to flash another ROM (I'm going to go with Vectus) but without FreeGee I cannot access recovery to flash the new ROM. I cannot keep my device from rebooting long enough to access the Play Store and combined with the fact that I need to sign in the Play Store to enable my Google account on my device (therefore eliminating the option of installing any programs online), I am unable to access FreeGee.
I originally started this process to just fix my data (by installing a Stock ROM to update my PRL) but using everything I have done has exacerbated or created more problems. If there are any solutions or suggestions from any of the more experienced users I would greatly appreciate your help. Thank you.
Click to expand...
Click to collapse
wow trying to not be offended by that but if i was you do lgnpst.. the advice everyone has offered including myself was solid...we cannot help the fact that it didnt go right for you obviously must be something missed or done incorrectly since multitudes of others have followed this same advice and links and recovered just fine..your best bet lgnpst back to stock..gl im done offering advice now

LOL spleef you miscontrued the tone of my post. The "more experienced users" was not a slight against you or anyone else who has offered advice, it was in reference to myself since I am continually creating more errors. I am sorry if I offended you but that was honestly not the intention of my post. I appreciate all the advice you have given me, honestly I would be lost without it. I'll update with results.

Viewman said:
LOL spleef you miscontrued the tone of my post. The "more experienced users" was not a slight against you or anyone else who has offered advice, it was in reference to myself since I am continually creating more errors. I am sorry if I offended you but that was honestly not the intention of my post. I appreciate all the advice you have given me, honestly I would be lost without it. I'll update with results.
Click to expand...
Click to collapse
Just to reenforce what sleef said. LGNPST with the ZVB.bin. That will definitely fix your phone. Another option is use teeny bin. Then in recovery, flash the stock odexed ROM by TheShadow1. It might not cute your problem, but it's a shorter way that might work.
Sent from my LG-LS970 using xda premium

Thank you everyone for your help (including you, spleef lol) I used LGNPST and got my phone back to stock then re-rooted and unlocked it. I'm going to try Dirty Unicorns again with the updated PRL and hopefully that fixes the original data problem. I just can't find the GAPPS 4.2.2 file now for Dirty Unicorns, when following the link on the OP the file is no longer available.
Nonetheless this was a great learning experience and thank you again!

let me know how that goes. as im also having data issue. im in the city all day and my reception/data would go from 4 bar to nothing in a matter of minutes lol. I would have to off/on data to get back my bars and data which is odd
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
spleef said:
have you tried to swap out your apns.xml
http://d-h.st/Xin
try this one ... download extract use a rootfile browser replace the apns.xlm in system/etc giving it the same permissions as the other on rename the old to apns.xml.bak just in case the outcome is worse... reboot into recovery wipe cache and fix permissions... let me know how that goes for you...also can try restoring efs .... and can try going back to a stock based rom update prl and profile the reflash and check again
Click to expand...
Click to collapse
hey i was able to download the apns.xlm onto my phone put a copy onto that location u said changed the original to .bak and wiped cache and fixed permission. I'll let u know if this works out fine since im home now using wifi

Problem with Flashing Almost Everything!

I am posting this as a new topic because I don't have enough posts to post my concern in the thread of the ROM I use.
I have been using PATB ROM for a while now without any issues. Since updating to the newest version I have run into severe issues trying to flash anything besides doing Restores. Every time I try to flash something new it fails immediately and this includes trying to flash a new recovery. I did some reading and thought I had found the answer in restoring the system to stock firmware via Odin. However after trying this a short while ago the process failed as well as soon as Odin showed Recovery in the process bar. This screwed my phone pretty bad, but I was able to Odin a new Recovery on to the phone which seems to have taken it back to functioning normally. I am still unable to flash anything and the only stuff I can do inside Odin is to put different Recovery zips on the device. But even after doing that I am unable to flash anything, and it jumps to Failed right away.
I am not much more then slightly experienced when it comes to rooting and flashing but I have never come across anything like this before. I was using Xposed Framework and I unistalled it because I thought it might be causing the issue. But still no luck. This is driving me crazy. Any help with this would be greatly appreciated because I would like to try out some new ROMs. By the way my flash count reads as only 4 when taken into download mode even though I am pretty sure I have flashed more then that; unless it only trips when completely changing ROMs which would make it a correct count. So I am hoping somebody out there has seen this before and knows how to help me get past this. Thanks to those who are able to help.

Have you tried flashing the full MK4 firmware? IIRC you can't go backwards. Try this out: http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
Use Odin 3.07. If it fails go with 3.09. Please let me know if it works or not. Your partitions may be corrupt but that's a LONG shot. Let's just stick with you're trying to downgrade and the bootloader isn't letting you
Sent from my SPH-L900 using xda app-developers app

After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.

dragonrider6218 said:
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
Click to expand...
Click to collapse
If you decide to go to MK4 be sure to install Philz Cwm Recovery or your problems will start all over again

Cell service constantly disconnecting and reconnecting

Hello!
My issue is that every so often (once every 20-30 minutes or so) my cell service just completely drops to absolute nothing, the drawer saying "NO SERVICE" at the bottom. Then about 20-30 seconds later, the connection is re-established and everything works fine again. Rinse and repeat. This has been going on for weeks now.
It seems very similar to an issue I noticed some other forum members had when d2att ROM builds were unified into d2lte. The fix was to Odin back to the stock 4.3 TW firmware and then start the custom ROM install process over again. However, I've already done this a few times and nothing has worked for me yet. CM, PA, Omni, Nameless, etc., I tried them all with no luck. The issue even happens on stock TW after I get through the Odin flashing process.
I recently upgraded to the newest UCUFNE4 bootloader/modem combo, thinking that a modem upgrade would do the trick. No dice. And now it sucks because I can't go back to 4.3 without bricking my phone (unless there's a 4.4 stock firmware for Odin floating around somewhere?).
My carrier is AT&T (well, it's actually an MVNO called StraightTalk), and I've contacted StraightTalk multiple times asking what might be going on. They seem to think it's a local cell tower malfunctioning. But I've waited and waited and am now assuming they simply don't know.
So I'm basically out of ideas. Help me, XDA. You're my only hope. Movie reference aside.
Is there perhaps a log I can provide or tool/app I can run that shows what I'm experiencing in more detail?
Thanks!

i have seen some custom rom OP instructions mention if having wifi issues to flash a custom kernel. dont know if that would help. BUT remember to double check compatibility and do a backup.
err on the side of kindness

Thanks for the reply.
The Wi-Fi is running great. It's only the cell radio that's causing problems.
Also, I'm usually running BMS kernel, but I've tried many variations and they all experience the same problem.

reflash ne4 modem? double check apn settings?
err on the side of kindness

Re-flashed NE4 modem.
APN settings look good, and I /do/ get LTE coverage. When the connection isn't cut out, of course.
Still no luck.

If its happening on every rom including every stock build youve tried its most likely hardware or the carrier. Ive heard of similar issues recently where we narrowed it down to those two as well. Im starting to think it may be straight talk.... No good way of knowing that im aware of though.

thank you mr huckleberry. my thimble of ideas was o-u-t. :thumbup:
err on the side of kindness

Thanks guys.
I might as well ask: is there any way to Odin back to the stock 4.4 firmware? I'm pretty sure only OTA is officially available, but has anyone perhaps made an unofficial .tar.md5? Seeing as how I can't go back to 4.3...

enewman17 has a stock 4.4.2(NE4) thread. maybe that?
http://forum.xda-developers.com/showthread.php?t=2788357
err on the side of kindness

I saw that thread/post earlier. But they look like recovery zips to me, not Odin .tar/.tar.md5.

my bad. yup, zips. will keep searching
err on the side of kindness
---------- Post added at 09:09 AM ---------- Previous post was at 08:55 AM ----------
what about... http://sammobile.com/firmwares
err on the side of kindness

I did find this post:
http://forum.xda-developers.com/showthread.php?p=53756950
But I'm not trusting an arbitrary post I found when I haven't seen anything similar from DocHoliday or anyone else working on the 4.4 release.
EDIT: The SamMobile site only has old firmwares available.

crap.:banghead:
err on the side of kindness

JJohnson1988 said:
I did find this post:
http://forum.xda-developers.com/showthread.php?p=53756950
But I'm not trusting an arbitrary post I found when I haven't seen anything similar from DocHoliday or anyone else working on the 4.4 release.
EDIT: The SamMobile site only has old firmwares available.
Click to expand...
Click to collapse
I must have missed that. No idea if itll work though. I did try to make an Odin package a while back but couldnt get it to work. Ive got a couple more ideas to try when ive got the time to focus on it, but i know that doesn't help now.
Its not for Odin, but i do have the firmware in a recovery flashable zip. Combined with enewman17's rom, it would almost accomplish the same thing. I think he has the stock recovery in that thread too which would be the last piece needed to get full stock.
Both threads are in the development section.

Well. Good news, guys. I finally solved the problem, mere hours after I became frustrated enough to start a post on XDA.
I ended up flashing to stock 4.4 via the recovery method, hoping to see a difference. Start using the phone for a few minutes, then the cell radio drops out as always. Wonderful.
So then I started thinking about what's common between all the ROM installs I've done. Was there something being left behind that wasn't being cleared properly? That's when I developed a crazy idea.
I remember reading about how there's a special area that's normally inaccessible where information like the phone's IMEI is stored. This is the /efs partition. Now, my IMEI was listed correctly in the phone information, but I decided to tinker around with some things as I was pretty desperate. I eventually got to the debug service menu by dialing *#27663368378# (I looked at a big list of codes online) and looked at what options I had.
The solution? Apparently an NV rebuild! I found this option in the service menu under UMTS >> COMMON >> NV REBUILD. I thought it was a long shot, but the longstanding problem I've had instantly fixed itself after a reboot!
So now my question is: HOW did the /efs partition become "corrupted" in the first place? And how was the phone actually able to make calls correctly and get working LTE data with the downside of service dropouts every so often? Shouldn't it... you know, either work or not work at all?
Anyways, thanks for the help guys. Looks like I don't need to send a nasty letter to StraightTalk after all (awww!).

glad to here you got it fixed. i wouldnt have a clue how it got corrupted, although docholiday77 might know (a WHOLE bunch smarter about this stuff than me), anyway :victory:
might want to hit doc's 'thank button'
err on the side of kindness

It may not have been the EFS partition that was the problem. Not much network related data is stored there. Much is on other partitions such as modemst1 and modemst2.
No one knows why flashing roms has the ability to mess up the NV Data. I suspect that when the system boots for the first time (after a rom flash, for example) it writes something to the NV Data and this is when things can get hosed. Thats just a theory though. Many have had problems with losing their IMEI because of this.
My theory on the IMEI is that after the new flash and boot something gets corrupted. These devices check for corruption during boot and will attempt to automatically restore from an on-device backup. The problem is the backup was never created, and it ends up restoring a null or blank value, causing the IMEI to become 0.
Something similar, but a little different may have happened here. Some data that is used by the carriers network to authenticate your device may have become corrupt or lost.
It wasnt an all or nothing type scenario because the device isnt constantly sending this info, probably only at certain times or intervals. But when it does, the network would not be able to authenticate your device and then block access, which would explain why it would happen every 20-30 minutes. Again, this is purely a theory.
The method you used to solve the problem has actually been around for a couple of years now, believe it or not! But its usually used to fix issues with GPS not being able to establish a lock. Whatever is used to authenticate for GPS, must be similar to what is used for the network in that it uses device specific info (such as the imei or s/n) to create a hash value that is then used in this process. When you chose NV Rebuild, it probably recreated these, thus fixing any issues due to the corruption of those values.
I hope all of that made sense! I am not positive that what i just wrote is 100% accurate, but it does make sense to me.
Now, i am guessing you never created the on-device backup i referred to, so this is how....super easy to do!
You do need to be running rooted stock.
Install and open Terminal Emulator and enter the following:
Code:
su
reboot nvbackup
Thats it! The device will reboot and create its backup. (Youll see blue text flash at the top, similar to when you boot recovery)
The backup is written across several partitions that are never touched by flashing, making it permanent. Flash all you want and itll remain intact unless you deliberately do something you shouldnt, or flash something not for your device.
As i stated before, every time the device boots up, it checks the NV Data for any corruption, and if detected it will auto restore from the backup. Youll never even notice anything was wrong!
Afaik, no one who has done this backup has ever lot their IMEI which is proof enough to me that it works!
SSL! Im glad you figured out a fix for your problem btw! Good work on that!

thank you mr huckleberry. never new how to backup this. guess i should read up on 'terminal emulator commands for newbs'
on it now.!:thumbup:
err on the side of kindness

You wont find the reboot nvbackup command. Its a Samsung specific one. But by all means learn more about the terminal if you can. It can help when writing scripts and troubleshooting all sorts of things!

samsung galaxy s3 i747 ?
err on the side of kindness