Develop Bugs

[Q] Cannon update on rooted phone

Hello guys! I have rooted optimus g, official firmware, unlocked bootloader. I tried update to the new
kitkat update, but after the download,when installing,an error coming up. Then the phone restarts
and a messaga that i cannot update because the phone may be rooted appears.
I unistall root via superuser settings but the problem still exists. So is there any way to update
to official kitkat? If not, if i flash official 4.1 can i update official? Will i lose my archivers,
contacts,apps e.t.c on my phone?

A assume you installed custom recovery so official update can't execute with it. Just flash KDZ.

nlooooo said:
A assume you installed custom recovery so official update can't execute with it. Just flash KDZ.
Click to expand...
Click to collapse
Thats right, i have cwm. If i flash kdz,will i lose cwm until root again? And should i flash kitkat or 4.1 kdz first?

Connon update I thought you've used Cannon camera update fo OG camera lol
Try flashing Kitkat 20b using Flash tool 2014.

akahroba said:
Connon update I thought you've used Cannon camera update fo OG camera lol
Try flashing Kitkat 20b using Flash tool 2014.
Click to expand...
Click to collapse
lol cannon i see that now i tried flash via lgkdz and mobile support tool or pc suite and not working either. kdz tool not working anymore? so i need to flash on kdz updater with 3GQCD and CS_EMERGENCY settings?

specialistas4 said:
lol cannon i see that now i tried flash via lgkdz and mobile support tool or pc suite and not working either. kdz tool not working anymore? so i need to flash on kdz updater with 3GQCD and CS_EMERGENCY settings?
Click to expand...
Click to collapse
[B]EDIT:[/B] Updated officially via mobile support tool! It's everything perfect except my photos and music! There all vanished! Is there a solution to that?
SOLVED

D855 w/ stock ROM but still personalisations

Hello people. If my trouble is not in correct forum, sorry.
Let's go.
I bought a LG G3 D855 (Brazilian) from Vivo/Telefonica operator. The gadget comes with Lollipop 5.0 and some apps from Vivo. I rooted the phone and removed the apps.
After this, updated to a stock ROM (20b) with no operator's stuff. But my phone still with some things from Vivo, like wallpapers and the version of the ROM didn't change. Still V20A-724-06 (I think the "06" is from Vivo). Reading Google I found that the stock G3 firmware is like 20x-724.
My question: is there anyway to full format my phone, like a formatted PC with no partitions, and create all from beginning? I tried to install TWRP, with full wipes, without success.
Anyone have a solution?
Thanks!

Hi
If i remember correctly there is a folder in the root that has all the stuff related to the operators.
You need to erase that folder.
If you search the forum you will findthe instructions.
Brgds

Do you know if in this folder I can solve the problem with version? Because I found a folder and deleted it, and the apps were killed. But the phone still with operator's wallpaper and the version of Android don't change when I update using LG phone tools...
I'll try to find. Thanks!

You need to flash the kdz after that you must perform a factory reset, if that doesn't work downgrade to 4.4 install twrp flash any 4.4 rom (not stock based) and then re flash something like cloudy and check if that works

I'll try that. Thanks.

jaimep01 said:
You need to flash the kdz after that you must perform a factory reset, if that doesn't work downgrade to 4.4 install twrp flash any 4.4 rom (not stock based) and then re flash something like cloudy and check if that works
Click to expand...
Click to collapse
I downloaded stock 4.4, a CloudyG3 2.5 and a Cyanogem 12. I'll downgrade to stock 4.4, them install CM12 and after, CloudyG3. Is that it you suggested? I want do stay with stock Lollipop, and I'll upgrade to LP5 after Cloudy.
Is that correct?
Thanks again.

Yes what the downgrade via kdz does is that it will delete return to a normal state then CM will write over system partition and to finish the reload of a stock bases rom to return to how you want it just make sue to flash correctly

Not works.
The apps from operator are gone. But still some wallpaper and the build number.

Ruffuss said:
Not works.
The apps from operator are gone. But still some wallpaper and the build number.
Click to expand...
Click to collapse
first, read that:
http://forum.xda-developers.com/lg-g3/general/how-to-change-region-t2904951
now that you know what you are doing, find your operator line in cust/cust_path_mapping.cfg and edit the ending to "=/cust/SUPERSET"
maybe you need a data wipe after to really get rid of things..

Rooting on 5.1.1

So I'm on stock 5.1.1 with locked bootloader and rooted.
Any idea where I can find a ftf file for 5.0.2 or 4.4.4 OR is there another way to root?

You can try flashtool > Xprifirm and see if there is one for you. I had a lot of broken downloads. I ended up flashing this D5503_14.4.A.0.157_Customized DE.ftf yesterday. I can, however, not find it and the moment, yet someone linked it on xda. Sorry.
Anyways, remember wipe cache/data after flash. Then you can root and install lockdualrecovery to flash a prerootet zip made with PRFCreater (Get newest rom from Xpirifirm)

Steffe89 said:
You can try flashtool > Xprifirm and see if there is one for you. I had a lot of broken downloads. I ended up flashing this D5503_14.4.A.0.157_Customized DE.ftf yesterday. I can, however, not find it and the moment, yet someone linked it on xda. Sorry.
Anyways, remember wipe cache/data after flash. Then you can root and install lockdualrecovery to flash a prerootet zip made with PRFCreater (Get newest rom from Xpirifirm)
Click to expand...
Click to collapse
My main problem is that I can't find a working link on XperiFirm...

Ah. Same problem as me. I can torrent the file for you?

doriandiaconu said:
So I'm on stock 5.1.1 with locked bootloader and rooted.
Any idea where I can find a ftf file for 5.0.2 or 4.4.4 OR is there another way to root?
Click to expand...
Click to collapse
Here's stock 5.0.2, (.270 fw), US customization - https://drive.google.com/file/d/0B1niPALD2vPeR25XM0ptUmltSVU/view?usp=sharing
Just for clarity, it says in your post that you are currently rooted on 5.1. Why do you want this file? Or is that a typo?

Need help getting sim card to be recognized after flashing cm13, Thanks!

I have spent the past 2 days trying to get a new cfw installed on my phone that didnt have many bugs. I settled with the cyanogenmod13 and read that it was good for a daily driver. At first i installed the wrong gapps and would make the keyboard crash, but now that i figured that out i need help with getting the rom to recognize the sim card. I tryed reflashing with twrp 2.8.6.0 because i read that it would flash the modem correctly, but still no luck. i'm fairly new to flashing and have only done it 3 times in the past. So now i made an account here to ask for help.
Thanks in advance to all the help i get here.

Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.

audit13 said:
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
Click to expand...
Click to collapse
Thanks for your rely, Im not 100% sure what you mean by modem as im fairly new to this whole business. I will go to the website to see what i can find. Where can i see that information about the modem i am currently running?

I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.

audit13 said:
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
Click to expand...
Click to collapse
Ok I did some research and learned that the modem is the baseband number that shows in the about phone section. This is currently unknown or my guess non existant and that is why the phone says that the sim card is not inserted.
I also learned that i can use ODIN to flash the modem/baseband directly without the need to reflash the whole rom.
I dont know where to find the file online for the modem that matches the rom. I have spent a while looking around and have seen older posts of people saying that they have experienced the same issues after flashing cm13 on n9005 Note 3.
Here is what i am running on my phone:
- Cyanogenmod Version: 13-20151031-UNOFFICIAL-hlte (maybe there is a newer version to this somewhere that has this issue fixed)
- Baseband: Unknown
- Kernal Version: [email protected] #5
- Build Number: 1
-hlte-userdebug 6.0 MRA58K 2127f69904 test-keys
What do you think? And thanks for you help so far. :good:

The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.

audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help

Wouldnt I be able to flash the modem with odin as long as it matches the phone model? or will that cause problems?

Good luck. I hope it works for your phone.

audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Tempestelf2 said:
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Click to expand...
Click to collapse
Updating to the latest version of TWRP is a bad idea. If you update to version 3.0+ you can't install ROM's that use the AROMA installer. The newer versions of TWRP do not support it. The best version I've found is 2.7.8.0 to be able to handle any flashing.

The biggest problem is the sim card in my opinion.

audit13 said:
The biggest problem is the sim card in my opinion.
Click to expand...
Click to collapse
The sim card works fine in Ecuador, I have used it before flashing to cm13. I found the website of the ones who made the build and noticed that the version that I have downloaded is 1.33 from Oct 31, 2015 and that their latest updates on the channel log is version 12. I will download and flash latest build and she if the issue is fixed.

I was referring to the card bot being recognized in CM, not on a stock ROM. Thanks.

Version latest stock rom

Does anyone have the latest retail version of the G5S rom stock?
Version latest is NPP26.102-49-1

this firmware will not come out, it will have to wait for the next one.

lohanbarth said:
this firmware will not come out, it will have to wait for the next one.
Click to expand...
Click to collapse
But mine version is on NPPS26.102-63-1
Will this version be released?
And if I try to flash .49 version will I get error?
Thanks a lot

I think I found one place where it's suposed to host the "MONTANA_NPP26.102-63_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" file, but it's a paid download site.
i'm not going to pay to download because money in Brazil is something very scarce especially for something charged in dollar :silly:
if you wanna try, here is: https://www.top-firmware.com/index.php?a=browse&b=file-info&id=26032
and if in any case you get this file, please share with us

bycabraljr said:
I think I found one place where it's suposed to host the "MONTANA_NPP26.102-63_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" file, but it's a paid download site.
i'm not going to pay to download because money in Brazil is something very scarce especially for something charged in dollar :silly:
if you wanna try, here is: https://www.top-firmware.com/index.php?a=browse&b=file-info&id=26032
and if in any case you get this file, please share with us
Click to expand...
Click to collapse
So my guess is, we can still flash .49 version rom even we're on higher version. (just simply not to flash gpt.bin, this cause error when your version is newer than .49)
And after installed .49 version, we will receive OTA update then we update it?
Not sure if this is the correct way to get back to stock rom and relock the bootloader...

michael50310 said:
So my guess is, we can still flash .49 version rom even we're on higher version. (just simply not to flash gpt.bin, this cause error when your version is newer than .49)
And after installed .49 version, we will receive OTA update then we update it?
Not sure if this is the correct way to get back to stock rom and relock the bootloader...
Click to expand...
Click to collapse
To relock the bootloader you'll need a firmware more recent than the previous one you installed. If you had the .49-1 installed, you'll may need to wait for one more recent firmware popout as this .49 will give errors while installing (the "oem lock begin" command only locks the bootloader if you install every single file from the firmware, which will fail because an lower version of the firmware was installed).
In short: you can get back to stock but can't relock bootloader unless you didn't installed the OTA .49-1 or have an more recent firmware available

bycabraljr said:
To relock the bootloader you'll need a firmware more recent than the previous one you installed. If you had the .49-1 installed, you'll may need to wait for one more recent firmware popout as this .49 will give errors while installing (the "oem lock begin" command only locks the bootloader if you install every single file from the firmware, which will fail because an lower version of the firmware was installed).
In short: you can get back to stock but can't relock bootloader unless you didn't installed the OTA .49-1 or have an more recent firmware available
Click to expand...
Click to collapse
Gotcha. So after reverted to .49 form higher version, will I be able to get OTA update to higher version? Tks a lot!

michael50310 said:
Gotcha. So after reverted to .49 form higher version, will I be able to get OTA update to higher version? Tks a lot!
Click to expand...
Click to collapse
Yes, you can update without worries. Just remember to maintain your system untouched before any update. If you root or install custom recovery, the update will fail and may get into a boot loop

bycabraljr said:
Yes, you can update without worries. Just remember to maintain your system untouched before any update. If you root or install custom recovery, the update will fail and may get into a boot loop
Click to expand...
Click to collapse
So I'm currently running NPPS26.102-63-1 , and my bootloader is unlocked. Am I still capable for OTA update? And if I decided to install custom recovery and rom, can I flash .49 version stock rom?

michael50310 said:
So I'm currently running NPPS26.102-63-1 , and my bootloader is unlocked. Am I still capable for OTA update? And if I decided to install custom recovery and rom, can I flash .49 version stock rom?
Click to expand...
Click to collapse
You can upgrade through OTA with unlocked bootloader, you only can't if you modify your system. But if you are running .63-1 I'm not certain about reinstalling the .49 ROM as they may be different, like different modem or other resources like NFC resulting in bricking. Test at your own risk. I'd like to test .63 ROM, but I can't find any free places to download it.
(Or if you want you can also try the ZUI ROM, it's a stock rom from a chinese moto g5s with ZUI interface)

bycabraljr said:
You can upgrade through OTA with unlocked bootloader, you only can't if you modify your system. But if you are running .63-1 I'm not certain about reinstalling the .49 ROM as they may be different, like different modem or other resources like NFC resulting in bricking. Test at your own risk. I'd like to test .63 ROM, but I can't find any free places to download it.
(Or if you want you can also try the ZUI ROM, it's a stock rom from a chinese moto g5s with ZUI interface)
Click to expand...
Click to collapse
So the reason is the latest firmware for locking bootloader
Untill now I have thought that the problem is with only my device can we ask for Motorola for the latest firmware releases so that we can relock our bootloader

Talwar sridhar said:
So the reason is the latest firmware for locking bootloader
Untill now I have thought that the problem is with only my device can we ask for Motorola for the latest firmware releases so that we can relock our bootloader
Click to expand...
Click to collapse
They used to have a site for you to download firmware, but it hasn't been updated like 3years... Even Moto support doesn't know where to get it..