Develop Bugs

What's wrong with my phone

Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.

are you clearing /cache and dalvik-cache before you reboot to the custom rom?

mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.

hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2

horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?

Try TWRP 2.2.1.1

hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2

horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.

I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium

Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.

The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.

OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.

Jellybean only boot loop

Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?

MARINERMOOSE241 said:
Hi guys I searched the forums but can't seem to figure this one out. I can flash and boot all ICS Roms completely fine. When I try ANY Jellybean ROM AOKP, CM whatever I get stuck on a boot screen loop. I use these steps:
Flash darkside super wipe
Flash ROM
Flash gapps
Flash darkside super wipe cache
Reboot
Now I've tried cwm 5.x.x and 6.x.x and twrp. Any suggestions?
Click to expand...
Click to collapse
Download the file again. Sounds like a bad flash.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.

MARINERMOOSE241 said:
Thanks elesbb but this bootloop happens with ANY JB from I try to.flash on my hercules. So I don't think its bad downloads I wonder if I posted a log at during boot if someone could help.
Click to expand...
Click to collapse
That's why I recommended downloading again. Sometimes packets are lost in cyberspace. I don't see how your device is the only one doing this. Gotta be something on your end. (Not trying to point fingers. Just saying it can be a million and 2 things )
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.

MARINERMOOSE241 said:
Ok, I now downloaded 4 different roms ALL Jellybean and ALL get frozen during the bootscreen and bootloop. ADB just sits at waiting for device when trying to logcat. I've reflashed to stock gingerbread just fine, reflashed to ICS AOKP just fine no loops. But going to JB after just keep causing a bootloop, its driving me crazy.
Click to expand...
Click to collapse
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium

Rememdium said:
What cwm are u using? I couldn't flash any Jb roms with cwm 6
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.

MARINERMOOSE241 said:
Were you getting freeze bootloops?
I have tried cwm 5.x nd 6 which I'm on now. Also twrp gave me the same loop. I've even gone as far.as.formatting sdcard and eemc with no luck.
Click to expand...
Click to collapse
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.

Digital1325 said:
Try switching to TWRP.
Then re-download the JB rom you want to use, put it on the root of your internal SD, make sure the MD5 matches and then try flashing again. I think most of these JB boot problems are coming from CWM recoveries.
Click to expand...
Click to collapse
No they aren't. Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
Teamchopsticks recommends cwm 6.0.1.1 as the optimal recovery to use.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside

Digital1325 said:
Where did you read that? And does 6.0.1.1 still have a broken cache wipe?
Someone had a similar problem in the dev thread and switching recoveries seemed to fix it. So worth trying.
Sent from a BAMF Jedi ROM from the Lightside
Click to expand...
Click to collapse
I read it on their website but i came across it in binarybishops nightly thread. And no the cache wipe is fixed. I use the touch version, tried TWRP and CWM 5 hell i tried them all! They all produced the exact same results for me as far as performance goes. But ive never had any issues with 6.0.1.1 i love it to death

Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.

MARINERMOOSE241 said:
Ok guys this is very puzzling. I have been flashing roms for years and have never had a loop like this.
So I flashed TWRP again verified the md5 has was correct for both AOKP JB nightly and gapps. Flashed following the correct steps posted in the thread by Whitehawkx and I still get a bootloop freeze on the AOKP unicorn. So I tried CM 10 nightly... same freeze/loop. I downloaded AOKP ICS, no loop at all boots fine.
I've tried cwm 5, 6, and twrp all with the exact same results. I have formated SD external and internal EMMC... nothing has worked.... All I want is some Jelly bean goodness.... I flashed AOKP on my nexus 7 just fine. Like I said I am really stumped on this one as to why ICS roms would flash perfectly fine and using the same steps JB roms bootloop.
Click to expand...
Click to collapse
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
It's something wrong with your flash file. Use an actual adapter to transfer the file. And download it again. Then if you still get the loop plug your phone into your computer and boot it up then run adb logcat.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.

MARINERMOOSE241 said:
When you say flash file do you mean the ROM? If so I've tried downloading it on my Mac and transferred it via USB mode still no dice. Also I.tried to.log at during the bootloop but adb never sees the device.
Click to expand...
Click to collapse
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.

elesbb said:
Yes im saying the zip. Something isnt getting placed where it belongs or something is corrupt. And DONT use the USB mode, get an actual Mirco SD to SD adapter and a SD to USB adapter and do it that way.
Click to expand...
Click to collapse
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.

MARINERMOOSE241 said:
I have an adapter so I can try that right now. However, if the md5 hash is correct wouldn't that mean the zip downloaded correctly? And it still doesn't answer why every JB from bootloops while ICS does not.
Click to expand...
Click to collapse
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?

elesbb said:
Yes that is usually the norm. But it is millions and millions and millions of bits of data we are talking about here... all it takes is for one of those bits to either not be there or be in the wrong place to screw it up. And yes that is extremely strange, but seeing as you are the only one experiencing this, i am sure its not the ROMs and its something you are doing or not doing. Im not trying to be rude or imply that you are dumb. its just extremely hard to pin point something weird like this when i dont have the device in my hands. See where im getting here?
Click to expand...
Click to collapse
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.

MARINERMOOSE241 said:
I totally agree I don't believe its the roms themselves as they seem to work for most people. I've just never ran across this before.
Click to expand...
Click to collapse
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
I have on my HD2. But a complete format of the memory card using HP USB disk tools fixed it. Have you tried that yet?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Formated the SD card ... used the external adapter to copy the flash to the SD same bootloop I also copied the file directly to internal storage removed the sd card and flashed same result... looks like no Jelly bean for me... so freaking odd as I can flash ICS any rom all day long just fine.

[Solved] Flashed cyanogenmod, stuck on boot screen

Hey guys, I'm really new to rooting, flashing roms, and Android in general (I've used iOS since 2007 until a month ago... please have mercy on my soul). I have an AT&T GN2 that I would like to remove the bloatware from, hence why I began investigating rooting, but it's snowballed into my desire to try out some of the amazing ROMs that the developers here have produced. Since the Note 2 uses the Exynos 4, I rooted using the ExynosAbuse exploit and downloaded Titanium Backup to freeze the AT&T apps. So far, so good.
However, I am wanting to get into how to flash custom ROMs, like CyanogenMod, so I downloaded the CWM RomManager and flashed the CWM Recovery. I downloaded the CyanogenMod 10.1 release for the i317 model (here: http://forum.xda-developers.com/showthread.php?t=2024495) and the latest gApps package (for 4.2.1), and flashed both from CWM RomManager. When it rebooted, it showed the CyanogenMod boot screen, but it appears to be stuck there. I'm not sure what to do at this point, and am hoping I didn't brick my phone. Is there anything I can do at this point?

Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium

Have you changed kernel???
Sent from my MT11i using xda app-developers app

id10terrordfw said:
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
When I booted into recovery, I got the CWM recovery (which is a good thing, I suppose). I wiped the cache, and then installed the CM 10.1 zip and gApps zip. However, I think I still need to wipe data/factory reset, right?
So, at this point, I've:
1. Rooted the device using Chainfire's ExynosAbuse apk (super easy).
2. Installed RootChecker (success) and TI backup (froze bloatware apps).
3. Downloaded CWM RomManager.
4. Flashed CWM Recovery.
5. Downloaded CM 10.1 port for i317 (the AT&T GN2 model) and the 4.2.1 gApps zips.
6. Chose to install ROM from SD card in RomManager, added both CM 10.1 and gApps, and only selected install (did not wipe cache or user data at this point).
7. Received blue CyanogenMod boot screen... excited... but it remains on the boot screen. Sad face.
8. Removed battery to power the device off, placed battery back in, and then booted into recovery mode (CWM recovery).
9. Installed the CM 10.1 zip and gApps zip from SD, then wiped cache.
10. ???

Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Peleus16 said:
Have you changed kernel???
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
This is a great point, at no point op has mentioned kernel.
Sent from my SAMSUNG-SGH-I317 using xda premium

cdshepherd said:
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...

NowhereOutThere said:
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
Click to expand...
Click to collapse
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.

NowhereOutThere said:
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
Click to expand...
Click to collapse
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?

NowhereOutThere said:
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
Click to expand...
Click to collapse
Plug it into your computer and see if you can mount your internal sd. If you can download a new rom to your computer and transfer it to sd. Did you make a backup before flashing?
Im just running stock rooted for now.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Well, I'm downloading CleanROM right now. I also downloaded another cm 10.1 file just in case, perhaps it's because I downloaded it on the mobile Chrome browser that I'm having problems? I also downloaded a kernel from the thread to help with performance. However, if I can't get these on the phone, it doesn't matter. Since I'm on a Mac, I have to use Android File Transfer, and it isn't registering my phone, unfortunately. I may have to go out and buy a cheap SD card and throw the files on there. It may not hurt to have one around, anyways.

Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
No... I thought that a backup of the original ROM was made when flashing CWM recovery, but I am a noob and that did not happen. Unfortunately, the browser doesn't even work! So I cannot text myself the link for the download. I should be able to flash a zip file from a micro sdhc, right?

Flash the right GAPPS, the crashing keyboard is a symptom of incorrect GAPPS. The December one is for 4.2.1 only, which is what CM10.1 is based on. Make sure you flash the right GAPPS with the right CM version.
Sent from my GT-N7105 using xda premium

The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs

ManelScout4Life said:
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
Click to expand...
Click to collapse
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.

Just grab goo manager from the market and dl the correct gapps to your phone. Either that or use your phones browser. No need for a pc. Boot in recovery, wipe cache and dalvik and flash correct gapps. Should be gtg.
Edit: just saw your browser isn't working. Goo manager's your best bet. Could always try another browser from the market as well. Good luck.

NowhereOutThere said:
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Click to expand...
Click to collapse
While in recovery plug usb into computer (make sure drivers are installed) in recovery menu navigate to mount usb storage. See if that works
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

[Q] Anything other than a TW and my camera just wont work, Help?

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

[Q] Having problems upgrading roms

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