Database Info

[Q] OTA update

Hi guys.
So AT&T released a software update to my d850, and it prompts to update each time I restart device, where I have to force stop/hibernate software updater.
I'm rooted on stock KK 4.4.2 and I'm comfortable with battery life, functionality, and the overall performance of g3. So I'm hesitant about the Lollipop upgrade, as I've never really bothered flashing any ROMs since I was satisfied with my g3 experience.
So can anyone give some pros/cons they've noticed with the stock Lolipop ? Is it worth the switch?
I have a general idea of what I would need to do to update. Unroot, restore the bloatware I have removed using LGs PC suite, update and root again. Or is there a flashable zip of the update that i can just download? I hit update during first prompt and I was stuck rebooting into TWRP so i had to flash an image recovery file to get back.

Best bet is to go read on the lounge and threads related to see all different all experiences

I agree that the lounge is probably the best place for answers to determine if you feel it is worth the effort. My personal experience was that lollipop didn't bring much new. Most was minor cosmetic stuff and I feel like performance is ever so slightly smoother but this could be a placebo. If you use xposed then sticking with KK for now is the way to go. The line can explain this more. If you choose to stay on KK for now, use TiBu to freeze and clear data of the software update to prevent the phone from nagging about the update. I updated out of curiosity mostly and since the use of xposed is not a big deal for me, I stock with L.

Shaxxi said:
Hi guys.
So AT&T released a software update to my d850, and it prompts to update each time I restart device, where I have to force stop/hibernate software updater.
I'm rooted on stock KK 4.4.2 and I'm comfortable with battery life, functionality, and the overall performance of g3. So I'm hesitant about the Lollipop upgrade, as I've never really bothered flashing any ROMs since I was satisfied with my g3 experience.
So can anyone give some pros/cons they've noticed with the stock Lolipop ? Is it worth the switch?
I have a general idea of what I would need to do to update. Unroot, restore the bloatware I have removed using LGs PC suite, update and root again. Or is there a flashable zip of the update that i can just download? I hit update during first prompt and I was stuck rebooting into TWRP so i had to flash an image recovery file to get back.
Click to expand...
Click to collapse
And there are stock roms in the forums, just flash a stock (lp) ROM done. If you don't like flash back to a backup of kk
Sent from my LG-D850 using XDA Free mobile app

Why I don't receive update to lolipop on my D850?
If connect to pc says ...no update availible,have stock 4.4.2 and same message if try to OTA.
My phone is AT&T factory unlocked and live in Europe(Romania).
What can I do?
Thanks

adilau said:
Why I don't receive update to lolipop on my D850?
If connect to pc says ...no update availible,have stock 4.4.2 and same message if try to OTA.
My phone is AT&T factory unlocked and live in Europe(Romania).
What can I do?
Thanks
Click to expand...
Click to collapse
you have to be on the at&t network to receive updates from them

Another way without root?
Trimis de pe G3

I just bought my phone and Im on Tmobile, do you know how do I upgrade to lollipop?
Sent from my LG-D850 using XDA Free mobile app

default boot set to bootloader not system

i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.

You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.

Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?

snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.

this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.

snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2

Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)

Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.

Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse

Bricked after update to MM

Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.

Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Experienced all. Tsk. Should have stayed away from the Marshmallow upgrade thread.

Khasim83 said:
Hi,
I did something stupid - I wanted to update my phone by creating a dload folder on internal memory and updating to EMUI 4.0 beta that's floating around on the internet (I got it from carbontesla). I knew it required a B326 version, I had B324 and still went through with it, because I mistakenly thought that B326 is only required for L10 (I have L09). Now the phone is stuck in bootloop.
I have tried the following:
1. Forced update - it was apparently successful, but still the phone kept resetting
2. I reset to factory settings and wiped cache - still keeps resetting
3. I tried to force update again, this time I get an 'update failed' info and asks me to reboot. Still the same.
4. Tried to reset to factory settings and wipe cache again - still no luck.
I can't even turn the phone off, so for now I keep it in recovery mode.
Any idea what can I do? Am I screwed for good?
I searched around on XDA and other forums but couldn't find anything - if anyone can help me, I will be very grateful. I just bought this phone 3 months ago and I can't afford a new one at the moment.
Click to expand...
Click to collapse
Uh-oh... Another Mate 7 phone bricked by the Marshmallow beta B511 update...
I guess you'll just have to wait for the full official marshmallow update (no longer beta) for your TL09 phone for your region, or at least, wait for the official TL09 marshmallow to lollipop downgrade package for your region. When Huawei releases one or both, then you can install one or both via forced update (power + volume up + volume down) and have a functioning phone again.
For now, there's nothing you can do but wait and wait... unless you know your way around rooting, unlocking bootloaders and custom ROMs. There are actually quite a lot of Mate 7 owners in the similar situation as you. If only you can BAND together with a common cause/objective, your 'bricked by Marshmallow B511' group could somehow be a FORCE to reckon with that Huawei cannot ignore. Your group can petition Huawei with emails to release at least the 'marshmallow to lollipop downgrade package' for other non-China regions NOW, or the EARLIEST humanly possible...
You may want to read other users similar experiences with their bricked mate 7 phone (by installing the beta marshmallow b511 update) here: http://forum.xda-developers.com/mat...-marshmallow-b511-t3304178/page2#post65176950
It will make you feel much better knowing you are not alone. Alternately, you can just vent out your frustrations to Huawei in another thread. Not sure if its allowed in XDA though.

Those with bricked mate 7 phones:
Can you try and see if this suggestion works?
=========== (quoted from http://www.carbontesla.com/2016/01/download-ascend-mate-7-b511-marshmallow-ota-zip/) by wissam marrash
wissam marrash • a day ago
Guys I have mt7-l09 and its working with marshmallow, yes it drains more battery and some lagging in some areas but this should happen because its a beta and incremental release. For people who got spoil their phone while installing, you should read the requirements very well before downloading this rom. Its clearly mentioned for B326 and for un-rooted phones. so before you install you should install the B326 (you can download using this link: http://m.huawei.com/pkmobile/c... make sure to choose mt7-l09 or mt7-l10 and after installing the B326 install marshmallow beta.
For people who wants to downgrade, yes you can but you have to choose a full release like the B326-B327-B328.
N.B. ONLY Marshmallow BETA rom, Don't unzip the after downloading, its not like the other updates. You should copy the zipped file as is to inside "dload" folder.
Just a tip, some releases are not supporting 4G lte especially when it marked Europe.
For people who keep rebooting, try to connect you phone to pc or take out the memory card and use card reader and access your files and then delete the files from the "dload" folder and then download using your pc any full release rom (b326 or b327 or b328) and extract it and then copy the "UPDATE" file to the dload folder and then turn off the phone and then boot your phone while holding Vol up + Vol down + Power buttons at same time to automatically trigger the update installation and should go smooth.
Hope my comments will help
==============
Here are the links to full ROMs:
TL10: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62450&key4=MATE7
L09: B326 full ROM:
http://consumer.huawei.com/pk/support/downloads/detail/index.htm?id=62371&key4=MATE7

reboot
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.

maksudbek said:
Hi Don
We tried to follow Wassim's nstructions unfortunately it didn't work. As you said there are so many mate 7 users' faced this problem.
Any way thanks a lot for your attention.
Click to expand...
Click to collapse
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!

"Debranding" without root/TWRP, preferably from fastboot.

I am trying to figure out how I can get my oeminfo partition flashed to report my AL10 device as an AL29 device, so I can successfully flash OTA updates for the AL29 going forward. However, fastboot does not allow flashing of oeminfo.
Also, what is the command or method for finding out what model the device is? I only know mine is likely still showing AL10 because the update.app files for AL29 always fail in recovery. I have to extract them and flash individually.
The reason I want to get this switched is I believe in manually flashing the .img files for boot, cust, modem, recovery, and system, I am missing something important that needs updating and hence could be causing my battery issues and/or lower antutu marks (I get around 80k on international firmware vs 92k on chinese firmware).

which international firmware are u sporting?
i actually had my highest antutu score with an international firmware on my AL10 at 97200. even now with my current B162 international im getting around 94-96k. as for battery life, im getting 10-12h sot so nothing to complain about there either. how did u flash the current firmware? maybe u have some borked settings or flash procedure...?
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

B160.
But, I decided to try the new TWRP, which actually worked to format my data, etc. So I went that route. Though I still have no idea if I am "debranded". Since the wipe I am back up to 90k in antutu. So obviously something was broken.
I just figured out it is nova launcher that lowers the antutu score.

Flashed every ROM available for Honor 6x BLN-L24

Only came up successful with LOS 13 but it doesn't have bluetooth support, drops LTE and calls. I can't access hidden menu to revert to stock. Any help will be met with great appreciation.

you can flash the Elite ROM from rom section.

ghostair said:
Only came up successful with LOS 13 but it doesn't have bluetooth support, drops LTE and calls. I can't access hidden menu to revert to stock. Any help will be met with great appreciation.
Click to expand...
Click to collapse
Do you want to revert to stock or not? Here you say yes, other thread you say no. Since you never answered the question I will once again assume that you never created a backup, otherwise you would already be back to stock.
-Download firmware B110 and unzip.
-Create a folder on external sdcard called dload
-Move update.app to dload
-Turn phone off
-Hold vol - / vol + / Power to force flash/update
This will lock your bootloader so you will need to unlock it and flash TWRP/root again. But before that make sure to OTA update to Android 7.0/EMUI 5.0 first. Then the very first thing you should do once you flash TWRP is make a complete backup so you never have to be in this situation again.
If you want to mess around and flash ROMs all the time make sure you always have a current backup on hand. If I like my setup I will make a backup once every week or so, and right before flashing a ROM so I can get right back to where I was in the event something screws up or I just dont like the ROM, which has been my experience with every single one so far.