Database Info

[Q] [SOLVED] 220.27.1 OTA install problems

Hi everyone,
I received the OTA update notification a long time ago but didn't have time to take a deep look into it (baby on the way... now arrived !), but I'm trying to install a lollipop ota update on my moto g.
It's not my first android device, I had about 10 of them and messed around with them, so don't be affraid to use the vernacular directly, but I'm aware that I might be making a rookie mistake too
My phone is a 1st gen 16Gb Moto G. IT's running 4.4.4 (System version 210.12.40.falcon_umts.Retail.en.FR, I'm in France by the way). I did a few things to it :
- unlock bootloader
- install CWM
- root
- install xposed
- install cerberus and moved it to system apps
Before trying to install it I tried to reverse the steps back to stock :
- move cerberus back to user apps, and uninstall it just in case
- remove xposed
- unroot using the option in the SuperSU menu
- go back to kitkat stock revovery, using mototool v2.6 (so this might a 4.4.2 but I didn't find another one so far)
Then I clicked on the OTA notification, anouncing that 220.27.1... was ready to be installed, downloaded it ok, chose to install it.
Everytime I tried the phone rebooted, began the install and after a short while showed a error message and rebooted.
I tried to install it by putting the OTA zip file in /sdcard and install it with the stock recovery, but here's what I found out :
After downloading the OTA on the phone if I go to /cache/ (where the ota zip file is downloaded. To do that I need root access so I got to flash cwm and root it again, fyi) it shows another file, not corresponding to 220.27 but named : Blur_Version.210.12.40.falcon_umts.Retail.en.FR.zip .... which is weird because it's the version that's supposed to be installed already !
I tried something else, found the "Blur_Version.220.27.1.falcon_umts.Retail.en.FR.zip" file on a forum, put it on /sdcard/ and try to install it through recovery... same error.
Does anyone have an idea on how to install it succesfully without having to flash back a stock firmware ?
Thanks a lot to anyone giving a shot, you rock !
Mat
Ps : i tried to find anything similar on the forum but didn't manage to. If i searched with the wrong terms or didn't notice it while browsing trough the different topics, please tell me if you have a clue, and sorry about not having searched well enough.

Found solace here :http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072
Worked perfectly
Sorry for not having searched enough !

Sensors problem, dlpkgfile update doesn't work, TWRP critical error, help me!

Hi, I bought a lg g2 D800 32gb on ebay about a year ago. I have some problem and no possible warranty.
One day, without, any physical damage, all the sensor (accelerate, gyro, brightness/proximity, etc... except camera and microphone) stopped working. Because I have no warranty, that everything stopped working at the same time for no reason, there is a chance is a software/firmware problem. Factory reset didn't worked
When I bought the phone, it was on android 4.x.x, so I root it and did a fota update according to this tutorial to update to 5.0.2 (d80030f).
Now I'm looking for a way to clean install the update d80030G, but doing it by really erasing everything thing possible, the cleanest installation possible. Maybe it's not possible to do it directly, I could clean install is to d80020(something) and then update to 30F and then 30G.
I was trying to install TWRP, I did it via an app (TWRP Manager) (my phone is rooted of course) and when I try to boot on it, it showing a critical error. I try to install it manually, I had some permission issue, but still critical error at the end.
I tried doing an dlpkgfile update to 30G, but when launching the update via adb, the phone go black for 1 or 2 seconds, and then comeback untouched. I tried reinstalling 30F, same problem.
I dont have a at&t sim card nor access to one, so no update via the legit way.
Basicly, I'm running out of idea and nothing is working. I just want the cleanest update to any version, i can always update it later via with dlpkgfile files
I need you!

must read this thread before to do anything else with your phone
http://forum.xda-developers.com/lg-g2/general/warning-to-people-bought-phones-ebay-t2991195

[SOLVED] OTA updates and root : need help

Hello xda.
A few weeks ago I started getting this notification telling me a new system update was available but when I tried to do it, it wouldn't install. I quickly discovered it was because my device was rooted. I followed this guide to get the update (more to get rid of the annoying notification really) ; I made sure do download the right stock image (my device is a XT1541 2 GB) and to flash all the system.img_sparsechunk files (there are 8 in this case) and it went smoothly (booted alright) up until the rooting part.
Basically, I followed RootJunky's video tutorial but after applying the root I can't get past the bootloader's warning screen. The only difference between me and RJ is both TWRP and SU I used are more recent versions (the latest ones).
In the end I just restored the backup I had made "just in case" before the manual update (boy am I glad I made this one) and my phone's back to working order, except not updated.
So here I am : what can I do about it? Is it still possible to root this phone (youtube commentaries indicate I'm not the only one with this issue)? Worst case scenario, is there a way to get rid of the update notification?
Any help is appreciated.

You'll need a systemless root.
Broadcasted from Zeta Reticuli

How to root ANY Moto G 2015 model on Marshmallow

Thank you both for your answer.
Turns out the method linked didn't work for me. Not only was the root not applied according the supersu app, but I still got an update notification after 'rooting' the phone (even though I checked for update after booting the newly installed rom for the first time and there wasn't any).
I decided to go a different route and used Titanium Backup to freeze the Motorola Update app. Hopefully this will do the trick of sparing me the notifications until I can figure out how to get OTA updates.

Isley_FR said:
Thank you both for your answer.
Turns out the method linked didn't work for me. Not only was the root not applied according the supersu app, but I still got an update notification after 'rooting' the phone (even though I checked for update after booting the newly installed rom for the first time and there wasn't any).
I decided to go a different route and used Titanium Backup to freeze the Motorola Update app. Hopefully this will do the trick of sparing me the notifications until I can figure out how to get OTA updates.
Click to expand...
Click to collapse
No offense, but if you didn't have root then TiBu wouldn't work properly... Obviously the rooting worked.
Rooting itself doesn't prevent updates or there notification, it just keeps it from being applied properly. Freezing the app in TiBu should prevent it though.

acejavelin said:
No offense, but if you didn't have root then TiBu wouldn't work properly...
Click to expand...
Click to collapse
I forgot to mention I restored my functional backup when I saw my manipulations didn't work. I used TB after that.

Isley_FR said:
I forgot to mention I restored my functional backup when I saw my manipulations didn't work. I used TB after that.
Click to expand...
Click to collapse
Fair enough..

Quick update : after a couple more tries I successfully rooted my phone by following this method.
I now have the latest stock rom and it's rooted
Thank you for existing XDA! :good:

Odd issue with Nougat updates on two BLN-24s

I picked up two Honor 6X BLN-24 models, the serial numbers are within a couple hundred of each other, so I'm assuming they're from the same batch. Right now they're both on Nougat, but one looks like it has a partial install of Nougat and the other has a "normal" install. Here's what happened:
1) The partial install phone - I unboxed it, connected it to WiFi, did a check for updates; it found the Nougat update, so I let the system update itself, rebooted, had Nougat B360. Flashed TWRP, which is working fine on the phone.
2) The "normal" install phone - instead of updating straight to Nougat, I installed TWRP first and had a bunch of issues with the wrong TWRP .img file; that's a separate issue. Got Nougat installed eventually on the phone but ended up with the "Test Keys" build issue. Ended up doing the rollback to MM, then did the check for updates, it found the Nougat update and I let it install. Phone has Nougat, build shows as B360.
Thought everything was fine and didn't really take a good look at the phones since I had to do other stuff to do before migrating to the Honors.. Now I'm ready and I'm noticing that one phone - the one that went to Nougat straight out of the box - doesn't have a bunch of apps that the second phone has, like the FM radio, CNN, Lyft, News Republic. Outside of the FM radio, I don't care about the other apps, but something else is missing - the System Update option in Settings. There may be other stuff missing, but the System Update thing is problematic.
So I figure my options are:
1) Rollback the phone that's missing things to MM, then retry the update, or
2) Try a dirty flash of the Nougat B360 update and data files.
3) Flash the smaller update_data file for the B360 build that contains most of the apps (but doesn't look like it has the FM radio)
Or is there another option?

Go with option 2. If no success then I would suggest for option 1.
Need couple of favours as you did rollback. Do you have the rollback package file? If yes, please share.
If you are rooted, use Huawei mutli tool and backup the oeminfo file. I need both these files so that if anyone messed up with their phone we will be able to revive and also address the nrd test keys issue and the best we can do is to debrand from other variant to US variant.
Thanks beforehand.

I had similar issues my phone was showing as nrd test keys and the backup of twrp also indentify phone as nrd test keys. When I checked updated update it was showing no update. My phone wassoft bricks so i download and updated package for build no b 340 and in build no it was showing nrd test key
Later i flashed zip shared in volte fix thread on xda as I was not having volte.
After flashing all thing went good test key issues resolved also so u can try that zip also.

Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205

You can use it if it matches with your last build no

WetWilly said:
Thanks for the replies, I'm away from the phones for a few days but will report back.
For shashank1320, the intermediate rollback package (the one that's flashed first from Nougat before the actual MM ROM) is still available on the US Honor site at http://www.hihonor.com/us/support/details/?DOC_ID=94205
Click to expand...
Click to collapse
Thanks downloading now. Yes then you can use this file for rollback.

Here's the latest update. - I tried the dirty flash method and it wouldn't work. AT ALL. I'm getting the "software failed update" at 5% message that several others have received. I downloaded the BLN-24C567B360 FullOTA package from three different sources; all had the same hash and *none* of them would work using the dload method. I ended up flashing the MM rollback package (which worked perfectly via the dload method) then flashed the MM firmware (also worked perfectly using the dload method). The phone booted into MM, it found the 2.35GB Nougat update (which is the same size of the Nougat .zips I downloaded), and it installed the update. It also installed the FM Radio (a system app) and the US package of apps that for some reason it didn't install when it upgraded to Nougat fresh out of the box.
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash. Thankfully the rollback worked. FYI, rolling back to MM relocks the bootloader. At this point I'm just keeping both the rollback and MM packages saved together on an SD card; flash rollback, pop card, rename folders on PC, pop card back in 6X, flash MM, reboot, find update, OTA to Nougat. Easier done than said, actually.
I am curious about why none of the B360 Nougat update.app files will flash on either phone. I don't think it's coincidental because the e-Recovery via WiFi doesn't find a package, and if I try System Recovery in HiSuite it says "no recovery available; take device to a Service Center".

WetWilly said:
I actually did this rollback/roll-forward twice since something odd happened while playing with SafetyNet with Magisk and the FRP Lock tripped. The next thing I know I'm getting the "data partition is corrupted" message and, again the B360 update.app files wouldn't flash.
Click to expand...
Click to collapse
If you get this issue again, try to format data inside TWRP.

itisiryan said:
If you get this issue again, try to format data inside TWRP.
Click to expand...
Click to collapse
I actually tried that. I ran into this same issue previously when I had TWRP installed, and TWRP's wipe data didn't work. Ultimately had to do the rollback to MM/roll-forward to Nougat and re-unlock the bootloader.
I can't figure out why my two phones won't flash Nougat using the dload method. The only logical reason is the upload.app file signatures, but I haven't found any alternative Nougat files for BLN-24C567B660.

How to install stock firmware? - FRD-L09

Before asking the question, let's give to it a little bit of story:
Basically, i have tried multiple times to pass that damn safetynet, to be able to use some apps like snapchat or banking apps...
i have uninstalled magisk, magisk manager, xposed and busybox. no luck.
So i visited some threads with the same problem, to wich has been suggested to completely reinstall the stock firmware.
As soon as i have read that answer, i immediately downloaded 3 packages needed to install it, called:
update_full_FRD-L09_hw_eu.zip
update_data_full_public.zip
update.zip
Every tutorial lists only two of these packages, the update.zip and the hw one, so i moved them to the sd card, wiped everything but the sdcard and tried flashing them in order, hw first and update in the end.
no luck. the flashing gave me error 7, and couldn't install anything.
I had the backup, so i restored it and didn't have to pass terrible days finding for another solution.
so, basically, from an already stock MIUI 5.0 rom, how do i install the stock firmware for my model?
-Omega

pls answer

guys i really need to make it work, not only because I need it, but because the information on the web is wrong