Related
Hi All
Bought a Zenfone 2 (ZE551ML) from lightinthebox...came this week and it is full of either bloatware or malware as I can't use the phone with it popping up randomly with adverts and installing apps. I thought it would be pretty straightforward to update to another ROM. It is running Android 5.0
I've had nothing but problems with every step and method I have used. I've downloaded the stock rom from Asus (Android 6) and tried to install from SD card in Recovery I got 'only android 5.0(newer than 20160504 version) or android 6.1 (older version) can upgrade to this version'
I've tried over ADB and even then had issues with drivers (running windows 10). I've also tried the Asus Flash Tool but that didnt work.
Please please before I literally pop this phone in the bin, can someone provide a link to a working stock ROM that I can just install from the SD or whatever method that is known to work.....too many sites have shown various methods all of which haven't worked for me.
mdemetri2 said:
Hi All
Bought a Zenfone 2 (ZE551ML) from lightinthebox...came this week and it is full of either bloatware or malware as I can't use the phone with it popping up randomly with adverts and installing apps. I thought it would be pretty straightforward to update to another ROM. It is running Android 5.0
I've had nothing but problems with every step and method I have used. I've downloaded the stock rom from Asus (Android 6) and tried to install from SD card in Recovery I got 'only android 5.0(newer than 20160504 version) or android 6.1 (older version) can upgrade to this version'
I've tried over ADB and even then had issues with drivers (running windows 10). I've also tried the Asus Flash Tool but that didnt work.
Please please before I literally pop this phone in the bin, can someone provide a link to a working stock ROM that I can just install from the SD or whatever method that is known to work.....too many sites have shown various methods all of which haven't worked for me.
Click to expand...
Click to collapse
Do you have a working phone now ?
You can if you have above , disable WiFi , click app drawer, click on junk app ,and disable junk and it will uninstall it.
Firmware upgrade...
Put Asus firmware on SD ...WW-4.20 bla bla etc , .184 is a good one of LP ..
Make sure it ends in WW-4-20bla bla .184 (user.zip )and reboot phone
You also can change name of firmware to MOFD_SDUPATE , Put in adb fasboot folder and adb sideload..command is.....
adb sideload MOFD_SDUPDATE.zip
Did you try a factory reset in recovery mode rather than a factory reset from the rom?
mdemetri2 said:
I've had nothing but problems with every step and method I have used. I've downloaded the stock rom from Asus (Android 6) and tried to install from SD card in Recovery I got 'only android 5.0(newer than 20160504 version) or android 6.1 (older version) can upgrade to this version'
Click to expand...
Click to collapse
Update to 2.20.40.184 or newer before upgrading to MM.
Sent from my ASUS_Z00A using XDA Labs
So, following this guide i tried to root my samsung galaxy a5 2017. Everything was okay, i flashed the custom recovery and tried to install magisk through twrp as said there but... the dreaded 'only official release binaries are allowed to be flashed' red message in black background popped up in my screen. Now i can only boot into download mode, and install official binaries.
So I'm trying to do now, i downloaded the last carrierless spanish sotck room for my mobille. Well, it turns out that it gives an error 'kernel rev check failed. Mobile:9 Binaries:8' aaand i don't know what to do now?
Also, I didn't know Samsung had come to a new way of blocking custom binaries in 8.0.0, so, is there any way to circumvent this? I found this page but I don't really know if that's what I'm looking for
carlosmedia said:
So, following this guide i tried to root my samsung galaxy a5 2017. Everything was okay, i flashed the custom recovery and tried to install magisk through twrp as said there but... the dreaded 'only official release binaries are allowed to be flashed' red message in black background popped up in my screen. Now i can only boot into download mode, and install official binaries.
So I'm trying to do now, i downloaded the last carrierless spanish sotck room for my mobille. Well, it turns out that it gives an error 'kernel rev check failed. Mobile:9 Binaries:8' aaand i don't know what to do now?
Also, I didn't know Samsung had come to a new way of blocking custom binaries in 8.0.0, so, is there any way to circumvent this? I found this page but I don't really know if that's what I'm looking for
Click to expand...
Click to collapse
Apparently I was NOT using the last firmware available, even though i checked it like 4 times, that was the problem. It is fixed.
Hi everybody,
i have a new Mi A2 Lite. I purchased it from a private person, not a shop, but it was still in foil and opened by me. It works nicely, is fast, the phone feels fine, i like it. It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates. The same for the security patches - they are from nov. 2018, which is nearly a year ago, but there are no updates either.
I wanted to install android 9, so i did lots of tricks and things like using a VPN to poland and resetting the phone and so on, but to no avail - there are no updates.
so...
(1) is there something that can be done wrong? why wouldnt the phone find updates?
(2) is there a way to flash the official OTA zip without unlocking? I do not want a special kernel or rom, i dont want to modyfy anything on the os, i just want the official, latest os on the phone
(3) Any other ideas?
Thanks in advance
damaltor said:
It has AndroidONE, Oreo, on it. If i search for updates, it tells me that it is up to date and there are no updates.
Click to expand...
Click to collapse
Hi!
Could you please share a screenshot showing your actual Android build number and kernel version? You might have a fake A2 lite (Redmi 6 Pro).
Edit: Don't flash anything before you're sure that your device is a geniue A2 lite, otherwise you will brick your device.
yep, i heard about that. unfortunately, i did flash it by now, but the flash worked perfectly. i unlocked the bootloader with fastboot, flashed the last fastboot package, and re-locked the bootloader. the device is now on android pie and it still works nicely. is there any way to find out if it is genuine after flashing?
So, now i can say the following:
- the deveice works still well with the flashed software.
- the device did just find and download the google security patches of sep 2019
- the imei of the device passes the xiaomi authentication test
so, i am somewhat sure that the device is an original.
still, i am interested why the device was stuck on the old version. maybe it could only handle incremental updates and the old incremental update was not available anymore?
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
My screens:
ibb.co/SKjNJ6D
ibb.co/YR4793D
Regards!
Facing The same in my Mi A1
The same thing is happening with my Mi A1, I have Android 8.1 an I hadn't update to Android 9. Every day the notification for Android 9 would appear in my phone, saying that is available.
Today that update didn't show and when I checked for updates, it said I was already up to date.
Sorry for my English, I barely know it
Well i could probably Help you to flash your device but you should be sure that the device is not a fake, too. I cannot help you with that though. I will look in here tomorrow and give you a few hints to the flashing process.
So, the screenshots of the A2 Lite look pretty mich exactly like mine did. for me the only way was to reflash the device. if you are interested, i can tell you how, but there is a risk of bricking your device if it is a fake a2 lite. i cannot tell by your screenshots, maybe @thorin0815 can?
Otherwise, do you want to try it and risk ist?
edit: you can put in your imei here to check your phone, though i would not entirely trust it.
https://www.mi.com/global/shield#imei_en
*Deleted* *replay *
chriss7777 said:
Hi!
I have simmiliar issue. New, 100% original Mi A2 Lite. It downloaded 1GB update 8.0 to 8.1 (?), but no update for Android 9, and now it is stuck.
Click to expand...
Click to collapse
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
well, thats what i did. fortunately there is no longer the need to wait for hours or days to unlock the bootloader, it works in an instant now even without registration.
thorin0815 said:
You're right, your device looks like a geniue A2 lite. We never had an update from 8.0 to 8.1, it was shipped with 8.1.
Maybe Xiaomi pulled the incremental (8.1->9.0) OTA updates from their servers.
The "safest" way to update would be to flash the latest available full firmware via Miflash tool.
Click to expand...
Click to collapse
I did not notice what update it was downloading. I unboxed it, then I connect to WiFi and it started downloading. Anyway it downloaded aprox. 1GB of data, then restart and update. And now it is stuck with 8.1. I thought it will be Android 9 after update with latest patches.
I validate IMEI's on site and it is valid, also it has all google logos, and so on.
Is there any comprehensive update manual for MiFlash for this model?
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Switch on your phone.
Go to settings, about phone.
Tap the build number multiple times until "you are a developer".
Open the developer options.
Switch on USB debugging.
Switch on "allow unlocking bootloader".
Leave settings.
Download this, and install it, answering yes to all three questions:
https://forum.xda-developers.com/showthread.php?t=2588979
Connect the phone and when asked, accept the adb debug question on your phone. Your computer is now allowed to debug your phone.
Also download your new os from here:
https://xiaomifirmwareupdater.com/miui/ (put your phone model in there and download the latest fastboot image)
Unpack it. Depending on your packing program you might have to unpack twice - you should have a few folders and files.
Download the mi flash tool here:
https://www.xiaomiflash.com/
Now you are ready. Take a deep breath. Make sure your phone is charged, 50% should be enough.
Disconnect and Switch off the phone. Hold volume down and power until a rabbit working on an Android robot is seen on the screen. Now reconnect the cable.
Open a command window on the computer by pressing windows+R and entering "cmd".
In that window, type "fastboot oem unlock" and press enter. You should get the answer "OKAY".
If your phone reboots now, hold volume down and power again until the rabbit is there again.
Start miflash. Show miflash the folder in which you unpacked the os files.
In the lower right select "clean and lock" and then press update, select your phone, and press flash.
Flashing now takes roundabout 5 minutes.
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
damaltor said:
Well, Not that I know of one that is really complete and up to date. But here you are (own phone, own risk!). Back up your phone first!
Afterwards your phone should reboot into Android 9. Your data will be gone (though my phone managed to keep a few of it's settings for some reason).
Good luck!
Click to expand...
Click to collapse
It works like a charm. Also now it is updating with new security patch. Thanks damaltor!
No problem, good to hear that it worked!
Hello everyone,
First of all, I can't thank the devs enough for the hard work they are doing for Sakura (R6P). I just have one confusion regarding the new Android 10 build of the Pixel experience. Am I the only one or anyone else also facing the mounting problem while trying to convert an app tp system app (a message showing 'system not in proc/mounts' or something like that). And if I try to do any modification to the build.prop or anything else, it stucks my device on boot-loop (well, I am no expert of course). Is this a problem or it's just something that is not possible on Android 10? An answer would be much more appreciated.
Thank you
Same problem
Hi,
I have the same problem with Android 10 in the Pixel Experience project. I just installed the Android 10 package using TWRP without any problem or notice but when trying to reboot after installation, the TWRP says "are you sure, No OS is installed" and if press yes the phone will stucks in bootloop.
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Latest OTA for le2123 is in the screenshot, are you updating using oxygen updater?
Are you out of file space on your phone?
@Appreciative I'm not out of space. 80Gigs are free.
@AndyC76 the system settings want to update to C.47, oxygen updater to C.64. The C.64 Full ROM shows an Error when I try to do a local update.
@nurbs999 what hardware version is your phone? You'll find this in the box.
I am puzzled, the screen shot i posted earlier shows c64 is the current version of oos A12 that has been pushed ota to my le2123.
AHH so I read from your message you're using oxygen updater attempt a local update c64 update
Before we go any further, which working version is currently installed on your phone, we know it's not c47, as you got an OTA update asking you to upgrade
Very strange, something got confused
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
There is an OOS 12 update before the Oxygen Updater app update. Use the OOS system update and not oxygen updater app
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
just let the system do what it has to do.
Update thru OTA System. Even if it fails once, do the updates again until you reach lastest official OTAs
fiskhest said:
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
Click to expand...
Click to collapse
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
And for me, I've probably tried the OTA update 20 times over a span of six months before I did a complete reflash with latest msmtools, hoping that would solve my issue. After reflash, I did five more tries before I started looking for alternative solutions. Are we supposed to just bash our heads on the failing OTA update until it (hopefully) succeeds?
nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
I have the same problem
Unlock bootloader, flash rom via recovery (you will not be able to relock it after updating)
nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
Are you able to reflash the latest Android 11 (10.10 version)?. This ways you would make sure you have the latest on both slots. From there just OTA system to get the latest
@Steve0007 I just tried that. I downloaded the image from here
The OTA update still fails. Same behaviour as before.
nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
What you have furnished is the OOS version. What we are asking for is the initial hardware version viz. whether China, India, Global etc. As the user you are replying to says, it will be on the box the phone came in.
nurbs999 said:
I'm not out of space. 80Gigs are free.
Click to expand...
Click to collapse
That is for the data partition. What is the space left in the system partition since the OS will install to that?
Hm, this is the only label I can find.
nurbs999 said:
Hm, this is the only label I can find.
View attachment 5726527
Click to expand...
Click to collapse
There it is, it is a LE2123. It is a EU model and it seems to be flashed with the EU version of OOS as stated by you. Now let others more knowledgeable than me reply to you.
I've posted here for you,
One option you have is to use the MSM tool and go back to full and working stock.
Post in thread 'OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)' https://forum.xda-developers.com/t/...ick-tools-tmo-eu-glo-in.4272549/post-87526839
@AndyC76 thank you.
Well.. That is the one I've reflashed and tried with on my end, with no change in behavior. I'll have to wait a couple of days until I am able to reflash again. Hoping you have better results than me @nurbs999 !