Develop Bugs

4.2 update problems

I recently flashed bigxie's ROM to update my gnex to jelly bean 4.2. Now I have noticed two big issues. For some reason I am unable to receive any file through Bluetooth though I can send without an issue and that my NFC doesn't seem to work. The NFC option itself is grayed out and Bluetooth goes into a cyclic crash as soon as trying to receive a file. Only removing the battery or switching the phone off seems to work.
Please advice as to how to proceed.
Sent from my Galaxy Nexus using xda app-developers app

1. Wrong section.
2. Flash google's stock 4.2.1 images and see if it gets fixed. Flash em via fastboot. Get them here: https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus

yhee nooby
wrong forum
maby use a toolkit to flash

Please read forum rules before posting
Questions go in Q&A
Development is only for developers to make threads with releases
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[solved] 4.2 bluetooth and NFC error
Sorry about the wrong post but just wanted to let everyone know...
Was trying to flash 4.2.1 but wasn't able to do it (a lot of problem with toolkit, phone not being detected or even the zip copy not possible). Saw an update, tried applying and to my shock wasn't able to go beyond the Google logo in the next boot up. So went ahead and re installed the bigxie j04c rom and found that it is functioning perfectly now. Bluetooth ok, NFC ok.
Don't know how, but its all good. Guess Christmas came early :good:
Hope it remains the same.... :fingers-crossed:

Strange flash

Today I attempted to port the chameleon ROM from the international gs2 using this script - http://forum.xda-developers.com/showthread.php?t=1927729
After it successfully ran I decided to flash it(stupid) and it successfully sent through and booted just fine. Everything was working great except for all radios failed to connect and captivate keys were out of position. Here's where it gets strange I rebooted and tried to go to download mode and held the wrong button leading me to recovery. It was running the recovery from the gs2 ROM which was supposed to be replaced by the epic touchs image by the script but I guess wasn't. So I accidentally but successful installed a gs2 custom jellybean kernel which was built from source and all the features worked. Does this mean with a few changes we can run jellybean kernels with just adding a few changes from our source???
Edit: here is the link tot the ROM I flashed - https://docs.google.com/file/d/0B3QharTm24mgQVBJMzVvVlBjWXc/edit
Sent from my Nexus 7 using xda app-developers app

You're gonna end up hard bricking your phone trying to use kernels and recoveries from other devices
I like to break stuff!

-EViL-KoNCEPTz- said:
You're gonna end up hard bricking your phone trying to use kernels and recoveries from other devices
I like to break stuff!
Click to expand...
Click to collapse
This is very true. I bricked my original Epic 4G Touch by doing something similar to this.
WHATEVER YOU DO, DO NOT USE THE RECOVERY FROM THE GS2 VARIANT THAT YOU ARE PORTING FROM TO DO ANY KIND OF WIPING OR FACTORY RESET!
You have been warned.

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] Help a OG

Hey guys,
It's been so long since I've flashed a Rom I don't even know where to start.
I'm on CleanGB MTD 1.1.2 and CWM v5.0.2.7
In general- where should I start to go to an updated Rom like CM9 or something --- (what is the 'go-to' Rom for something that 'just works'? My priorities are stability, battery life, speed, in that order).
Do I have to ODIN to FC09 first? <---- Is that even the latest factory android? I'm not even sure what version I'm on right now but I've been getting a prompt to update OTA for a while now.
Sorry for creating a thread you guys are probably sick of looking at, I just need a general direction to go in.
Thanks

I took everyone's silence as my answer and figured it out on my own lol

Questions go in Q&A
And you waited 2 whole hours? You do realize there are very few Epic users left right?
Thread moved
I am glad you figured it out.
What did you end up flashing?

kennyglass123 said:
Questions go in Q&A
And you waited 2 whole hours? You do realize there are very few Epic users left right?
Thread moved
I am glad you figured it out.
What did you end up flashing?
Click to expand...
Click to collapse
I ended up doing CM9 but saw that there was a CM10 stable and flashed that about an hour later. It's fantastic.
Thanks for moving the thread. I was wondering if you guys could help me find instructions for recalibrating gyroscope. My screen isn't auto-rotating now. (I have auto-rotation turned on).
Any help?
Thanks

1greek4u said:
I ended up doing CM9 but saw that there was a CM10 stable and flashed that about an hour later. It's fantastic.
Thanks for moving the thread. I was wondering if you guys could help me find instructions for recalibrating gyroscope. My screen isn't auto-rotating now. (I have auto-rotation turned on).
Any help?
Thanks
Click to expand...
Click to collapse
That is same as it has ever been. You either need to restore your TW ROM and calibrate it there or find the thread about the kexec boot from sd card, set that up and run the calibration in settings after booting from FC09. IIRC there is like 3 places to turn on auto rotate too.

kennyglass123 said:
That is same as it has ever been. You either need to restore your TW ROM and calibrate it there or find the thread about the kexec boot from sd card, set that up and run the calibration in settings after booting from FC09. IIRC there is like 3 places to turn on auto rotate too.
Click to expand...
Click to collapse
Ok so I fixed that by using SD card bootable stock FC09 and using calibration; I get in my car and Bluetooth doesn't work haha. Apparently it's a problem with CM10 across multiple devices. Real bummed too because CM10 is so perfect otherwise....

1greek4u said:
Ok so I fixed that by using SD card bootable stock FC09 and using calibration; I get in my car and Bluetooth doesn't work haha. Apparently it's a problem with CM10 across multiple devices. Real bummed too because CM10 is so perfect otherwise....
Click to expand...
Click to collapse
Yes, Bluetooth has been an issue for some time. If you want everything to just work the best choice is something based off stock like CleanGB ot The People's ROM. It is very difficult to recreate all the drivers needed to make everything work on these phones on AOSP ROMs. Thus the appreciated tremendous efforts of the CM team.

Random rebooting and crashing issues

Hello I am trying to fix a Canadian Virgin Mobile?bell Mobile Galaxy S3 for a friend.
He had installed CM10.1 on it awhile back and somewhere along the line had an issue and tried to back to stock and lost his IMEI number. He did some work himself and was able to get the IMEI number re-injected. But since then the phone has been very unstable, constant apps and processes crashing, random reboots and the like. Was also experiencing issues with the only connecting to 2G/ Edge Data. I searched around and found the solution to the data connection issue.Had to rebuild the NVdata QCN.
The phone still experiencing issues with rebooting and apps crashing all the time. Does anyone have any ideas? I have downloaded stock firmware from SamMobile and tried doing forced updates from Kies. Have searched and been unable to find anything further to attempt.
Thanks for any help.

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

kennyglass123 said:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Sorry thought I had that night.

So I have an idea why the phone is having issues right now. I decided to try loading CM 10.1.2 on the phone. When I had the stock rom running it was the latest 4.1.2 which should be using the latest and greatest JB bootloader included, yet when I try to install CM I get a bootloader error and have to install a new bootloader to get it to install.
This makes me think that for some reason when I am putting stock on here it is downgrading the bootloader and that could be causing issues? Not sure if that makes sense or is even possible. If anyone has input on this would be greatly appreciated.

trltespr thinks it's trltetmo or i'm stupid.

--- Mods, didn't want to post in Android Development and clutter that section, thought General would be a bit better. My deepest apologies if I'm yet in the wrong section, just move it and tell me. Thank you. ---
Alright guys, tried to do some searching on this topic - no help found. So i'm resorting to what I hate to do, flooding the forums with more topics. Little bit of background to help troubleshoot, I've been rooting and rom-ing for about 4 years now with all Verizon Samsung phones (locked bootloaders and all that fun stuff) but just switched to sprint recently and having a few issues with roms.
On to my issue...
My phone has been experiencing a bunch of lag lately. So bad where the phone locks up for about 5 to 7 seconds about 3-4 times an hour and it is getting annoying as it's locking it at some crucial points. So, I have TWRP on there, rooted on stock 4.4 and tried to flash CM12 nightlies for this phone (the Sprint version). TWRP refused to install it, saying that the phone itself was the trlteTMO version and couldn't flash the trlteSPR roms. I flashed the TMO CM12 nightly and it flashed perfectly fine, but my service didn't work. I believe I got 3G/LTE and calling (unsure, can't confirm.) But no texts went through. But what the great part was, is that it did not stutter and Lollipop was absolutely f-in' gorgeous. So i'm assuming the phone accepted the software, but the radios weren't correct. I loved CM12 so much, but I use XPOSED for a few things. (Basically just Keepchat), So i'm okay with going to CM12 if someone can get my Sprint phone, which i got through Sprint, to work with Sprint roms. I'm at a brick wall.
Mind you that I have access to a windows computer, but it's junk and would rather flash using ODIN PRO on my phone, or just using my recovery. I use a Macbook Pro as my daily, but I can't get heimdall to work as i once did on my S3. I can't even find support or any downloads for it. So, i'm pretty much back to noob status and just need some good guidance. Thank you for reading, and help me flash something new!

Did you use the correct recovery for spr? Is only thing I can think of.... Maybe you flashed the tmo recovery

spleef said:
Did you use the correct recovery for spr? Is only thing I can think of.... Maybe you flashed the tmo recovery
Click to expand...
Click to collapse
Definitely checking that. Sounds like it could be a very good reason for it to reject the tar.

Branski81 said:
Definitely checking that. Sounds like it could be a very good reason for it to reject the tar.
Click to expand...
Click to collapse
Using a .tar file in recovery could be your 1st problem....
Sent from my SM-N910P using Tapatalk

I agree with spleef. There's no other reason I can think of that would cause TWRP recovery to not install a sprint rom and give you that error message. You should really double check the tar files bwhen downloading them and definitely before flashing them with odin. Another thing, you are very brave for knowlingly flashing a T-Mobile rom on your Sprint phone. Seriously, you might want to Odin back to the stock. Sprint NK2 rom .tar and startb over fresh. It would be in your best interest at this point.

BigJPNut said:
Using a .tar file in recovery could be your 1st problem....
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Excuse me, you're right. The recovery file was not tar. You're correct though, that does seem as it would just a littttttle bit of an issue..
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
tx_dbs_tx said:
I agree with spleef. There's no other reason I can think of that would cause TWRP recovery to not install a sprint rom and give you that error message. You should really double check the tar files bwhen downloading them and definitely before flashing them with odin. Another thing, you are very brave for knowlingly flashing a T-Mobile rom on your Sprint phone. Seriously, you might want to Odin back to the stock. Sprint NK2 rom .tar and startb over fresh. It would be in your best interest at this point.
Click to expand...
Click to collapse
I cannot fully confirm that it was the wrong TWRP as the only recoveries I had on my computer and phone storage were sprint versions.
I did however reinstall the sprint recovery again after having to flash back to stock due to a random bootloop issue. So after reflashing 4.4 stock, reinstalling the recovery and restoring to a previous backup, I am now clean flashed on 5.0.2 all cellular features working on CM12 Official.
Mods, if you could please close or delete this thread, that would be appreciated.
Thank you @spleef, I'm sure you were correct anyways.
/end

[email protected]
I feel your pian. Same somewhat similar happend to me on the Snapdragon S5.
I did a factory reset. Hook up to Kies3. Upgraded to NK2. Did a little Coding.Wiated for Lolipop to role out Official. Rooted debloated N knox free. Found in General tips and tricks.
All OS is running Super Fast-