Database Users

Stuck at 4.2.2, bootloop on higher versions

Whenever I try to update 4.2.2 to a newer version via about -> phone, I get bootloop at Google logo. I've already tried to follow "official" guide for rooting but flashing any ROM in CWM newer than 4.2.2 resulted in the same error. I've been desperately looking for solutions for a while and finally came across this blog http://fixandoridproblems.blogspot.co.il/ . I actually managed to get working 4.3 with those steps, but again, as soon as I update it, I get bootloop.
In addition I got weird error while flashing ParanoidAdroid + GAppps, so that obviously didn't help as well. Of course I always wipe data, cache and dalvik cache before flashing anything whatsoever:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I really don't know what else to do, so some help would be greatly appreciated. Thanks in advance.

this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

hp420 said:
this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Flash the factory image from developers.google.com for Nexus4 4.4 then reflash the latest versions of custom recovery and SuperSU

I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.

krneki10 said:
I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.
Click to expand...
Click to collapse
Dude, we've told you repeatedly....FLASH A FACTORY IMAGE WITH FASTBOOT! STOP USING RECOVERY, BECAUSE THAT IS YOUR PROBLEM!!
Read the guide on how to flash with fastboot.

Jd is right, there are devices out there that after a certain amount of time will refuse to boot any OS above 4.2.2, regardless of how the OS is flashed to the device. No idea why this happens, and the only solution is to get another device.
Sent from my Nexus 4 using XDA Free mobile app

I have the exact same problem on my nexus 4, have you found a fix?

I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
Take a look: http://forum.xda-developers.com/nexus-4/help/help-please-bootloop-4-4-4-imei-t2882868
I'm tired of trying different solutions whit the same result, its exhausting

conquesoextra said:
I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
I'm tired of trying different solutions whit the same result, its exhausting
Click to expand...
Click to collapse
I think this has happened to a few people recently. It happened to me too. For now I have ogt 4.2.2 running, I managed to fix the baseband and IMEI but if i update to a new version it gets broken again.
This is what I did to fix IMEI, hope it works for you
http://forum.xda-developers.com/nexus-4/help/fix-nexus-4-bad-imei-t2882694

ROOT with Security updates ( TESTED )

So for someone who plans to root , but stay on stock rom ( possibility decrypt) how would this work ? Is there a way to not lose data every month ?
EDIT- Tested on my 6P. check post 8 in this thread
Sent from my Nexus 6P using Tapatalk

I'm wary of rooting for this exact reason.

I unlocked my bootloader but am wary of doing anything more, but i really do want to root and get twrp installed.

I'm new to the N6p but if like other platforms you should be able to dirty flash the full rom without wiping any of your data. I would think google would be the best at posting those roms after the update.

I will be more comfortable rooting after the guru developers get hold of Google source code they're waiting on and get things working with encryption. May be a few weeks.....

I'm not rooting for a while with this beast. With tethering available for UDP on VZW working out of the box....that's my biggest root factor. Sure I'd love to get nandroid backups and try new roms, but that's more for my enjoyment than necessity. I am missing titanium right now, but I'll wait for more Devs to really delve into this thing and then make a decision. I've never bought a phone at launch (except for the S4) until I knew root was attainable (and the S4 had been loki'd before release).

318sugarhill said:
I'm not rooting for a while with this beast. With tethering available for UDP on VZW working out of the box....that's my biggest root factor. Sure I'd love to get nandroid backups and try new roms, but that's more for my enjoyment than necessity. I am missing titanium right now, but I'll wait for more Devs to really delve into this thing and then make a decision. I've never bought a phone at launch (except for the S4) until I knew root was attainable (and the S4 had been loki'd before release).
Click to expand...
Click to collapse
I wonder if its possible to just flash the system part of the update , then reroot and be good to go

Ok so took a shot due to lack of response here;
Before flash - Rooted , stock ROM , chainfire boot.img
- I did a nandroid ( incase tits were pointed in the upward direction i.e tits up )
- Downloaded the latest image from Google, extracted
- then i just extracted the system.img and vendor.img
- fastboot flash system system.img
- fastboot flash vendor vendor.img ( without this you get some " something went wrong in your system, contact etc error on boot )
- Boot android ( Android is upgrading for 3-4 mins )
- Re-root in TWRP
- see for yourself
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure if this will work every time, if the boot.img changes significant'y between an update i would assume it won't ( in which case you will need a new root boot.img from a dev ) , so just be aware of that for future releases.

Is it just the factory image?

I am still curious about this
http://www.androidpolice.com/2015/1...d-root-without-touching-the-system-partition/
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2

Might just give this a try. Thanks!
italia0101 said:
Ok so took a shot due to lack of response here;
Before flash - Rooted , stock ROM , chainfire boot.img
- I did a nandroid ( incase tits were pointed in the upward direction i.e tits up )
- Downloaded the latest image from Google, extracted
- then i just extracted the system.img and vendor.img
- fastboot flash system system.img
- fastboot flash vendor vendor.img ( without this you get some " something went wrong in your system, contact etc error on boot )
- Boot android ( Android is upgrading for 3-4 mins )
- Re-root in TWRP
- see for yourself
Not sure if this will work every time, if the boot.img changes significant'y between an update i would assume it won't ( in which case you will need a new root boot.img from a dev ) , so just be aware of that for future releases.
Click to expand...
Click to collapse

dwertz said:
I am still curious about this
http://www.androidpolice.com/2015/1...d-root-without-touching-the-system-partition/
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
Click to expand...
Click to collapse
Working just fine for me and Android pay is working.

cammykool said:
Working just fine for me and Android pay is working.
Click to expand...
Click to collapse
Are you on the mdb08m image?

Thanks!
Thank you so much. I just tried this and can confirm that it works. I created an account on here just to reply to this. I was searching everywhere for an answer to this yesterday. This was the only solution I found.
italia0101 said:
Ok so took a shot due to lack of response here;
Before flash - Rooted , stock ROM , chainfire boot.img
- I did a nandroid ( incase tits were pointed in the upward direction i.e tits up )
- Downloaded the latest image from Google, extracted
- then i just extracted the system.img and vendor.img
- fastboot flash system system.img
- fastboot flash vendor vendor.img ( without this you get some " something went wrong in your system, contact etc error on boot )
- Boot android ( Android is upgrading for 3-4 mins )
- Re-root in TWRP
- see for yourself
Not sure if this will work every time, if the boot.img changes significant'y between an update i would assume it won't ( in which case you will need a new root boot.img from a dev ) , so just be aware of that for future releases.
Click to expand...
Click to collapse

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

Moto G4 XT1625 Nougat OTA (crazy?) Error

Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
TLDR: OTA to Nougat refuses to install on XT1625...because Consumer Celluar?
So here's the long version... Bought a refurbished Moto G4 XT1625 (not amazon) with the intention of using it as a learning aid for unlocking, rooting, etc.
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it. However, I captured the file, pulled up the stock ROM download from the official Moto website after checking that the build numbers matched, and proceeded to unroot and reflash that stock ROM (except for bootloader and gpt files). I booted back up, got the notification again, and hit OK. Fail. So I booted into recovery and tried to sideload OTA (using "Blur_Version.24.31.65.athene.retail.en.US.zip" pulled from "com.motorola.ccc.ota-20171028-062630.tar.gz"). Fail.
Maybe somehow I misread the multiple how-tos out there, and I'm screwing something up in the process here?
After numerous rinse and repeats of the above steps, I cannot for the life of me get past this damn error which (assuming my inexperienced eyes are reading it properly) seems to say that the current CCMyConsumer.apk on my phone is somehow wrong (corrupted/incorrect/missing?), and so the OTA's response to me is a big FU.
Verifying current system...
E3005: "/oem/app/CCMyConsumer/CCMyConsumer.apk" has unexpected contents.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This seems.......weird to me? If I have both the stock ROM and am using the actual OTA, why would a random provider's app be screwed up, much less screwing up the update.
Also, if it matters at all, here's that particular directory tree in a file manager...an apk file doesn't appear to even be there?
Could a lack of existence be the "unexpected contents?"
So, the question as in the TLDR, any ideas on what the cause or solution to this error or overall OTA issue could be? I'm at a loss.
The only other item I noticed is that my "Settings" now crashes if I attempt to navigate into "Apps" within its menu. However, if I navigate directly into an App's info page via the app drawer, I can access those. Not saying this is related, I have no idea, but being the only other oddity, and since it persists through flashes, I figured I'd mention it (even if unrelated, I am still curious what could be going on there too...).
Thanks in advance for any help, education, or peace of mind. =P

NobodyByChoice said:
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it.
Click to expand...
Click to collapse
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458

lmacmil said:
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
Click to expand...
Click to collapse
Thanks for the advice, sorry for the late reply as I was out of the country. I do understand the need to get rid of TWRP first, but I'll read through your recommended threads and see what happens!

October 2020 Security Update now available

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
October Security Update just released today.

Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
CAPTCHA:
After clean fastboot flashing of this version with flash_all_except_data -> rebooting phone forces to stock recovery and requests factory reset.
Seems like after installing OTA possible behaviours are: either the same request for reset, or bootloop.
Reflashed back V11.0.14.0.QDIMIXM in order to make data backup

Aerobatic said:
Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
Click to expand...
Click to collapse
nice! thanks for this!

Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.

Yes, the update seems buggy.
Even my phone was not able to start after the update.
Tried multiple times. Eventually had to factory reset it ?
xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse

update works fine for me with no issues at all.

xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM

So this is yet another botched update to skip, got it.
Thank you, brave ones who are willing to update first.
I'm just too afraid to update this device nowadays.

I had to reset device after last update this is really worst device support I had

For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop

updated successfully. there are no visible improvements

gromez said:
For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop
Click to expand...
Click to collapse
Try to switch to inactive slot.

How is your experience with stock rom and october patch?

HTCDevil said:
How is your experience with stock rom and october patch?
Click to expand...
Click to collapse
for me, it's snappy and stable.

Same problem here, unacceptable

Failed install here too, had to do a full reset
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
PereVidi_77 said:
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM
Click to expand...
Click to collapse
I tried unsuccessfully to reboot, Everytime showed this message, finally I accepted to erase the phone and let download the backup, I lost some downloaded stuff I may download again later.
It's an Shane this happening to Android one devices, suddenly we got from special to second class citizens

I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one

oferwald said:
I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one
Click to expand...
Click to collapse
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2

maxou88 said:
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2
Click to expand...
Click to collapse
Hi,
All I did was go into fastboot using the power and volume shortcut, and than I connected the device to my laptop and issued the command:
fastboot reboot recovery
(naturally using the SDK Platform tools)
After that, the phone started working again. Although there is no reasonable reason it should have worked. I was surprised enough so that I decided to take the effort to create an account here and share this for others. But again, maybe it was pure luck, YMMV.
Will be crossing my fingers for you.

I've tried to update and got the "Can't load Android system. Your data may be corrupt" messege. Tried again a few times, until the phone reverted back to the previous version and said it couldn't install the update. No October update for me. =(