Related
This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.
I wanted to try out an AOSP 4.3.1 rom (IllusionRom-2.6 ) coming from a TouchWiz 4.1.2 rom (Trans-Nebula Build 2). I made a nandroid of my current rom using TWRP before installing the AOSP rom. I factory data rest and wiped system, dalvik, and cache 3 times. I installed the AOSP rom with no problem. The problem came when I tried to go back to the TouchWiz rom. On three programs so far (K-9, Google Drive, RoundR), the screen is black and barely readable. I tried restoring my nandroid, factory rest and a fresh install of the rom, and formatting data. I even tried restoring my original stock backup. Nothing has fixed the problem. The only thing I haven’t tried is to Odin back to stock. The reason for being hesitant on Odin is I had so many problems the first time on Windows 8 and using CASUAL to root. I have considered changing to ClockworkMod Recovery and using Mobile Odin to get back to stock. Before doing that, I would take any suggestions for correcting the colors.
If I restore the AOSP rom, the colors are correct. I don’t want anyone to think anything is wrong with either rom. Both worked fine, just I prefer some of the TouchWiz features.
Hi,
I'm having this issue where I get a pop-up window saying "Android is upgrading..." and "Starting applications..." every time I reboot the phone. It's not the same as when I wipe the dalvik cache where it states "Optimizing applications # through #" for about a minute or two on reboot. What I'm seeing is about 1 to 3 seconds.
I did a complete factory reset, re-flashed the ICS RUU as well as the ROM. It was fine in the beginning and for quite a while after I reinstalled my apps but it eventually came back.
I tried uninstalling apps a few at a time and it didn't change anything until I got down to the last four and then it went away. So, I then tried restoring from nandroid backup and just removing those four apps but it didn't work that time. The issue was unaffected.
I realize that the symptoms point to one or more of my apps but I was wondering if there is some kind of diagnostic logger that I can use to record whats happening during reboot that might offer some hints as to which one(s). One possible indirect culprit might be Superuser. I've had a permanent issue with updating the SU binary. When I do, I lose the ability to add new root apps. I keep root for existing root apps, but SU won't detect any requests from new apps. Therefore, I simply don't update the binary and I have no problems with new apps.
Any suggestions or recommendations would be greatly appreciated.
Thanks.
RuLEoF2 said:
Hi,
I'm having this issue where I get a pop-up window saying "Android is upgrading..." and "Starting applications..." every time I reboot the phone. It's not the same as when I wipe the dalvik cache where it states "Optimizing applications # through #" for about a minute or two on reboot. What I'm seeing is about 1 to 3 seconds.
I did a complete factory reset, re-flashed the ICS RUU as well as the ROM. It was fine in the beginning and for quite a while after I reinstalled my apps but it eventually came back.
I tried uninstalling apps a few at a time and it didn't change anything until I got down to the last four and then it went away. So, I then tried restoring from nandroid backup and just removing those four apps but it didn't work that time. The issue was unaffected.
I realize that the symptoms point to one or more of my apps but I was wondering if there is some kind of diagnostic logger that I can use to record whats happening during reboot that might offer some hints as to which one(s). One possible indirect culprit might be Superuser. I've had a permanent issue with updating the SU binary. When I do, I lose the ability to add new root apps. I keep root for existing root apps, but SU won't detect any requests from new apps. Therefore, I simply don't update the binary and I have no problems with new apps.
Any suggestions or recommendations would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
1.) How did you root the rez? some are very picky 2.) are you using Titanium backup to restore system apps or using an app like kernel tuner?
I used the ICS RUU installation guide on TeamBAMF which walks you through using the HTC bootloader unlocker, flashing a recovery and a custom ROM. Later on, I used the S-OFF tool from JuopunutBear and flashed RezROM Ex 3.4.
I do use TBU but not to restore system apps or any data in general. I understood a long time ago that restoring data can lead to trouble so I rarely do it. I occasionally use TBU to restore user apps (no data) but have gotten into the habit of using the market links to get the app directly from the market.
RuLEoF2 said:
I used the ICS RUU installation guide on TeamBAMF which walks you through using the HTC bootloader unlocker, flashing a recovery and a custom ROM. Later on, I used the S-OFF tool from JuopunutBear and flashed RezROM Ex 3.4.
I do use TBU but not to restore system apps or any data in general. I understood a long time ago that restoring data can lead to trouble so I rarely do it. I occasionally use TBU to restore user apps (no data) but have gotten into the habit of using the market links to get the app directly from the market.
Click to expand...
Click to collapse
what recovery are you using? Amon ra 3.1.6 has the su and superuser installer built in and ive never had issues....id also suggest after actually running an RUU.exe and not an OTA (ph98img file) to do the amon ra method and a pure clean flash...should fix your issue
Ok. I'll try your suggestion to help solve the Superuser problem, but what do you think about getting rid of the "upgrading" messages? Is there a way to record what the system is doing during reboot?
RuLEoF2 said:
Ok. I'll try your suggestion to help solve the Superuser problem, but what do you think about getting rid of the "upgrading" messages? Is there a way to record what the system is doing during reboot?
Click to expand...
Click to collapse
if you are familliar with adb you can pull a logcat....to be honest though this does sound like either a bad or unclean flash of a rom or the whole rom itself
REV3NT3CH said:
if you are familliar with adb you can pull a logcat....to be honest though this does sound like either a bad or unclean flash of a rom or the whole rom itself
Click to expand...
Click to collapse
You are correct that the re-flash will solve the problem, but only temporarily. If this was a first time occurrence, I agree that a pure clean re-flash is the best approach but I've already done that numerous times, well over a dozen in the past year or so.
Only a couple weeks ago I did a complete wipe of everything (factory reset, data, cache, dalvik cache, boot, system, rotate settings AND battery stats) and then re-flashed the RUU four (4) times back-to-back. The TeamBAMF guide says to flash it twice so I doubled it to be sure. I then flashed the ROM twice. That solved the "Updating" problem as it always has. However, once I finished re-installing my most frequently used apps, the problem came back.
It hasn't been consistent. It doesn't always come back. Doing the wipe and re-flash works about 50% of the time. I'll go months without it showing up again and then all of the sudden, there it is. It doesn't seem to correlate to the installation of any one particular app. I've tried installing only a few at a time and watching it but when it does come back, it never occurs until after I've installed my most basic line-up.
If there is any one activity that it seems to follow it is after I've had another issue (usually tinkering with a root app or mod and didn't like the way it turned out) and performed a wipe and nandroid restore. It doesn't come back every time, but it's on that initial reboot when I usually first notice it. In those cases, it's always hard to say whether the root app or mod caused the problem or did the wipe and restore do it.
RuLEoF2 said:
You are correct that the re-flash will solve the problem, but only temporarily. If this was a first time occurrence, I agree that a pure clean re-flash is the best approach but I've already done that numerous times, well over a dozen in the past year or so.
Only a couple weeks ago I did a complete wipe of everything (factory reset, data, cache, dalvik cache, boot, system, rotate settings AND battery stats) and then re-flashed the RUU four (4) times back-to-back. The TeamBAMF guide says to flash it twice so I doubled it to be sure. I then flashed the ROM twice. That solved the "Updating" problem as it always has. However, once I finished re-installing my most frequently used apps, the problem came back.
It hasn't been consistent. It doesn't always come back. Doing the wipe and re-flash works about 50% of the time. I'll go months without it showing up again and then all of the sudden, there it is. It doesn't seem to correlate to the installation of any one particular app. I've tried installing only a few at a time and watching it but when it does come back, it never occurs until after I've installed my most basic line-up.
If there is any one activity that it seems to follow it is after I've had another issue (usually tinkering with a root app or mod and didn't like the way it turned out) and performed a wipe and nandroid restore. It doesn't come back every time, but it's on that initial reboot when I usually first notice it. In those cases, it's always hard to say whether the root app or mod caused the problem or did the wipe and restore do it.
Click to expand...
Click to collapse
which leads me to believe its a rom issue for that specific rom...ive never used that one so i cant verify thats what it for sure is....but having to flash the same rom twice for it to work seems like what can cause it in the first place because it already obviously clearly has some bugs...also flashing an RUU (which is a windows .exe based program...many people confuse this with an OTA ph98img file) is actually partitioning, wiping, and re installing the pure factory OS, HBOOT, and Recovery... which no recovery can do....which shouldnt be done directly before a rom install...a full thorough wipe in a custom recovery and then the install of the actual rom you are trying to obtain is how it should be done...to be honest though with how buggy this rom sounds id just suggest going to a new rom....which i have good suggestions for sense based ones
REV3NT3CH said:
which leads me to believe its a rom issue for that specific rom...ive never used that one so i cant verify thats what it for sure is....but having to flash the same rom twice for it to work seems like what can cause it in the first place because it already obviously clearly has some bugs...also flashing an RUU (which is a windows .exe based program...many people confuse this with an OTA ph98img file) is actually partitioning, wiping, and re installing the pure factory OS, HBOOT, and Recovery... which no recovery can do....which shouldnt be done directly before a rom install...a full thorough wipe in a custom recovery and then the install of the actual rom you are trying to obtain is how it should be done...to be honest though with how buggy this rom sounds id just suggest going to a new rom....which i have good suggestions for sense based ones
Click to expand...
Click to collapse
Well, if you wouldn't mind offering some of your ROM suggestions and perhaps a sound RUU download source I'll give it a go and see what happens. I'm sure the initial results will be positive, it's the long-term that will be the real test.
One more piece of potentially useful information. I've converted one market app from user to system and froze, uninstalled or converted several user apps that were installed as system apps by the ROM. I read in one thread where someone had the same issue and a responder theorized that it could be from converting a user app to system. The responder followed saying the issue could be a symptom of the converted app not having corresponding "odex" files. I'm only a modest tinkerer and certainly not a developer so I'm not sure what that means or how important that is. However, I tried reversing the three conversions that I did and the issue persisted.
RuLEoF2 said:
Well, if you wouldn't mind offering some of your ROM suggestions and perhaps a sound RUU download source I'll give it a go and see what happens. I'm sure the initial results will be positive, it's the long-term that will be the real test.
One more piece of potentially useful information. I've converted one market app from user to system and froze, uninstalled or converted several user apps that were installed as system apps by the ROM. I read in one thread where someone had the same issue and a responder theorized that it could be from converting a user app to system. The responder followed saying the issue could be a symptom of the converted app not having corresponding "odex" files. I'm only a modest tinkerer and certainly not a developer so I'm not sure what that means or how important that is. However, I tried reversing the three conversions that I did and the issue persisted.
Click to expand...
Click to collapse
if youve already used an ruu once you dont need to do it everytime you flash a rom....and depending on the rom certain recoveries wont work for them...good example amon ra will not work for JB or higher....if staying on ICS or sense based roms stick with amon ra only....im guessing your looking for a good Sense based rom correct?.....as for converting apps...i highly suggest against it on sense rom and can cause issues with the rom...on aosp its fine but sense just doesnt like some of them
REV3NT3CH said:
if youve already used an ruu once you dont need to do it everytime you flash a rom....and depending on the rom certain recoveries wont work for them...good example amon ra will not work for JB or higher....if staying on ICS or sense based roms stick with amon ra only....im guessing your looking for a good Sense based rom correct?.....as for converting apps...i highly suggest against it on sense rom and can cause issues with the rom...on aosp its fine but sense just doesnt like some of them
Click to expand...
Click to collapse
My mistake, but I should have been more specific. I've only re-flashed the RUU three... maybe four times since I've owned the phone and only as a last resort to fix a problem that a wipe and/or ROM re-flash alone wasn't correcting.
As for recovery, I've only used Amon Ra on my Rezound. It's what was recommended in the Team BAMF guide and I've stuck with it. I do prefer a sense-based ROM and ICS works fine for me right now. The HTC Incredible was my first smart phone and I rooted that within a month of getting it. I tried a few ROMs but eventually settled on Skyraider which I really liked. RezROM is the only comperable ROM that I've come accross for the Rezound, but if you have recommendations, I'll give them a try.
Here's what I've done so far. The ICS RUU linked in the Team BAMF guide was an internal flash through the bootloader. To eliminate that as a possible cause, I found a couple .exe versions to run from my PC.
On the first run, I immediately flashed RezROM and used Amon Ra to install Superuser and SU as you suggested. I updated Superuser and then installed a few basic root apps: Titanium Backup, Root Explorer, QuickBoot, Busy Box, Root Checker and Root Validator. There were no issues until I starting using those root apps. I was periodically rebooting and it wasn't until I updated Busybox and ran TBU and Root Explorer that the "Android is upgrading..." message came back. Worse than before, it was doing the "Optomizing apps # through ##" part where before it was just the "upgrading" message. I uninstalled all of them one-by-one but whatever happened was perminant because it didn't go away so I did a full wipe and used the second ICS RUU .exe. On the second run I stayed stock. Again, I used Amon Ra to install Superuser and SU. I updated Superuser and then installed those same basic root apps. So far, no issues.
With these results, it's pretty evident that the problem is ROM related, but not necessarily a bug as much as a compatibility discrepancy. This issue has never been this persistent until the last few months and within that time, there has been several updates for TBU, Root Explorer and Busybox. I agree that switching to a different ROM may be the ultimate solution, but unless there is one that is a RezROM comparable, I'm not ready to write it off just yet. If there's a way to pin point which app is the cause, I might be able to find a workaround or persuade the developer to come up with a fix, I'd much rather try that first.
But again, I'm certainly interested in trying out any ROM suggestions you might have to offer in the meantime.
In the process of trying to nail down this problem, I've discovered that it appears to have something to do with the relationship between superuser and RezROM.
Since I first flashed RezROM, I haven't been able to update superuser or the binary in any way. In addition to downloading from the market, I've tried re-installing superuser with Amon Ra, flashing it from the sdcard in recovery and from adb. No matter how I do it, I either lose root or it shuts down superuser's ability to detect requests from new root apps. I tried to find a solution but had no success so I just decided to ignore it as long as it didn't effect functionality. I've had root app issues here and there but always chalked it up to a bug with that particular app and either found a fix or ditched the app altogether.
I've been able to isolate superuser as the cause of the "upgrading" message issue with several full wipes, RezROM and RUU re-flashes. In my last three attempts to narrow it down, I did completely sterile RUU and RezROM flashes and used Root Explorer and Root Checker as test apps. In each attempt, I lost root and the "upgrading" messages returned as soon as I updated superuser or the binary. I tried doing the same with the stock ROM and with one of the BAMF ROMs and these problems don't occur with either of them.
So, with the "Android is upgrading" message popping up repeatedly, having new stability problems with previously dependable apps and increasing system bugs, it's apparent that the consequences of having such a severely outdated superuser has finally caught up with me. It definitely looks like RezROM is the problem and unless there are some options that I might try to fix it myself, it's up to the developer. I've contacted them but I'm not optimistic that they'll be willing to put any time into coming up with a fix since the Rezound is so "dated".
I had this popup on every boot on my Evo 3D with the stock ICS Sense 3.6 ROM, I still have it on my Rezound with a custom ICS Sense 4.1 ROM. I just assumed it's standard behaviour from Android, why would you think it's an issue if it doesn't cause any problems?
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse