320 replies to this topic

[7eregrine]

Its happening virtually every rom I've tried so far, GPS somewhat seems to be working fine..... except the fact that it's about a mile or two off.

 

 

That might be fun for Ingress.

[artnig]

That might be fun for Ingress.

Have yet to play it, But without veering off topic I'm flashing back to stock KK for now and I'll report on my my GPS functionality, which seems like a hit-or-miss problem with everyone on KitKat ROMs. Hardly use WiFi or Bluetooth with my phone but I'll test what I can in regard as well.

[ibolski]

CM11 seems to be good on GPS. As I stated earlier, yesterday I ran into an issue, but have since fixed it. I'm back on CM11 and GPS seems to be functioning just fine, as it was before.

[pegs520]

Anyone willing to fill me in on why GPS and WiFi are taking so long to fix?

I don't know much about ROM building and whatnot, so a little info would be appreciated.

[wooddale]

Anyone willing to fill me in on why GPS and WiFi are taking so long to fix?
I don't know much about ROM building and whatnot, so a little info would be appreciated.

If you mean why its taking so long for Roms to get fixed its because they are free and the guys working on them have real lives too if I misunderstood your question disregard.

[pegs520]

If you mean why its taking so long for Roms to get fixed its because they are free and the guys working on them have real lives too if I misunderstood your question disregard.

I was actually wondering what the specific problem was with WiFi and GPS. More out of curiosity than anything else.

To clarify - I don't need either fixed any time in the near future. Haven't been to leave the house for a while because of injury, and WiFi is good in my house.

[wooddale]

lol I'm sure if they knew it would be fixed. Sometimes when youyou get one thing to work it breaks another. That's what it is all about.

[Playb3yond]

I'm having a problem booting the pac-man ROM on my maxx HD. I'm on the KitKat boot loader currently running sokp without any issues, but even after wiping the data partition and repairing it as ext4, the ROM still won't boot. I always factory reset and wipe data when changing Roms. PA, CM11, Omnirom and liquid smooth don't have this issue. I've tested almost all Roms for KitKat and found this small issue with a large majority of the PAC ROM nightly builds. The ones that are bootable are the few builds a Dev test, which were not daily drivers, very buggy.

[nobe1976]

Question from someone at DroidForums: He rooted and Unlocked. He wants to put a JB Rom on it. NBD, right? Or is the fact that he has the KK recovery going to screw it up?

 

He could actually downgrade the bootloader quickly by using FlashBack. A quick tool that I put together to run in the current Recovery that the person is on. Follow the line

Please Login or Register to see this Hidden Content

and read, read, read.....

[hkam1978]

Hey guys!  I am a Noob so take it easy on me...I unlocked my bootloader and installed Validus 5.2 which is Android v4.4.2.  The phone reboots and burns up while using it so I want to try a different ROM.  When trying to flash the gummy or baked roms I get an error saying that my bootloader is not 4.4.  What can I do to install baked or gummy?

 

thanks in advance!

[RikRong]

Hey guys! I am a Noob so take it easy on me...I unlocked my bootloader and installed Validus 5.2 which is Android v4.4.2. The phone reboots and burns up while using it so I want to try a different ROM. When trying to flash the gummy or baked roms I get an error saying that my bootloader is not 4.4. What can I do to install baked or gummy?

thanks in advance!

You need to update. There's a thread on here to show you how.

Please Login or Register to see this Hidden Content

Sent from your Mom's M8

[Aqua009]

I'm having problems installing CM.  I'm using TWRP and I have been able to install Gummy with no problems.  When I try either CM cm-10.2.1-xt926  or cm-11-20140218-NIGHTLY-xt926... on the reboot, they both stay in the Motorola logo startup screen.  Am I supposed to go back to Jelly Bean before installing?

Build is KTU84p

And the Gummy wont stay connected to home wifi.  It's a zyxel router.  I installed Gummy-M3.0-09-26-14-NIGHTLY-moto_msm8960.

 

 

Thanks

[nobe1976]

I'm having problems installing CM. I'm using TWRP and I have been able to install Gummy with no problems. When I try either CM cm-10.2.1-xt926 or cm-11-20140218-NIGHTLY-xt926... on the reboot, they both stay in the Motorola logo startup screen. Am I supposed to go back to Jelly Bean before installing?

Build is KTU84p

And the Gummy wont stay connected to home wifi. It's a zyxel router. I installed Gummy-M3.0-09-26-14-NIGHTLY-moto_msm8960.


Thanks

Both those versions require one to be on the 4.1.2 bootloader in order to boot correctly. You can fastboot back using HOM and the universal script use the FlashBack.zip located in the development tread. If you use a xt926 device look for that version. If you use a xt907 device there is a version located in there tread as well. Best of luck and read 4 times before doing so. Thanks

[Caliburno]

Hello i'm sorry to bother, but i just got stuck in some strange behavior.

 

 

I bougth the phone a week ago, finally unlocked my bootloader accouple days ago and flashed KitKat slimrom, but is too choppy and i would like to test some others. Now CWM (6048) tells the rom is for certain models correctly, but that it can't flash it because my phone -> is a " " and ends up in an error.

 

I don't know what could have happened because i bought a used phone and still had the official VZW Jelly Bean with locked bootloader.

 

¿Any advise? ¿Is there something i need/could to write somewhere?

 

Thanks for your time.

[nobe1976]

Well hopefully you updated the stock Rom to the first stage of 4.4.2 then it can be unlocked again to preserve both root and have the ability to flash custom firmware onto it. More then likely this is th case since most builds based off of the 4.4.2 bootloader have a insert to look for the bootloader and stop the install before anything happens. If you have not update to the 4.4.2 OTA then you are stuck installing ROMs based off of 4.1.2 bootloader.

Sent from my VS980 4G

[hkam1978]

You need to update. There's a thread on here to show you how.

Please Login or Register to see this Hidden Content

Sent from your Mom's M8

Thanks RikiRong, just saw this!

[Caliburno]

Hello, sorry to bother. This is not a question about one rom particularly but about an strange issue that appeared on my phone.

 

I have recently bought a second hand xt926 with 4.1.2 official Android on it. It does not seem to have any kind of fidling on it, so i guess is full factory.

 

Now, i upgraded to official KK, unlocked bootloader and then flashed slimrom. But, any time i try to flash anything not slimrom, CWM tells the rom is for certain models (and names them -xt926 among-) but also tells my -> phone is a " " <- and i can't flash anything else.

I tried disabling signature check on CWM but it is the same.

 

May some string be missing somewhere?

Anything i can do to solve this?

 

Thanks in advance.

[RikRong]

Try changing over to TWRP and see if that solves your problem.

[Caliburno]

Will try but i find it hard to identify wich TWRP is for my phone, already search for it but i got messed up. I don't want to end up with an expensive brick.

 

Thanks

 

 

 

EDIT: OK, it went great i already flashed a new rom.

 

THANKS!

[kandyar]

Every time I click on that link it tells me it's forbidden.

Sent from my XT1060 using Tapatalk