Develop Bugs

[Important] Verizon Droid Pro stock update 4.7.3 - READ BEFORE PROCEED

You cant imagine, Moto just released 4.7.3 update for our DP.
Google around, you will get some image whats going on on new improvements
PLUS: Android version updated from 2.3.3 to 2.3.4
2.3.3 has been so notorious for its daxned battery drainage. And from my experience with Xperia SK17I, 2.3.4 has solved this problem, so it is so worthwhile for you to update.
[Very Important - ROOT]
You will loss root if you go directly for the update, no existing rooting method would work on 4.7.3 directly
Solution:
1. Before update, backup all your Apps and data
2. Install "OTA Root Keeper" from Market
3. Save Root information by OTA RootKeeper
4. Update by the below section's methods
5. Reboot, restore root information by RootKeeper
6. Restore backuped Apps/Data
7. DONE
[Update Method]
A. Go to Setting>About Phone>Check Update
or
B. Use update.zip of 4.7.3 to update through Recovery Mode
ht#tp://w#ww.badongo.c#om/file/26630469
(Remove Hash)
(I prefer this. My experience, higher success rate + you can see the commandlines running, you would know if it is halted or not)
**ENJOY

No update in my area
Since no 4.7.3 update is coming here in Japan, could you upload the updater?
It would be very appreciated.

Did not improve the signal GSM?

I got 4.6.8 but
I received the 4.6.8 update info from OTA, then I successfully updated.
But, I have not yet received 4.7.3. although I tried to access from setup menu.

ggb01010 said:
Since no 4.7.3 update is coming here in Japan, could you upload the updater?
It would be very appreciated.
Click to expand...
Click to collapse
Konichiwa!
Here you go
ht#tp://w#ww.badongo.c#om/file/26630469
(remove hashes)

die_dmitriy said:
Did not improve the signal GSM?
Click to expand...
Click to collapse
GSM signal, please refer other tutorials in this forum,
there are tweaks on system files to enhance signal.
To me, before tweak, both version = crap
After tweak, both versions rocks.

can this somehow be flashed to german xt610?
refering to cm7 and cm9 mod here there i assume is a american sbf used.

Thank you!

could not download from there
that's put on motofan
http://forum.motofan.ru/index.php?s=&showtopic=1730230&view=findpost&p=1661311

Received it today, but cannot install. Tried at least 5 times - OTA and from sdcard, at approx 30% there is an exclamation mark and finish.

Khachikyan said:
Received it today, but cannot install. Tried at least times - OTA and from sdcard, at approx 30% there is an exclamation mark and finish.
Click to expand...
Click to collapse
You must have modified/deleted Stockwares/bloatwares or have modified stock files in any kind.
Restore deleted apks if you know what you have done,
or Titanium Backup all apps/data, then reflash 4.6.8sbf to restore,
then upgrade and restore backup
This must work.

4.6.8 is not necessary to sew. the easiest way to install a sd card when there is an error to write because of what did not. You can pull the files are not proshivaya phone. How I solved the problem I described here http://forum.motofan.ru/index.php?s=&showtopic=1730230&view=findpost&p=1661375

sorry, delete

motostigr said:
4.6.8 is not necessary to sew. the easiest way to install a sd card when there is an error to write because of what did not. You can pull the files are not proshivaya phone. How I solved the problem I described here http://forum.motofan.ru/index.php?s=&showtopic=1730230&view=findpost&p=1661375
Click to expand...
Click to collapse
Ok... Can you explain in English....?

Ok.l
I also had problems installing the update. I put the update through sdcard. If you are upgrading an error and showed that the error due to build.prop I remembered my old manual http://forum.xda-developers.com/showpost.php?p=13146095&postcount=3.
I found the firmware 4.6.8, dismantled it and took from there build.prop, and put in place. After this update has been in place.
Sorry for my english.

motostigr said:
Ok.l
I also had problems installing the update. I put the update through sdcard. If you are upgrading an error and showed that the error due to build.prop I remembered my old manual http://forum.xda-developers.com/showpost.php?p=13146095&postcount=3.
I found the firmware 4.6.8, dismantled it and took from there build.prop, and put in place. After this update has been in place.
Sorry for my english.
Click to expand...
Click to collapse
Hi,
could you please upload correct build.prop here?
dyakuyu!

Khachikyan said:
Hi,
could you please upload correct build.prop here?
dyakuyu!
Click to expand...
Click to collapse
please
budlaska

didn't help I will try with SBF and inform.

can you flash this file using RSDlite or just rename to update.zip and flash in recovery?

cn2661 said:
You cant imagine, Moto just released 4.7.3 update for our DP.
Google around, you will get some image whats going on on new improvements
PLUS: Android version updated from 2.3.3 to 2.3.4
2.3.3 has been so notorious for its daxned battery drainage. And from my experience with Xperia SK17I, 2.3.4 has solved this problem, so it is so worthwhile for you to update.
[Very Important - ROOT]
You will loss root if you go directly for the update, no existing rooting method would work on 4.7.3 directly
Solution:
1. Before update, backup all your Apps and data
2. Install "OTA Root Keeper" from Market
3. Save Root information by OTA RootKeeper
4. Update by the below section's methods
5. Reboot, restore root information by RootKeeper
6. Restore backuped Apps/Data
7. DONE
[Update Method]
A. Go to Setting>About Phone>Check Update
or
B. Use update.zip of 4.7.3 to update through Recovery Mode
ht#tp://w#ww.badongo.c#om/file/26630469
(Remove Hash)
(I prefer this. My experience, higher success rate + you can see the commandlines running, you would know if it is halted or not)
**ENJOY
Click to expand...
Click to collapse
I am not able to Update using either A or B method... I Currently have Team black hat version of gingerbread 2.3.3 version... Anyone has a solution for this. When i use the update through recovery method it gives me the "error in /sdcard/update.zip status 7"

This does not look good for devs.....

I just read this article from Android Police....I copied and pasted this. The link is below..... PSA: New Lollipop OTA Procedure On Devices With Verified Boot Means Your Update Will Fail If Your System Is Modified In Any Way At All
Published on November 13th, 2014
Written by: Shawn De Cesari
Next
Skip to Responses
Prev
Ever since the beginning, Android OTA updates have worked by patching each file on your system partition individually. With Lollipop, that is all changing, and it has some important implications for those who like to root and mod their devices.
Here's what a pre-Lollipop update script looked like:
image
As shown, the recovery looks at this, finds each file, checks its signature, then applies a patch to it if it matches. This is the slow way of doing things, but it had a big benefit for rooters and those who like to mod their devices. As long as none of those files were touched, you could have anything you wanted on your system partition (the "su" binary for instance, maybe an INI file for a root app, etc.) and you could still apply OTA updates successfully.
With Lollipop, this has all been turned on its head because now, the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Here's a look at the update script in a recent Nexus 9 OTA:
image
From a technical standpoint, the reason behind the change was the addition of verified boot functionality in Lollipop. Though verified boot was introduced in KitKat, it appears that Google has only started using it with the Nexus 9 and (presumably) Nexus 6.
As for whether or not older devices like the Nexus 5 or 7 (that were updated to Lollipop from older versions) will have this same issue, that remains to be seen. We'll have to see what happens when those devices get their first Lollipop -> Lollipop OTA update.
Even outside of verified boot, though, it makes all the sense in the world to do OTAs this way. Patching the system block directly is far faster than trying to patch a lot of individual files. That said, if you're one of those who like to tinker with your devices, you'll have to flash a completely stock system image before applying an update because changing anything by so much as one byte will throw off the signature and make it so the OTA will fail.
Android Source Documentation
Original Article here:http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/

So, I just went through hell trying to go back to stock for the 4.4.4 update. after about 4 hours of complete brain screwing I finally managed to do it, and don't know how I did it, through different flashable ZIPs, nandroid backups, FUUs, RUUs, etc...
My question is, "Would it be better for me to leave my phone on the stock image until the Android L update or go ahead and root it again and wait & look for a rooted version of the Android L to appear on XDA after it comes out?"

[Q] Prepare for transition: 10L -> 20E & back.

Hi,
I have 855 (generic European version), V10L, rooted (using towel rooter), no TWRP, all OTA (since July 2014) installed automatically and seamlessly so far (keeping the root).
Today I got a prompt about V20E available upgrade.
I have LG PC Suite up-to-date backups of this device, and anyhow don't have anything that can't be restored, but in general prefer to not reconfigure everything manually.
Did nothing so far.
Questions:
Is it worth to move to V20E, is the version stable enough, worth to wait for V20F or whatever comes next ?
If I decide to proceed now, I want to be able to return to my current state (I do not need to fast switch between multiple roms, just way to get back V10L with my current configuration).
I prefer the way that allows me to keep receiving OTAs, and not to flush next updates manually.
After looking on the forums I though about the following workflows
First (without TWRP):
1. Create one more backup using LG PC Suite.
2. Unroot (just to be safe).
3. Accept OTA.
If I understand correctly I will loose root here, and it can not be restored (for now).
In case of need to restore:
1. Follow LG G3 Stock Firmware (Go Back to Stock) to flash D855 V10A. I hope after flushing it will receive 10L OTA ? Am I right, or I will be stuck with 10A ?
2. Restore my existing backup using LG PC Suite. If I do restore on V10A, will it bring me back to 10L ?
3. Reroot if needed.
Second, with TWRP:
1. Install TWRP.
2. Create full backup from inside TWRP.
3. Get prebumped Lollypop image (I see only V20C here. Where can I get more recent versions ?)
4. Install it and reroot if needed.
In this case I must reject upcoming OTA prompts and flash future prebumped images manually.
To restore
1. Restore full TWRP backup, and I'll get V10L with all my stuff preconfigured.
2. If at this step I want to get rid off TWRP, can I remove it somehow ? Will it restore the phone to the current state (rooted, V10L, able to get OTAs) ?
Sorry for multiple questions but currently the whole process looks a bit unclear for me.

Q: Is it worth to move to V20E, is the version stable enough, worth to wait for V20F or whatever comes next ?
A: No V20H got released today and its probably gonna be available in your region really soon
Note: If you do ever want to install stock lollipop please be aware LG backup cannot save the appdata of any system applications such as chrome etc etc
Q: Follow LG G3 Stock Firmware (Go Back to Stock) to flash D855 V10A. I hope after flushing it will receive 10L OTA ? Am I right, or I will be stuck with 10A ?
A: Check (http://lg-phone-firmware.com/index.php?id_mod=41) and download the v10 firmware the corrosponds with your country. If the firmware has a 6 in front of it its for the 16GB variant
Q: Where can I get more recent versions?
A: http://forum.xda-developers.com/lg-g3/development/stock-t2961073
Q: If at this step I want to get rid off TWRP, can I remove it somehow ? Will it restore the phone to the current state (rooted, V10L, able to get OTAs) ?
A: Yes, by flashing stock recovery.img. Restoring your TWRP backup will restore the phone to the current state

itsbighead said:
A: Yes, by flashing stock recovery.img. Restoring your TWRP backup will restore the phone to the current state
Click to expand...
Click to collapse
Thanks, but I am not sure about this one. What is the process ?
If I flash stock kdz it will remove TWRP, but I will not be able to restore TWRP backup (without TWRP), right ?
Is it possible to first restore TWRP backup, then flash "something" that will replace only TWRP, leaving android OS intact ?

Before saying anything, I would just like to give you a thank you for your post, it's very clear and pleasant to read. Looks like you also did a bit of research before asking so that is also very good :good:
So, I'm not gonna be able to help you a lot about the backup thing because I like to always start fresh when I change Rom or if I want to go back to stock. I backup my data manually and restore what I want to. Using a Google account it will automatically reinstall your apps, but you'll have to reconfigure them manually.
Anyway, I also got a D855, French variant A6FR. (A6 means 16GB) You can check what is the latest version that LG offers you by checking the link bellow. You just put your IMEI at the end and it will give you an XML with information about your phone, like your specific variant (German, UK, ... don't know where you are from) and the latest firmware available for your and a link to download it. For me it says D85520F_00 so it's LL version F.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI
So, you can go back to stock using the KDZ method and with the firmware LG offers you (removing root, revovery, ...), but as you probably now, LL is not rootable. To summarize, that is not really interesting unless you want a STOCK STOCK LL.
But you guessed right with the V10A. If you go back to stock with this version, it will remove the root, custom recovery and anything else you have, you will also end up with a completely stock G3, but KitKat G3. There is no obligation to use V10A, if you find a KDZ of a later version you can use it too. Of course we are talking here about V10something not V20 that is LL. Just make sure to use a version suitable to your phone (16/32GB).
Flashing that, LG will be happy and will let you do OTAs. So if you flash V10A, it will give you all the OTAs untill the latest available. So you can go V10A --> V10B --> V10C --> ...... --> V10L --> ..... --> Lollipop
You won't be stuck with V10A.
Now if you want a rooted LL, you will need to use a custom Rom. In the Dev section you can find for example GloudyG3 that is based on the stock LG rom with a few enhancements. It is currently based on V20F and will probably move to V20H which is a brand new version that went up like 2 days ago.
To summarize
KDZ with V10something allows you to go completely stock and give you official OTAs. It can be rooted.
KDZ with V20something works too and will give you OTAs, but is not rootable, so if you want a custom rom, you will have to downgrade to V10, root and install TWRP.
Flashing a KDZ always erase everything on your phone.
If you flash a custom rom, you won't have LG's OTAs so you won't have to worry about rejecting them.
Before doing anything crazy, backup your EFS (basically your IMEI partion) with TWRP and manually. Always nice to have several ways to do it.

UPDATE.......full OTA .... does not work with TWRP

Hello,
my Pixel XL came from T-Mobile Germany.
I am in TWRP alpha2 and SR4-SuperSU-v2.78-SR4.
My Pixel XL is on NDE63H.
I logged the OTA download process used the link in there and got now the 68MB small OTA.zip.
Can I use TWRP and this small update OTA to update to NDE63U,
or do I need to use the large 850MB OTA file from the google develope site to do so -> marlin-ota-nde63u-56d5b07a.zip?
I think I will loose root by using the large one, but will I loose TWRP as well?
My preference would be to use the small one, but will it work via TWRP and will I loose root as well or will this only update the necessary files?
Any help is highly appreciated.
mancman

I haven't tried it on the pixel, but on my previous Nexus device (N6), the small OTA would fail if the devices was rooted or had any changes to the system partition - that's because the small OTA was an incremental update, and was checking to see if the system partition was modified in any way before applying the OTA.
The full OTA would work - but you would lose the root/TWRP. Reinstalling TWRP is just a fastboot command away, so why is that a big deal?

Hello jj14,
I tried it.
First within TWRP and then by sideload and both failed with the same error.
I first needed to get a newer version of adb, but it failed as said above as well via sideload.
See error message here in the attached picture.
Any hint?

As far as that error, it means the binary update files are missing. That could be because the structure of OTA's changed. Without seeing the OTA I cannot say for sure. I would post that screenshot in the twrp thread and ask @Dees_Troy what he thinks.

Hello Scott,
thanks for your answer.
I wrote Dess a message.
Attached 2 screenshots which show what is in the zip from the OTA file and one for the comparison to a Nexus 10 zip,
you see that the update-binary is missing, so Goggle has changed things here as you postulated.
Thanks,
mancman

I assume you are trying to sideload the full OTA file. If so, what error did you get using the ADB sideload? (yes, you will need the newest version of ADB - download from the Google developers site). TWRP is still very new, so there may still be some bugs to address - Dees is pretty good about quick updates/fixes though.

I may be wrong here but shouldn't you flash back stock recovery before applying stock ota ??

Flash stock software update through TWRP?

First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.

ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.

sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.

ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.

This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs