Develop Bugs

No GPS... HELP

Okay, well I'm a flashaholic and my gps worked for awhile until 3 ROMs ago. Now I'm trying to flash BlackJelly but no dice on the GPS
The icon doesnt even pop up when its enabled
I have a Rogers I747M model.
Things I've tried:
in CWM factory reset, wipe dalvik cache, wipe cache.
factory reset in black jelly
restore stock with ODIN
in CWM again, do the exact same as above^^
factory reset in stock rom
pull hair out of head.
HELP!

First, search is your friend, use him wisely
Second, see if this helps
http://forum.xda-developers.com/showthread.php?t=1923067

I had the same problem, no gps signal, gps never locked!! I had to send it to samsung because it was a hardware issue and not a software issue. They did replace a part and since I got it back no problem.

mrhaley30705 said:
First, search is your friend, use him wisely
Second, see if this helps
http://forum.xda-developers.com/showthread.php?t=1923067
Click to expand...
Click to collapse
1. I've spent the last 3 days search reading and testing. Not new to XDA lol
2. Read every page, nutting works.
any other suggestions?
rick2906 said:
I had the same problem, no gps signal, gps never locked!! I had to send it to samsung because it was a hardware issue and not a software issue. They did replace a part and since I got it back no problem.
Click to expand...
Click to collapse
I can't send it to sammy care I rooted it. I heard they'll know.

egyptshun said:
1. I've spent the last 3 days search reading and testing. Not new to XDA lol
2. Read every page, nutting works.
any other suggestions? .
Click to expand...
Click to collapse
If you have old nandroid backups, keep restoring different ones till the GPS works again. Then try to upgrade your ROM again. If you don't have backups then you have to restore back to stock with ODIN and upgrade from there.
It is unknown why this "feature" is triggered at this time just speculation. I've been calling the the "AT&T GPS Death" issue

Check your flash counter, reset to zero with Triangle away if need be, flash stock lg1, let the phone auto update to lh9, call att (or visit your local store), get warranty replacement

mrhaley30705 said:
Check your flash counter, reset to zero with Triangle away if need be, flash stock lg1, let the phone auto update to lh9, call att (or visit your local store), get warranty replacement
Click to expand...
Click to collapse
If you flash a lot of ROM's the odds are it's going to eventually happen to you again. I would personally save the warranty replacement for something else. If you keep going back for replacements they are eventually going to deny you...IMO.

vw671 said:
If you flash a lot of ROM's the odds are it's going to eventually happen to you again. I would personally save the warranty replacement for something else. If you keep going back for replacements they are eventually going to deny you...IMO.
Click to expand...
Click to collapse
so, what would you do if it were your phone?

I'm having this issue too. Not so much as a single satellite showing up in GPS Test, much less a lock.
It's always something...

mrhaley30705 said:
so, what would you do if it were your phone?
Click to expand...
Click to collapse
I did have the issue:
http://forum.xda-developers.com/showthread.php?p=33584759#post33584759
If your going to play with your phone...you got to fix it when it breaks...

This code HARD factory reset my phone and it brought back up the pgs flashing icon. But no lock. Code: *2767*3855#
It's progress but I still can't get it to lock on. Plus I have no backups that work. somehow all corrupted and not working.
I dont want to send it in because it's been rooted.

factory reset in settings. Phone gps locks to a different province. damnnnnnn it

Try "GPS Status" maybe? I'm just guessing at this point

mrhaley30705 said:
Try "GPS Status" maybe? I'm just guessing at this point
Click to expand...
Click to collapse
Well it shows im in a different province aswell. I've never been this stumped before. I usually have a lead to go on but GPS is just so complex.
I am where the star is.

Did you try to clear your AGPS data and reload it?

I finally got it working again.
Flashed the stock firmware tar through Odin, let it boot up and fill in your info as normal. Once you're booted to the homescreen, do a factory reset from settings, not recovery. Once I rebooted and signed back in, GPS was working correctly again. Just locked on to 18 sats after not being able to even see one for the last couple days.

Did that wipe your internal sd?

mrhaley30705 said:
Did that wipe your internal sd?
Click to expand...
Click to collapse
Actually, I had wiped my internal storage earlier in the day, so I can't really say.

mrhaley30705 said:
Did that wipe your internal sd?
Click to expand...
Click to collapse
It shouldn't. even doing the HARD factory reset (which I found out only works on ICS based sammy roms) doesnt touch your ubs storage (16 n 32gb internal)

Got a fix. http://forum.xda-developers.com/showthread.php?p=34200632#post34200632

New update messed up my tablet

So I was rooted, received and installed the latest update (I knew this was a mistake) and now the tablet is frozen. When I unlock the start screen, the Nexus cross comes up and then it goes back to the lock screen. I hooked it up to the Nexus Toolkit and when I try and reroot the tablet, it says that it cannot find ADB.
Any help would be appreciated.
Thanks, Dennis

I don't think re-rooting the tablet will fix it.
Do you have stock Android recovery installed?

RMarkwald said:
I don't think re-rooting the tablet will fix it.
Do you have stock Android recovery installed?
Click to expand...
Click to collapse
yes

You may be able to boot into stock Android recovery, and select "wipe factory data" or "factory data reset" to fix it. That's going to wipe your apps/data too, just an FYI.

fyrmd said:
yes
Click to expand...
Click to collapse
I am by no means an expert, but I would think you could get the original image for your tablet by looking here. If you have the Windows drivers properly installed on your computer (also available at that link), then you should be able to use ODIN to restore your tablet to stock. After that, reapply any updates if you find any, and then re-root your device.
This has worked for me (more often than I would care to mention) on literally every other Android device, so I can't see why it would not work here.
Good luck...

I was afraid you were going to say that. It looks like that did the trick, thanks.

[Q] phone in constant rebooting.

I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.

ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.

cheasfridge said:
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
Click to expand...
Click to collapse
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try

ghettovirtuoso said:
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
Click to expand...
Click to collapse
I finally was able to fix it after flashing twrp and then doing a wipe from there. then updated superSU and everything seems fine now. sorry about the different accounts. I need to delete that other one.
Sent from my HTC One_M8 using Tapatalk

ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005

RockStar2005 said:
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
Click to expand...
Click to collapse
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.

ghettovirtuoso said:
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
Click to expand...
Click to collapse
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.

chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
I was having the same problems. I'm getting my replacement phone today. My current one is only working (for now) b/c I did a restore, but not far back enough for it to be working 100% right. I'm working with someone who might have a plan, so we'll see. He said he did everything, including root and S-OFF, and got Harman/Kardon sound too (on his non-Sprint phone). I'll post again here when I get more info. First gotta get my replacement phone. lol I had H/K but I think rooting it after the OTA messed it up, but we'll see. H/K did improve the sound, so I really want it back.
RockStar2005

chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.

ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.

ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
chattguy said:
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005

[Q][HELP] N7 Hard Bricked, Multiple Fixes Not Working

Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam

droidian1441 said:
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
Click to expand...
Click to collapse
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.

graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
On this tablet I tend to prefer stock roms however I'm not against custom roms. I will give your suggestion a try. Thanks a lot.
Sent from my VS985 4G using Tapatalk

graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
Okay. I flashed TWRP recovery however my touchscreen is not working. So I am now back in the corner.
Do you happen to have any other suggestions?
EDIT: Now the screen is working.

It worked! Thanks a lot. I appreciate it.
Sent from my VS985 4G using Tapatalk

bricked?

is my phone bricked it only boots into fastboot and if I go on recovery or start the phone just shows a black screen this is after a twrp restore

You are clearly not bricked if you get to Fastboot. You can try writing the boot.img to both slots, and if that doesn't recover you install the factory image using flash-all (get rid of the -w in the batch file to retain your data). Read up a bit before posting. There are a lot of guides and good info here.

sliding_billy said:
You are clearly not bricked if you get to Fastboot. You can try writing the boot.img to both slots, and if that doesn't recover you install the factory image using flash-all (get rid of the -w in the batch file to retain your data). Read up a bit before posting. There are a lot of guides and good info here.
Click to expand...
Click to collapse
i took it to a shop they said they flashed it but it was doing the same thing

atari260 said:
i took it to a shop they said they flashed it but it was doing the same thing
Click to expand...
Click to collapse
What did you restore in twrp?

jd1639 said:
What did you restore in twrp?
Click to expand...
Click to collapse
i think it was system can't remember i did a backup then restore

jd1639 said:
What did you restore in twrp?
Click to expand...
Click to collapse
all i know is it said restored failed then started doing this

atari260 said:
all i know is it said restored failed then started doing this
Click to expand...
Click to collapse
Ok, I assume you made a backup of boot, system, and data in twrp and then restored that? You backed up system and not system image? Have you flashed a factory image before using fastboot commands or have you been using a tool kit of some sort to do your flashing? I'm trying to gauge your proficiency and how your PC is set up to determine the next steps.

jd1639 said:
Ok, I assume you made a backup of boot, system, and data in twrp and then restored that? You backed up system and not system image? Have you flashed a factory image before using fastboot commands or have you been using a tool kit of some sort to do your flashing? I'm trying to gauge your proficiency and how your PC is set up to determine the next steps.
Click to expand...
Click to collapse
I have never flashed a factory img before took me while to grasp how to root not a software person what i got told by a friend who's tried fixing it for me is that he has flashed the stock rom on to it and it is still doing the same thing

atari260 said:
I have never flashed a factory img before took me while to grasp how to root not a software person what i got told by a friend who's tried fixing it for me is that he has flashed the stock rom on to it and it is still doing the same thing
Click to expand...
Click to collapse
When you tried to restore in twrp, was it a backup you made on your device or was it backup from some other device? Is your friend pretty proficient at flashing google devices? It may be that there's nothing you can do at this point. To walk you through flashing a factory image is going to be a time consuming process.

jd1639 said:
When you tried to restore in twrp, was it a backup you made on your device or was it backup from some other device? Is your friend pretty proficient at flashing google devices? It may be that there's nothing you can do at this point. To walk you through flashing a factory image is going to be a time consuming process.
Click to expand...
Click to collapse
backup I made on the device and you got any idea what has actually happened?
and he owns a repair shop so presume he does

jd1639 said:
When you tried to restore in twrp, was it a backup you made on your device or was it backup from some other device? Is your friend pretty proficient at flashing google devices? It may be that there's nothing you can do at this point. To walk you through flashing a factory image is going to be a time consuming process.
Click to expand...
Click to collapse
sad times ah i broke the lcd 2 weeks after i got it the phones been in a repair shop longer then I have had it

atari260 said:
backup I made on the device and you got any idea what has actually happened?
and he owns a repair shop so presume he does
Click to expand...
Click to collapse
I don't have an idea of what happened. Google devices are pretty hard to brick. And if they turn on and boot to anything they technically aren't bricked. But with that said, these dual slot devices are a bit finicky. It could be just a coincidence that something failed while you where restoring.

jd1639 said:
I don't have an idea of what happened. Google devices are pretty hard to brick. And if they turn on and boot to anything they technically aren't bricked. But with that said, these dual slot devices are a bit finicky. It could be just a coincidence that something failed while you where restoring.
Click to expand...
Click to collapse
a dumb question would a rma work if I relocked the bootloader?

atari260 said:
backup I made on the device and you got any idea what has actually happened?
and he owns a repair shop so presume he does
Click to expand...
Click to collapse
It is not a certainty that he does. He could have sideloaded the OTA or even used the wrong factory image. Here is the guide for the 3XL. #4 has the information on a factory image.
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195

atari260 said:
a dumb question would a rma work if I relocked the bootloader?
Click to expand...
Click to collapse
Your biggest problem with a RMA is that you had the screen replaced. Something could have been damaged when doing that. Whether the bootloader is locked or not usually isn't an issue with Google. But it's worth a try. If you don't ask you definitely won't get a RMA. But I don't condone you fib on anything they ask you.
If it were my device I'd flash the factory image. Then change the active slot and flash it again. Then if that didn't work I'd flash each partition separately to both slots. That's a real pita as there's 20 to 30 different partitions, maybe more I haven't looked for awhile. That probably wouldn't do me any good but it might tell what partition is failing, not that I could do anything about it if one did.

I would probably even take it a step farther and fastboot erase the system on both partitions, the data, and the vendor on both. Then install the factory image.

If u can get to fastboot you are far from bricked

jd1639 said:
I don't have an idea of what happened. Google devices are pretty hard to brick. And if they turn on and boot to anything they technically aren't bricked. But with that said, these dual slot devices are a bit finicky. It could be just a coincidence that something failed while you where restoring.
Click to expand...
Click to collapse
well i got told by the shop/dads friend who owns it that I've apparently messed around with the system files and that it's ****ed tbh i think he is bs but idk as i did a system twrp backup and restore which the restore then failed

atari260 said:
well i got told by the shop/dads friend who owns it that I've apparently messed around with the system files and that it's ****ed tbh i think he is bs but idk as i did a system twrp backup and restore which the restore then failed
Click to expand...
Click to collapse
None of the suggestions here have involved using TWRP. The days of just restoring a TWRP backup on your phone do not apply for this device. Even the most skilled have issues with TWRP and the Pixel series. I have been on it since the OG Pixel and Pixel XL, and to be honest I haven't bothered restoring a TWRP backup. I can reinstall the factory image (with or without a wipe) and be back to normal sooner and with less headaches.

I ran into a similar situation after restoring a backup a little while ago. I ended up fixing it by flashing the stock build to both slots using the flash all bat. At this point I wouldn't be concerned about removing the -w. Just let it wipe everything and start from scratch.