A7 2017 w/ Binary 9 - RMM State Unlock - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

I bought this phone from second hand, and sadly it had been officially updated to the latest Oreo firmware (A720FXXU9CSKA) so I'm now stuck with binary 9.
I have tried every and each method to enable OEM unlock in my dev options (date trick, MiracleBox and z3x procedures) to no avail :/
I was wondering if I'm really screwed up or if anyone can help me or if anyone has OEM unlocked with binary 9. Thanks for any info!

nevertechdose said:
I bought this phone from second hand, and sadly it had been officially updated to the latest Oreo firmware (A720FXXU9CSKA) so I'm now stuck with binary 9.
I have tried every and each method to enable OEM unlock in my dev options (date trick, MiracleBox and z3x procedures) to no avail :/
I was wondering if I'm really screwed up or if anyone can help me or if anyone has OEM unlocked with binary 9. Thanks for any info!
Click to expand...
Click to collapse
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/

matkali said:
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
That's the date trick I was trying to refer to. Have tried it a few times but not working for me

It finally worked!
Dear lord, I'm finally on Lineage OS. My life is complete now!
I found some steps here. In summary, flashing latest firmware for your binary and then following the steps (verbatim) included in the link did the trick for me. It looks like the date trick works but you need to first set it 10 days behind, then after first reboot set it 10 days ahead, and after the other reboot add it up to 8 days.
After that if you don't see OEM unlock under developer options, give it a day or so and it will eventually show up! By the way, the steps were shared by the user "nacho2018" so make sure to check that info out.
I'm so freaking happy right now lol hope this helps somebody. I really had lost any hope; this is surely the hardest Android device I have ever worked on...

nevertechdose said:
Dear lord, I'm finally on Lineage OS. My life is complete now!
I found some steps here. In summary, flashing latest firmware for your binary and then following the steps (verbatim) included in the link did the trick for me. It looks like the date trick works but you need to first set it 10 days behind, then after first reboot set it 10 days ahead, and after the other reboot add it up to 8 days.
After that if you don't see OEM unlock under developer options, give it a day or so and it will eventually show up! By the way, the steps were shared by the user "nacho2018" so make sure to check that info out.
I'm so freaking happy right now lol hope this helps somebody. I really had lost any hope; this is surely the hardest Android device I have ever worked on...
Click to expand...
Click to collapse
can you explain in more details!

matkali said:
can you explain in more details!
Click to expand...
Click to collapse
For this to work, you must flash the oldest firmware available for your binary version through ODIN.
IMPORTANT: Make sure your SIM card is not inserted before flashing firmware.
How do I know what's my binary version?
Answer below, quoted from a post by @corsicanu on his RMM state issue thread:
You can find out what bl/modem rev you have by checking the current build number of your current rom. Let's take A520FXXU7CRL8 - in this build number 7 is the revision, leave other numbers and letters for some other time. To be able to flash older firmware it must be same revision, or odin will fail. Search on the firmware related websites for older fw of your phone/region that has that same revision. So for the device mentioned before A520FXXU7CRHA is the oldest fw that can be flashed.
Click to expand...
Click to collapse
Once the firmware has been flashed, follow these steps:
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later)
Enable developer options and disable automatic system updates from there
Connect to a WiFi network and go to software update under settings and disable automatic software update
Go to date and time settings and select for the time to be set manually. Set the date to be 10 days BEHIND from your current date
Go to developer options and turn it off (click on the right top corner toggle)
Now go to software update and check for a manual update, after result is shown restart your device. IMPORTANT: After the phone has rebooted, your date and time should be reset to the current time automatically
Go to date and time again but this time set it to be 10 days AHEAD, then check for software update one more time and reboot once finished
After reboot, go to date and time and add 8 more days AHEAD (you should be 18 days ahead of your actual date at this point) and perform a software update check once again and restart your phone
As a last step after the final reboot, enable developer options again and OEM unlock should be available!
If this didn't work for you at first try, wait a day or two for the toggle to show up. If you still don't see OEM unlock after those 48 hours, start over and try again.

Thanks

nevertechdose said:
For this to work, you must flash the oldest firmware available for your binary version through ODIN.
IMPORTANT: Make sure your SIM card is not inserted before flashing firmware.
How do I know what's my binary version?
Answer below, quoted from a post by @corsicanu on his RMM state issue thread:
Once the firmware has been flashed, follow these steps:
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later)
Enable developer options and disable automatic system updates from there
Connect to a WiFi network and go to software update under settings and disable automatic software update
Go to date and time settings and select for the time to be set manually. Set the date to be 10 days BEHIND from your current date
Go to developer options and turn it off (click on the right top corner toggle)
Now go to software update and check for a manual update, after result is shown restart your device. IMPORTANT: After the phone has rebooted, your date and time should be reset to the current time automatically
Go to date and time again but this time set it to be 10 days AHEAD, then check for software update one more time and reboot once finished
After reboot, go to date and time and add 8 more days AHEAD (you should be 18 days ahead of your actual date at this point) and perform a software update check once again and restart your phone
As a last step after the final reboot, enable developer options again and OEM unlock should be available!
If this didn't work for you at first try, wait a day or two for the toggle to show up. If you still don't see OEM unlock after those 48 hours, start over and try again.
Click to expand...
Click to collapse
Firmware in newer or older
---------- Post added at 06:55 PM ---------- Previous post was at 06:22 PM ----------
The first time you ask to delay 10 days and the second time to delay it again for another 10 days.

step 6- time does not reset to current time automatically

drjis said:
step 6- time does not reset to current time automatically
Click to expand...
Click to collapse
didnt for me either..

Related

Need Help, Can not flash International Rom on my new HTC One M8

Hello,
I just purchased an HTC M8 On Aliexpress which I assume being an asian Version...
The actual Android installed is 5.0.1 / Sense 6.0 / Software 4.18.708.12 ==> This version seems to be quite old and when trying to update it says no update available...
I have another HTC One M8 (Girlfriend) from Ali which is actually in the latest Android 6...
How is that possible ? I tried also to download and flsh the latest available stock rom, and when installing it says me that the version is not the asian version...
What do you recommend e to do as I really want to update and get the lastest Android...
If you need more info, let me know
Thanks for your HELP
Buzz
buzjay said:
The actual Android installed is 5.0.1 / Sense 6.0 / Software 4.18.708.12 ==> This version seems to be quite old
Click to expand...
Click to collapse
Its not that old, its Lollipop, which is the version before the current Marshmallow. In particular, MM ROMs seem to run fine with LP firmware.
Its technically true, that you should update to MM firmware (either OTA or RUU) for maximum compatibility (with MM ROMs). But depending on your current state, you may opt to just bypass this and flash a custom ROM with MM base.
Failure to flash MM ROMs is probably due to some other reason (besides firmware). What version TWRP are you using?
What exactly was the sequence of events, and the current state (you've mentioned a lot of different things.
It seems you tired to update OTA while on full stock, didn't work; then you unlocked the bootloader, flashed TWRP, and tried to flash a ROM (failed). Then tried to flash a stock ROM or RUU (did you relock the bootloader)?
List the exact sequence of the actions you've taken so far, in as much detail as possible.
buzjay said:
I have another HTC One M8 (Girlfriend) from Ali which is actually in the latest Android 6...
How is that possible ?
Click to expand...
Click to collapse
Probably different stock, so from the factory with MM some still with LP. Probably still exhausting some of their stock with LP firmware, mixed in with more current stock (MM firmware).
buzjay said:
I tried also to download and flsh the latest available stock rom, and when installing it says me that the version is not the asian version...
Click to expand...
Click to collapse
Can't tell exactly what you tried to flash. Please give exact file name and link the source.
You can't update from LP to MM by RUU (if that is what you are referring to) unless you flash MM firmware first (new requirement on MM RUUs).
Duplicate post -
http://forum.xda-developers.com/showpost.php?p=67893973&postcount=4160
ckpv5 said:
Duplicate post -
http://forum.xda-developers.com/showpost.php?p=67893973&postcount=4160
Click to expand...
Click to collapse
&%$#!?!#
I can't stand when folks do that (cross post).
Thanks for pointing it out.
Hi , I open this topic again as a request from ckpv5 in general post :
Quote:
Originally Posted by buzjay
My device ihas been updated in 4.19.707.2... 5I don't know why not ening by .4 ?)
You want I change my CID ? Which CID number should I need to write ?
Isn't that possible to flash directly Android 6 ?
---------- Post added at 10:53 PM ---------- Previous post was at 10:32 PM ----------
Ok, just fasboot CID, now is in 044... I reset phone, the only update is samll mail and minor software update of 4 Mb...
Then I'm still in 4.19.707.2...
Open a separate thread for your problem .. then I'll guide you.
There are two options that you can take.
1. Manually install OTA
2. Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware
I'll guide on new threas only as it is confusing to put guide here as there are many various questions from various users.
Thanks
buzjay said:
My device ihas been updated in 4.19.707.2... 5I don't know why not ening by .4 ?)
Isn't that possible to flash directly Android 6 ?
Ok, just fasboot CID, now is in 044... I reset phone, the only update is samll mail and minor software update of 4 Mb...
Then I'm still in 4.19.707.2...
Click to expand...
Click to collapse
There are 3 options that you can try. Option 1 was successful before because at that time there was no Mail update, only the 3 small Marshmallow preparation update.
Option 1 : (It may work and it may not work)
1. Make a factory reset as your current version is 4.19.707.2. After run setup wizard and you'll be advised there are 4 small update. Just ignore them.
2. Go to app drawer, select Settings - about - software update, check for update again. Previously, the system will allow you to download 4.19.707.4. If yes, download and install.
3. After reboot, recheck software update again, you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 2 : (manually install OTA)
1. Download this 4.19.707.4 OTA zip - https://mega.nz/#!echSCaiJ!WEESN5T2Uy32260hN-PB1VjwqQ4DXq7Kn0yuDElXGsw
2. Put it in your internal storage
3. Reboot to fastboot/bootloader - press power once to get to hboot then select recovery.
4. If it stay in blank screen, press & hold volume up button and tap power button once - this will get you in recovery
5. Select "aplly from phone storage" - then select the OTA.zip and press power to install.
6. Once completed, recheck software update - you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 3 : (Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware)
we keep this for the last as it involve many things to do. You just try the first 2 options and see how it goes.
ckpv5 said:
There are 3 options that you can try. Option 1 was successful before because at that time there was no Mail update, only the 3 small Marshmallow preparation update.
Option 1 : (It may work and it may not work)
1. Make a factory reset as your current version is 4.19.707.2. After run setup wizard and you'll be advised there are 4 small update. Just ignore them.
2. Go to app drawer, select Settings - about - software update, check for update again. Previously, the system will allow you to download 4.19.707.4. If yes, download and install.
3. After reboot, recheck software update again, you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 2 : (manually install OTA)
1. Download this 4.19.707.4 OTA zip - https://mega.nz/#!echSCaiJ!WEESN5T2Uy32260hN-PB1VjwqQ4DXq7Kn0yuDElXGsw
2. Put it in your internal storage
3. Reboot to fastboot/bootloader - press power once to get to hboot then select recovery.
4. If it stay in blank screen, press & hold volume up button and tap power button once - this will get you in recovery
5. Select "aplly from phone storage" - then select the OTA.zip and press power to install.
6. Once completed, recheck software update - you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 3 : (Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware)
we keep this for the last as it involve many things to do. You just try the first 2 options and see how it goes.
Click to expand...
Click to collapse
clear explanation. :good:
MM preupdate distrubs to take some ota, doesn't it?
ckpv5 said:
There are 3 options that you can try. Option 1 was successful before because at that time there was no Mail update, only the 3 small Marshmallow preparation update.
Option 1 : (It may work and it may not work)
1. Make a factory reset as your current version is 4.19.707.2. After run setup wizard and you'll be advised there are 4 small update. Just ignore them.
2. Go to app drawer, select Settings - about - software update, check for update again. Previously, the system will allow you to download 4.19.707.4. If yes, download and install.
3. After reboot, recheck software update again, you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 2 : (manually install OTA)
1. Download this 4.19.707.4 OTA zip - https://mega.nz/#!echSCaiJ!WEESN5T2Uy32260hN-PB1VjwqQ4DXq7Kn0yuDElXGsw
2. Put it in your internal storage
3. Reboot to fastboot/bootloader - press power once to get to hboot then select recovery.
4. If it stay in blank screen, press & hold volume up button and tap power button once - this will get you in recovery
5. Select "aplly from phone storage" - then select the OTA.zip and press power to install.
6. Once completed, recheck software update - you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 3 : (Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware)
we keep this for the last as it involve many things to do. You just try the first 2 options and see how it goes.
Click to expand...
Click to collapse
I'm processing with option 1 while downloading Files
When I look at the files stored on Mega, it is clearly written version ending by 707.2... not 4... is that normal
buzjay said:
I'm processing with option 1 while downloading Files
When I look at the files stored on Mega, it is clearly written version ending by 707.2... not 4... is that normal
Click to expand...
Click to collapse
I can't check as I'm on mobile.
Does it say OTAxxxxx...4.19.707.4-4.19.707.2...xxxxx.zip ?
If yes, it is correct ... OTA from 4.19.707.2 to 4.19.707.4
umesh.lk said:
clear explanation. :good:
MM preupdate distrubs to take some ota, doesn't it?
Click to expand...
Click to collapse
Yes .. had the same problem before.
ckpv5 said:
I can't check as I'm on mobile.
Does it say OTAxxxxx...4.19.707.4-4.19.707.2...xxxxx.zip ?
If yes, it is correct ... OTA from 4.19.707.2 to 4.19.707.4
Click to expand...
Click to collapse
HEY HEY FINALLY GOT MY UPDATE WITH OPTION 1 !!!
I REALLY THANK YOU ALL for the help, I then updated to Android 6.01
THANKS TANKS FOR YOUR HELP
Buzz
:good:
Great :good:
Enjoy your Marshmallow
Please help..having headphone mode problem..
hello there,
My International HTC M8 Android 6,Sense 7, Software 6.12.401.4.
without any reason after playing videos from YouTube or from my device for7/10 minutes, my phone automatically goes in to headphone mode and I can't hear anything from my speakers. Sometimes I see the headphone icon even when I am browsing internet and suddenly it goes away.
I do factory reset from settings twice and twice from boot men but No luck...I recently unlock the device but I didn't root my phone yet.
Apart from that my phone is running perfect but I brought this phone because of it's speakers because I watch lots of movies.
Bro,is there any way to fix the problem.....do I have to downgrade to Android 5 where I had no problem regarding my speakers...actually I don't know how to do that..
or I have to install a custom room to solve this problem...
Please help me out of this annoying problem...
and I should mention, recently I have noticed that whenever my phone gets hot, this annoying headphone icon appears.
Please HELP...I don't want to go to a repair shop

[GUIDE] [SOLUTION] Windows update stuck at "Checking updates..."

Note: The update packages linked down below are for ARM devices (basically for the Windows RT OS)
After contacting Microsoft, and doing research for at least a few weeks, I found a solution to this major problem.
Alright, so I got a permanent solution for the Windows Update searching disaster!
Step 1: Restore your Surface RT with the recovery image from the microsoft website. (optional)
Step 2: Set up your surface and head to Windows update.
Step 3: Search for updates, after 30m-1h you will see a firmware update, press install without modifying the update list.
Step 4: After the installation got succeeded, and your surface rt restarted go ahead and search again for updates.
Step 5: Again you will see a package of updates, this update includes the Windows RT 8.1 Update 1 update (kb2919355).
Step 6: When you finished installing the updates and your surface rebooted again, go to "installed updates" and check if kb2919355 is installed.
Step 7: If not, try to install the updates again. If yes, start searching for updates again.
Step 7B (Read before doing): IF kb2919355 is not installed and you are stuck on the search for updates part please download THIS file, turn off your WiFi, install the file by opening it, restart when finished and turn on WiFi
Step 8: Once Windows Update is searching for at least 4 hours we came at the point where most of us are stuck.
THE SOLUTION
Step 9: Download kb3173424 from HERE.
Step 10: Download kb3172614 from HERE.
Step 11: Turn off your Wifi, and reboot the surface.
Step 12: Install kb3173424 by opening it.
Step 13: Reboot the surface.
Step 14: Install kb3172614 by opening it.
Step 15: Reboot the surface.
Step 16: Turn on your Wifi, start searching for updates and after 10+/- minutes you will see 180+ updates coming your way .
I hope this helps a lot of people, since it was a major problem on the Surface RT.
Don't forget to hit that donation ehh... Thanks button!
Great work and thanks for the help ill try this on my surface 2 when I have more free time. I basically did that but instead got to the point where I was able to manually install the update 3 (which was about 60 updates in) and just stopped there and blocked updates so I could use the store without errors and use the development tool to run ported desktop apps.
mattschwantes said:
If this really works, you are heroic. How did you figure this out?
Click to expand...
Click to collapse
I restored an image on my surface RT more then 80 times in total. Contacted Microsoft which couldn't do anything and just told me to live with it. And finally came at the conclusion that 8.1 update 1 did something with the Windows update module (still doing research what exactly went wrong with that update).
However I tested this 2 times on my own tablet I can guarantee you this will work!
mattschwantes said:
My friend, you are very dedicated. Much more than MS it appears. I tested your method on a Surface 2 last night. It works great. Excellent work.
Click to expand...
Click to collapse
Glad I could help!
Hmm. I can't say if it is working or not yet. After finally fixing the errors I was getting after a reset (80240440) now I am updating, and after 2 large installs I still have no kb2919355. In fact I don't even have it's pre-requisite of kb2919442. I would really hate to be the guy that discovered this not working for every RT out there. :crying: I will just keep installing large groups until I either get them or it gets stuck again, and I will be absolutely sure to update this for the benefit of others.
Update: It worked, but I had to download and restart 5 separate sets of updates. My theory is that it is tied to the wi-fi connection. I had several errors at first indicating that I wasn't able to connect to the update servers. Internet Explorer worked fine so I went chasing a red herring looking at network settings, firewall etch. Then I brought the Surface from my living room into my office, where the router is, and suddenly it is working perfectly. So my point is, remember that this thing is finicky, and don't take any chances. The community thanks you Stjinchan, awesome job.
CptDraco said:
Update: It worked, but I had to download and restart 5 separate sets of updates. My theory is that it is tied to the wi-fi connection. I had several errors at first indicating that I wasn't able to connect to the update servers. Internet Explorer worked fine so I went chasing a red herring looking at network settings, firewall etch. Then I brought the Surface from my living room into my office, where the router is, and suddenly it is working perfectly. So my point is, remember that this thing is finicky, and don't take any chances. The community thanks you Stjinchan, awesome job.
Click to expand...
Click to collapse
Glad it worked! I love helping people!
Holy cow it works. Thank you so much I've been trying to resolve this issue for weeks. I didn't even have to reformat it.
Stjinchan said:
Alright, so I got a permanent solution for the Windows Update searching disaster!
Click to expand...
Click to collapse
This is awesome, can't wait to test it. But what about the Update 3 for Windows RT 8.1 (KB3097667) ?
I didn't read anything about it in your guide.
Niel86 said:
This is awesome, can't wait to test it. But what about the Update 3 for Windows RT 8.1 (KB3097667) ?
I didn't read anything about it in your guide.
Click to expand...
Click to collapse
After you installed the 2 mentioned updates manually windows update should be fixed and you are able to receive all the updates including update 3 through windows update again.
Stjinchan said:
After you installed the 2 mentioned updates manually windows update should be fixed and you are able to receive all the updates including update 3 through windows update again.
Click to expand...
Click to collapse
Thanks mate, I'll try it ASAP on my Surface RT
I can't manually install the first of the two updates, it say it's not possible to install it. Looks like I miss the 2919355 after the two big bacth of updates.
Any idea?
I'm very surprised and somehow happy to let you guys know that my Surface RT updated itself to the latest Update 3 after few days of downloading updates.
I was ready to follow this new guide, downloaded the manual updates but I've never used it.
I started everything by restoring Windows, keeping all my data and just refreshing WinRT, after that I started the typical updates cycles but something was different. I noticed I was missing the Kb2919355 (update 1), some of the updates were titled "KB **WhateverNumberItIs** without KB2919355", so I was a bit concerned but instead of the KB2919355 my Surface keeped find new updates in a very small time. After another batch of 137 updates, which took almost 3 hours to install, few other not important ones, here I am with my Windows 8.1 RT Update 3.
I really did nothing different from the previous 7/8 times.
Thank you, it works!
Now my Nokia 2520 tablet is back to life.
Not working for my Surface 2
I already have the first update listed to install, but when I try to install the second one it just says searching for updates on this computer...
Is there anything else I can try like resetting it? I just got it today.
amazing
Thank you for detailed instructions.
Advice for others, the key update we're looking for is the only one that ends with "55", so it's easier to search for it, just check the KB numbers in update history until you see it.
Also, another advice, DO NOT lightly install any optional updates. At the end of the process you will see a few optional updates. Please google each and every KB number, some of them caused big problems in the past! I personally installed 3 updates out of recommended list, including the new start menu and some other fixes that no one complained about.
In my case it took a couple days of waiting until my device got and installed the kb2919355 update, and I could take the matter into my own hands.
Now I just installed the two updates, and started searching for updates online.
Let's see where does it take me.
It's a completely new surface RT I purchased for laughable money to see if I could use it as a portable typewriter
For others out there who are still going through the process, the timeline was as follows:
- Friday 4pm I reset the device to official image, and started searching for updates (not connected to my microsoft ID, just local account)
- Friday 5pm I got a message about firmware update, downloaded and installed
- Friday 6pm I set it to search for updates, and left it at work.
- Saturday night I came to check it out, and it told me it wants to install updates. I installed some updates, there was no kb2919355 update, so I set it to search again
- Monday morning I cam full of hopes, the device told me it wants to install some updates, but kb2919355 wasn't among them. I installed whatever was ready, and set it to search again.
- It was still searching at 1pm. I got tired of waiting, and went to power menu. It suggested "Update and restart", so I chose it. It installed 50 updates, kb2919355 was amoung them, but failed.
- I fiddled around for 5 minutes, and it said that 3 updates were available (without searching), kb2919355 among them. Installed them, restarted.
- Then as per instruction, installed 2 updates manually (wifi off) and rebooted.
- searched for updates, took 10 minutes and voila! 161 important updates, and 8 optional.
- took an hour to download all 161 important updates, then about 2 hours to install.
- patience is a virtue! After installation of all 160 updates above, surface offered to do a restart. After clicking the Restart button, it spent >30 minutes with Restarting and a spinning circle. I was pondering about hard-resetting it, but then it started showing progress of update installation, so wait and wait until it does.
- Took about an hour to finalize updates installation. Like I mentioned at the beginning, I installed 3 optional updates (carefully chose them out of the list of 6)
- only then I connected my microsoft account, installed and updated all Metro UI apps (do not start using them before you update them, trust me on this one).
Stjinchan said:
Note: The update packages linked down below are for ARM devices (basically for the Windows RT OS)
After contacting Microsoft, and doing research for at least a few weeks, I found a solution to this major problem.
Alright, so I got a permanent solution for the Windows Update searching disaster!
Step 1: Restore your Surface RT with the recovery image from the microsoft website. (optional)
Step 2: Set up your surface and head to Windows update.
Step 3: Search for updates, after 30m-1h you will see a firmware update, press install without modifying the update list.
Step 4: After the installation got succeeded, and your surface rt restarted go ahead and search again for updates.
Step 5: Again you will see a package of updates, this update includes the Windows RT 8.1 Update 1 update (kb2919355).
Step 6: When you finished installing the updates and your surface rebooted again, go to "installed updates" and check if kb2919355 is installed.
Step 7: If no, try to install the updates again. If yes, start searching for updates again.
Step 8: Once Windows Update is searching for at least 4 hours we came at the point where most of us are stuck.
THE SOLUTION
Step 9: Download kb3173424 from HERE.
Step 10: Download kb3172614 from HERE.
Step 11: Turn off your Wifi, and reboot the surface.
Step 12: Install kb3173424 by opening it.
Step 13: Reboot the surface.
Step 14: Install kb3172614 by opening it.
Step 15: Reboot the surface.
Step 16: Turn on your Wifi, start searching for updates and after 10+/- minutes you will see 180+ updates coming your way .
I hope this helps a lot of people, since it was a major problem on the Surface RT.
Don't forget to hit that donation ehh... like button!
Click to expand...
Click to collapse
On step 7 = if KB2919355 still hasn't installed, do you continue checking for updates or remove whats been updated and start again, ive been trying this for 3 days now
ouatitw said:
On step 7 = if KB2919355 still hasn't installed, do you continue checking for updates or remove whats been updated and start again, ive been trying this for 3 days now
Click to expand...
Click to collapse
Continue checking for updates till you are stuck in the endless search. You should got the *355 update before that loop.
Stjinchan said:
Continue checking for updates till you are stuck in the endless search. You should got the *355 update before that loop.
Click to expand...
Click to collapse
The surface has 196 updates installed, it hasn't found anymore for over 12 hours - it still hasn't found KB2919355, i have reset the machine approx 3 times now and i always get this far only. Is KB2919355 available to install manually ?
ouatitw said:
The surface has 196 updates installed, it hasn't found anymore for over 12 hours - it still hasn't found KB2919355, i have reset the machine approx 3 times now and i always get this far only. Is KB2919355 available to install manually ?
Click to expand...
Click to collapse
Hmm, could you try to install this manually and report back to me if it worked? If so I will add it to the guide.
Stjinchan said:
Hmm, could you try to install this manually and report back to me if it worked? If so I will add it to the guide.
Click to expand...
Click to collapse
Stjinchan................... YOU ARE A LEGEND !..................... it worked, after 5 days of resets and refreshes you have resolved my issues, KB2919355 would never install via windows update itself. I am currently installing 210 updates at present........ I turned off WiFi and installed KB2919355 manually it took approx 40 mins to verify and install, from then i followed from step 9 of your guide and now things are looking good, so far i have 210 updates to install and after approx 3 hours installing as we speak we are at update 184 ...................... so we are almost there. Thank you for providing the standalone KB2919355 file ! That was the problem for me. I am delighted that forums such as XDA help people to resolve issues such as this its just a pity Microsoft themselves cant help more - credit to you STJINCHAN !

Mi A2 Lite Stuck on Android 8.1 - What am i doing wrong?

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!

OEM Unlock option missing on S985F/DS Tried everything....

Hey guys,
as the title says, I can't get the OEM Unlock option to show in the developer options. I tried everything, fake backward date and time..., disabling of updates, resets and pretty much all possible combinations of the aforementioned steps but the damn OEM Unlock option is just not showing. I double and triple checked if I have an Exynos device (yes) and I didn't have the issue on my S20 which I got from the same provider in Germany.
What am I missing? Any help would be mega appreciated :laugh:
Kerranax said:
Hey guys,
as the title says, I can't get the OEM Unlock option to show in the developer options. I tried everything, fake backward date and time..., disabling of updates, resets and pretty much all possible combinations of the aforementioned steps but the damn OEM Unlock option is just not showing. I double and triple checked if I have an Exynos device (yes) and I didn't have the issue on my S20 which I got from the same provider in Germany.
What am I missing? Any help would be mega appreciated :laugh:
Click to expand...
Click to collapse
Try this, set date to January 3, 2020. Go to Software Update, right after it displays "Connecting to server" close Software Update, don't update the device. Now go back to Developer Options, OEM Unlock should be displayed.
I finally figured it out, and from my point of view at least, it was a small detail that wasn't explicitly stated in all the guides/posts I read so far:
The phone needs to be connected to WiFi /Internet after you reboot post changing the date (and having all sorts off automatic updates turned off ofc)! :laugh:
Kerranax said:
I finally figured it out, and from my point of view at least, it was a small detail that wasn't explicitly stated in all the guides/posts I read so far:
The phone needs to be connected to WiFi /Internet after you reboot post changing the date (and having all sorts off automatic updates turned off ofc)! :laugh:
Click to expand...
Click to collapse
Can you please do a step by step instruction of how did you manage to make that damn OEM Unlock option to be available in developer options? I have also tried everything with no success on my S20.

General Android 12 for everyone :) /RM6,RM6Pro/

Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Says "everyone" but then leaves out RM6R
Gunhawk32 said:
Says "everyone" but then leaves out RM6R
Click to expand...
Click to collapse
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
I did a completely clean update. I completely formatted it, deleted all partitions /even the "persist" by accident, but I managed to restore it, but that's another story/.
Then I reset the phone using the Mitool-EDL method and then updated the clean system to EUCommon-V5.10.
The only mistake is that it lists the battery as 3550 mah instead of 5050 mah.
What you write about not receiving calls on Wi-Fi, etc., also occurred to me on the V3.28 system. If I set the mobile network as preferred in the vowifi settings, the error disappeared. Now I haven't experienced this error, vowifi works normally even in wifi preferred mode.
So far, I have not experienced any errors apart from the incorrect listing of the battery, although I cannot test 5G because it is not yet installed at our place...:/
Pisti870923 said:
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
Click to expand...
Click to collapse
I doubt it since it took 7-9 months for the android 12 update to release globally for the RM6 & 6 pro after it came out in china.
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
bro i have the same issue
do you solve it
Please i
Pisti870923 said:
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
Click to expand...
Click to collapse
do you have instructions or video .i dont have experience with that
moatazamer83 said:
do you have instructions or video .i dont have experience with that
Click to expand...
Click to collapse
I'll describe how I did it, but I can't promise that everything will work the same way for everyone. I don't know if there are hardware differences between each phone because I could only test it with mine /RM6P/. If someone tries it, do it at your own risk!
Be sure to save the "persist" partition before doing anything!!! Also save Qcn, these two are very important!!!
1. Backup partitions:
2. Backup Qcn:
3. /Optional/ Erase ALL:
After backup, I entered the partition manager in qfil, and after right-clicking, I clicked on "erase entire flash". But it's not absolutely necessary, but I definitely wanted a clean install. When I returned from Chinese Android 12 to EU 11 and didn't do this, the first time I started it, the phone setup got stuck in the wizard and wouldn't let me continue. From this I realized that the Mitool-EDL method alone does not completely clean the phone.
If you have completely reformatted the phone with qfil, you will need to restore the "persist" partition and Qcn with qfil after Mitool is finished. If you haven't formatted it completely, you don't need to restore it, but you should still have a backup of them, you never know when you'll need them, believe me!
4. And here is the description of the much talked about Mitool-EDL method:
RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU
Hello guys, I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU. The process is super easy: 1) Download &...
forum.xda-developers.com
5. Update rom:
If you're done with Mitool, you download the ROM you want, copy it to the internal storage and install it with local update in system update!
I did it this way and still found no errors. (Except that it says the battery is 3550mah). I use the EU510.
After Mitool finished, any rom goes up with local update, I tried EU328, UN428, CN810, UN610 and EU510
This method did not require unlocking the bootloader.
According to my theory, I could root with qfil without opening the bootloader, but I haven't tested it yet. If I try it sometime, I will write about my experience.
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Pisti870923 said:
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Click to expand...
Click to collapse
oh my god i can't do it bro
but thx alot for your help should i wait fix from company
moatazamer83 said:
bro i have the same issue
do you solve it
Please i
Click to expand...
Click to collapse
Bro me to i don't have network for calling before it wasn't a probleem but android 12 is smooth tho sad Nubia has to present it like this
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
Bro i got same network problem it's really sad Nubia has to present android 12 like this tho do you know something more
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
thx bro i will wait for your feedback .should i reset before installing
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
moatazamer83 said:
thx bro i will wait for your feedback .should i reset before installing
Click to expand...
Click to collapse
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
I've installed it too the network problem seems to be fixed but I need time to to confirm if this is solved
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
An Droid said:
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
Click to expand...
Click to collapse
I have EU version the changelog is the same as v.5.10 idk why
I think only if you get it with an OTA update... This is what I see:

Categories

Resources