Hi
It seems that the new 4.4 PAC ROM just reboots with a bunch of errors. Has any one had luck flashing this ROM?
SpiKeTheOne said:
Hi
It seems that the new 4.4 PAC ROM just reboots with a bunch of errors. Has any one had luck flashing this ROM?
Click to expand...
Click to collapse
Honestly, the only issue I had was the bork roaming radio. (Fix: on stock change modem from Global to lte/cdma only before flashing)
Besides that I never really had issues. I did Have random reboots on Carbon though.
Related
I am trying to troubleshoot a phone issue for a co-worker and their phone goes a blank yellow screen and then reboots randomly. Anyone have any suggestions on how to fix this?
What is the story behind the problem?
Sent from my SGH-I717D using xda app-developers app
Murmur95 said:
I am trying to troubleshoot a phone issue for a co-worker and their phone goes a blank yellow screen and then reboots randomly. Anyone have any suggestions on how to fix this?
Click to expand...
Click to collapse
I'd like some more info if you know.
What version android is it running?
Is the phone rooted or running a custom rom?
Does the phone boot up and run at all?
What version android is it running?
I have tried different roms the current one is supernexus 4.2.2 and the last was PA 3.5#. PA seemed to run the best so far
Is the phone rooted or running a custom rom?
Rooted w/ custom rom
Does the phone boot up and run at all?
Yes and for the most part it worked fine, it just rebooted randomly.
I have tried a bunch of other ROMs as well but they seem to crash a lot / random reboot more.
I installed the ROMs myself (I know how to do it) and he never touched the system, when I installed I used TWRP 2.5.0.0 deleted cache, system, factory reset installed rom and cleaned cache afterwards.
He has a bell Galaxy Note - i717 which is calle QunicyATT i believe.
One partially unresolved issue with the 4.2.2 roms are random reboots, due to the kernel they have been building with.
There are some stable rom-kernel combinations available.
rangercaptain said:
One partially unresolved issue with the 4.2.2 roms are random reboots, due to the kernel they have been building with.
There are some stable rom-kernel combinations available.
Click to expand...
Click to collapse
Any you suggest?
I use stock, for greatest stability. I value that above all the other features.
No opinion on 4.2.2.
rangercaptain said:
I use stock, for greatest stability. I value that above all the other features.
No opinion on 4.2.2.
Click to expand...
Click to collapse
It doesn't need to be 4.2.2, just anything stable and minus TW crap.
What TouchWiz crap?
You can use the debloated stock and change to any launcher.
I have to chime in and say ... ics Gubment Cheeze was ALWAYS as stable as stock for me ... yes I am very partial to it But it is fact .. but any ics rom should do the trick for you ... (but Cheeze is best) .. best of luck
rangercaptain said:
What TouchWiz crap?
You can use the debloated stock and change to any launcher.
Click to expand...
Click to collapse
I concur.
Hello everyone,
It has been more than one year that I've been using Samsung-based custom ROMs on my S3, but now when I want to use an AOSP ROM, I can't make calls with them!
I've tried Cyanogenmod 10.2 (latest weekly) and SlimBean 4.3 (latest stable) and when I try calling someone, the call ends immediately. If I try opening the phone app -> settings -> Additional settings, I get a "Call settings error: Network or SIM card error". This does not happen when I use the stock ROM or a Samsung-based ROM (like Wanamlite or Omega, which I've used the most).
What should I do? I'd appreciate any help!
Tormeister said:
Hello everyone,
It has been more than one year that I've been using Samsung-based custom ROMs on my S3, but now when I want to use an AOSP ROM, I can't make calls with them!
I've tried Cyanogenmod 10.2 (latest weekly) and SlimBean 4.3 (latest stable) and when I try calling someone, the call ends immediately. If I try opening the phone app -> settings -> Additional settings, I get a "Call settings error: Network or SIM card error". This does not happen when I use the stock ROM or a Samsung-based ROM (like Wanamlite or Omega, which I've used the most).
What should I do? I'd appreciate any help!
Click to expand...
Click to collapse
Try flashing different modem... That might be the problem... as EFS partitions for OLD modems and NEW modems are completely different format...
Chaitanyapatel8880 said:
Try flashing different modem... That might be the problem... as EFS partitions for OLD modems and NEW modems are completely different format...
Click to expand...
Click to collapse
Seemed like a good idea - I tried flashing 3 different versions (via Odin) and none of them made the calls work
Maybe I'm just using the wrong ones?
Can anyone link me the latest modems available for the international S3 that works with the 4.3.x android versions and the new EFS partition formats? I'd appreciate it so much, as I can't find anything past 4.1.2 versions :good:
Tormeister said:
Seemed like a good idea - I tried flashing 3 different versions (via Odin) and none of them made the calls work
Maybe I'm just using the wrong ones?
Can anyone link me the latest modems available for the international S3 that works with the 4.3.x android versions and the new EFS partition formats? I'd appreciate it so much, as I can't find anything past 4.1.2 versions :good:
Click to expand...
Click to collapse
the cm roms use the modems that exist on the rom your phone is already consisting of. http://forum.xda-developers.com/showthread.php?t=1740061 check the above link for any modems. hope it helps you. may be you are flashing the roms in some wrong way.
sriram231092 said:
the cm roms use the modems that exist on the rom your phone is already consisting of.
Click to expand...
Click to collapse
That's EXACTLY the problem! Those modems from 4.0.4 or 4.1.2 samsung-based ROMs won't work on the 4.3.x builds from CM or SlimBean and I can't find any that works
sriram231092 said:
http://forum.xda-developers.com/showthread.php?t=1740061 check the above link for any modems. hope it helps you.
Click to expand...
Click to collapse
I did - I tried three versions (old, new and random one) and none worked
Also, I've checked this modem+RIL thread: http://forum.xda-developers.com/showthread.php?t=2076857
And it says "Official CM10.1 uses open source RILs so these Samsung RILs won't be compatible". Well, I guess I'll try flashing CM 10.1 instead of 10.2 to see if it works, but the point is... It seems that if I go from a samsung-based ROM to an AOSP one it will fail unless I find a working modem or an AOSP ROM that includes the damn modem
sriram231092 said:
may be you are flashing the roms in some wrong way.
Click to expand...
Click to collapse
To install the stock ROM I do a full wipe and flash it via Odin;
To install the Clockworkmod Recovery I flash it via Odin;
To install any custom ROM, be it sammy-based or AOSP, I do a full wipe and install it via CM recovery;
To install the modems I flash them via Odin
What could be wrong?
Also, I really appreciate the help!
Tormeister said:
That's EXACTLY the problem! Those modems from 4.0.4 or 4.1.2 samsung-based ROMs won't work on the 4.3.x builds from CM or SlimBean and I can't find any that works
I did - I tried three versions (old, new and random one) and none worked
Also, I've checked this modem+RIL thread: http://forum.xda-developers.com/showthread.php?t=2076857
And it says "Official CM10.1 uses open source RILs so these Samsung RILs won't be compatible". Well, I guess I'll try flashing CM 10.1 instead of 10.2 to see if it works, but the point is... It seems that if I go from a samsung-based ROM to an AOSP one it will fail unless I find a working modem or an AOSP ROM that includes the damn modem
To install the stock ROM I do a full wipe and flash it via Odin;
To install the Clockworkmod Recovery I flash it via Odin;
To install any custom ROM, be it sammy-based or AOSP, I do a full wipe and install it via CM recovery;
To install the modems I flash them via Odin
What could be wrong?
Also, I really appreciate the help!
Click to expand...
Click to collapse
i was on the latest indian samsung official firmware. later i rooted and flashed cm 10.2 by temasek. i faced no such problems till now when ever i flash aosp or aokp roms. i didn't say you WERE wrong, i said you MAY be wrong. try flashing the latest f/w of your region first and then flash any of your like custom roms.
sriram231092 said:
i didn't say you WERE wrong, i said you MAY be wrong.
Click to expand...
Click to collapse
I didn't imply anything, I just wrote how I flash stuff to check if something could be wrong
sriram231092 said:
i was on the latest indian samsung official firmware. later i rooted and flashed cm 10.2 by temasek. i faced no such problems till now when ever i flash aosp or aokp roms. try flashing the latest f/w of your region first and then flash any of your like custom roms..
Click to expand...
Click to collapse
Thanks for the suggestion, I will try that too!
Tormeister said:
I didn't imply anything, I just wrote how I flash stuff to check if something could be wrong
Thanks for the suggestion, I will try that too!
Click to expand...
Click to collapse
cool mate good luck
sriram231092 said:
cool mate good luck
Click to expand...
Click to collapse
Did it, still can't make calls. What the hell...
Tormeister said:
Did it, still can't make calls. What the hell...
Click to expand...
Click to collapse
Are you on CM based ROM? If yes you need modem without RIL.
EDIT: Sorry you mentioned that.
Device: Maguro
ROM: crDroid build 16
I know this error is often due to 3G/4G connection in 4.3, but I had no problem with this before when I was with CarbonROM.
However when I flashed Vanir yesterday with a custom kernel, 'process.android.com.phone stopped working' kept popping up..
I tried switching ROM to crDroid which many other folks had no trouble flashing Mpokang v10 kernel with, and the same error occurred.
I tried wiping data, cache and dalvik, and reflash again but to no avail.
I'm desperate for help folks, please lend a hand. Thanks.
Try flashing again but sticking with stock kernel that comes with the rom, it has something to do with changes in the latest CM nightlies that most aosp roms are based on. Wait for your favorite kernel devs to update or repack the kernel yourself.
Sent from my OptimusX4HD using Tapatalk
spamcakes said:
Try flashing again but sticking with stock kernel that comes with the rom, it has something to do with changes in the latest CM nightlies that most aosp roms are based on. Wait for your favorite kernel devs to update or repack the kernel yourself.
Sent from my OptimusX4HD using Tapatalk
Click to expand...
Click to collapse
Funny thing is other folks are flashing custom kernels on the same build as I am on and having no troubles. any ideas?
Hi, I have a problem with my s3, since the upgrade to version 4.3 from 4.1 via OTA wifi it stopped working in 4.1 worked fine and when I upgrade to 4.3 stopped working, I flash, wipes, back to 4.1 , 4.2, put custom ROMS as omega, cyanogenmod and not work, it always stays at Turning on and ever on, not how to solve this problem try everything really, I am currently in version 4.3 and I still have the problem, here attached an image.
Did you try flashing back to a stock TW rom? Some signal issues were fixed for me when I restored back to stock, let gps lock, then set up custom rom.
Sgh-i747
Quantum style
aircooledbusses said:
Did you try flashing back to a stock TW rom? Some signal issues were fixed for me when I restored back to stock, let gps lock, then set up custom rom.
Sgh-i747
Quantum style
Click to expand...
Click to collapse
I put the stock rom and the same thing happens with the custom also, you say that you install rom?
Somneus said:
I put the stock rom and the same thing happens with the custom also, you say that you install rom?
Click to expand...
Click to collapse
when some of the lte builds I was running played havock on my signal setting, reception and such, the only fix was to revert back to stock (for my phone), update the boot loader and modem, then try the custom again. Im speaking from the experience of the ATT I747, but I imagine it could be similar with the international version of the s3.
You did everything, flash a lot of roms and none is solved
I have been out of the loop for a while. I recently updated from 4.3.1 to 4.4.4 AOKP KK... It seams to run smooth... But I noticed the baseband is still VRALJB. Should that be updated? I have has a couple instances where I've had to go into airplane mode and back out just to send a text message. Possible issue with radio?
Screenshot
I605vrufnd7
I'm testing I605VRUFND7 radio now....
Guess I should research first...
I flashed the ND7 zip I found in one of these rom threads via TWRP and all is working great.
glockman4519 said:
I flashed the ND7 zip I found in one of these rom threads via TWRP and all is working great.
Click to expand...
Click to collapse
Thanks. I actually had to reload the phone completely with the ND7 rom until I get things figured out. The AOKP rom and ND7 modem combination for me didn't work. I had way to many failed SMS messages.... and in the middle of fighting with and ex.... I can't have that..... yes... via text.... lol