I tried to install October Patch/Version 7.1.2, but it not install and got stuck in Recovery Mode. I restarted several times, but Nokia 6 was going to Recovery Mode. I think the Software was Corrupted. Please help..
{
"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"
}
.
Did something go wrong while applying the update? What happens when you boot up the phone now, are you stuck in recovery or like what comes up on your screen?
TheMadxtremist said:
Did something go wrong while applying the update? What happens when you boot up the phone now, are you stuck in recovery or like what comes up on your screen?
Click to expand...
Click to collapse
When power on the screen goes to recovery mode instead of booting up.
And you're not able to escape recovery mode in any way? As in, the reboot system option or the key combination. Did you try factory reset?
TheMadxtremist said:
And you're not able to escape recovery mode in any way? As in, the reboot system option or the key combination. Did you try factory reset?
Click to expand...
Click to collapse
Yes, I tried. Is there any alternatives to get back my phone back to normal stage.
Maybe.
msr_xda said:
Yes, I tried. Is there any alternatives to get back my phone back to normal stage.
Click to expand...
Click to collapse
I wouldn't know for sure until I have the device in my hand but since you got this problem while applying 7.1.2, one thing you could do is go back to 7.1.1. If you can get the 7.1.1 OTA update file or stock for the TA-1021, you could put it on your SD card and then apply through the recovery mode that you're stuck in.
Here's a link that has the 7.1.1 update file but I'm not sure if it's for the TA-1021. I suggest you find out first.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/
Again, confirm everything before you attempt this. Also, try applying the 7.1.2 again properly. Maybe something didn't go as planned the first time.
Here's the link for 7.1.2 for TA-1021 :
http://www.mediafire.com/file/t8q2nn95xvq27ad/Nokia6_Android_7.1.2_OTA.zip
TheMadxtremist said:
I wouldn't know for sure until I have the device in my hand but since you got this problem while applying 7.1.2, one thing you could do is go back to 7.1.1. If you can get the 7.1.1 OTA update file or stock for the TA-1021, you could put it on your SD card and then apply through the recovery mode that you're stuck in.
Here's a link that has the 7.1.1 update file but I'm not sure if it's for the TA-1021. I suggest you find out first.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/
Again, confirm everything before you attempt this. Also, try applying the 7.1.2 again properly. Maybe something didn't go as planned the first time.
Here's the link for 7.1.2 for TA-1021 :
http://www.mediafire.com/file/t8q2nn95xvq27ad/Nokia6_Android_7.1.2_OTA.zip
Click to expand...
Click to collapse
Not Worked, and the thing is, when I tried to install any package for Nokia 6 TA-1021 it shows an error that installation aborted, see picture..
Status 7.
It shows a Status 7 error. The only instance in which the Status 7 error can be seen on a non-rooted Android device is when a person, instead of waiting for a new system update to reach them Over the Air, decides to sideload and flash a ZIP file containing the official software update onto their device. A non-rooted Android device only displays a Status 7 error when a system update is being flashed onto it and something is found to be out of place or, to be more precise, modified. It's not a very serious issue though.
The Status 7 error only affects non-rooted devices that are not in complete stock condition, so the only way to fix the Status 7 error on a non-rooted Android device is to restore every bit of the device back to its stock condition. So I guess you'll have to find the stock ROM. Have you tried contacting the customer service center?
U can't go back .u flashed wrong file. The same problem happened to me in last month I tried to update software through sd card after several time that was aborted , now u need to install full stock rom that was available in XDA developer forums about 1.52 gb . Download that rom flash through OST.LA software and flashing method step by step listed there . But one problem is in that rom u will stuck with June security patch, further updates not available with that rom , rom is bug free full stock rom of nokia 6 for all except Chinese version . I'm using the same.
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Otherwise u need to go services center they can fix the problem .
TheMadxtremist said:
It shows a Status 7 error. The only instance in which the Status 7 error can be seen on a non-rooted Android device is when a person, instead of waiting for a new system update to reach them Over the Air, decides to sideload and flash a ZIP file containing the official software update onto their device. A non-rooted Android device only displays a Status 7 error when a system update is being flashed onto it and something is found to be out of place or, to be more precise, modified. It's not a very serious issue though.
The Status 7 error only affects non-rooted devices that are not in complete stock condition, so the only way to fix the Status 7 error on a non-rooted Android device is to restore every bit of the device back to its stock condition. So I guess you'll have to find the stock ROM. Have you tried contacting the customer service center?
Click to expand...
Click to collapse
Not yet, I have to go., Thanks
lins.cjose24 said:
U can't go back .u flashed wrong file. The same problem happened to me in last month I tried to update software through sd card after several time that was aborted , now u need to install full stock rom that was available in XDA developer forums about 1.52 gb . Download that rom flash through OST.LA software and flashing method step by step listed there . But one problem is in that rom u will stuck with June security patch, further updates not available with that rom , rom is bug free full stock rom of nokia 6 for all except Chinese version . I'm using the same.
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Otherwise u need to go services center they can fix the problem .
Click to expand...
Click to collapse
Thanks, I will try it later..
lins.cjose24 said:
U can't go back .u flashed wrong file. The same problem happened to me in last month I tried to update software through sd card after several time that was aborted , now u need to install full stock rom that was available in XDA developer forums about 1.52 gb . Download that rom flash through OST.LA software and flashing method step by step listed there . But one problem is in that rom u will stuck with June security patch, further updates not available with that rom , rom is bug free full stock rom of nokia 6 for all except Chinese version . I'm using the same.
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Otherwise u need to go services center they can fix the problem .
Click to expand...
Click to collapse
Is it a International Rom or Chinese Rom
Yes ww rom check XDA forums . U can c firmware for MENa region that is for global rom
msr_xda said:
Not yet, I have to go., Thanks
Click to expand...
Click to collapse
Same exact problem, is their any solution available.
Any Way to Update
lins.cjose24 said:
U can't go back .u flashed wrong file. The same problem happened to me in last month I tried to update software through sd card after several time that was aborted , now u need to install full stock rom that was available in XDA developer forums about 1.52 gb . Download that rom flash through OST.LA software and flashing method step by step listed there . But one problem is in that rom u will stuck with June security patch, further updates not available with that rom , rom is bug free full stock rom of nokia 6 for all except Chinese version . I'm using the same.
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Otherwise u need to go services center they can fix the problem .
Click to expand...
Click to collapse
I tried and succeed. But it was stuck on June Security patch. Is there any way to update it.
msr_xda said:
I tried and succeed. But it was stuck on June Security patch. Is there any way to update it.
Click to expand...
Click to collapse
goto this thread https://forum.xda-developers.com/nokia-6/help/stuck-june-patch-update-help-t3721971
hi
plz link
stock rom that was available in XDA developer forums about 1.52 gb
Related
Just got a notification saying that the 5.1 GPE update is available for download. I don't even have a gpe phone just the loserskater gpe rom....I'm downloading the update right now if someone wants me to upload it.
{
"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"
}
Sent from my HTC One_M8 using XDA Free mobile app
Can you pull the OTA file and upload it?
digitalhigh said:
Can you pull the OTA file and upload it?
Click to expand...
Click to collapse
I have it uploaded to my site already.
I need someone who isn't rooted and hasn't touched the system on 5.1 to PM me please so you can help me pull the system partition so I can create a 5.1 RUU. You must have time to be able to pull the system, root the device and then pull the system again and upload both images.
Thanks
Update error
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
ratatella said:
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
Click to expand...
Click to collapse
As far as I understand you will need a rooted 5.1 version... Or you can flash the unrooted ruu and then update...
Have had the same Problem with an Moto G GPE. I needed to unroot and factory reset the device, then it worked.
Destroyer706 said:
Have had the same Problem with an Moto G GPE. I needed to unroot and factory reset the device, then it worked.
Click to expand...
Click to collapse
Mmm.. not so cool.. but thanks for the reply anyways.
Maybe to much of an effort to unroot (any link on how to do that for this device?).
Might wait for the RUU rooted/unrooted from graffixnyc as that's much more simple to apply.
Ratatella
ratatella said:
Hi All,
After downloading the 5.1 OTA update on my converted GPe M8 device it verifies the download and asks to reboot and install.
When hit the button to let it reboot and install I see the green android and it attemts to install the update but then after a minute or 2 I get the android with explanation and error message "error"
I've tried a second time but same thing happens.
I updated my devies using OTA before without any problem and running stock recovery as well and no additional tweaks, just running like a stock GPe M8, only thing is I'm rooted, which shouldn't be any problem as far as I know.
Luckly I can just still reboot my phone and still use it running 5.0.1 without it being briked but of course I'd like to update to 5.1 using the OTA.
Does someone experience the same or has any tips, please?
Ratatela
Click to expand...
Click to collapse
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
benj! said:
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
Click to expand...
Click to collapse
Thanks, sounds like a good one.
Where did you get the OTA file? Is it here on XDA already?
Ratatella
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
benj! said:
I did a fresh install of the non-rooted RUU, having backed up all my Titanium folder and other stuff, then sideloaded the OTA file, flashed TWRP and re-rooted. All worked perfectly.
Click to expand...
Click to collapse
PS: Found rooted and non-rooted 5.1 RUU for M8 here:
http://www.graffixnyc.com/m8.php
Ratatella
ratatella said:
Thanks, sounds like a good one.
Where did you get the OTA file? Is it here on XDA already?
Ratatella
Click to expand...
Click to collapse
Funnily enough, it's in the GPe OTA thread
boot issue
Please help,
Had the latest 5.1 rooted ruu flashed to my device for a month or two when I got this OTA update notification. I accepted the update and my phone rebooted. I saw the android robot do it's thing for a minute or two and without errors my phone continued further along the boot process. However it's currently stuck on the bootup animation ( ie the colored balls that move around ). It's been like this for an hour and I've event tried to reset the phone but it never makes it past the animation.
--- EDIT: UPDATE ---
Also, I had TWRP flashed as well when I accepted the update. I Think this may have been my problem but not sure. TWRP no longer works and all I see is the Android with a red exclamation mark. I can still manage to pull up the backup android recovery menu.
------------------------
Do anyone have any ideas about what could have happened?
Did I do something wrong?
What should I try/do?
Is there a way to recover from this without losing my apps & their data?
Thanks in advance for any guidance/help.
So if I'm on a custom ROM this update is just the stock GPE ROM? So in order to maintain the ROM I'm using I need to wait for a rom release and ignore this?
I just got this OTA update as well.
I converted my phone to UNrooted 5.1 RUU last week.
I run the update, it reboots goes through the install with no errors, restarts, goes through the "Android is upgrading... and optimizing apps".
But once it's finished, the update notification still popsup as if it didn't upgrade... ran it a second time, and for whatever reason this time it "took". Checked my phone and it said it's up to date.
Very odd.
Is it needed?
Hi everyone,
A bit of a newbie, so not quite sure if this is obvious to everyone else, but here goes...
I recently installed the rooted version of [RUU] M8 Google Edition Conversion. 5.1 LMY470.H4 provided by @graffixnyc as per this thread.
Everything worked fine, and I now have a rooted HTC One M8 running stock GPE 5.1. All fine & dandy, thankyou @graffixnyc...
Today (July 8, 2015) I am told that my phone has downloaded the OTA Android L-MR1 modification. Being in New Zealand it seems to have finally arrived here two months after everyone else received it.
My question is this - do I need to install the upgrade, or have I already got it thanks to the ROM I have already installed?
Another question is - if I do need to install it, are there any special steps and/or procedures I need to take in order to install it without doing something bad (& irrevocable!) to my phone?
Hope this doesn't sound newbie-ish... I am quite prepared to RTFM if someone can point me in the direction of appropriate answers to my questions,
Cheers,
Attobrute
adamparsons said:
Please help,
Had the latest 5.1 rooted ruu flashed to my device for a month or two when I got this OTA update notification. I accepted the update and my phone rebooted. I saw the android robot do it's thing for a minute or two and without errors my phone continued further along the boot process. However it's currently stuck on the bootup animation ( ie the colored balls that move around ). It's been like this for an hour and I've event tried to reset the phone but it never makes it past the animation.
--- EDIT: UPDATE ---
Also, I had TWRP flashed as well when I accepted the update. I Think this may have been my problem but not sure. TWRP no longer works and all I see is the Android with a red exclamation mark. I can still manage to pull up the backup android recovery menu.
------------------------
Do anyone have any ideas about what could have happened?
Did I do something wrong?
What should I try/do?
Is there a way to recover from this without losing my apps & their data?
Thanks in advance for any guidance/help.
Click to expand...
Click to collapse
I'm pretty sure I've been able to answer my own questions after a many hours of searching and reading.
Just in case, for other noobs like me, here is what i learned:
There are many things that might cause havok for OTA updates including being rooted and having custom boot and custom recovery images; all of which I had.
I found the following sites to be useful:
littlegreenrobot.co.uk : serach their tutorials page for ota updates
wugfresh.com : faqs
( sorry for the lack of links but the site is preventing me from posting them )
I also learned that I should have taken a backup before applying something as simple as an OTA update. Lesson learned.
I am going to attempt to flash only the system partition and hopefully that will get me back up and going.
adamparsons said:
I'm pretty sure I've been able to answer my own questions after a many hours of searching and reading.
Just in case, for other noobs like me, here is what i learned:
There are many things that might cause havok for OTA updates including being rooted and having custom boot and custom recovery images; all of which I had.
I found the following sites to be useful:
littlegreenrobot.co.uk : serach their tutorials page for ota updates
wugfresh.com : faqs
( sorry for the lack of links but the site is preventing me from posting them )
I also learned that I should have taken a backup before applying something as simple as an OTA update. Lesson learned.
I am going to attempt to flash only the system partition and hopefully that will get me back up and going.
Click to expand...
Click to collapse
I was able to recover from my issue .
For anybody else that runs into the same issue, this is what I did:
1) re-flashed twrp custom recovery
2) made data backup
3) created by own custom (system-only) ruu using graffix's gpe rooted ruu as a base. I basically deleted all img files from the zip file except for the system image.
4) I flashed the custom (system-only) ruu via fastboot
5) let the system boot
6) skipped all the account signup and settings stuff
7) rebooted the system one more time just to make sure things are still good ( I don't think this is necessary but I did it and things seemed to work for me )
8) rebooted into recovery
9) restored data backup that I made in step 2
10) let android do it's thing ( optimize and stuff )
And that's it. Things seem to be back to the way they were before applying the update. Even the android update notification, which caused me all this pain to begin with, is back.
The only thing I have left to do I guess is figure out how to get rid of the notification.
BTW, If I'm not mistaken, this update is not needed. I think it's already included in the 5.1 GPE room graffix supplies.
Hello,
I installed Android 5.1 GPE with the "Rooted Flashable Stock Rom Build"(zip file install wit twrp) from graffixnyc a month ago. Is there an Update package(ruu?/ota?) that I can use to apply the L-MR1 upgrade without losing my data?
Thanks
Got this update this week too. In fact are two updates, one is 24mb and other is 20mb. Still stays on Android 5.1 instead 5.1.1, but build number changed two times, ending .h5 and .h6. Don't know what changed, maybe just bugfixes.
Can someone upload the ota packages?
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.
Hello, my name is Chris and I was beeing stupid.
I accidentaly started the latest OTA System Update (in Germany) on my rooted 830L.
After that, it was stuck in Bootloop.
I thought I was being smart and tried to go back to stock Kitkat so start over from there.
So i used the tool from this post http://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-830-1050-1380-to-kitkat-t3240487 whichh seemed to work.
Afterwards i tried to flash Stock Kitkat using this firmware http://forum.xda-developers.com/showpost.php?p=62237392&postcount=9 and according to a german how to. That seemed to go well, too. But now the tablet starts in strange mode:
It is not recognized by the PC in this mode. I still can enter fastboot mode though. In Fone flash tool it is shown as INT1503... and not as Bayflie or whatever it was before.
Ist there anything i can do to repair this? Thank you very much in advance!!
Chris
UPDATE: Fastboot Screen
[UPDATE 2]
heineken123 said:
Hello, my name is Chris and I was beeing stupid.
Chris
Click to expand...
Click to collapse
go in fastboot mode and take a picture
try flashing the lollipop stock rom , maybe you are still on the lollipop bios.
1. download and extract someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
I just realized that I was even more stupid than I thought.
I flashed a 830F KitKat Rom to my 830L!!!! Is there a way to revert that?
I have added a picture of the fastboot screen above, since i couldnt link it here.
Thank you!
heineken123 said:
I just realized that I was even more stupid than I thought.
I flashed a 830F KitKat Rom to my 830L!!!! Is there a way to revert that?
I have added a picture of the fastboot screen above, since i couldnt link it here.
Thank you!
Click to expand...
Click to collapse
already instructed you with some stuff (also, that one is the DNX mode, fastboot mode is the one with the Droidboot menu etc). it is likely that your bios is still a lollipop one, the rom i linked is for lollipop. if it does not work just download the kitkat stock rom for your model and flash it
Ok, I am a step forward. At least there seems to be something.
Flashing your image with the tool did not work. It lead to the same screen as the first picture above.
However, when i tried to flash the KitKat Rom with your tool it startet and it went into Droidboot.
Flashing did not finish thoug. i get this error, see UPDATE 2 Above.
heineken123 said:
Ok, I am a step forward. At least there seems to be something.
Flashing your image with the tool did not work. It lead to the same screen as the first picture above.
However, when i tried to flash the KitKat Rom with your tool it startet and it went into Droidboot.
Flashing did not finish thoug. i get this error, see UPDATE 2 Above.
Click to expand...
Click to collapse
go in File->Options check the Force sparsing box and input 500MB in there (if is not already) then repeat the whole flashing procedure
i asked you to flash lollipop first just in case you were still on the lollipop bios (for the future so you should know, you can flash a stock rom matching your existing install if you brick, for eg you could have flashed a stock lollipop rom from the beginning) no longer the case as now you have downgraded the bios to kitkat. after you flash kitkat rom remember to set your region code before you start to update through ota's.
ionioni said:
go in File->Options check the Force sparsing box and input 500MB in there (if is not already) then repeat the whole flashing procedure
i asked you to flash lollipop first just in case you were still on the lollipop bios (for the future so you should know, you can flash a stock rom matching your existing install if you brick, for eg you could have flashed a stock lollipop rom from the beginning) no longer the case as now you have downgraded the bios to kitkat. after you flash kitkat rom remember to set your region code before you start to update through ota's.
Click to expand...
Click to collapse
Excellent, Tab is booting and seems to be working!!! Region code is changed to de. Thank you very much.
From your other post that i have seen there it seems possible to flash the LC Formware to enable Calling?
Would i proceed by updating to Lilipop, all ota updates and then flash the lolipop 830LC firmware as sugested in the other post? Will it work with region code de and is it rootable?
Thank you very much again!
heineken123 said:
Excellent, Tab is booting and seems to be working!!! Region code is changed to de. Thank you very much.
From your other post that i have seen there it seems possible to flash the LC Formware to enable Calling?
Would i proceed by updating to Lilipop, all ota updates and then flash the lolipop 830LC firmware as sugested in the other post? Will it work with region code de and is it rootable?
Thank you very much again!
Click to expand...
Click to collapse
yes, yes and yes
Hello there,
I'm facing pretty much of the same issues.
Having the 1050l Version, tried to update the ota while having the device rooted. So after that, it just booted until the "those who do"-sign.
I followed the "get back to kitkat" thread, downgraded the bios (might have worked i think) and flashed YT2-1050L_S0225_150422_ROW to it.
Right now it is just coming to the very first "powered by Android"-screen and aborts rebooting, booting again, and so on and so on.
Might it be that theres sill the lollipop bios on it?
Thought about flashing yoga_tab_2_osc_android_to_lollipop_201505.rar (Official stock rom) on it, but dont want to make any further stepp before having your advice.
I hope for you help,
Thank you.
Pikku said:
Hello there,
I'm facing pretty much of the same issues.
Having the 1050l Version, tried to update the ota while having the device rooted. So after that, it just booted until the "those who do"-sign.
I followed the "get back to kitkat" thread, downgraded the bios (might have worked i think) and flashed YT2-1050L_S0225_150422_ROW to it.
Right now it is just coming to the very first "powered by Android"-screen and aborts rebooting, booting again, and so on and so on.
Might it be that theres sill the lollipop bios on it?
Thought about flashing yoga_tab_2_osc_android_to_lollipop_201505.rar (Official stock rom) on it, but dont want to make any further stepp before having your advice.
I hope for you help,
Thank you.
Click to expand...
Click to collapse
this is the 1050L kikat stock rom and this is the lollipop one
if you are sure that you downgraded the bios when using the restore kitkat bios tool then flash the kikat one
Thank you very much.
It just appeared to me that i flashed the "erase" image, so i might try to flash the "blank factory" one.
Pikku said:
Thank you very much.
It just appeared to me that i flashed the "erase" image, so i might try to flash the "blank factory" one.
Click to expand...
Click to collapse
do not use other files than flash.xml, you can erase the imei for eg or even worse some xml files are writing a bios that will hard-brick. always use a known stock rom and never use other files than flash.xml unless instructed otherwise!
Oh boy... ye i will keep that in mind definately!
Is there btw any possibility to charge the device in the current status?
---------- Post added at 02:44 PM ---------- Previous post was at 02:35 PM ----------
Ok, so after your hint with the bios i went to reexecute your kitkat-bios-reset, and i'm in the same bootcycle, the programs i preparing for pushing files all the time. Hardbrick confirmed?
Pikku said:
Oh boy... ye i will keep that in mind definately!
Is there btw any possibility to charge the device in the current status?
---------- Post added at 02:44 PM ---------- Previous post was at 02:35 PM ----------
Ok, so after your hint with the bios i went to reexecute your kitkat-bios-reset, and i'm in the same bootcycle, the programs i preparing for pushing files all the time. Hardbrick confirmed?
Click to expand...
Click to collapse
if you used the 'restore kitkat bios' tool once there's no need to use it again (you already have the kitkat bios)
download the kitkat stock rom i linked, extract it and flash using intel phone flash tool (flash.xml file) from dnx mode (from pwr off, press and hold both vol keys then pwr on, screen will stay on a 'fastboot starting...' message, you must have this message on your tab when you click the 'start flashing' on the intel phont flash tool)
Ok, 7m of dl left, tho many thanks to you already, really appreciate your effort!!
---------- Post added at 03:22 PM ---------- Previous post was at 02:59 PM ----------
ionioni said:
if you used the 'restore kitkat bios' tool once there's no need to use it again (you already have the kitkat bios)
download the kitkat stock rom i linked, extract it and flash using intel phone flash tool (flash.xml file) from dnx mode (from pwr off, press and hold both vol keys then pwr on, screen will stay on a 'fastboot starting...' message, you must have this message on your tab when you click the 'start flashing' on the intel phont flash tool)
Click to expand...
Click to collapse
Ok i flashed the kitkat, now im facing "E: cannot remove cache/fastboot.tmp".
Any advice?
EDIT: Sorry it just toook a few times!
Pikku said:
Ok, 7m of dl left, tho many thanks to you already, really appreciate your effort!!
---------- Post added at 03:22 PM ---------- Previous post was at 02:59 PM ----------
Ok i flashed the kitkat, now im facing "E: cannot remove cache/fastboot.tmp".
Any advice?
Click to expand...
Click to collapse
ignore it... in the intel phone flash tool log window (in the boottom) is it reporting as finished? if so just reboot the tab
It worked!
Oh man, really thank you, glad you were up to help me Thanks!
Hi, unfortunately I got the IMEI changed/reset (probably due flashing other than flash.xml)... would you pls know about any solution to change it back so that LTE starts working? Thanks a lot!
ionioni said:
ignore it... in the intel phone flash tool log window (in the boottom) is it reporting as finished? if so just reboot the tab
Click to expand...
Click to collapse
Hi, hi hope you can help me. Yesterday I tried to flash the 830lc rom but it stopped at 16% so I turn it off and tried again but it didn't recognize the tablet. If I turn it on it show this
{
"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"
}
And when I put it in fastbot mode and try again to flash phone flash tool give me this error.
Any idea? I really don't know what to do.
Thank you
I can't post pic from iPad...
I don't know how to show it
Saw many users struggling with official stock marshmallow update and were looking for downgrade procedure(on Facebook, honor community) to go back to stable and official Lollipop version from Beta/stable stock Marshmallow version(instead of trying the custom ROMs). Below method is thoroughly checked personally by me for more than 5-6 times and I am writing this detailed step by step guide for downgrade. Original link to my thread on official Honor community-
https://club.hihonor.com/in/techsup...android-marshmallow-to-android-lollipop-.4825
Prerequisites-
It will work only if your phone is non rooted. (no changes to the system partition and bootloader made)
Make sure you are running the beta marshmallow version. (not custom version )
Make sure you are on stock recovery.
Make sure to take full backup of the data and apps as this downgrade process will erase all your data and will wipe the internal memory. (you can use this backup to restore your contacts, call/sms logs, app with data, your home screen layout etc. )
Make sure your device is charged to at least 50%.
SD card with minimum 4 GB free space (as main product package is around 2.77 GB in size)
Lets start the process.
Updating product transfer package-
Download the update.app product transfer package for Honor 5X device from link https://drive.google.com/open?id=0B42SZzKuosucZllsQk5WVGNRNjA
Create a folder dload in the root directory of your SD card.
Copy the update.app package which you just downloaded to dload folder.
Power off the phone.
Press volume up+volume down keys and simultaneously press power button.
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
Updating the main product package (lollipop package)
Delete the old dload folder from SD card. (which had transfer package file of size 13 KB) - Do not forget to delete this folder or rename it or else the same file will be keep on flashing again and again.
Download the full version package from the link http://consumer.huawei.com/in/suppo...0=Mobile Phones&key1=Smartphones&key2=KIW-L22
You will see a zip file with name Honor 5X_Firmware_KIW-L22_Android 5.1_EMUI 3.1_C675B130_India
Unzip and extract the package. You will get 1 folder and 2 files as
{
"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"
}
Copy the dload folder to SD card root directory. (dload folder contain update.app file of 2.77 GB size)
Power off the phone.
Press volume up+volume down keys and simultaneously press power button.
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Once the phone is booted and up, it will ask for the initial setup like language, wifi, agreement etc.
Validation-
Once the phone is setup, go to setting—about phone—check the android version and build number to verify you are running on Android Lollipop version.
NOTE:
This process will completely erase your data, so make sure to have a backup before proceeding further.
This process will downgrade your phone to Android Lollipop 5.1, EMUI 3.1 and Build version KIW-L22C675B130.
I have personally tested this method and downgraded my phone to Lollipop without any issue.
If you follow the guide correctly, you should not face any issue with condition that all the Prerequisites are met and you followed the steps in order.
If anyone still have any doubt or a slight hesitation, please feel free to ask in the comment before proceeding and risking your phone.
Steps will remain the same for all devices only the package will change.
I've been experiencing a lot of random boot loops on my phone... Tried removing sdcard, had a replacement simcard, no go. it's completely random. Sometimes it reboots right after pin insert, sometimes it stays ok for 1 day and then it starts again. I think i'm going to try to revert to lollipop and see if it solves my problem, before sending it to warranty repair... Thanks for your guide.
Bravopt said:
I've been experiencing a lot of random boot loops on my phone... Tried removing sdcard, had a replacement simcard, no go. it's completely random. Sometimes it reboots right after pin insert, sometimes it stays ok for 1 day and then it starts again. I think i'm going to try to revert to lollipop and see if it solves my problem, before sending it to warranty repair... Thanks for your guide.
Click to expand...
Click to collapse
This package provided was for only kiw-L22..steps will be same but you need to get the correct package from honor website.
Sent from my HUAWEI KIW-L22 using XDA Labs
Thank you for warning... Mine is KIW-L21
Bravopt said:
Thank you for warning... Mine is KIW-L21
Click to expand...
Click to collapse
No worries...it was just a heads up..dont want anyone to get into trouble...so clearly mentioned in title as well.
Sent from my HUAWEI KIW-L22 using XDA Labs
Bravopt said:
I've been experiencing a lot of random boot loops on my phone... Tried removing sdcard, had a replacement simcard, no go. it's completely random. Sometimes it reboots right after pin insert, sometimes it stays ok for 1 day and then it starts again. I think i'm going to try to revert to lollipop and see if it solves my problem, before sending it to warranty repair... Thanks for your guide.
Click to expand...
Click to collapse
Hope you were able to solve your issues...
Oh yeah, I'm back on B140, running quicker & trouble free, so far! thanks!
Bravopt said:
Oh yeah, I'm back on B140, running quicker & trouble free, so far! thanks!
Click to expand...
Click to collapse
Glad to hear that
Sent from my HUAWEI KIW-L22 using XDA Labs
hi gays i have kiw-l21c185b140 i chang my build number to c10b130 and my imei is lost and bootloder lock again i can use my sim cart there are any transfer file till i back to c185b140 in 4x i flash a update.app and my build number gone after that i able to flash any buildnumber
i need file like that for 5x
Thanks
faramarzq said:
hi gays i have kiw-l21c185b140 i chang my build number to c10b130 and my imei is lost and bootloder lock again i can use my sim cart there are any transfer file till i back to c185b140 in 4x i flash a update.app and my build number gone after that i able to flash any buildnumber
i need file like that for 5x
Thanks
Click to expand...
Click to collapse
try this
https://mega.nz/#!Q0YQmIQD!KSwQvGymMUf-YA4A5oDFBvg12UwQlPDm5dIOdTDsEjc
Sent from my KIW-L21 using Tapatalk
Nahid s said:
try this
https://mega.nz/#!Q0YQmIQD!KSwQvGymMUf-YA4A5oDFBvg12UwQlPDm5dIOdTDsEjc
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
ita dont work
Bravopt said:
Oh yeah, I'm back on B140, running quicker & trouble free, so far! thanks!
Click to expand...
Click to collapse
could you please mention from where you downloaded LP package and Transition package for L21. links?
hatim_rajput said:
could you please mention from where you downloaded LP package and Transition package for L21. links?
Click to expand...
Click to collapse
Head out to the repository post and you will get the respective packages.
Sent from my HUAWEI KIW-L22 using XDA Labs
hatim_rajput said:
could you please mention from where you downloaded LP package and Transition package for L21. links?
Click to expand...
Click to collapse
Check Here
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288?goto=newpost
Sent from my KIW-L21 using Tapatalk
hatim_rajput said:
could you please mention from where you downloaded LP package and Transition package for L21. links?
Click to expand...
Click to collapse
Go to the 5x repository on XDA, you'll find a rollback guide there
Hello Shashank, thanks for ur detailed steps to roll back form MM to Lolipop for Honor 5x, I have successfully completed the downgrade but my phone conf. is showing incorrect, it show EMUI version as 2.0, Ram 1.0, CPU Quad core 1.2GHz.. can you .. I have downloaded the exact version as u mentioned.
umrailalec said:
Hello Shashank, thanks for ur detailed steps to roll back form MM to Lolipop for Honor 5x, I have successfully completed the downgrade but my phone conf. is showing incorrect, it show EMUI version as 2.0, Ram 1.0, CPU Quad core 1.2GHz.. can you .. I have downloaded the exact version as u mentioned.
Click to expand...
Click to collapse
Glad it worked. I have never faced any issue and have uswd the same method for more than 20 times for downgrade.
Whats tour phone model and whats the firmware you downloaded?
umrailalec said:
Hello Shashank, thanks for ur detailed steps to roll back form MM to Lolipop for Honor 5x, I have successfully completed the downgrade but my phone conf. is showing incorrect, it show EMUI version as 2.0, Ram 1.0, CPU Quad core 1.2GHz.. can you .. I have downloaded the exact version as u mentioned.
Click to expand...
Click to collapse
flash again full rom with local update method in updater
Sent from my KIW-L21 using Tapatalk
I am using Honor 5x, the Firmware I used is Honor 5X_Firmware_KIW-L22_Android 5.1_EMUI 3.1_C675B130_India, tried downloading from Honor site as well as form the link shared by you from Huawei site... but both gave me same results... when I go with Marshmallow the configuration shows correct but SIM does not detects so I have stay with downgrade version. Also to add I did try Honor 5X_Firmware_KIW-L22_Android 5.1.1_EMUI 3.1_C675B150_India but again same results with incorrect configuration.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Thanks for suggestion can you please help me with process or with link that can help me with correct process and software required. Using Honor 5x.
just what i was looking for,,,
im now on kiw-l22 b320, will it work?
{
"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. =(