[Q] Lost camera after AOSP flash and even ODIN to stock won't work - Verizon Samsung Galaxy S III

So I finally took the plunge to AOSP since I have my note 2 to run stable. First thing I noticed was that the camera got a "can't connect to the camera" error. Fixed permissions, wiped multiple times, tried a couple different AOSP roms and nothing, so I looked deeper and found some file replacements for the data folders, tried that and still nothing. Wiped again flashed a stock rooted image and still nothing, so last resort was 2 different stock rooted and not-rooted images through ODIN. Successful flashes of both and still no camera.
I am stumped i thought my fail safe ODIN would work but it didn't if anyone has any suggestions I would greatly appreciate it.
p.s. my bootloder is unlocked.

::UPDATE::
Ok so after continuing the troubleshoot finally stumbled upon something. After restoring a stock ODIN of ICS from when i first got the phone I let Verizon run through and do its update and after it finished VOILA my camera's working. I honestly don't know how it happened but nothing else had worked, now i have to go through and unlock root and get a custom ROM again. hopefully this can help someone if this happens to them.

Related

[Q] Can't flash back to stock

I've downloaded the stock image directly from the Motodev site for my MZ604. It successfully flashes boot.img. When I try to flash system.img, it just hangs. I thought maybe I was rushing it before giving up but I left it going for a couple of hours this morning with no luck. I'm happy with cwm and running ics roms but this is puzzling me as to why I can't get back to stock. My stock recovery img got trashed last month so recovering back to stock isn't an option. Any suggestions?
More specifically, I get a successful send of system.img, the hang up happens while writing.
I know this may not help you but have u tried downloading the file another time and compare the md5 between the file.. If they are the same then i have no idea mine was able to write correctly.. If they are different download it a 3rd time and see which one is truly correct.?
Sent from my mind control device
Downloaded from another site and got the same results. I kept rebooting the xoom and repeatedly tried flashing and it finally went through. For some reason, I had to do the same thing for recovery and userdata. It's back to stock and working normally now.
ps now i'm about to root again and flash a nightly lol. I just couldn't understand why it did the same thing last month when i tried to revert to stock and gave up. I was determined to figure it out today.
Awesome to hear! Flash away lol
Sent from my mind control device

Help - constant Samsung Logo on boot

HELP!, I have been very lucky in the past and have had very few issues rooting and applying different themes, kernels etc. but the fact is I have little idea of what I am doing. For some reason I can't explain I tried to load the ninja rom to get FP5, ( and I did not back up before I tried to install it. because I am that stupid). Not sure what happened but I got stuck in a Samsung logo boot loop. I read where someone else had similar issues and got going again by putting Tweaked 2.2 over top after a clearing data etc so I tried that. Now when I boot I get the Samsung logo and it just sits there. I have rebooted several times, battery pulls, mounted everything and I still get the same frozen logo.
I would like any file I can load from CWM or Odin to get me back up. I will go back to stock if need be but I am not sure what I need to get back to stock FP1 to start again from there. or stock FP5 or whatever.
I have cleared data already so whatever gets me working I will try
I found a video with instructions to to EP4 but I thought that might be a little too far back. I know how to use CWM and Odin, I am just not sure what I need to get to stock, or any good working version, starting from my current state.
(Seached for FP1 stock but mostly found discussions of "upcoming" OTA and the EP4 videos.)
Thanks
fsuinnc said:
HELP!, I have been very lucky in the past and have had very few issues rooting and applying different themes, kernels etc. but the fact is I have little idea of what I am doing. For some reason I can't explain I tried to load the ninja rom to get FP5, ( and I did not back up before I tried to install it. because I am that stupid). Not sure what happened but I got stuck in a Samsung logo boot loop. I read where someone else had similar issues and got going again by putting Tweaked 2.2 over top after a clearing data etc so I tried that. Now when I boot I get the Samsung logo and it just sits there. I have rebooted several times, battery pulls, mounted everything and I still get the same frozen logo.
I would like any file I can load from CWM or Odin to get me back up. I will go back to stock if need be but I am not sure what I need to get back to stock FP1 to start again from there. or stock FP5 or whatever.
I have cleared data already so whatever gets me working I will try
I found a video with instructions to to EP4 but I thought that might be a little too far back. I know how to use CWM and Odin, I am just not sure what I need to get to stock, or any good working version, starting from my current state.
(Seached for FP1 stock but mostly found discussions of "upcoming" OTA and the EP4 videos.)
Thanks
Click to expand...
Click to collapse
Take a look this, you have many FP1 stock roms (debloated/deodex/root etc..) http://forum.xda-developers.com/showthread.php?t=1560117
thanks for the links.
now I can't mount the SD card. Maybe that's why it is stuck in the first place. I know I have run into this before but can't recall what I did to get it mounted.

[q] major screw up. Helpppp!!!

So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
Why don't you try to Odin a pre-rooted Verizon stock can be found here http://forum.xda-developers.com/showthread.php?t=1984436 to see if it addressed both our your issues?
I just had some major issues with this as well. There is something wrong with the nightly versions of CM 10.1.
Like you - I flashed CM 10.1 12/18 and found that my data was not working. I then searched this forum and found that other users were having the no data issue as well. I decided that I would do the same and flash back to an earlier CM 10 release from December, but the update did not go as expected. Due to going 10.1 to 10 I had to wipe data/cache/dalvik. At this point I got CM 10 reinstalled, but the phone came up with NO cell coverage. I went to System Settings -> About -> Status and found that the phone was no longer registering my cellular network (Verizon) or phone number. My IMEI data was dead.
Luckily in my case I had already made backups of my IMEI data per this post: http://forum.xda-developers.com/showthread.php?t=1852255
I restored my IMEI and reflashed CM 10 12/16. Everything is now working as expected. Your issue sounds identical to mine - I just spent half the day fighting with the exact same issue. I definitely learned my lesson about staying so current with the NIGHTLY builds for day-to-day non-dev use. I knew it before, it just never bit me like this.
Anyways, I hope this information helps you somewhat. Good luck!
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.

[Q] HELP! Galaxy S3 (i535) Stuck in roaming after root attempt, tried everything...

First, I'd like to say that I have seen other threads on this topic and tried but failed.
I've gone through different roms, stock roms, stock radio, Odin, etc. I attempted to download ADB but it doesn't work on my windows 8 and I've just gone through so many problems that I can't take it anymore. I need help.
I have a Samsung Galaxy S3 i535 on the Verizon network.
It started with me trying to root my phone
I used the Odin method and CM 10.1 with Clockwork mod.
Phone booted up and everything and had Superuser but kept getting errors about process.android failing/closing as well as other processes.
I needed Gapps so I tried to flash the one for CM 10.1 and the installation when I boot it up would always fail due to network error. It showed up every reboot so to get rid of the endless failing I tried to change the rom in recovery.
Changing to Synergy Mod
As I went through the installer for Synergy, everytime it got to the wiping data/cache portion it rebooted the phone and failed to install.
BUT, when I went back to CM 10.1 the Gapps screen had finally vanished.
At this point
I had signal but could not send out texts or calls and I had no data connectivity.
Stock Attempts
Tried multiple attempts on this site as well as others, mostly having to use Odin. As of now, I'm in Android 4.0.4 stock rom and recovery with call/text ability, stuck in roaming (little R/triangle above bars), Google Play not opening, and no ability to update software due to no network connection.
Please, I don't know what else to do. I'm going insane and am losing hope, I need the help of you beautiful people.
I'm in the Air Force and it's hard to spend this much time trying to fix this issue, a lot of things are tied to my phone with it being my only communication. I'm okay with rooting my phone again but I need to get the 4G data working first. Thank you in advance.
I'll try anything, even if I have before, and i'll post the results. Any help is appreciated.
If you're completely stock on 4.0.4 try reprovisioning your phone. Open dialer and type this *2767*3855#
Sent from my SCH-I535 using Tapatalk 4

[Q]WiFi stuck, unable to turn on

So ever since yesterday I've been able to use WiFi. I was chromecasting something and while it was casting my phone went through a reboot, thought nothing of it since its happened lately. Well i think it did it a few times. Well I check my phone after my show is over and my WiFi is off., and I can't turn it on. I rooted my phone last night since it was unlocked already from when I had it rooted before. It's on Android 6.0 right now. I was just wondering if anyone had any ideas of how to fix it. I was getting a logcat error in reference to the wifistatemachine.
Did you try flashing an older stock rom?
I have a phone with the same problem and it believe it is a hardware problem because stock and custom kk, lp, and M ROMs do not solve the problem. After swapping out the motherboard, everything was fine.
I have not yet. I was trying to create a nandroid backup first, but NRT doesn't seem to want to let me do that because i don't have a modified boot image.

Categories

Resources