Database Develop

[GUIDE] How To Fix GPS Issues On CM7

Sup People.
I recently noticed that my GPS wasnt working on CM 7.1.0.1. After searching this forum I found that quite a few people were also having the same issues so i've decided to compile this guide (all credits to OP's, i'm just putting this info in one place)...
theres not much to it to be honest, its just the information on the issue is just scattered around - plus there are probably better and more complete guides out there
Firstly, Originally Posted by bharat_xda19
bharat_xda19 said:
First install cm7 and then make a nandroid backup of it. Then wipe everything and restore the previous nandroid backup of stock froyo rom (or any rom with working gps) and use gps to capture your location. Then again wipe everything and restore the cm7 backup. Now gps will be working. And once gps on cm7 works, then even after a hard reset it still works. This seems to be an issue only when freshly installing cm7. This is definitely a safe method.
Click to expand...
Click to collapse
The next procedures are really for advanced users only...or if you know what you are doing if you dont understand anything in this next part I would do a little reading on the topic first
Secondly, Originally Posted by CroWarrior
CroWarrior said:
I found out in this topic here:
http://forum.cyanogenmod.com/topic/2...s-doesnt-work/
that some people fixed issues with this radio:
Radio_13.53.55.24H_3.35.19.25
Click to expand...
Click to collapse
OR
[OP - http://forum.xda-developers.com/showthread.php?t=1029318&highlight=flash+a+radio by 3xeno]
3xeno said:
-- The following will only work with Clockworkmod 2.5.x.
1. To get Clockworkmod 2.x when you have a newer version, flash the 'update1.zip' in the attachments
2. If you have ROM Manager, use the 'select older cwm' at the bottom of the list to select 2.5.0.7
-- Make sure you have sufficient battery charge and do not interrupt the flashing process.
•Radio_13.55.55.24H_3.35.20.10
•Radio_13.53.55.24H_3.35.19.25
•Radio_13.53.55.24H_3.35.15.31
Click to expand...
Click to collapse
THEN...
nejc121 (edited by arkoze) said:
Download radio zip above [19.25 or 20.10 as you probably have 15.31]
Put Radio .zip on root of SD card i.e not in any folders
Start ROM Manager
(ensure you have CWM 2.x.x.x)
Click Reboot into Recovery
Flash .zip from here by going to install zip from SD card
Don't forget to wipe caches first
Reboot phone by using the "reboot" option in cwm NOT by removing the battery
Click to expand...
Click to collapse
The process will take about 10 mins so be patient
Make sure you have sufficient battery charge and do not interrupt the flashing process.
I used the 3xeno and nejc121 method's above. Downgraded my CWM (which is only temporary if selecting through ROM manager) then flashed the 20.10 radio. 3xeno recomends flashing the 19.25 radio first to see if that works but i went straight for the 20.10 = WORKING GPS
!!!DISCLAIMER!!!
I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. IT IS YOUR DECISION TO GO AHEAD WITH THESE MODS SO ONLY YOU CAN BE BLAMED FOR YOUR ACTIONS
p.s. if followed correctly, you shouldn't go wrong

In simple terms.
1.gain temp 2.5.0.7 cwm via Rom manager or temp update zip if your on a newer version already.
2. Flash 19.25 or/and 20.10 radio.
3. Reboot.
I have NEVER wiped anything to flash a radio as it has no influence over caches whatsoever.!!!!
Whenever I had gps issues I just flashed the 19.25 radio then test gps. Then re flash 20.10 radio. Never failed me yet. Lol.
regards,slymobi

slymobi said:
In simple terms.
1.gain temp 2.5.0.7 cwm via Rom manager or temp update zip if your on a newer version already.
2. Flash 19.25 or/and 20.10 radio.
3. Reboot.
I have NEVER wiped anything to flash a radio as it has no influence over caches whatsoever.!!!!
Whenever I had gps issues I just flashed the 19.25 radio then test gps. Then re flash 20.10 radio. Never failed me yet. Lol.
regards,slymobi
Click to expand...
Click to collapse
hi I dont suppose you could send me a link to those 2 radios as i can't download them now because of megaupload.com gone done please.

apollopayne said:
hi I dont suppose you could send me a link to those 2 radios as i can't download them now because of megaupload.com gone done please.
Click to expand...
Click to collapse
yes here they are

slymobi said:
yes here they are
Click to expand...
Click to collapse
thank you so much

apollopayne said:
hi I dont suppose you could send me a link to those 2 radios as i can't download them now because of megaupload.com gone done please.
Click to expand...
Click to collapse
the links still work. just dont use the megaupload one, scroll down and use other options

Hi there!
I've tried this multiple times but it still doesnt seem to work :/ Any suggestions on what to do next?

MacGyver Jack said:
Hi there!
I've tried this multiple times but it still doesnt seem to work :/ Any suggestions on what to do next?
Click to expand...
Click to collapse
Try using an app that triggers gps like gps test from the market. It worked 99% of the cases for me.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5

[Q] CM Update

So i'm using the first nightly that came out (CM10) and saw the one that has been released today 20121102. I used the CM Updater and it downloaded it pretty fast and reboot.
The thing is, it reported a error saying "20121102.zip can't be found" and ask me if i want to install "untrust.zip" so i'd cancel it.
Was that actually the update?

well it updated for me nicely, try to find the downloaded rom in folder /cmupdates

Questioned said:
well it updated for me nicely, try to find the downloaded rom in folder /cmupdates
Click to expand...
Click to collapse
does it wipe it all or i don't need to make a backup?

Javiern said:
does it wipe it all or i don't need to make a backup?
Click to expand...
Click to collapse
You don't need a backup but it's recommended in case something goes wrong. And no it doesn't wipe your data. Just flash the update over your current ROM.

It works.......

[ROM] Stock rooted OTA 4.08.605.19 710RD - 02-10-2013

Stock Rooted OTA 4.08.605.19 710RD Rom​
Stock rooted ota 4.08.605.19 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy ​
[standard flashing disclaimer here]​
Do a full wipe (boot, system, data, datadata, cache, android secure) except for sdcard and emmc, then flash like any other rom. ​
Stock rooted ota 4.08.605.19 rom may be able to be flashed over Stock rooted ota 4.08.605.15 rom, but is untested. If you flash over and have issues, do a full wipe and fresh install.​
DOWNLOAD ODEXED - MD5 - Mirror​
DOWNLOAD DEODEXED - MD5 - Mirror​
_

2-13-2013 - Fixed TWRP flashing issues.
3-13-2013 - Fixed Superuser issues.

Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.

ToyTank said:
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
Click to expand...
Click to collapse
Just grab a root file explorer.
Sent from my Nexus 7 using Tapatalk 2

Osiris19 said:
Just grab a root file explorer.
Click to expand...
Click to collapse
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.

ToyTank said:
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
Click to expand...
Click to collapse
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?

IceDragon59 said:
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
Click to expand...
Click to collapse
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.

cmlusco said:
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
Click to expand...
Click to collapse
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.

IceDragon59 said:
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
Click to expand...
Click to collapse
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.

cmlusco said:
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
Click to expand...
Click to collapse
Deleting them in WinZip. That's how I've always successfully done it before.

IceDragon59 said:
Deleting them in WinZip. That's how I've always successfully done it before.
Click to expand...
Click to collapse
I will try it and see if it does the same for me.

cmlusco said:
I will try it and see if it does the same for me.
Click to expand...
Click to collapse
Any luck?

IceDragon59 said:
Any luck?
Click to expand...
Click to collapse
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.

cmlusco said:
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
Click to expand...
Click to collapse
Thanks so much =), honestly I am surprised updates are still being released. I really need to get to a Verizon store and snag the 4G version but I've been traveling a lot so my Blackberry has been getting a workout thanks to the international SIM support. Regardless I still use my Dinc for Google Auth (2-pass auth FTW!) and other activities everywhere (in network or not).

Fixed issues with superuser. For those who have already downloaded reflash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip thru recovery.

Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.

leo72793 said:
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
Click to expand...
Click to collapse
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.

cmlusco said:
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
Click to expand...
Click to collapse
having pertition error :/

leo72793 said:
having pertition error :/
Click to expand...
Click to collapse
What kind of partition error?
I tested both cwm and twrp with both a flashover from stock rom 605.15 and a clean install and all worked just fine. Did you check the md5? Try redownloading.

Just got my INC back from my little sister after she upgraded and i'm excited to have this as my backup! Thanks for uploading this for everyone!

Xperia V recogonizing tsubasa as "mint"

Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader

Allen Hu said:
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Click to expand...
Click to collapse
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it

St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
TWRP not working too :silly::crying:

Allen Hu said:
TWRP not working too :silly::crying:
Click to expand...
Click to collapse
Same problem. Have you find any solution?

zaize said:
Same problem. Have you find any solution?
Click to expand...
Click to collapse
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this

Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
Man thats crazy - but it worked! Thank you :victory:

zaize said:
Man thats crazy - but it worked! Thank you :victory:
Click to expand...
Click to collapse
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
First flash kernel of ROM that you're going to install via fastboot, then reboot to recovery and flash ROM :laugh:

Allen Hu said:
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Click to expand...
Click to collapse
Does the error say only "status 7", or does it say anything else also, such as "this device is xxxx, etc."?

Antiga Prime said:
Does the error say only "status 7", or does it say anything else also, such as "this device is xxxx, etc."?
Click to expand...
Click to collapse
The problem is already solved here...
it showed the " this device is "mint"" or something like that

Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
Aria.A97 said:
First flash kernel of ROM that you're going to install via fastboot, then reboot to recovery and flash ROM :laugh:
Click to expand...
Click to collapse
Allen Hu said:
The problem is already solved here...
it showed the " this device is "mint"" or something like that
Click to expand...
Click to collapse
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
assert(getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" || abort("This package is for \"LT29i,hayabusa\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.

Many thanks
Antiga Prime said:
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Click to expand...
Click to collapse
Thank you for solving this properly, it worked perfectly for me!

worked for me
Antiga Prime said:
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Click to expand...
Click to collapse
works fine

Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
Hi, i have the same problem, but i don't know were i can find the AOKP, can you please help with this?
Thank you

celupapas said:
Hi, i have the same problem, but i don't know were i can find the AOKP, can you please help with this?
Thank you
Click to expand...
Click to collapse
http://xfer.aokp.co/get.php?p=AOKP/tsubasa/aokp_tsubasa_jb-mr2_milestone-1.zip
Here you go
Well if this doesn't work you can try deleting some lines in updater-script as the method provided above?

Allen Hu said:
Here you go
Well if this doesn't work you can try deleting some lines in updater-script as the method provided above?
Click to expand...
Click to collapse
Thanks a lot, I flash AOKP and this work, everything is normal again.
Never happen but I read that the problem was the rom and some problems with the recovery.

Hello,
I have tried to install CM12 using CWM but I got this error.
After deleting the first line on updater-script file I got another error:
Creating symlinks....
symlink: some symlinks filederror in /storage/...
(Status 7)
installation aborded.
I have tried to delete also the second line and the third and the 4th but every time the same error.
Do you have any idea of what is happening?
Can you please provide some basic instructions on how to install this custom ROM with Flashtool?
Thank you

nicu.s said:
Hello,
I have tried to install CM12 using CWM but I got this error.
After deleting the first line on updater-script file I got another error:
Creating symlinks....
symlink: some symlinks filederror in /storage/...
(Status 7)
installation aborded.
I have tried to delete also the second line and the third and the 4th but every time the same error.
Do you have any idea of what is happening?
Can you please provide some basic instructions on how to install this custom ROM with Flashtool?
Thank you
Click to expand...
Click to collapse
First, you can't just go deleting lines; if they are there, it's for a reason. Second, I'm pretty sure your CWM version isn't up to date in order to flash a CM12 ROM. And, you can't flash a Custom ROM with Flashtools.
What you can do, however, is extract the boot.img from the ZIP file, flash that kernel with Flashtool, and then Flash the ROM in what most likely would now be TWRP recovery.

no start after I clicked TWRP Fix Permissions

Hello,
I need advice, please. MOTO G2 (2014) XT1068
XT1068 unlocked>TWRP installed>TWRP Fix permissions clicked>now boot animation and goes into black screen (with backlight).
More detailed:
Last night I have unlocked my XT1068 and installed TWRP, no problem.
(following this https://www.youtube.com/watch?v=BLSTDsFG1xw, citing https://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165).
First deviation was I got TWRP from http://www.devfiles.co/download/4lhHC4Uv/TWRP_2.8.0.1_Titan_v2.img as I ran into an unavoidable sign-up trap following the cited url).
Second deviation was I chose to install SU offered by the TWRP app via Gplay, which was unsuccessful.
So I decided to go back and follow the instruction, using the provided "Update SU" file but found my Windows Explorer but it didn't give me access to internal memory or SD card. After short research, I found that XT1068 "developer options>USB configuration" toggling MTP to Charging only and back MTP helped https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ as the Windows Explorer was able to access the XT1068 memory. (SD card was setup as internal memory).
I copied the file over, rebooted into TWRP but couldn't see the file. I remember having seen something like "unable to mount or access memory" in TWRP and remembered from XDA thread that permissions might be messed up. It was late, I jumped to a conclusion when I found the TWRP option "Fix permissions". I clicked it and have since the issue.
I can get into the menu which offers "recovery" and also get into TWRP
I have tried "Factory reset" but I am not sure what happens there, Motorola boot animation comes and then the black screen again (with backlight)
I think I have options but feel like in a minefield and better ask for what to do next.
Thank you

can you tell me you're bootloader version and on what android version you were when you messed up things? If your phone boots up to the bootloader i.e. the menu which allows you to enter recovery then you're having more than one options to fix this problem. But be careful this time. as this may brick your phone and it will be gone for good..
Read this XDA thread and do the steps carefully. This may restore your phone
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682

Hi, I had the stock Marshmallow and bootloader is showing 48.86 (if that is actually the number). I was aiming to do a titanium backup and then probably try a custom ROM.
I will follow the steps in the link provided to get back to a known working state before trying a custom ROM but I really like to understand what went wrong and in what state the phone now is. I don't think my deviations where a bad choice but clicking "Fix permissions" obviously was. I like to learn from mistakes.
Thanks for helping me out.

Ok, read the guide and am uncertain which firmware is the correct one for New Zealand (the thread is full of confusion about the versions). I am waiting for a reply there and asking here if I could from this point also try to flash a custom rom via TWRP? Or better back to a working condition before doing this? Thanks.

karteileiche said:
Ok, read the guide and am uncertain which firmware is the correct one for New Zealand (the thread is full of confusion about the versions). I am waiting for a reply there and asking here if I could from this point also try to flash a custom rom via TWRP? Or better back to a working condition before doing this? Thanks.
Click to expand...
Click to collapse
Umm.. About the firmware version of the stock ROM, you can search google for it. And as far as your question about trying a custom ROM, you can try whichever ROM you want (except Ubuntu Touch, it's installation methods are too confusing). Just download the ROM in .zip file and download "Google Apps (GApps)", I prefer open gapps and install the rom via TWRP.
Wipe out these paritions in TWRP > Wipe > Advanced Wipe:
Dalvik/ART cache
Cache
Data
System
Also before installing any custom ROM read the steps plus read user comments before flashing anything
P.S. make sure your TWRP is latest. For TITAN it is TWRP-3.2.0-0

pkdon123 said:
Umm.. About the firmware version of the stock ROM, you can search google for it. And as far as your question about trying a custom ROM, you can try whichever ROM you want (except Ubuntu Touch, it's installation methods are too confusing). Just download the ROM in .zip file and download "Google Apps (GApps)", I prefer open gapps and install the rom via TWRP.
Wipe out these paritions in TWRP > Wipe > Advanced Wipe:
Dalvik/ART cache
Cache
Data
System
Also before installing any custom ROM read the steps plus read user comments before flashing anything
P.S. make sure your TWRP is latest. For TITAN it is TWRP-3.2.0-0
Click to expand...
Click to collapse
Yes, thanks.
I have flashed ROM's successfully before on Galaxy S3 and Tab 2 and used gapps via TWRP.
I have tried Google for the correct version but find myself turning in circles, most-likely my limited search term knowledge.
https://www.reddit.com/r/MotoG/comments/4bgg02/info_all_moto_g_codenames_models_variants/ shows "XT1068 : Latin America/EU/UK/Asia/Australia/Germany/Brazil/India, Dual SIM" and the listed ROMs named XT1068_TITAN_RET ...(BR for Brazil?) (LA for Latin America?) (DSDS for India?) (GB for UK?) (DE for Germany?) then what? Some are obvious others are what I have read through various comments, DSDS may even be for (EU/INDIAN/GLOBAL), I have not been able to find a really good page explaining this.
You did not answer my last question directly but given that you stated how to flash a ROM and what to wipe, I assume you mean that I could alternatively install a custom ROM at this stage. (Which is what I had planned originally).
Still, would be nice to know the correct firmware version and also why clicking "Fix permission" turned things into custard.
Thanks.

pkdon123 said:
.........
P.S. make sure your TWRP is latest. For TITAN it is TWRP-3.2.0-0
Click to expand...
Click to collapse
Yeah, I´ve seen in the post of @karteileiche that link: http://www.devfiles.co/download/4lhHC4Uv/TWRP_2.8.0.1_Titan_v2.img. That recovery is outdated and not from the original source. Maybe that´s the reason why things get messed up.
Downlad latest TWRP always from this site if you don´t need something unoffical for your device: https://dl.twrp.me/
For titan this would be: https://twrp.me/motorola/motorolamotog2014.html
About installation of custom roms: When you check any thread of custom roms you´ll find in the OP what to wipe and what to use.
And imho it would be better to first flash the actual recovery before flashing any custom rom.

Valid point, thanks for reminding me and providing the link.

karteileiche said:
Valid point, thanks for reminding me and providing the link.
Click to expand...
Click to collapse
You're welcome. Just send me a PM if you need further help or instructions.
Sent from my Moto G 2014 using XDA Labs

Wolfcity said:
Yeah, I´ve seen in the post of @karteileiche that link: http://www.devfiles.co/download/4lhHC4Uv/TWRP_2.8.0.1_Titan_v2.img. That recovery is outdated and not from the original source. Maybe that´s the reason why things get messed up.
Downlad latest TWRP always from this site if you don´t need something unoffical for your device: https://dl.twrp.me/
For titan this would be: https://twrp.me/motorola/motorolamotog2014.html
About installation of custom roms: When you check any thread of custom roms you´ll find in the OP what to wipe and what to use.
And imho it would be better to first flash the actual recovery before flashing any custom rom.
Click to expand...
Click to collapse
Yeah.. I Agree with your point?
---------- Post added at 03:34 AM ---------- Previous post was at 02:45 AM ----------
karteileiche said:
Yes, thanks.
I have flashed ROM's successfully before on Galaxy S3 and Tab 2 and used gapps via TWRP.
I have tried Google for the correct version but find myself turning in circles, most-likely my limited search term knowledge.
https://www.reddit.com/r/MotoG/comments/4bgg02/info_all_moto_g_codenames_models_variants/ shows "XT1068 : Latin America/EU/UK/Asia/Australia/Germany/Brazil/India, Dual SIM" and the listed ROMs named XT1068_TITAN_RET ...(BR for Brazil?) (LA for Latin America?) (DSDS for India?) (GB for UK?) (DE for Germany?) then what? Some are obvious others are what I have read through various comments, DSDS may even be for (EU/INDIAN/GLOBAL), I have not been able to find a really good page explaining this.
You did not answer my last question directly but given that you stated how to flash a ROM and what to wipe, I assume you mean that I could alternatively install a custom ROM at this stage. (Which is what I had planned originally).
Still, would be nice to know the correct firmware version and also why clicking "Fix permission" turned things into custard.
Thanks.
Click to expand...
Click to collapse
Yess, you can try installing custom rom and see if that works.. otherwise flashing stock rom will also be an option for you.

Fixed
Resolved by using the latest TWRP version and a clean flash of a custom ROM.
Thank you Wolfcity :good:

Fixed
Resolved by installing the latest TWRP version and a clean fash of a custom ROM.
Thank you Wolfcity :good:

karteileiche said:
Resolved by installing the latest TWRP version and a clean fash of a custom ROM.
Thank you Wolfcity :good:
Click to expand...
Click to collapse
You're welcome. Nice to hear it's working.
Sent from my Moto G 2014 using XDA Labs