Database Develop

[Q] Phone bricked?

hey guys i searched and havent really found anything that matched quite what i had going on so here we go... I was 95 percent through flashing the ICS rom it got through the hboot section and rebooted.. on the screen i saw two arrows in circular form above a phone .. and something was definitely being downloaded.. then the phone went black, doesnt go into hboot, doesnt a charging light when plugged in , but is picked up by the computer, ie. connection noise. Im in no way a noob at flashing roms , but something is definitely wrong with my phone.. Any ideas? It was charged full battery by the way.. it does glow in a dull light when i push volume down and power, or power alone...

Your phone indeed seems to be bricked. The identification noise from the computer may just mean that your USB is receiving power from the battery.
When my friend had a similar problem with his Amaze, he went to the HTC service center and they replaced his phone after keeping it for 4 days

So taking it to bestbuy to get it serviced is probably the only alternative, since its insured through them... lol just my luck

I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium

Dxtra said:
I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's not fair to say. There's plenty of users that flashed without bricking their devices.
I followed the alternate directions here and had no issues.

Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA

meatwad0222 said:
Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium

Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.

As far as im concerned each one of us is responsible for what happens to our phones, warnings are put for a reason.. ive jailbroken, rooted the hardest of phones .. it was just my time for the inevitable to happen. I get my phone back in three days and you can be sure ill be back here again doing crazy rooty stuff to my phone no rom or dev should be held responsible for what ive done ..
Sent from my MB860 using Tapatalk

dusty2422 said:
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.
Click to expand...
Click to collapse
Saying something is noob proof will inevitably prove that some where some noob will sow its not noob proof. I'll admit there were a few moments of panic when I flashed the zip method pg released. When that happened I just breathed deep and took my time and everything worked great in the end. I personally feel that what the devs have put out there is fairly safe as long as the directions are followed exactly.
Sent from my HTC PH39100 using xda premium

Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't have the money to buy tons of new devices....its about knowing ur own limitations...do not criticise a devs hard work when it is proven to work...no its defenitly not idiot proof but it is very easy...I've done it to 3 phones already with no problems...the devs are not responsible for bricked phones
Sent from my HTC PH39100 using XDA

yea i must say it was a hundreed percent my fault in bricking my device so im not mad at anyone..and as far as the money goes its not a super big deal..i always make more o and btw im gonna be getting my replacement today and im gonna try this all again aft6er reading everything again and again and agian o and again lol

So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.

I bricked my phone Sunday night, still not 100% sure what I did wrong but it did what yours is doing now. I simply called the AT&T exchange by mail and used the factory warranty. Granted I guess there is a slight chance they could find out it was rooted (if they can somehow get it to recover or even turn on) but it got me a replacement... Food for thought.
Btw I got the new one and used the RUU and it worked seamlessly.
Sent from my HTC PH39100 using xda premium

bsSkunkApe said:
So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.
Click to expand...
Click to collapse
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.

dizzyraider said:
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.
Click to expand...
Click to collapse
Fraid it doesn't search for anything. I posted in the threads and tried everything I could think of and everything that was suggested. Though there isn't much you can do besides keep removing the battery and trying vol dn + pwr. Just a black screen.
Just a few things I tried (removed battery each time)- vol down + power (no sd card in) = blank black screen
vol down + power (with sd card and PH39IMG file) = blank black screen
vol down + power > boots to blank black screen, wait few seconds > press power button (like I'm going to fastboot) > plug into computer > type fastboot command into command prompt = command prompt says waiting for device
I always read the directions and threads a bunch of times before doing anything. Did lots of reading, google-ing, and searching. Fraid it bit the dust. I appreciate the help though. This is the first device snafu I've had. I've never had to send a phone in for any kind of warrantee work before. Hence my question above about getting it fixed.
Just in case, if it were to boot to that screen, what would I want to do? Just the PH39IMG? Or is there some other procedure?

Dxtra said:
Why would I tell anyone to flash when is not safe to.
Click to expand...
Click to collapse
Who TOLD you to flash the phone??? When I got my first android phone, a Samsung Fascinate, I LOVED the phone but nervous AS HELL that I would brick the phone. And I read, and read, and REREAD, trying to make sure I understood everything so that when I went looking for help, I at least could say, "Yes, I already tried this, this, and this".
I think the key thing to all of this is in two-fold - one, as someone stated before, this is a developer's forum. If you work on your car, and forgot to put oil in it, are you going to blame your mechanic? If you change your brakes and did not do something correctly, causing an accident, are you going to blame the car manufacturer??? Two, it states in MANY places, before you post, READ, READ, READ. It was actually ADVISED to NOT FLASH this ROM...
From this point forward, it almost seems as if there needs to be a waiver release to download roms, stating you will not ridicule nor torment the developers. And though I had heard about it but never seen it before, as I am on my 4th Android phone, there definitely are a few VERY NOTICEABLE disrespectful and ungrateful individuals in this forum. If you were my kid, and acted like that to me for something I GAVE YOU, I would do the same as PG - TAKE IT WAY and forget you.

they say it cant happen

well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!

I read lot about "antutu benchmark" as it's bad for Nexus 4 and cause this problem!.
hope somebody can help you out.

maddoggin said:
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
Click to expand...
Click to collapse
If it's easy to take back do it. However couple of folks have got it fixed by opening the backplate and disconnecting/reconnecting battery terminals.
Almost 90%+ people having this issue were running Antutu.

Why would you think its a good idea to flash a custom kernel on to stock?

There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4

http://forum.xda-developers.com/showthread.php?t=2128392

XxSilent22xX said:
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
Click to expand...
Click to collapse
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.

This for the help. I'll try this tomorrow morning. Of course I tab a search bit could not find the threads. I hit red light and it took me to legacy phone. I type brick in search fort n4 and nothing. So I never saw those threads about this issue. So thanks. And ive never had a problem with running custom kernels on stock ROM. Never! Lol
Any ways thanks for help! Can moderator close this thread please! Thanks!
Sent from my Galaxy Nexus using xda premium

And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app

Franco R53 is fine on stock - running it here with minimal other changes (I.e. root + email security policy hack)
I've updated every Franco kernel and all seen OK. Perhaps the benchmark related hardware failure is worth looking closely at.
FWIW, if you're back to stock, lock the bootloader and send it back as it sounds hardware to me.
Daern
Sent from my Nexus 4 using Tapatalk 2

synergeticink said:
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
Click to expand...
Click to collapse
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.

Charge your phone?
Im pretty sure you get the red light if your device has not enough power to display the screen.. Put your phone on charge through the main plug

qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
So true man so true!
Sent from my Galaxy Nexus using xda premium

This happened to me, except I was bone stock. You need to hold down all 3 buttons at the same time; several times, and then try to get into the bootloader. That's what worked for me. Once you're in the bootloader you can flash the stock image(s) via fastboot.

qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4

OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
if this is true then why do i need to pull the phone apart and disconnect the battery and reconnect? apparently this is a known issue and has happened to others and taking phone apart and disconnecting battery and rconnecting it fixes the issue. unfortunately i dont have the right tools to do this so i will be taking my phone to t-mobile this morning. thanks for all the help guys. really appreaciate all the responses i got.

At times the power button wont work. In some cases of soft bricks. I have this issue since i had HD2.
Sent from my GT-N7000 using xda app-developers app

estallings15 said:
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Click to expand...
Click to collapse
That's exactly what I said in my last post. Next time the op needs to clarify if the custom kernel supports stock. But regardless I was correct.

OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
The service manual says ten seconds but yes it fully cuts power from the battery.

So sitting in my car waiting for t mobile store to open I decide to plug phone in to car charger since I know this will be first thing t mobile does and lo and behold phone booted up and start working. Battery drained to 0 and charging now. Go figure
Sent from my Nexus 4 using xda premium

HTC One Roms on carrier HTC Ones

Hey guys - quick question, and sorry if this has been answered before. I did a quick search and couldn't find an answer under FAQ or recent threads. I apologize in advance for any duplicativeness. Here it goes:
I ended up getting my One directly through T-Mobile, so it's not the HTC developer edition or unlocked model. Once I unlock/root my "TMo" HTC One, will the ROMs under the "HTC One" dev forums work, or do I have to stick to the ones posted on the "T-Mobile HTC One" dev threads? Thanks in advance.

They will work on your T mobile HTC One.
Sent from my HTC One TrickDroid 5.3.0 using XDA Premium
Sign up for Copy! A great dropbox alternative that gives you tons of FREE space! http://copy.com?r=luU4NP
Start off with 10 gigabytes of free storage with my referral!

Do I need to do anything after flashing ROMs from this forum to "adjust " them to tmo radios or anything?
Sent from my HTC One using xda app-developers app

Hate to shamelessly bump, but can anyone confirm this?

No, tmobile varients are supported on nearly any Rom out atm
Sent from the one and only HTC One

ManBearPig618 said:
Do I need to do anything after flashing ROMs from this forum to "adjust " them to tmo radios or anything?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Have you seen those custom desktops, Like Stardock or Fences, that have widgets and functions you can't get in regular windows? This is far from 100% accurate but think of the rom as the skin over windows. Those never really effect your drivers(the radio) since they just tweak your GUI so as long as they can run on your hardware you'll never have to worry about them effecting your printer.
Does that make sense or is my brain fried from my self directed 36 hour crash course on this forum?

BableMan said:
Have you seen those custom desktops, Like Stardock or Fences, that have widgets and functions you can't get in regular windows? This is far from 100% accurate but think of the rom as the skin over windows. Those never really effect your drivers(the radio) since they just tweak your GUI so as long as they can run on your hardware you'll never have to worry about them effecting your printer.
Does that make sense or is my brain fried from my self directed 36 hour crash course on this forum?
Click to expand...
Click to collapse
Makes enough sense. I've only ever rooted/unlocked/flashed ROMs on Nexus devices, so I just want to make sure I know what I'm doing before I dive in here. Thanks!

ManBearPig618 said:
Makes enough sense. I've only ever rooted/unlocked/flashed ROMs on Nexus devices, so I just want to make sure I know what I'm doing before I dive in here. Thanks!
Click to expand...
Click to collapse
IDK about ARHD, but triuckdroid will ask you AT&T/INTL/T-MO before you flash, so everything works correctly. I believe all HTC Ones in the US(So Far) are the same as the INTL..... there's a thread about it somewhere.... But just make sure you have the right APN settings. P.S New radios are usually a good thing if you have bad signal all the time (WiFi/Cellular).

Has this been confirmed by anyone else?

[Q] 4g/LTE/3G not working on Custom Roms

Hello XDA,
So I've purchased my 1st quad-core phone Saturday. I'm extremely happy about the phone's cosmetics and performance. Of course, being the flash-aholic that I am, I decided to beef it up!! After finially getting an AOSP rom that I felt comfortable with, I flashed and everything was great.... Until I noticed that my data stopped working. The funny thing is if I turn on airplane mode, make a call, or restart the phone the data comes on for about 2 minutes and then turns back off. After messing around with settings and such, I restored my stock rom. On the stock rom data works like it should. So I decided to try 2 other roms. One being GE and the other AOSP. Both are doing the same thing with data connectivity.
Is this a known issue? Did I do something wrong? I looked through the Q&A's and I didn't find anything. Keep in mind that I am very experienced up to full development of rooting/flashing/customizing/etc
Thanks in Advanced!!!!!
Update: T-mobile is my service provider

*bump*
It's imperative that I find out if this is fixable or not as I will return the unit if it's not...
Apologies
Sent from my HTC One using xda app-developers app

DonSolo said:
Hello XDA,
So I've purchased my 1st quad-core phone Saturday. I'm extremely happy about the phone's cosmetics and performance. Of course, being the flash-aholic that I am, I decided to beef it up!! After finially getting an AOSP rom that I felt comfortable with, I flashed and everything was great.... Until I noticed that my data stopped working. The funny thing is if I turn on airplane mode, make a call, or restart the phone the data comes on for about 2 minutes and then turns back off. After messing around with settings and such, I restored my stock rom. On the stock rom data works like it should. So I decided to try 2 other roms. One being GE and the other AOSP. Both are doing the same thing with data connectivity.
Is this a known issue? Did I do something wrong? I looked through the Q&A's and I didn't find anything. Keep in mind that I am very experienced up to full development of rooting/flashing/customizing/etc
Thanks in Advanced!!!!!
Update: T-mobile is my service provider
Click to expand...
Click to collapse
Did you try updating the radio firmware to match the ROM that you were using? Did you try another Sense ROM to see if the issue wasn't an underlying setting from a GE or AOSP ROM? Did you flash a custom Kernel? Did you match the RILs? Lots of things that you could try to isolate the issue.

Athrun88 said:
Did you try updating the radio firmware to match the ROM that you were using? Did you try another Sense ROM to see if the issue wasn't an underlying setting from a GE or AOSP ROM? Did you flash a custom Kernel? Did you match the RILs? Lots of things that you could try to isolate the issue.
Click to expand...
Click to collapse
I fixed the issue... Wasn't aware that there was a different section for T-Mobile. Man I fell incompetent smh.... I'm running a Cyanogen Mod now
Thanks as I'm noting your suggestions
Sent from my One using xda app-developers app

DonSolo said:
I fixed the issue... Wasn't aware that there was a different section for T-Mobile. Man I fell incompetent smh.... I'm running a Cyanogen Mod now
Thanks as I'm noting your suggestions
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
I use PA from the regular HTC One forum even though I'm on T-Mobile... It shouldn't matter, I still get the same speeds. Some different ROMs will use different names, like the aosp stuff uses 3g, H, H+ and LTE. In order to enable lte you have to go into the settings for mobile data, APN and then make sure it's the one that's like fast.tmo whatever. That's the LTE APN
Sent from my HTC One using xda app-developers app

what's the exact APN name that should be there? I was reading about it but no one said what T-mobile's APN should be. they just noted that it should be changed the correct carrier.
edit: Thanks Button hit!!

DonSolo said:
what's the exact APN name that should be there? I was reading about it but no one said what T-mobile's APN should be. they just noted that it should be changed the correct carrier.
edit: Thanks Button hit!!
Click to expand...
Click to collapse
"fast.t-mobile.com" for LTE.

GPE on the m8

Runs so smooth, just got this phone free from sprint, S-OFF it, installed a GPE lollipop ROM and I am in LOVE. And I've had a lot of phones. Thank you XDA!
Sent from my HTC One_M8

evangeleet said:
Runs so smooth, just got this phone free from sprint, S-OFF it, installed a GPE lollipop ROM and I am in LOVE. And I've had a lot of phones. Thank you XDA!
Sent from my HTC One_M8
Click to expand...
Click to collapse
agreed, probably the smoothest gpe port ive used on the m7 and now m8. Props should go to captin throwback and digitalhigh and their respective teams on making such a wonderful rom.

Aside from the annoying voice-mail notification, this thing it tits.

adam.kelly2 said:
Aside from the annoying voice-mail notification, this thing it tits.
Click to expand...
Click to collapse
Go swap out the teleservice.apk I posted in the forum change permissions reboot and you should be golden

tjeeeeee said:
Go swap out the teleservice.apk I posted in the forum change permissions reboot and you should be golden
Click to expand...
Click to collapse
And this is why I love this forum.

adam.kelly2 said:
And this is why I love this forum.
Click to expand...
Click to collapse
I spent weeks figuring and fixing it finally got it
Also digitalhigh incorporated it into his next update

tjeeeeee said:
I spent weeks figuring and fixing it finally got it
Also digitalhigh incorporated it into his next update
Click to expand...
Click to collapse
What I've been doing is every few hours clearing the phone.apk cache. Goes away, come back in a couple hours, maybe the next day. What was causing the issue?

adam.kelly2 said:
What I've been doing is every few hours clearing the phone.apk cache. Goes away, come back in a couple hours, maybe the next day. What was causing the issue?
Click to expand...
Click to collapse
From what I've read its a voicemail that's been left on an old phone but still shows up I never got it on sense based Roms but as soon as I put aosp or gpe, voicemail consistently and I'm doing the easy pay which means I can't swap out to another phone leave a voicemail on it then delete it and switch back which should also clear it, thus my solution was to edit the smali in the apk and haven't had a problem since and since I'm not the only one with the issue I posted a fix for us unfortunate enough to have said issue. Annoying? Yes, but now its all good with the fix. It should work for any gpe and even cm(haven't tested yet)

Is your GPS working on GPE lollipop? I'm on HK edition.

ceo.mtcl said:
Is your GPS working on GPE lollipop? I'm on HK edition.
Click to expand...
Click to collapse
Yeah if it isn't for you easiest method is to boot a sense based rom and open maps to get a lock on location then reboot immediately from there to gpe

Thank you this worked perfectly.