Can anyone advise how one would go about fixing the S3's internal partition tables? I believe I need to flash someone else's table?
Help!
Some context:
I've been having this issue where my S3 runs into a symlink failure/Status 7 error whenever I try to flash a Jelly Bean rom, ie. CM10/PA/Jellybro. This occurred despite me having the latest 5.8.4.7. CWM, wiped and reformatted EVERYTHING, etc. I posted a sample of where the recovery error log shows the flashing processes failing here:
http://forum.xda-developers.com/showpost.php?p=30287780&postcount=302
Lots of XDA member offered advice with no avail. I remember one member mentioned something about partition tables, so I dug a little deeper. I noticed that the error log also contained error messages about missing directories and my sd-ext not mounting, which is strange since I can access my external sdcard under /mnt/extsdcard directory, and the two directory names aren't matching. So I downloaded an partition table app and saw the following:
http://imgur.com/6r4Vo
Basically, it looks like my partition tables are somehow corrupted and my sdcard and external SD is being mounted for use, but somehow...incorrectly. I'm thinking this is the likely culprit.
What was the app you ran to get that? And what rom were you running when you took that screenshot?
You said its happening when you try to flash jellybean. Do you have any problems with cm9, or stock?
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
What was the app you ran to get that? And what rom were you running when you took that screenshot?
You said its happening when you try to flash jellybean. Do you have any problems with cm9, or stock?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I ran this app called partition table.
https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsImNvbS5jbHMucGFydGl0aW9uIl0.
Oy, I missed the reviews where people are saying that this returns bogus info.
Anyways, here's the situation with what I could/could not flash
-Could not flash CM10/ParanoidA/Jellybro/one other ICS rom that I couldn't think of
-COULD flash CM9, as well as restore nandroid backup of older redrum stripped stock (which is what I ran this off of)
-Tried to flash from CWM/TWRP, neither worked
Back to the partition table, even though that app may be malfunctioning, there were still lines in the recovery error log that indicated that the loader was trying to access /sd-ext, when the external SD in my CWM is displayed as /external_sd. Also, it was trying to reference, edit, and delete from non-existent sources, which seems to indicate that these instructions are being misdirected. If this sounds like another error, I'm all ears.
Well, that is an odd problem! If stock based and other roms flash and run normally, I seriously doubt it'll be a partition related problem. While in cwm recovery, in mounts and storage did you check to make sure your sd was mounted? I may be wrong but I seem to remember some had problems with it correctly recognizing the external sd. In twrp there should be an option just above the slider to use either internal or external.
Sounds like its a problem more with your recovery to me. Try downloading goo.im from play store and use that to install the latest twrp recovery.
If that doesn't work the only other thing I can think to try is to apply the FULL latest update from samsung, UVALH I believe. Install using kies and I think it will rewrite the whole system to pure stock. You will have to reroot, but its definately worth trying before messing with the partitions. If you do that, use goo.im to reinstall twrp and give it a go again.
If I think of anything else to try ill let you know but for now that's the best I can think of.
Just to be sure what model phone do you have? T999, T999V, i9300?
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Well, that is an odd problem! If stock based and other roms flash and run normally, I seriously doubt it'll be a partition related problem. While in cwm recovery, in mounts and storage did you check to make sure your sd was mounted? I may be wrong but I seem to remember some had problems with it correctly recognizing the external sd. In twrp there should be an option just above the slider to use either internal or external.
Sounds like its a problem more with your recovery to me. Try downloading goo.im from play store and use that to install the latest twrp recovery.
If that doesn't work the only other thing I can think to try is to apply the FULL latest update from samsung, UVALH I believe. Install using kies and I think it will rewrite the whole system to pure stock. You will have to reroot, but its definately worth trying before messing with the partitions. If you do that, use goo.im to reinstall twrp and give it a go again.
If I think of anything else to try ill let you know but for now that's the best I can think of.
Just to be sure what model phone do you have? T999, T999V, i9300?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm on the T999, T-Mobile.
To your question I've tried TWRP and CWM and neither works. The external SD cards were mounted in recovery during my attempts. I've actually tried using an earlier version of CWM to flash directly from the external SD card, to the exact same results.
I'll try the Samsung update; my hope is that it also provides a partition refresh. It is indeed a unique problem!
Its the best thing I can think of, so hope it fixes everything. If it is a corrupt partition it should rewrite it, so lets hope!
One other thing, what version of twrp were you using? 2.2.1.1 is the latest for our phone. I think there's an older unofficial one out there and even though it would say the sd was mounted, you would have to go into the backup section and look at available space to confirm that. There were also problems with the touch cwm recovery...
I think the way the gs3 handles the sdcard is part of the problem with those though.
Anyway, good luck! Let me know how it goes!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Its the best thing I can think of, so hope it fixes everything. If it is a corrupt partition it should rewrite it, so lets hope!
One other thing, what version of twrp were you using? 2.2.1.1 is the latest for our phone. I think there's an older unofficial one out there and even though it would say the sd was mounted, you would have to go into the backup section and look at available space to confirm that. There were also problems with the touch cwm recovery...
I think the way the gs3 handles the sdcard is part of the problem with those though.
Anyway, good luck! Let me know how it goes!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
TWRP didn't work and neither did flashing the new Samsung update.
I'm absolutely baffled at this point. I can't find what the hell are causing these symlink errors anywhere.
Sorry I don't have any other ideas. Just to be sure though, did you flash the rooted rom, or use kies or odin to install the update directly from samsung?
Actually, one or two more ideas, though I wouldn't expect much at this point.
You could try using odin to reflash the original shipped version....you never know.
Or
Go into the updater-script and wherever it tries to use /sd-ext, change it to /external_sd, or whatever your error log says its looking for.
Definately ask another dev if its worth trying before doing that!
You may want to examine what is happening with any simlinks in there as well. Unfortunately Im probably not the best person to troubleshoot that stuff. But if you want to attach a copy of your logfile ill be glad to take a look.
Sorry I haven't been better help for you.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Sorry I don't have any other ideas. Just to be sure though, did you flash the rooted rom, or use kies or odin to install the update directly from samsung?
Actually, one or two more ideas, though I wouldn't expect much at this point.
You could try using odin to reflash the original shipped version....you never know.
Or
Go into the updater-script and wherever it tries to use /sd-ext, change it to /external_sd, or whatever your error log says its looking for.
Definately ask another dev if its worth trying before doing that!
You may want to examine what is happening with any simlinks in there as well. Unfortunately Im probably not the best person to troubleshoot that stuff. But if you want to attach a copy of your logfile ill be glad to take a look.
Sorry I haven't been better help for you.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
No I'm more than appreciative, believe me.
I've attached some log files from various attempts. There are some common error lines, including various referencing missing directories and such.
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Click to expand...
Click to collapse
Cool, just got home so ill take a look at these in a bit.
In the meantime there's a new rom, Speed Rom which you may want to try. A few min ago I saw the dev had posted that it is in fact based on cm10.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Cool, just got home so ill take a look at these in a bit.
In the meantime there's a new rom, Speed Rom which you may want to try. A few min ago I saw the dev had posted that it is in fact based on cm10.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Hey, I actually fixed it; It turns out I had to reflash a stock insecure kernel, reboot into recovery, AND force a signature check to get it to work. It's strange, because the first flash had some issues and upon trying to reflash it I had to repeat the whole kernel flash process all over again or else it ran into the same symlink error.
I had tried flashing other kernels before but still had errors; it took be sitting down and flashing every kernel for the phone I could find, paired with a ODIN stock flash, to get it to work. I'm still not sure why this phone seems to have this sensitivity about it.
Anyways, thanks for your help; I'm going to post this around in case anyone else has this issue.
Awesome! Great work figuring that out!
(And props for changing the title!)
I'm still a little confused as to why symlinks were failing, but in the end as long as there's a resolution Im thinking it'll be ok!
After getting it to install again have you tried installing anything from recovery? Just curious if its a problem you will have to dance around on future flashes, or if this seems to have solved it altogether.
Either way, excellent job! I love solutions!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Awesome! Great work figuring that out!
(And props for changing the title!)
I'm still a little confused as to why symlinks were failing, but in the end as long as there's a resolution Im thinking it'll be ok!
After getting it to install again have you tried installing anything from recovery? Just curious if its a problem you will have to dance around on future flashes, or if this seems to have solved it altogether.
Either way, excellent job! I love solutions!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I just can't tell. And it's also worth noting that that failure occurred with different kernels.
I'm going to flash more JB roms as they come along but I'll have backups ready this time. Ostensibly, now that I have a base down I should be able to get around similar errors with a little elbow grease, as opposed to days of OCD-driven anguish. But you'll note that I already ran into the error right after successfully flashed it the first time. I still feel like there's some setting or another that needs to be adjusted in the background. But for now, at least I can sleep.
Cheers and thanks for the help and suggestions mate. :good:
Rest well! You deserve it after all that!
And id be keeping multiple nandroid backups laying around!
Anyway, I've only had a chance to glance at those logs you posted. Now that things have calmed down ill look at em more closely in case anything jumps out at me. I think you are probably right that there is still some issue in there somewhere. I don't know about you but I hate that feeling!
But at least that sense of urgency is diminished!
Ill let you know if I find anything a little later.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Rest well! You deserve it after all that!
And id be keeping multiple nandroid backups laying around!
Anyway, I've only had a chance to glance at those logs you posted. Now that things have calmed down ill look at em more closely in case anything jumps out at me. I think you are probably right that there is still some issue in there somewhere. I don't know about you but I hate that feeling!
But at least that sense of urgency is diminished!
Ill let you know if I find anything a little later.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I just tried to flash the latest 8/20 CM10 with all of the aforementioned precautions and it failed a couple of times, even reflashing the 8/18 rom from last night didn't work. It seems like after several tries it just...clicked? And it then did flash.
I wonder if it's a bad sector in my internal memory?
Ugh, I would hope not. How long have you had the phone? If you can it may be worth thinking about trying to exchange for another.
Bad memory can cause all sorts of crazy problems. If it were me I might not want to risk waiting to see how it goes.
Sent from my SGH-T999 using xda app-developers app
I have similar issues. If I flash speed rom or any cm10, I get the error. Also if I flash wicked v2 it won't boot, this is a rom based on stock4.0.4. My question is where did you find the signature verification? I have stock recovery 3e I believe, but don't see that option.
Btw, all other roms flash and run fine, including aokp, wicked v1, xquisite, and everything else.
You'll have to have a custom recovery installed.
Sent from my SGH-T999 using xda app-developers app
feckmu said:
I have similar issues. If I flash speed rom or any cm10, I get the error. Also if I flash wicked v2 it won't boot, this is a rom based on stock4.0.4. My question is where did you find the signature verification? I have stock recovery 3e I believe, but don't see that option.
Btw, all other roms flash and run fine, including aokp, wicked v1, xquisite, and everything else.
Click to expand...
Click to collapse
DocHoliday77 said:
You'll have to have a custom recovery installed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Right, you'll want CWM or (I think) TWRP. CWM definitely has it; you should be able to flash it from rom manager if nothing else.
Meh, looks like I'm right back where i started, symlink failures up the wazoo again.
Need to find way to flash roms in ODIN, if that's even possible.
Related
Is anyone else having an issue backing up via cwm? For some reason, it will go as far as backing up data then give me an error message. Sometimes it will even seem to complete a successful backup but when I try to restore, it says md5 mismatch. Is there a way to fix this or can someone point me in the direction of finding another backup app? Thanks
Sent from a Sammy Galaxy far, far away..
I got the same issue before. Some have recommended not using Tom manager and just doing it through recovery with button combo.
Message relayed from the dark side.
Mine gow trough the whole back up and always at the end says that "it could not back up image for /data" :/
Here ya go..... This will resolve your issue. Good luck!
http://forum.xda-developers.com/showthread.php?t=976453
The steps involve downloading android SDK and possibly upgrading your Java but it is a one time fix issue so it's worth it. Which means you don have to do this everytime u want to do sucessful restore/backup.
anomy13 said:
Here ya go..... This will resolve your issue. Good luck!
http://forum.xda-developers.com/showthread.php?t=976453
The steps involve downloading android SDK and possibly upgrading your Java but it is a one time fix issue so it's worth it. Which means you don have to do this everytime u want to do sucessful restore/backup.
Click to expand...
Click to collapse
Thanks for the help but it didn't work. Now it went through the process of the backup and during the restore, it failed at trying to restore system. Not sure what the problem could be. Is there an alternate backup solution?
Sent from a Sammy Galaxy far, far away..
kkholidaze said:
Thanks for the help but it didn't work. Now it went through the process of the backup and during the restore, it failed at trying to restore system. Not sure what the problem could be. Is there an alternate backup solution?
Sent from a Sammy Galaxy far, far away..
Click to expand...
Click to collapse
Did u actually try it or ud rather find a different solution? Cuz i had the exaxt same problem and this resolved my issue once and for all.
Sent from my SGH-T989D using XDA App
kkholidaze said:
Is anyone else having an issue backing up via cwm? For some reason, it will go as far as backing up data then give me an error message. Sometimes it will even seem to complete a successful backup but when I try to restore, it says md5 mismatch. Is there a way to fix this or can someone point me in the direction of finding another backup app? Thanks
Sent from a Sammy Galaxy far, far away..
Click to expand...
Click to collapse
Are you using rom manager? I've never encountered an issue with cwm backups made via recovery mode.
Sent from my Hercules using XDA App
It was happening to me regardless. Rom manager backup doesn't take you to backup anymore. It just takes you straight to recovery. Must be a bug in the new version. Three button combo also results in similar md5 mismatches. What I did was backup my SD card and reformatting it. Also I erased anything in my internal having to do with rom manager and also did a fresh install of my rom. I just tried three button combo and it backedup and restored properly. I can't pinpoint which of what I did helped but something must have been messed up
jordanishere said:
Are you using rom manager? I've never encountered an issue with cwm backups made via recovery mode.
Sent from my Hercules using XDA App
Click to expand...
Click to collapse
Message relayed from the dark side.
I know this is super basic, but have you pulled out your sd card and done a dual check with your computer? Also, ensure you have at least a gigabyte of free space on it.
My CWM backups were failing due to these two reasons.
Hope this helps!
~~ Douglas
Sent from my SGH-T989D using xda premium
chib1panda said:
It was happening to me regardless. Rom manager backup doesn't take you to backup anymore. It just takes you straight to recovery. Must be a bug in the new version. Three button combo also results in similar md5 mismatches. What I did was backup my SD card and reformatting it. Also I erased anything in my internal having to do with rom manager and also did a fresh install of my rom. I just tried three button combo and it backedup and restored properly. I can't pinpoint which of what I did helped but something must have been messed up
Message relayed from the dark side.
Click to expand...
Click to collapse
This is the one. Think it's a issue with ROM manager in general. Deleted the cwm folder, wiped cache/dalvik, backup worked! Somethings up with RM
Sent from a Sammy Galaxy far, far away..
Tried your suggestiongs but at the end still says
"Error while making a backup image of /data!"
linye said:
Tried your suggestiongs but at the end still says
"Error while making a backup image of /data!"
Click to expand...
Click to collapse
Never mind. Tried a second time but as like you, got a error when it got to backing up data. Anyone know what could be causing this?
You guys ahould email koush- the developer of the app. Or follow the link posted in the first few pages as an alternative fix.
Message relayed from the dark side.
Newest update fixed this problem... Works great now
Sent from my SGH-T989 using xda premium
rpolito73 said:
Newest update fixed this problem... Works great now
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ok, I updated the recovery to touch (paid for it instead of fastboot to support by the way) and it was still giving me errors. After some testing, I found out what my issue is. If I try to backup to my external SD, I get the errors. If I just backup to my internal SD, backup goes fine. Did the tests a few times to test theory. I have a 32g Kingston card. Not sure why that would be an issue.
Sent from a Sammy Galaxy far, far away..
The fact that you have a 32 gb kingston card doesnt mean anything. Try it with a different card.
and what kind of errors are you getting when you try to backup with external?
anomy13 said:
The fact that you have a 32 gb kingston card doesnt mean anything. Try it with a different card.
and what kind of errors are you getting when you try to backup with external?
Click to expand...
Click to collapse
Various errors at different times. Sometimes at data, sometimes at md5, sometimes at Android secure
Sent from a Sammy Galaxy far, far away..
kkholidaze said:
Various errors at different times. Sometimes at data, sometimes at md5, sometimes at Android secure
Sent from a Sammy Galaxy far, far away..
Click to expand...
Click to collapse
Do get this as well? Error while making a backup image of /data?
Also, I wanted to ask you, did you really try my suggestion earlier? I understand that solution is a bit of work to do but if you'd like I can help you step by step.
anomy13 said:
Do get this as well? Error while making a backup image of /data?
Also, I wanted to ask you, did you really try my suggestion earlier? I understand that solution is a bit of work to do but if you'd like I can help you step by step.
Click to expand...
Click to collapse
I tried it but I think I did it wrong. I downloaded the necessary files, I think (NotePad ++ etc.) But if you could walk me through it, is appreciate it
Sent from a Sammy Galaxy far, far away..
DouglasK said:
I know this is super basic, but have you pulled out your sd card and done a dual check with your computer? Also, ensure you have at least a gigabyte of free space on it.
My CWM backups were failing due to these two reasons.
Hope this helps!
~~ Douglas
Sent from my SGH-T989D using xda premium
Click to expand...
Click to collapse
This was my issue, not enough space. cleared it and it got fixed.
I'm more familiar with my nexus, but my friend has the epic 4g touch for sprint and he needs my assistance in getting CM9 on this. He has a rom on it now, but it sucks and giving him issues. I don't think he has clockwork on it, just an ODIN mode and I'm not too familiar with that.
Can someone lend some insight and help for me to help him do his phone. I need to get CM9 on this guy. Is there a clockwork I can flash? Can you flash at all, or have to use ODIN? I'm not familiar with using ODIN at all. Does it work the same way with putting zips on the sdcard and flashing? Can I even get clockwork, and then flash cm9?
Thank you!
Ok so I found out, he already has agat_recovery trec v0.2.1 on it.....which I guess is clockwork but for this phone. So that's cool. I want to nandroid, but its saying it cannot mount the backup path. I think because we took out his microsd card. Is there anyway we can make it so it mounts to internal rom instead?
chugger93 said:
Ok so I found out, he already has agat_recovery trec v0.2.1 on it.....which I guess is clockwork but for this phone. So that's cool. I want to nandroid, but its saying it cannot mount the backup path. I think because we took out his microsd card. Is there anyway we can make it so it mounts to internal rom instead?
Click to expand...
Click to collapse
Choose the 'switch to internal storage" option.
I got it, thank you! So just throw on cm9 alpha 6 zip, flash, and call it a day right?
Ok so the nandroid backup failed. Error: while making a backup image of /data!
which ok, whatever..if I can't backup my image that's fine. Maybe its cuz I only have my 1.6G free on my internal storage
Only time I've seen that is a space issue. Id say that you're correct.
Sent from my SPH-D710 using Tapatalk 2
Making a backup of his ROM, but I dont think wiping/data impacts that. Any good kernels to run alongside cm9, or is the majority of you using stock?
I dont run cm builds. Only thing I can suggest is to read the thread.
Sent from my SPH-D710 using Tapatalk 2
Do I have to flash gapps with cm9? if so, where are they?
chugger93 said:
Making a backup of his ROM, but I dont think wiping/data impacts that. Any good kernels to run alongside cm9, or is the majority of you using stock?
Click to expand...
Click to collapse
According to this, the E4GT isn't supported by Cyanogen:
http://wiki.cyanogenmod.com/wiki/Samsung
I myself run (and prefer) the stock rooted rom with cwm. That may change one day, but I find that I can customize my setup and software to my satisfaction. In fact, I tried the OTA FF18 (rooted) and didn't like it, especially the fact that Google seems to be more invasive (i.e., auto signing into all google sites with no apparent recourse). I also had wifi LOS on 2 separate E4GTs that required me to turn wifi off and back on every few mins.
I odined back to GB, installed a hack to get rid of the OTA update nag and haven't looked back. I guess I'll wait for the next rollout.
Well, it clearly works at least tho...
http://e4gtcm.blogspot.com/p/cm9-install-guide.html
chugger93 said:
Ok so the nandroid backup failed. Error: while making a backup image of /data!
which ok, whatever..if I can't backup my image that's fine. Maybe its cuz I only have my 1.6G free on my internal storage
Click to expand...
Click to collapse
I wouldn't flash anything until I had a known good nandroid. In fact, that's the first issue you should address, even if it means making room on the card or getting an external SD card to write it to.
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
chugger93 said:
Well, it clearly works at least tho...
http://e4gtcm.blogspot.com/p/cm9-install-guide.html
Click to expand...
Click to collapse
I stand corrected.
http://forum.xda-developers.com/showthread.php?p=28507701
Cm9 is well on its way to official support and has been a great ROM for some time now
Sent from my SPH-D710 using Tapatalk 2
Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?
Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.
The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.
mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)
mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.
mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA
Was it already rooted?
Sent from my SGH-T999 using xda premium
mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium
Any time I try to flash a rom or anything I keep getting this message: E:/error opening '/data/lost+found'
I've tried flashing different roms but it hasn't helped.
I'm having this weird problem where when I flash a new rom about 20 random apps are transferred over to the new rom. (like random games and apps)
Also every time I uninstall any app I get "cannot read data/xposed/modules.whitelist"
The app still uninstalls but this just concerns me.
Could anyone help me out? I just want to do a fresh install of liquid smooth.
Rayz321 said:
Any time I try to flash a rom or anything I keep getting this message: E:/error opening '/data/lost+found'
I've tried flashing different roms but it hasn't helped.
I'm having this weird problem where when I flash a new rom about 20 random apps are transferred over to the new rom. (like random games and apps)
Also every time I uninstall any app I get "cannot read data/xposed/modules.whitelist"
The app still uninstalls but this just concerns me.
Could anyone help me out? I just want to do a fresh install of liquid smooth.
Click to expand...
Click to collapse
I found this in the Nexus 4 forum-http://forum.xda-developers.com/showthread.php?t=2147501. Sounds like the same issue.
joeyhdownsouth said:
I found this in the Nexus 4 forum-http://forum.xda-developers.com/showthread.php?t=2147501. Sounds like the same issue.
Click to expand...
Click to collapse
When I searched around with this issue I did find that and tried to follow those steps but even after trying it a few times I'm still having the same problem.
Rayz321 said:
When I searched around with this issue I did find that and tried to follow those steps but even after trying it a few times I'm still having the same problem.
Click to expand...
Click to collapse
Are you wiping data?
joeyhdownsouth said:
Are you wiping data?
Click to expand...
Click to collapse
Yes and I'm on Team Win 2.5
Does anyone think they can help me out?
Rayz321 said:
Does anyone think they can help me out?
Click to expand...
Click to collapse
Wipe everything, data, system, cache and dalvik
Then try reflashing your rom
Ok have you installed any app to sd type of application? It sounds like your internal storage is being read as external and visa versa.
Also i know there's lots of support for twrp but I swear by cwm when it comes to the GS3. I use twrp on my Nexus and that's fine but on the S3 cwm has always worked better in my opinion.
What roms are you trying to flash? They are sprint s3 roms right from this section?
Sent from the future via Xparent Green Tapatalk 2
CNexus said:
Wipe everything, data, system, cache and dalvik
Then try reflashing your rom
Click to expand...
Click to collapse
I've done that. That's what the one post suggested.
I just don't understand why I'm still getting apps showing up when I install new roms.
What about wiping storage? I know you don't want to lose anything but it sounds like something in your storage causing this.
Rayz321 said:
I've done that. That's what the one post suggested.
I just don't understand why I'm still getting apps showing up when I install new roms.
Click to expand...
Click to collapse
Please see my post right above this one I quoted here. Let us know a few of those things and maybe we can get you going in the right direction.
Sent from the future via Xparent Green Tapatalk 2
edfunkycold said:
Ok have you installed any app to sd type of application? It sounds like your internal storage is being read as external and visa versa.
Also i know there's lots of support for twrp but I swear by cwm when it comes to the GS3. I use twrp on my Nexus and that's fine but on the S3 cwm has always worked better in my opinion.
What roms are you trying to flash? They are sprint s3 roms right from this section?
Sent from the future via Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I haven't installed any app to sd type applications.
I do think part of the internal is being used as external but I thought that's just how it was.
I only have roms, nandroids, and titanium backups on my sd card.
I installed twrp because when I first started it seemed like that was what most people were recommending but it doesn't matter to me. I might switch.
Also I've been switching between cleanbean and liquid smooth, both from this section.
The main thing that bugs me is when uninstalling apps says "cannot read data/xposed/modules.whitelist"
The app still uninstalls but it just doesn't seem good.
Rayz321 said:
I haven't installed any app to sd type applications.
I do think part of the internal is being used as external but I thought that's just how it was.
I only have roms, nandroids, and titanium backups on my sd card.
I installed twrp because when I first started it seemed like that was what most people were recommending but it doesn't matter to me. I might switch.
Also I've been switching between cleanbean and liquid smooth, both from this section.
The main thing that bugs me is when uninstalling apps says "cannot read data/xposed/modules.whitelist"
The app still uninstalls but it just doesn't seem good.
Click to expand...
Click to collapse
A couple weeks ago, I was switching from a AOSP ROM to a TW ROM and I got the same error. Thinking it was TWRP, I hooked my phone up to my computer and flashed CWM. I then tried to flash the ROM in CWM and it was a no go. I still got the same error. I just decided to transfer all my data from my internal sd to my computer. I used Odin to flash the stock tar file. After that, I used QBKing77's method to root from recovery. Then I flashed my ROM and I got 0 errors. So all I had to do was start fresh haha. It took a bit of time because I was taking many precautions (as should you) Good luck!
Sent from my SPH-L710 using xda app-developers app
Yes just as posted above, but before going the route of Odin back to stock. Copy all your files (important) from internal and external to your computer. Then boot into recovery no need to change now and reformat your internal and external storage, wipe cache and dalvik and fix permissions and reboot. Then download a fresh zip of a rom to flash and test it. If it all works then go through your files and move back what you need. I'm pretty sure you have a bunch of O folders in your internal.
Sent from the future via Xparent Green Tapatalk 2
I'm running LiquidSmooth ROM and even with a complete wipe and re-install of the ROM my phone will randomly lock up. Can't replicate it on demand and it could take a few days before it does it. Sometimes it happens a couple times a day, and sometimes it'll go a week without locking up. It always when the screen is off so I can't wake the phone up and have to pull the battery to get it back in a working state. Any ideas on what it could be? I'm open to any suggestions and will provide any info needed.
Open terminal emulator (get from store if you haven't already) and type this:
Getprop ro.bootloader
Tell us what it says.
It could be an app you are using causing issues.
Do you restore anything from backups? Titanium, nandroid or otherwise?
Sent from my SGH-T999 using xda premium
Is this the first custom ROM you've flashed? How about the first 4.2 ROM? Did the others run fine?
DocHoliday77 said:
Open terminal emulator (get from store if you haven't already) and type this:
Getprop ro.bootloader
Tell us what it says.
It could be an app you are using causing issues.
Do you restore anything from backups? Titanium, nandroid or otherwise?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
T999UVDLJC - I restored some apps via titanium backup like google music and some other various apps, but I didn't restore the data with it; just the app. I thought it was due to using autostarts and maybe had an app/service stopped and was causing the issue, but after the wipe and reinstall of the ROM, I didn't re-install autostarts and it still happened.
zeekx4 said:
Is this the first custom ROM you've flashed? How about the first 4.2 ROM? Did the others run fine?
Click to expand...
Click to collapse
I don't recall if it happened on the stock ROM as I didn't have it long enough for it to lock up. Actually, I take that back. It did lock up with the stock ROM, but was rooted. I've flash ROMs on previous phones I've owned, but this is the first custom ROM on this phone specifically. The stock ROM was 4.1 so yeah, this is the first 4.2.x ROM.
Sounds like you're restoring an incompatible app, or you didn't wipe data prior to changing roms.
Try flashing, but do not restore the apps. Reinstall them clean via the play store.
We're you restoring them as system apps, or user apps?
Sent from my SGH-T999 using xda premium
Sorry for the long delay. I tried another ROM, pac man, and it locked up within 2 hours of using it and no apps installed yet (except for google apps). I was watching logcat today and I see a ton of messages saying "unknown permissions". I tried the fix permissions option from CWM, but I'm still seeing those messages in logcat. I'm going to leave my phone hooked up to my PC and logcat running hoping maybe I can catch the issue via logcat when it happens. If need be, I can save logcat to a file for review.
DocHoliday77 said:
Sounds like you're restoring an incompatible app, or you didn't wipe data prior to changing roms.
Try flashing, but do not restore the apps. Reinstall them clean via the play store.
We're you restoring them as system apps, or user apps?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If you're still having problems with it, and especially if it happens on different roms, you should Odin flash the latest stock firmware (root66 ok), and wipe everything. Run clean and stock for a while. If it continues after this it's probably a hardware issue.
Sent from my SCH-I535 using Tapatalk 4
It only happens when the phone is idle/sleeping (screen off, not being used). While actually using it, it never locks up. Do you happen to have a link to the stock rom/firmware handy? If not, I can search for it. Could I have rooted the phone incorrectly? Could it be an issue with the partitions? Any ideas on how to track down the hardware problem?
Also, I see what seems to be a lot of errors in logcat, but I don't know if these are legit or not.
DocHoliday77 said:
If you're still having problems with it, and especially if it happens on different roms, you should Odin flash the latest stock firmware (root66 ok), and wipe everything. Run clean and stock for a while. If it continues after this it's probably a hardware issue.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
bloodfilledwater said:
It only happens when the phone is idle/sleeping (screen off, not being used). While actually using it, it never locks up. Do you happen to have a link to the stock rom/firmware handy? If not, I can search for it. Could I have rooted the phone incorrectly? Could it be an issue with the partitions? Any ideas on how to track down the hardware problem?
Also, I see what seems to be a lot of errors in logcat, but I don't know if these are legit or not.
Click to expand...
Click to collapse
I honestly don't know a lot about non-touchwiz roms, but from all the bugs people mention it wouldn't surprise me at all to see a lot of errors in your logical.
You can find my firmware thread linked in my Sig, and stickied in development. It's probably not anything specific you did. It's hard to say for sure. If it's only happening while asleep, it may be the kernel. But still, I think flashing stock to test is the best option. If it stops happening you will know for sure it's not the hardware. Before trying to track it down, first determine if it's even likely.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I honestly don't know a lot about non-touchwiz roms, but from all the bugs people mention it wouldn't surprise me at all to see a lot of errors in your logical.
You can find my firmware thread linked in my Sig, and stickied in development. It's probably not anything specific you did. It's hard to say for sure. If it's only happening while asleep, it may be the kernel. But still, I think flashing stock to test is the best option. If it stops happening you will know for sure it's not the hardware. Before trying to track it down, first determine if it's even likely.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
So, I downloaded the stock 4.3 OTA ROM and flashed it. All problems are solved. No issues, but now I'd like to try to re-root the phone and try again, but from what I've read you can't downgrade from 4.3.