Related
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
boardsportsrule said:
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
Click to expand...
Click to collapse
Find the modem cognition uses that gives you the least problems. Are you flashing to stock before each ROM?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yep, back to stock & master cleared between(only once problems arised..back in the day I could just flash to what I wanted and never really had a problem. Went back to stock once when the new flash responded strangely.)
Looking at cognition, I get minimal information, I THINK it's stock radio/kernel..
http://forum.xda-developers.com/showthread.php?t=912657
Any one???
I would..check your usb plug/cable/port first..make sure it isn't bad and effecting your data transfer..Make sure your not plugged into a external port and plug into PC directly..
Re down load your roms and kernels again..keep them separate from what you have already used..
Flash back to stock..master clear delete all data on your internal and your data
Re-install everything over again..cause it sounds like something got corrupted along the way
Mac
Mac11700 said:
it sounds like something got corrupted along the way
Click to expand...
Click to collapse
Thats how I am leaning, but i dont think it's with the roms/kernels/radios i have downloaded...since I have tried so many damn copies that wouldn't make sense. also tried downloading directly to phone, eliminating the "3rd party" computer, and have used drop box in the past...
I have flashed to stock and master cleared, i could do it again, but i am tempted to go back to stock and try to exchange it for a new one due to either random shut-offs or GPS(both of which mine are effected by..) but i would like to avoid this hassle...
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
boardsportsrule said:
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
Click to expand...
Click to collapse
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
opcow said:
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
Click to expand...
Click to collapse
hopped back to Stock... Gonna run things here, see which problems arise, and go from there. Can you flash a different kernel onto the stock ROM? I'd assume you need a 2.1 kernel, and i don't think many are retrofitted to 2.1, but the KP1 modem is a good idea, ill let things pan out on stock and see what happens if/when i flash kp1 modem.
funny fact: fire fly made problems for me... it's based on rogers 2.2, same as cognition. that seemed odd to me.
I am currently running CM7. But I would rather have my Old stock 2.1. I am running On a Huawei Ascend on Cricket Wireless. I have CWM and ever since I ran CM7 and changed things around it still drains my Battery Faster than usual and heats up my phone. I lowered the CPU and such.
Anyways to the problem:
I have been trying to get the old stock version back on to my phone but for some reason I can not get things to work right. I Try a fast boot and it just reboots the phone back into CM7 and does nothing. I have tried to do it through CMW and same thing happens. I want to try to us the SD Card update option through the Systems settings but I can not find it. I just want to get CM7 off of my phone and mess around with a few other things before I commit to a new mod.
If anyone has any ideas on what I can do just let me know. Is there anything I can do that I have not tried already?
Edit: Yes I know I am new and yes this is my first post. I just need help please, and thank you.
So I started to read up on the new ICS update for Rogers Skyrocket, and the consensus is that it's slow and laggy. I do want to try it out.... but here's the big question...
If I don't care for it.... can I downgrade back to 2.3.6? With no relative issues?
And how would I go about doing it?
No0b question I'm probably sure... but hey if you don't ask you'll never know!
It would be best to back up. Back up creates a copy of your entire phone so you can swap between the two images if you'd like. If you really have important data then I would back up stuff to your PC first.
Im not finding it slow and laggy at all. But yes, pretty sure if youre gonna downgrade you gotta odin the stock tar from sammobile. Might be able to do it through kies, but im not sure
Its not slow and lagy for me. Works great. I upgraded with the sammobile tar installed cwm and rooted. You can always go back. Just install modem and rom or get tar from sammobile.
Sent from my SGH-I727R using XDA
Well I am downloading a TAR from the site here that I found of 2.3.6 so that's ok... I've backed up the phone from Kies so I at least have a copy there... but for the most part I won't lose anything there either. Most everything I have is backed up on Google...
SO I guess I would jsut load the 236 to my external and then install it if i wanted to?
This is a question. therefor, belongs in Q&A. Moved.
Cheers
Hi, noob here (obviously)
I went ahead to downgraded my Rogers GSII LTE from ICS 4.0.4 to GB 2.3.5. It's the correct stock ROM, as I've used it previously without any problems.
I wiped all data while still on ICS, put the phone in download mode, launched Odin with the option "Auto Reboot" checked, nothing else. Pointed the PDA section to the stock ROM. Flashed it, and after about 4 mins it rebooted.
I get to the Android setup page but I can't even launch the setup.
"The process android.process.acore has stopped unexpectedly. Please try again" and it Force Closes.
Anything I can do to clean the phone properly to reload the stock rom?
prbassplayer said:
This is a question. therefor, belongs in Q&A. Moved.
Cheers
Click to expand...
Click to collapse
No Worries PR.... Thanks for the heads up....
And I notice that it's laggy here and there... especially while texting. I've been using advanced app killer and seems to help a little....
Battery life has increased too which is a good thing. But all in all.... They fell flat. Lots of programs that just aren't ICS ready for the GSII
blanchardc said:
Hi, noob here (obviously)
I went ahead to downgraded my Rogers GSII LTE from ICS 4.0.4 to GB 2.3.5. It's the correct stock ROM, as I've used it previously without any problems.
I wiped all data while still on ICS, put the phone in download mode, launched Odin with the option "Auto Reboot" checked, nothing else. Pointed the PDA section to the stock ROM. Flashed it, and after about 4 mins it rebooted.
I get to the Android setup page but I can't even launch the setup.
"The process android.process.acore has stopped unexpectedly. Please try again" and it Force Closes.
Anything I can do to clean the phone properly to reload the stock rom?
Click to expand...
Click to collapse
factory data reset from recovery.
digitalnights said:
So I started to read up on the new ICS update for Rogers Skyrocket, and the consensus is that it's slow and laggy. I do want to try it out.... but here's the big question...
If I don't care for it.... can I downgrade back to 2.3.6? With no relative issues?
And how would I go about doing it?
No0b question I'm probably sure... but hey if you don't ask you'll never know!
Click to expand...
Click to collapse
2.3.6 is not rogers, im guessing u r not rooted or have cwm, if u want to go back to rogers stock its 2.3.5 , u can use kohanes method but not his firmware files, go to sammobile to get the stock files, use i727r in the search box in the firmware section
4.2.1 and 4.2.2 all have 0dbm data drops on them. They also sometimes happen on TW roms. I don't know where else to turn for this, every time I ask it gets buried. Any suggestions for a fix? I was thinking about Root66 and trying again but I'm afraid of messing up my phone.
Are you saying your phone is dropping data completely and it doesn't come back or does a reboot fix it? I would go back to stock and see if the problem goes away. If it goes away the rom doesn't like your phone. If you need help going back to stock there's lots of information available and plenty of people willing to help you.
Ryno77 said:
Are you saying your phone is dropping data completely and it doesn't come back or does a reboot fix it? I would go back to stock and see if the problem goes away. If it goes away the rom doesn't like your phone. If you need help going back to stock there's lots of information available and plenty of people willing to help you.
Click to expand...
Click to collapse
CM10 will never go to 0dmb. Or any 4.1 for that matter. But ANY 4.2 rom will give me 0dbm, especially at my house. Data still goes through but it's to a crawl.
If I go Root66, can I just unlock the bootloader after that and then try again?
Recon0212 said:
CM10 will never go to 0dmb. Or any 4.1 for that matter. But ANY 4.2 rom will give me 0dbm, especially at my house. Data still goes through but it's to a crawl.
If I go Root66, can I just unlock the bootloader after that and then try again?
Click to expand...
Click to collapse
Root66 is stock rooted. Install EZ unlock from rootzwiki version 1.2 and unlock your bootloader. Your basically starting over from the beginning with root. Are you in a 4g fringe area?
Ryno77 said:
Root66 is stock rooted. Install EZ unlock from rootzwiki version 1.2 and unlock your bootloader. Your basically starting over from the beginning with root. Are you in a 4g fringe area?
Click to expand...
Click to collapse
I have 4G in my area. But even Speedtest is a noticeable difference. 4G isn't great in my area, but I still get better signal on 4.1 roms.
Recon0212 said:
I have 4G in my area. But even Speedtest is a noticeable difference. 4G isn't great in my area, but I still get better signal on 4.1 roms.
Click to expand...
Click to collapse
What radio are you on? You can also just flash a different radio.....different roms come with different radios and that might be your problem.
Ryno77 said:
What radio are you on? You can also just flash a different radio.....different roms come with different radios and that might be your problem.
Click to expand...
Click to collapse
I've tried the most recent 3 radios.
EDIT: To add to that, VRLK1, K3, and VRBMA2
AOSP doesn't have the same "strength" that stock touchwiz does...that's just the way it is until the whole ril thing is figured out. If data speeds are more important than the AOSP features to you I would flash back to stock or flash a touchwiz rom. Since you said this happens sometimes on touchwiz you may be better off starting from scratch......using the root66 odin file then unlocking bootloader and going from there. I don't think the problem is you, I think it has to do with AOSP and the area your in. If you decide to go back to stock because data speeds and reliability are important to you I would personally stick with that for a couple of days to see if things are resolved....then you could rule your phone out as the problem.
Ryno77 said:
AOSP doesn't have the same "strength" that stock touchwiz does...that's just the way it is until the whole ril thing is figured out. If data speeds are more important than the AOSP features to you I would flash back to stock or flash a touchwiz rom. Since you said this happens sometimes on touchwiz you may be better off starting from scratch......using the root66 odin file then unlocking bootloader and going from there. I don't think the problem is you, I think it has to do with AOSP and the area your in. If you decide to go back to stock because data speeds and reliability are important to you I would personally stick with that for a couple of days to see if things are resolved....then you could rule your phone out as the problem.
Click to expand...
Click to collapse
So they're just having issues with the RIL in roms?
AOSP roms, yes. Touchwiz roms are stock Touchwiz debloated with added features so things like data speeds should be relatively consistent. Your going to have more issues on AOSP roms on this phone...sucks, but that's the way it is for now.
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.
Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium
TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.